Windows 8 and 8.1 Forums


"driver_state_power_failure" / "inaccessible_boot_device"

  1. #1


    Posts : 7
    Windows 8.1

    "driver_state_power_failure" / "inaccessible_boot_device"


    Dear EightForums Team,

    I am new to your platform and according to what I've seen around here, you guys will definitely help me solve a problem I've been experiencing for quite some time with my ASUS R501V laptop, Windows 8.1.

    There are 2 main issues I am experiencing at the moment:

    1. "DRIVER_STATE_POWER_FAILURE" - which occurs from time to time, whether on battery or not. I have spotted a slight trend with this BSOD, as it (sometimes) appears after waking up my laptop from sleep mode, but it sometimes appears whilst doing stuff with the charger plugged in as well.

    2. "INACCESSIBLE_BOOT_DEVICE"
    - This one is a bit trickier. Basically, usually after software/driver updates, my laptop is stuck in a rather annoying boot loop where after the Windows 8.1 loading screen a very short BSOD is displayed (by short I mean, milliseconds) and it restarts again. I am then forced to put my laptop in Recovery Mode and do a system restore.

    Again, this issue (usually) occurs after software/driver updates and/or new software installation and sometimes the two errors are followed by each other, number (1) and then boot loop with number (2)

    I have followed the instructions on your forum and generated an analysis using the SF Diagnostic Tool, as I am not very good with Windows errors and the Internet didn't seem to be of much help in this case.

    I would be very grateful if you could help me fix this issue. Please be very explicit with your recommendations, giving me step-by-step instructions, as I am not very familiar with those kind of errors.

    Thank you very much,
    Claude

      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Let's start with the inaccessible boot device....
    Did the laptop come with Win8/8.1 installed?
    If not, does it have a BIOS or does it use UEFI?

    Currently the system is set in Legacy mode.
    In the case that the UEFI tries to update itself, it'll usually reset to defaults (which includes resetting to UEFI rather than Legacy mode - and will enable the Secure Boot feature. When it does this the boot environment is changed and the system cannot find the proper boot stuff until you reset it.

    The solution here is a wipe and reinstall - making sure that you use the UEFI and Secure Boot.
    Just FYI - this is only one scenario for your issues - there are lot's of other things to try before wiping and reinstalling Windows!

    There are plenty of memory dumps in the attachment, but they date from 06 July 2014 and earlier.
    Have you had any crashes that are more recent?

    The STOP 0x9F memory dumps point to your video drivers. Please update them to the latest, WIn8.1 compatible version available from the Asus website.

    Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
    Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
    Alternate link: Disk-Tools.com
    Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
    Riva Tuner (along with MSI Afterburner and EVGA Precision) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys). Please un-install them immediately!

    If you're overclocking, please stop the overclock while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized.

    If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions: Driver Verifier Settings

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Sun Jul  6 11:54:39.968 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\070614-6625-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 6:59:35.685
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe000d7f27800, fffff802068f0930, ffffe000d559c010}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000d7f27800, Physical Device Object of the stack
    Arg3: fffff802068f0930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe000d559c010, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Jun 22 12:43:07.037 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\062214-6859-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 9:38:08.753
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe00131563060, fffff800b44f0930, ffffe0012f757240}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe00131563060, Physical Device Object of the stack
    Arg3: fffff800b44f0930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0012f757240, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Jun  8 14:16:04.975 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\060814-6406-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 8:25:45.692
    Probably caused by :hardware ( nt!MiReferenceControlArea+29d )
    BugCheck 1000007E, {ffffffffc0000005, fffff8008e056001, ffffd00021e2b8b8, ffffd00021e2b0c0}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8008e056001, The address that the exception occurred at
    Arg3: ffffd00021e2b8b8, Exception Record Address
    Arg4: ffffd00021e2b0c0, Context Record Address
    PROCESS_NAME:  System
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    FAILURE_BUCKET_ID: IP_MISALIGNED
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Jun  7 09:58:23.176 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\060714-6406-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 0:04:10.892
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe00144520060, fffff800c8af2930, ffffe00145f6c680}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe00144520060, Physical Device Object of the stack
    Arg3: fffff800c8af2930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00145f6c680, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri May 30 07:48:02.764 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\053014-6390-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 3:46:00.480
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe001b97b3060, ffffd0002066a930, ffffe001be57f2b0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe001b97b3060, Physical Device Object of the stack
    Arg3: ffffd0002066a930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001be57f2b0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu May 29 17:02:07.486 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\052914-6312-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 0:42:26.203
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe000cf71d060, ffffd0013b3e9930, ffffe000d33d2b10}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000cf71d060, Physical Device Object of the stack
    Arg3: ffffd0013b3e9930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe000d33d2b10, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu May 29 15:20:57.852 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\052914-6421-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 1:32:20.570
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe000b5b44060, ffffd000adee3930, ffffe000b4631700}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000b5b44060, Physical Device Object of the stack
    Arg3: ffffd000adee3930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe000b4631700, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed May 28 14:24:27.399 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\052814-7093-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 5:35:11.116
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe0003f546540, fffff803898f2930, ffffe0003d8fa2b0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0003f546540, Physical Device Object of the stack
    Arg3: fffff803898f2930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0003d8fa2b0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun May 25 17:46:34.586 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\052514-6546-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 5:02:48.304
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe000f2f47060, fffff800ff2f2930, ffffe000f0714010}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000f2f47060, Physical Device Object of the stack
    Arg3: fffff800ff2f2930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe000f0714010, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat May 24 08:26:49.376 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\052414-6531-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 0:42:21.093
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe0019cec4600, ffffd00106bae930, ffffe0019ff1c720}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0019cec4600, Physical Device Object of the stack
    Arg3: ffffd00106bae930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0019ff1c720, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri May 23 05:51:32.782 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\052314-6296-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 0:14:02.499
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe00132abf5b0, ffffd0016a3ae930, ffffe00136230180}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe00132abf5b0, Physical Device Object of the stack
    Arg3: ffffd0016a3ae930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00136230180, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu May 22 10:12:43.207 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\052214-6250-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 1:09:59.923
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe001016c1060, fffff80032af2930, ffffe0010624bbf0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe001016c1060, Physical Device Object of the stack
    Arg3: fffff80032af2930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0010624bbf0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu May 22 08:30:58.843 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\052214-6203-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 3:49:09.561
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe000f10bf060, fffff8015def2930, ffffe000f1173e10}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000f10bf060, Physical Device Object of the stack
    Arg3: fffff8015def2930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe000f1173e10, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri May  9 19:44:26.915 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\051014-6390-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 0:03:43.632
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe001dccc1060, ffffd000d0de9930, ffffe001e1e18e10}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe001dccc1060, Physical Device Object of the stack
    Arg3: ffffd000d0de9930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe001e1e18e10, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu May  8 11:24:30.777 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\050814-6296-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 0:09:43.494
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe000fb53a060, ffffd001dd171930, ffffe000ffe23cc0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000fb53a060, Physical Device Object of the stack
    Arg3: ffffd001dd171930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe000ffe23cc0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu May  8 09:11:31.619 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\050814-6359-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 4:01:48.337
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, ffffe000a00c1060, ffffd0010af3b930, ffffe0009e4b7e10}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe000a00c1060, Physical Device Object of the stack
    Arg3: ffffd0010af3b930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0009e4b7e10, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon May  5 11:07:13.323 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\050514-6671-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 4:47:38.040
    *** WARNING: Unable to verify timestamp for igdkmd64.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
    Probably caused by :igdkmd64.sys ( igdkmd64+62c47 )
    BugCheck D1, {28, 2, 0, fffff80044af2c47}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: 0000000000000028, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff80044af2c47, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  dwm.exe
    FAILURE_BUCKET_ID: AV_igdkmd64+62c47
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Sun Jul  6 11:54:39.968 2014 (UTC - 4:00)**************************
    moufiltr.sys                Sun Mar  8 23:16:13 2009 (49B489FD)
    ASMMAP64.sys                Thu Jul  2 05:13:26 2009 (4A4C7A36)
    walvhid.sys                 Wed Aug 26 01:15:08 2009 (4A94C4DC)
    ntk_PowerDVD_64.sys         Tue Aug  3 05:04:12 2010 (4C57DB8C)
    000.fcl                     Thu Nov 18 19:53:28 2010 (4CE5CA88)
    dtsoftbus01.sys             Thu Jan 13 03:27:08 2011 (4D2EB75C)
    atkwmiacpi64.sys            Tue Sep  6 21:44:52 2011 (4E66CC94)
    GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
    AsHIDSwitch64.sys           Wed May 30 22:38:32 2012 (4FC6D9A8)
    HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
    kbfiltr.sys                 Wed Aug  1 23:22:22 2012 (5019F26E)
    iaStorA.sys                 Mon Nov 19 15:09:40 2012 (50AA9204)
    dump_iaStorA.sys            Mon Nov 19 15:09:40 2012 (50AA9204)
    t_mouse.sys                 Mon Dec  3 01:19:30 2012 (50BC4472)
    athw8x.sys                  Thu Jan 17 04:15:39 2013 (50F7C13B)
    RTCore64.sys                Mon Mar 11 01:32:06 2013 (513D6C56)
    L1C63x64.sys                Sun Mar 31 23:15:17 2013 (5158FBC5)
    AsusTP.sys                  Thu May  9 05:23:42 2013 (518B6B1E)
    vmci.sys                    Fri May 17 21:19:18 2013 (5196D716)
    RTKVHD64.sys                Tue Jul  9 09:19:59 2013 (51DC0DFF)
    VMNET.SYS                   Thu Jul 18 15:42:50 2013 (51E8453A)
    vmnetbridge.sys             Thu Jul 18 15:43:47 2013 (51E84573)
    iwdbus.sys                  Wed Jul 24 21:06:12 2013 (51F07A04)
    vsock.sys                   Wed Jul 31 22:46:10 2013 (51F9CBF2)
    intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
    tap0901.sys                 Thu Aug 22 08:40:01 2013 (521606A1)
    igdkmd64.sys                Mon Sep 16 20:08:54 2013 (52379D96)
    aswRvrt.sys                 Fri Oct  4 03:48:58 2013 (524E72EA)
    aswVmm.sys                  Fri Oct  4 03:49:05 2013 (524E72F1)
    aswKbd.sys                  Tue Oct  8 05:10:19 2013 (5253CBFB)
    hcmon.sys                   Wed Oct  9 11:03:51 2013 (52557057)
    aswRdr2.sys                 Fri Oct 11 07:11:37 2013 (5257DCE9)
    vmnetuserif.sys             Fri Oct 18 14:19:38 2013 (52617BBA)
    VMkbd.sys                   Fri Oct 18 14:50:26 2013 (526182F2)
    vmx86.sys                   Fri Oct 18 15:34:39 2013 (52618D4F)
    aswNdisFlt.sys              Thu Oct 31 08:57:11 2013 (527253A7)
    aswSP.sys                   Thu Oct 31 08:57:15 2013 (527253AB)
    IntelHaxm.sys               Mon Nov  4 20:06:16 2013 (52784488)
    aswMonFlt.sys               Wed Nov  6 07:36:00 2013 (527A37B0)
    aswFsBlk.sys                Wed Nov  6 07:36:05 2013 (527A37B5)
    aswSnx.sys                  Wed Nov  6 07:37:52 2013 (527A3820)
    IntcDAud.sys                Wed Nov 27 09:25:44 2013 (529600E8)
    nvvad64v.sys                Fri Mar 28 09:32:06 2014 (533579D6)
    NvStreamKms.sys             Tue Apr 29 20:59:44 2014 (53604B00)
    nvpciflt.sys                Mon May 19 19:00:22 2014 (537A8D06)
    nvlddmkm.sys                Mon May 19 19:08:44 2014 (537A8EFC)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Jun  8 14:16:04.975 2014 (UTC - 4:00)**************************
    AmUStor.SYS                 Wed Oct  3 05:26:57 2012 (506C04E1)
    usbaapl64.sys               Tue Nov 27 18:38:02 2012 (50B54EDA)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri May 30 07:48:02.764 2014 (UTC - 4:00)**************************
    IntcDAud.sys                Tue Jun 19 10:40:51 2012 (4FE08F73)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu May 29 15:20:57.852 2014 (UTC - 4:00)**************************
    vmnetadapter.sys            Thu Jul 18 15:43:00 2013 (51E84544)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed May 28 14:24:27.399 2014 (UTC - 4:00)**************************
    L1C63x64.sys                Fri Sep 21 02:34:46 2012 (505C0A86)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun May 25 17:46:34.586 2014 (UTC - 4:00)**************************
    nvpciflt.sys                Tue Mar  4 05:58:52 2014 (5315B1EC)
    nvlddmkm.sys                Tue Mar  4 06:07:52 2014 (5315B408)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri May 23 05:51:32.782 2014 (UTC - 4:00)**************************
    ssudbus.sys                 Thu Jan  2 04:51:22 2014 (52C5369A)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon May  5 11:07:13.323 2014 (UTC - 4:00)**************************
    nvlddmkm.sys                Wed Oct 23 02:21:50 2013 (52676AFE)
    nvpciflt.sys                Wed Oct 23 02:22:31 2013 (52676B27)
    nvvad64v.sys                Fri Mar 21 13:42:58 2014 (532C7A22)
    
    http://www.carrona.org/drivers/driver.php?id=moufiltr.sys
    http://www.carrona.org/drivers/driver.php?id=ASMMAP64.sys
    http://www.carrona.org/drivers/driver.php?id=walvhid.sys
    http://www.carrona.org/drivers/driver.php?id=ntk_PowerDVD_64.sys
    http://www.carrona.org/drivers/driver.php?id=000.fcl
    http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys
    http://www.carrona.org/drivers/driver.php?id=atkwmiacpi64.sys
    http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
    http://www.carrona.org/drivers/driver.php?id=AsHIDSwitch64.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=kbfiltr.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=t_mouse.sys
    http://www.carrona.org/drivers/driver.php?id=athw8x.sys
    http://www.carrona.org/drivers/driver.php?id=RTCore64.sys
    http://www.carrona.org/drivers/driver.php?id=L1C63x64.sys
    http://www.carrona.org/drivers/driver.php?id=AsusTP.sys
    http://www.carrona.org/drivers/driver.php?id=vmci.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=VMNET.SYS
    http://www.carrona.org/drivers/driver.php?id=vmnetbridge.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=vsock.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=tap0901.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys
    http://www.carrona.org/drivers/driver.php?id=aswVmm.sys
    http://www.carrona.org/drivers/driver.php?id=aswKbd.sys
    http://www.carrona.org/drivers/driver.php?id=hcmon.sys
    http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
    http://www.carrona.org/drivers/driver.php?id=vmnetuserif.sys
    http://www.carrona.org/drivers/driver.php?id=VMkbd.sys
    http://www.carrona.org/drivers/driver.php?id=vmx86.sys
    http://www.carrona.org/drivers/driver.php?id=aswNdisFlt.sys
    http://www.carrona.org/drivers/driver.php?id=aswSP.sys
    http://www.carrona.org/drivers/driver.php?id=IntelHaxm.sys
    http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
    http://www.carrona.org/drivers/driver.php?id=aswFsBlk.sys
    http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
    http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
    http://www.carrona.org/drivers/driver.php?id=nvpciflt.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=AmUStor.SYS
    http://www.carrona.org/drivers/driver.php?id=usbaapl64.sys
    http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
    http://www.carrona.org/drivers/driver.php?id=vmnetadapter.sys
    http://www.carrona.org/drivers/driver.php?id=L1C63x64.sys
    http://www.carrona.org/drivers/driver.php?id=nvpciflt.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=ssudbus.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=nvpciflt.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
      My System SpecsSystem Spec

  3. #3


    Posts : 7
    Windows 8.1


    Hi usasma,

    First of all, thank you very much for the quick reply. I've followed your steps and updated/removed all the drivers, even stopped "NvStreamSvc" which was reported to cause BSODs, freezes etc. (information I got from a thread discussed previously on this forum).

    Well, for two days I actually thought I've solved the problems with my laptop, but today it turned out I was wrong. I've shut down my computer and when tried to start it again, it was stuck on a boot loop, showing the same "INACCESSIBLE_BOOT_DEVICE" as last time. So I had to do a system restore again to yesterday's settings, undoing everything I've done.

    In order to answer your previous questions, the laptop didn't have the Windows OS installed so I've installed it personally, and it's got BIOS, not UEFI.

    I've attached another diagnosis created with the SF Diagnostic Tool.
      My System SpecsSystem Spec

  4. #4


    Posts : 5,139
    Win8.1Pro - Finally!!!


    I'm uncertain of how to proceed from here.
    When the system throws the Inaccessile Boot Device error - have you tried Startup Repair/Automatic Repair?
    If so, what happens when you do try it?

    Let's try these 2 things:

    Please do the following:
    - open Event Viewer (run eventvwr.msc from the "Run" dialog))
    - expand the Custom Views category (left click on the > next to the words "Custom Views")
    - right click on Administrative Events
    - select "Save all Events in Custom View as..."
    - save the file as Admin.evtx
    - zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
    - upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

    If we're looking for Event ID 41 errors, there's more info on that here: Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first" in Windows 8.1, Windows 8, Windows Server 2012 R2, Windows Server 2012, Windows 7, or Windows Server 2008 R2

    While waiting for a reply, please monitor your temps with this free utility: HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
    and

    Then please run the following DISM commands to see if there's any problems with the system (from an elevated (Run as administrator) Command Prompt). Press Enter after each one:
    Code:
    Dism /Online /Cleanup-Image /ScanHealth
    Code:
    Dism /Online /Cleanup-Image /CheckHealth
    Code:
    Dism /Online /Cleanup-Image /RestoreHealth
    FYI - I have repaired systems using the last command even though problems weren't found with the first 2 - so I suggest running them all.

    From this article: Repair a Windows Image

    You can also run sfc.exe /scannow from an elevated (Run as administrator) Command Prompt to check for further corruption.
      My System SpecsSystem Spec

  5. #5


    Posts : 7
    Windows 8.1


    Hi again,

    Unfortunately, Automatic Repair doesn't do anything to me, it's still stuck on boot loop. The only solution I have found is a System Restore to a previous date.

    I've attached the archive file, as requested. Yes, we're looking at Event ID 41 errors. In fact, all errors in the event log are ID 41.

    I've read the information on the link you provided and I have to mention that the error occurred while my laptop was plugged in and the battery was not removed. Also, I am sorry I forgot to add the following information, which may be essential:

    - the laptop has a 4GB RAM upgrade and a 128GB SSD on a caddy replacing the optical drive.

    I'll do the DISM commands tonight.

    Thank you
      My System SpecsSystem Spec

  6. #6


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Interestingly, the Critical Errors (the EventID 41 errors) don't have anything prior to them occurring
    There are errors immediately following it though - and all seem to relate to pointing device errors

    You have (I think) 3 different pointing devices:
    - a wheel type mouse (either USB or wireless USB most likely)
    - an Asus touchpad
    - a Tablet Mouse
    Why so many input devices? Can you live without all except for the touchpad (for long enough to see if that helps with the BSOD's)?

    I don't think that DISM is going to help here. It seems to me that this is a hardware problem, and it corrupts the system at a low-level - which is what corrupts the system (I'm uncertain of the exact mechanism of this). Removing the pointing devices will be a start towards ruling out that hardware.

    Then I'd suggest starting with these free hardware diagnostics: Hardware Diagnostics
      My System SpecsSystem Spec

  7. #7


    Posts : 7
    Windows 8.1


    Well, I've got my cable USB mouse I'm using at the moment and the touchpad incorporated in the laptop. I am using a drawing tablet from time to time for design purposes, but that's pretty much it.

    I'm not sure whether I can give up on my USB mouse, as I am a part-time freelance designer, but I can try to not use it for a while.

    Now, if I think about the issue, I've had my laptop since January, and I've only experienced the "DRIVER_STATE_POWER_FAILURE" from time to time, but no other issues. The bootloop, together with the "INACCESSIBLE_BOOT_DRIVE" error cam about 1-2 months ago, so it's relatively recent.
      My System SpecsSystem Spec

  8. #8


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Let's focus on the hardware (Inaccessible Boot Drive) errors for now.
    Do without the table and cable USB mouse as much as possible - and when the system BSOD's remember if you have them attached or not (and if you've rebooted since removing them).

    Finish up the hardware diagnosics that I requested, they'll help to rule out a lot of hardware parts.
      My System SpecsSystem Spec

  9. #9


    Posts : 7
    Windows 8.1


    Hi again,

    It's been around 3 days since you suggested to disconnect my mouse and drawing tablet, and I haven't had a single BSOD/boot-loop since. I don't really know whether this is a coincidence or not, but it's definitely behaving as it should do at the moment.

    If the input devices are the actual problem, what is the next thing to do?

    I haven't run the diagnostic tests yet, but I will as soon as it BSODs again (if it does, of course).
      My System SpecsSystem Spec

  10. #10


    Posts : 5,139
    Win8.1Pro - Finally!!!


    There's several possibilities here:
    - the input devices are bad (may only be one is bad)
    - the cables connecting the input devices to your computer are bad (may only be one is bad)
    - the connection in your computer is bad
    - the drivers for the device/devices is/are corrupted/incompatible/bad

    What to do?
    - try the devices separately (to see if you can figure out which one causes the BSOD's)
    - replace the drivers for that device - download a fresh copy, then uninstall the current copy.
    check to be sure that the drivers are removed (after a reboot), then install the freshly downloaded version
      My System SpecsSystem Spec

Page 1 of 2 12 LastLast
"driver_state_power_failure" / "inaccessible_boot_device"
Related Threads
Hello My Brand new Laptop: Lenovo g505 after upgrading it to windows 8.1 from MS Apps store now i am not able to connect to internet i get "limited" or "No Internet Access". i have tried to re install the driver no luck Lenovo support suggests to do factory rest but i dont want to go back...
Hi all, So I'm kind of stuck.. I currently have the problem where I am in an endless cycle of "loading files" -> "Windows Boot Manager" (see: How To Boot Into Safe Mode On Windows 8 (The Easy Way)). I have tried to load all of the options -- and none successfully load. I also end up at...
Hi guys, as most of you will be aware with the show desktop feature in the windows, which in the system tray on bottom right of your screen. I need a tweak or registry edit to make it do "Win + M" Minimize all Windows, instead of "Win + D" show desktop. Reason is it hides my gadgets and...
Hello everyone,I've been having a problem since I updated to Windows 8.1My internet wi-fi connection is unusually low and is not working after only minutes of browsing the internet. The problem is always fixed after I run troubleshoot problems and is saying that the default Gateway is unavailable....
As the title states, I was wondering how I would do that? Because I really want to add a custom ".tga" 'close' button to my windows theme. I am using WindowBlinds: (link) - Skin the Windows desktop interface with WindowBlinds WindowBlinds let's me edit and make my own theme by using their own...
Hi everyone! Just got my brand new HP Envy DV7250US with Windows 8 (64) pre-installed. Recently I got boughr windows 8 pro (64) and would like to install/upgrade this on my HP laptop. Popped the 8 pro disc in, went to 'my computer', launch the dvd, installed it. Halfway during the installation,...
So got windows 8 Dev installed so far so good, I thought I would like the left screen bump to go to last app or program used feature till I installed some games and tried to play them suddenly my left side of my screen is no good if needing to scroll to the side say in a game like Starcraft II,...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook