BSOD on NEW win 8.1 Computer

Hello i have been using this computer for less than two months.

I have googles this a lot, and it seems that most people suffer the same problem while going in and out of Sleep mode. were as on mine, it can happen at any time, even while i am working.

Please help me on this, as i don't know what to do any more.

I have tried to debug with WinDbg. but i did not get any answers.

My system is as follows:

  • Intel® Core™ i7-4700MQ quad core processor
  • Windows 8
  • 16GB DDR3L memory
  • 256GB Solid SDD + 1TB Hybrid hard drive
  • NVIDIA® GeForce® GTX 770M 3GB with Optimus™
ALSO connected to a Dynadock U3.0 (which does not seem to create any problems)
I have disconnected, and the Bsod still comes back. 

The debugging is as follows:

A driver has failed to complete a power IRP within a specific time.
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe00001dda060, Physical Device Object of the stack
Arg3: ffffd00020aaa960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe000072672a0, The blocked IRP

Debugging Details:

OVERLAPPED_MODULE: Address regions for 'aksusb' and 'WpdUpFltr.sys' overlap


IMAGE_NAME:  pci.sys



FAULTING_MODULE: fffff80000400000 pci





ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre


ffffd000`20aaa928 fffff802`784838d2 : 00000000`0000009f 00000000`00000003 ffffe000`01dda060 ffffd000`20aaa960 : nt!KeBugCheckEx
ffffd000`20aaa930 fffff802`784837f2 : ffffe000`018618e0 00000000`00000008 00000000`00000001 fffff802`7830ddbc : nt!PopIrpWatchdogBugcheck+0xde
ffffd000`20aaa990 fffff802`7830c6e2 : 00000000`00000000 ffffd000`20aaaae0 ffffe000`01861918 ffffe000`0052f0e8 : nt!PopIrpWatchdog+0x32
ffffd000`20aaa9e0 fffff802`783dcbea : ffffd000`20a80180 ffffd000`20a80180 ffffd000`20a8c200 ffffe000`07d3c140 : nt!KiRetireDpcList+0x6b2
ffffd000`20aaac60 00000000`00000000 : ffffd000`20aab000 ffffd000`20aa5000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  6.3.9600.16384

FAILURE_BUCKET_ID:  0x9F_3_nvlddmkm_IMAGE_pci.sys

BUCKET_ID:  0x9F_3_nvlddmkm_IMAGE_pci.sys


FAILURE_ID_HASH_STRING:  km:0x9f_3_nvlddmkm_image_pci.sys

FAILURE_ID_HASH:  {a47222af-fbac-bc49-47e0-2cf5d31cc673}
Thanks for the dump files!

All of the attached DMP files are of the DRIVER_POWER_STATE_FAILURE (9f) bug check.

This bug check indicates that the driver is in an inconsistent or invalid power state.

If we run an !irp on the 4th parameter of the bug check (blocked IRP address), we get the following:

>[ 16, 2]   0 e1 ffffe000057f1040 00000000 fffff802783a10e0-ffffe000018618e0 Success Error Cancel pending
           \Driver\nvlddmkm    nt!PopRequestCompletion

^^ nvlddmkm = nvlddmkm.sys which is the nVidia video driver.

Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.


You also have an Aladin security product + avast! installed, which is more than likely creating NETBIOS conflicts and therefore eventual memory corruption.

Remove and replace avast! with Windows 8's built-in Windows Defender for temporary troubleshooting purposes. Please also go ahead and remove the Aladin security product you're using.

avast! removal -

Windows Defender (how to turn on after removal) -


If you're still crashing after all of the above, please enable Driver Verifier:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 -

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select  - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is [B]NOT[/B] provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・    Restart and boot into normal Windows.

If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:


Debugger/Reverse Engineer.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.


Question Info

Last updated February 12, 2018 Views 263 Applies to: