Windows 8 and 8.1 Forums


BSOD with ntoskrnl.exe+1509a0

  1. #1


    Virginia
    Posts : 4
    Windows 8.1 64 bits

    BSOD with ntoskrnl.exe+1509a0


    I have had this problem for a week or so now. It happens multiple times a day, approximately every two or three hours. It seems random. I have noticed that it happens at that "random" frequency even if the computer has been asleep for an hour or two, when I get it out of sleep, I will get the BOSD withing a few minutes of waking it up.
    I have re-installed windows completely to try to solve the problem with no luck.
    The best way I have found to be able to use my computer is to reboot every couple of hours.

    Another problem that might not be related, is that my second hard drive was disappearing from window and from Disk management<storage<computer management. I solved that problem by moving the second hard drive to a VANTEC EZ-SWAP box. The second hard drive disappearance started after I installed a SSD drive as my C: drive. I have tried two different brand of SSD drives both giving the same problem.

    Any help and suggestion would be appreciated.
    Thanks
    Raymond

      My System SpecsSystem Spec

  2. #2


    Posts : 2,480
    Windows 10 Pro x64


    Update drivers in red.
    Code:
    V0230Vfx.sys Fri May 5 08:14:03 2006  (445AED2B) 
    EyePower Games Pte. Ltd. 
    http://www.carrona.org/drivers/driver.php?id=V0230Vfx.sys 
    
    V0230VID.sys  Tue Jul 25 07:52:54 2006 (44C5B1B6) 
    EyePower Games Pte. Ltd.  
    http://www.carrona.org/drivers/driver.php?id=V0230VID.sys 
    
    PxHlpa64.sys  Thu Jun 21 00:27:08 2007 (4679A9BC) 
    Sonic CD/DVD driver (used by  many different CD/DVD programs) 
    http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys 
    
    wdcsam64.sys  Wed Apr 16 10:39:08 2008 (4805BB2C) 
    
    wdcsam64.sys - this driver hasn't been added to the DRT as  of this run. Please search Google/Bing for the driver if additional information  is needed. 
    
    afcdp.sys Wed Jul 20 16:46:03 2011  (4E26EA2B) 
    Acronis File Level CDP Kernel Helper 
    http://www.carrona.org/drivers/driver.php?id=afcdp.sys 
    
    TuneUpUtilitiesDriver64.sys Fri May  25 12:28:19 2012 (4FBF5EC3) 
    
    TuneUpUtilitiesDriver64.sys - this driver hasn't been added  to the DRT as of this run. Please search Google/Bing for the driver if  additional information is needed. 
    
    npf.sys Fri Mar 1 02:31:24 2013  (513004EC) 
    
    npf.sys - this  driver hasn't been added to the DRT as of this run. Please search Google/Bing  for the driver if additional information is needed. 
    
    tib.sys Wed  Mar 20 10:00:38 2013 (51497AB6) 
    Acronis TIB manager 
    http://www.carrona.org/drivers/driver.php?id=tib.sys 
    
    fltsrv.sys Mon May 13 11:40:09 2013  (5190B4F9) 
    Acronis Storage Filter Management Driver 
    http://www.carrona.org/drivers/driver.php?id=fltsrv.sys 
    
    TMEBC64.sys Mon Jul 1 15:02:09 2013  (51D17DD1) 
    Trend Micro early boot driver 
    http://www.carrona.org/drivers/driver.php?id=TMEBC64.sys 
    
    snapman.sys Wed Aug 14 14:17:26  2013 (520B7556) 
    Acronis True Image Snapshot Manager driver also included in  Seagate DiscWizard 
    http://www.carrona.org/drivers/driver.php?id=snapman.sys 
    
    dump_storahci.sys Thu Aug 22  13:40:39 2013 (5215F8B7) 
    driver created to provide disk access during crash  dump file generation 
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys 
    
    tap0901.sys Thu Aug 22  14:40:01 2013 (521606A1) 
    TAP-Win32 Adapter V9 or[br]OpenVPN driver or COMODO  
    http://www.carrona.org/drivers/driver.php?id=tap0901.sys 
    
    tib_mounter.sys Mon Sep 30  15:04:20 2013 (524976D4) 
    Acronis Tib Mounter for Backup Archive Explorer  
    http://www.carrona.org/drivers/driver.php?id=tib_mounter.sys 
    
    point64.sys Thu Dec 12  14:16:17 2013 (52A9B721) 
    Microsoft IntelliPoint Filter Driver 
    http://www.carrona.org/drivers/driver.php?id=point64.sys 
    
    dc3d.sys Thu Dec 12 14:16:35 2013  (52A9B733) 
    Filter Driver for Identification of Microsoft Hardware Wireless  Mouse and Keyboard Device Models - Microsoft IntelliType Pro / IntelliPoint  
    http://www.carrona.org/drivers/driver.php?id=dc3d.sys 
    
    SmartDefragDriver.sys Mon Dec 23  11:05:52 2013 (52B80B00) 
    Smart Defrag 
    http://www.carrona.org/drivers/driver.php?id=SmartDefragDriver.sys 
    
    tmnciesc.sys Tue Apr 8  06:10:45 2014 (534376C5) 
    Trend Micro Maximum Security driver 
    http://www.carrona.org/drivers/driver.php?id=tmnciesc.sys 
    
    TotRec8.sys Wed Apr 30 14:08:01  2014 (5360E7A1) 
    Total Recorder WDM audio filter driver 
    http://www.carrona.org/drivers/driver.php?id=TotRec8.sys 
    
    tmeevw.sys Thu May 29 12:23:06  2014 (53870A8A) 
    Trend Micro Maximum Security driver 
    http://www.carrona.org/drivers/driver.php?id=tmeevw.sys 
    
    tmusa.sys Mon Jun 30 12:53:58 2014  (53B141C6) 
    Trend Micro Osprey Scanner driver 
    http://www.carrona.org/drivers/driver.php?id=tmusa.sys 
    
    nvlddmkm.sys Wed Jul 2 19:42:02 2014  (53B4446A) 
    nVidia Video drivers 
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys 
    
    tmevtmgr.sys Mon Jul 14 09:38:53  2014 (53C3890D) 
    Trend Micro Internet Security 
    http://www.carrona.org/drivers/driver.php?id=tmevtmgr.sys 
    
    tmcomm.sys Mon Jul 14 09:38:55  2014 (53C3890F) 
    Trend Micro Internet Security/ Housecall scanner 
    http://www.carrona.org/drivers/driver.php?id=tmcomm.sys 
    
    tmactmon.sys Mon Jul 14 09:39:07  2014 (53C3891B) 
    Trend Micro Internet Security 
    http://www.carrona.org/drivers/driver.php?id=tmactmon.sys 
    
    Rt630x64.sys Tue Aug 26 08:24:06  2014 (53FC2806) 
    Realtek PCI/PCIe Adapters 
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys 
    
    BthHfAud.sys Wed Oct 8 09:33:31  2014 (5434E8CB) 
    Bluetooth Hands-free Audio Device Driver - uncertain if this  is a Windows driver or a 3rd party bluetooth driver. See bthav.sys for more  speculation 
    http://www.carrona.org/drivers/driver.php?id=BthHfAud.sys 
    
    RTKVHD64.sys Tue Oct 28 11:32:13  2014 (544F70AD) 
    Realtek High Definition Audio Function Driver 
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys 
    
    HWiNFO64A.SYS Sun Nov 23 17:24:07  2014 (54720A27) 
    HWiNFO32 Kernel Driver 
    http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS 
    
    
    
    Debug session time: Sat  Feb 21 19:40:35.805 2015 (UTC + 1:00) 
    Loading Dump File  [C:\Users\Mihael\SysnativeBSODApps\022115-13203-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days  14:59:16.581 
    *** ERROR: Module load completed but symbols could not be  loaded for partmgr.sys 
    *** WARNING: Unable to verify timestamp for atapi.sys  
    *** ERROR: Module load completed but symbols could not be loaded for  atapi.sys 
    Probably caused by : atapi.sys 
    BugCheck 9F, {3,  ffffe00186547060, fffff8007d624aa0, ffffe0018b191800} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe00186547060, Physical Device Object of the stack 
    Arg3:  fffff8007d624aa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe0018b191800, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Sat Feb 21 04:40:04.822 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\022015-38281-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 6:04:30.622  
    *** WARNING: Unable to verify timestamp for atapi.sys 
    *** ERROR: Module  load completed but symbols could not be loaded for atapi.sys 
    Probably caused  by : atapi.sys 
    BugCheck 9F, {3, ffffe0001d106610, fffff803b3424aa0,  ffffe00021f038b0} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe0001d106610, Physical Device Object of the stack 
    Arg3:  fffff803b3424aa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe00021f038b0, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Fri Feb 20 21:21:48.892 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\022015-37750-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 1:42:17.683  
    *** ERROR: Module load completed but symbols could not be loaded for  partmgr.sys 
    *** WARNING: Unable to verify timestamp for atapi.sys 
    ***  ERROR: Module load completed but symbols could not be loaded for atapi.sys  
    Probably caused by : atapi.sys 
    BugCheck 9F, {3, ffffe0014dd7d610,  fffff802cfe24aa0, ffffe00153db7b50} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe0014dd7d610, Physical Device Object of the stack 
    Arg3:  fffff802cfe24aa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe00153db7b50, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Fri Feb 20 19:38:16.915 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\022015-12375-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 5:41:37.691  
    *** WARNING: Unable to verify timestamp for atapi.sys 
    *** ERROR: Module  load completed but symbols could not be loaded for atapi.sys 
    Probably caused  by : atapi.sys 
    BugCheck 9F, {3, ffffe00049f07060, fffff8003b424aa0,  ffffe0004bf59ad0} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe00049f07060, Physical Device Object of the stack 
    Arg3:  fffff8003b424aa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe0004bf59ad0, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Fri Feb 20 13:55:32.142 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\022015-11046-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 5:04:16.920  
    *** WARNING: Unable to verify timestamp for atapi.sys 
    *** ERROR: Module  load completed but symbols could not be loaded for atapi.sys 
    Probably caused  by : atapi.sys 
    BugCheck 9F, {3, ffffe000ec143060, fffff800b8424aa0,  ffffe000f01c1b20} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe000ec143060, Physical Device Object of the stack 
    Arg3:  fffff800b8424aa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe000f01c1b20, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Fri Feb 20 08:50:10.012 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\022015-38421-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 2:33:33.812  
    *** WARNING: Unable to verify timestamp for atapi.sys 
    *** ERROR: Module  load completed but symbols could not be loaded for atapi.sys 
    Probably caused  by : atapi.sys 
    BugCheck 9F, {3, ffffe00061571060, fffff800f6224aa0,  ffffe00060202c60} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe00061571060, Physical Device Object of the stack 
    Arg3:  fffff800f6224aa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe00060202c60, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Fri Feb 20 06:15:32.071 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\022015-38078-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 2:18:57.847  
    *** WARNING: Unable to verify timestamp for atapi.sys 
    *** ERROR: Module  load completed but symbols could not be loaded for atapi.sys 
    Probably caused  by : atapi.sys 
    BugCheck 9F, {3, ffffe00055f79060, fffff80249224aa0,  ffffe000579d7010} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe00055f79060, Physical Device Object of the stack 
    Arg3:  fffff80249224aa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe000579d7010, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Fri Feb 20 03:55:23.789 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\021915-37718-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 2:03:50.579  
    *** ERROR: Module load completed but symbols could not be loaded for  partmgr.sys 
    *** WARNING: Unable to verify timestamp for atapi.sys 
    ***  ERROR: Module load completed but symbols could not be loaded for atapi.sys  
    Probably caused by : atapi.sys 
    BugCheck 9F, {3, ffffe00182d46060,  fffff80229424aa0, ffffe00184c71830} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe00182d46060, Physical Device Object of the stack 
    Arg3:  fffff80229424aa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe00184c71830, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Fri Feb 20 01:50:31.004 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\021915-38328-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 3:32:31.783  
    *** ERROR: Module load completed but symbols could not be loaded for  partmgr.sys 
    *** WARNING: Unable to verify timestamp for atapi.sys 
    ***  ERROR: Module load completed but symbols could not be loaded for atapi.sys  
    Probably caused by : atapi.sys 
    BugCheck 9F, {3, ffffe000f1d07060,  fffff802f8024aa0, ffffe000f0e456c0} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe000f1d07060, Physical Device Object of the stack 
    Arg3:  fffff802f8024aa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe000f0e456c0, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Thu Feb 19 22:16:57.049 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\021915-10750-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 1:09:31.828  
    *** WARNING: Unable to verify timestamp for atapi.sys 
    *** ERROR: Module  load completed but symbols could not be loaded for atapi.sys 
    Probably caused  by : atapi.sys 
    BugCheck 9F, {3, ffffe00165f7a060, fffff8039c22bcb0,  ffffe0016967dca0} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe00165f7a060, Physical Device Object of the stack 
    Arg3:  fffff8039c22bcb0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe0016967dca0, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: chrome.exe 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Thu Feb 19 21:06:09.230 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\021915-38718-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 2:12:04.023  
    *** WARNING: Unable to verify timestamp for atapi.sys 
    *** ERROR: Module  load completed but symbols could not be loaded for atapi.sys 
    Probably caused  by : atapi.sys 
    BugCheck 9F, {3, ffffe001b1742060, fffff8018f62bcb0,  ffffe001b5661c60} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe001b1742060, Physical Device Object of the stack 
    Arg3:  fffff8018f62bcb0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe001b5661c60, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: chrome.exe 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Thu Feb 19 18:52:44.817 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\021915-12406-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 5:47:47.598  
    *** ERROR: Module load completed but symbols could not be loaded for  partmgr.sys 
    *** WARNING: Unable to verify timestamp for atapi.sys 
    ***  ERROR: Module load completed but symbols could not be loaded for atapi.sys  
    Probably caused by : atapi.sys 
    BugCheck 9F, {3, ffffe000d7706060,  fffff803cea24aa0, ffffe000db542010} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe000d7706060, Physical Device Object of the stack 
    Arg3:  fffff803cea24aa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe000db542010, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Thu Feb 19 13:03:50.279 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\021915-38109-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 1:10:09.075  
    *** WARNING: Unable to verify timestamp for atapi.sys 
    *** ERROR: Module  load completed but symbols could not be loaded for atapi.sys 
    Probably caused  by : atapi.sys 
    BugCheck 9F, {3, ffffe000add52060, fffff80219a24aa0,  ffffe000af2ccc60} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe000add52060, Physical Device Object of the stack 
    Arg3:  fffff80219a24aa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe000af2ccc60, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Thu Feb 19 11:52:28.111 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\021915-37890-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 1:46:14.902  
    *** WARNING: Unable to verify timestamp for atapi.sys 
    *** ERROR: Module  load completed but symbols could not be loaded for atapi.sys 
    Probably caused  by : atapi.sys 
    BugCheck 9F, {3, ffffe0009f746060, fffff8020dc24aa0,  ffffe000a33837d0} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe0009f746060, Physical Device Object of the stack 
    Arg3:  fffff8020dc24aa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe000a33837d0, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Thu Feb 19 10:05:01.010 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\021915-38234-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 1:16:07.812  
    *** WARNING: Unable to verify timestamp for atapi.sys 
    *** ERROR: Module  load completed but symbols could not be loaded for atapi.sys 
    Probably caused  by : atapi.sys 
    BugCheck 9F, {3, ffffe000ae505060, fffff802e0024aa0,  ffffe000afe23b10} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe000ae505060, Physical Device Object of the stack 
    Arg3:  fffff802e0024aa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe000afe23b10, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Thu Feb 19 08:47:38.150 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\021915-38296-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 1:20:28.945  
    *** WARNING: Unable to verify timestamp for atapi.sys 
    *** ERROR: Module  load completed but symbols could not be loaded for atapi.sys 
    Probably caused  by : atapi.sys 
    BugCheck 9F, {3, ffffe000eed4e060, fffff8030f620aa0,  ffffe000f2b9b300} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe000eed4e060, Physical Device Object of the stack 
    Arg3:  fffff8030f620aa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe000f2b9b300, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Thu Feb 19 07:26:11.968 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\021915-38515-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 2:34:32.748  
    *** WARNING: Unable to verify timestamp for atapi.sys 
    *** ERROR: Module  load completed but symbols could not be loaded for atapi.sys 
    Probably caused  by : atapi.sys 
    BugCheck 9F, {3, ffffe00068704060, fffff8018fc24aa0,  ffffe00067f3cc60} 
    BugCheck Info: DRIVER_POWER_STATE_FAILURE  (9f) 
    Bugcheck code 0000009F 
    Arguments: 
    Arg1: 0000000000000003, A  device object has been blocking an Irp for too long a time 
    Arg2:  ffffe00068704060, Physical Device Object of the stack 
    Arg3:  fffff8018fc24aa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the  Functional Device Object of the stack 
    Arg4: ffffe00067f3cc60, The blocked  IRP 
    BUGCHECK_STR: 0x9F 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID: 0x9F_3_IMAGE_atapi.sys  
    BiosVersion = 1708 
    BiosReleaseDate = 04/10/2013 
    SystemManufacturer =  To be filled by O.E.M. 
    SystemProductName = To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    
    
    
    
    --- E O J --- 2015 Feb 21 20:27:36 PM _88-dbug Copyright  2012 Sysnative Forums 
    --- E O J --- 2015 Feb 21 20:27:36 PM _88-dbug  Copyright 2012 Sysnative Forums 
    --- E O J --- 2015 Feb 21 20:27:36 PM  _88-dbug Copyright 2012 Sysnative Forums
    Run SFC: http://www.sevenforums.com/tutorials...e-checker.html
    Are you running your SSD in IDE mode? If yes, change it to AHCI in your BIOS.
      My System SpecsSystem Spec

  3. #3


    Virginia
    Posts : 4
    Windows 8.1 64 bits


    Thank you
    softwaremaniac, since I could not find the drivers, I uninstalled the related softwares and the problem seems to be gone.
    BTW where can I find how to do this kind of debugging by myself?
      My System SpecsSystem Spec

  4. #4


    Posts : 2,480
    Windows 10 Pro x64


    I'm using a specialized software.
      My System SpecsSystem Spec

  5. #5


    Virginia
    Posts : 4
    Windows 8.1 64 bits


    Is it possible to get it? What is the name?
    Thanks.
      My System SpecsSystem Spec

  6. #6


    Posts : 2,480
    Windows 10 Pro x64


    BSOD Processing Apps.
      My System SpecsSystem Spec

  7. #7


    Virginia
    Posts : 4
    Windows 8.1 64 bits


    OK Thanks.
      My System SpecsSystem Spec

BSOD with ntoskrnl.exe+1509a0
Related Threads
BSOD due to ntoskrnl.exe+1509a0 in BSOD Crashes and Debugging
Guys, I had this BSOD due to ntoskrnl.exe+1509a0. I am using Windows 8.1 Pro 64 bits. PC is new, i7 4770 and according to AMD all video card drivers (R7 265) were updated. Using Zone Alarm as firewall. At the moment, the computer was downloading/uploading too much, don't know if this is...
BSOD due to ntoskrnl.exe+1509a0 in BSOD Crashes and Debugging
Hi, I'm getting BSOD after upgrading to Windows 8.1. I believe all the drivers are installed. I checked minidumps with nirsoft's BlueScreenView and got that those BSODs are caused by the same ntoskrnl.exe error 0xc0000139. I have noticed that this happens when I play a video (usually a Mkv...
BSOD Win 8.1 x64 (ntoskrnl.exe) in BSOD Crashes and Debugging
hello I need help to solve this problem. tried just about everything! has become a mystery to me - And I am grateful to any assist ;)
ntoskrnl.exe BSOD in BSOD Crashes and Debugging
Hi everyone! So I recently bought a new laptop within the last month or so. Its the new line of Asus ROG gaming. i7, 12 GB RAM, GTX 860, Windows 8.1, 1 TB HDD. I've been getting BSODs after playing games such as Batman Arkham Orgins and Borderlands 2. During the game, everything runs smoothly at...
BSOD sometimes, ntoskrnl.exe in BSOD Crashes and Debugging
Hi! Everytime I shutdown the Laptop, computer close all programs and windows start to shutdown and after that screen goes black, computer still running. May be after 5-30 min will computer completely. Short summary: Computer: HP Probook 4530s OS: Windows 8.1 Event view and...
BSOD - (hal.dll - ntoskrnl.exe, etc) in BSOD Crashes and Debugging
Sincerely, my English is not very good (Spanish). Apologies, thank you very much. I've had blue screens, very consistently, I've noticed that when using the Spotify program. is more common. They are the only ones who can help. Under the last minidump. thank you in advance.
Solved Ntoskrnl.exe bsod in BSOD Crashes and Debugging
Hello, i have a Problem with my Lenovo S205 in irregular times. In the attachment have I add my Minidump. I hope somebody can help me. I doesnt understand the dump Thanks
Eight Forums Android App Eight Forums IOS App Follow us on Facebook