[SOLVED] BSOD - DRIVER POWER STATE FAILURE (ACPI.sys)

Fardarkside

Fardarkside

Member
Joined
Sep 10, 2013
Posts
18
I've been consistently getting BSODs. Not only DRIVER_POWER_STATE_FAILURE but VIDEO_TDR_FAILURE (nvlddmkm.sys) too. The second one only happens when im playing some games. I think its the graphic card. Thanks for the help.

Details:
OS: Windows 8 64 bits
Processor: Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHZ 2.40GHZ
Graphic card: NVIDIA GeForce GTX 675M
 
So i tried to run Driver Verifier but then i got an BSOD. Now i can't even log in. I get an BSOD every time i turn on my laptop. What should i do?
Really appreciate ur help.
 
Hi,

Boot into Safe mode and disable it there by running cmd and typing verifier /reset or delete pre-existing settings via verifier.exe.

Restart and then boot into normal Windows and post dump(s) here.

Regards,

Patrick
 
Hi,

There is no DMP file attached in your jcgriff output folder. Can you instead pleasure manually navigate to C:\Windows\Minidump and zip up and attach the dump?

Regards,

Patrick
 
The attached DMP is not verifier enabled. Can you zip up all of the dumps that are in the Minidump folder and attach that? If the above attached DMP is the only one, do the following:

1. Enable Verifier

2. When you crash, navigate to Safe Mode as I instructed above and disable it like that

3. Boot back into normal Windows and attach the LATEST dump (should be verifier enabled)

Regards,

Patrick
 
Patrick said:
The attached DMP is not verifier enabled. Can you zip up all of the dumps that are in the Minidump folder and attach that? If the above attached DMP is the only one, do the following:

1. Enable Verifier

2. When you crash, navigate to Safe Mode as I instructed above and disable it like that

3. Boot back into normal Windows and attach the LATEST dump (should be verifier enabled)

Regards,

Patrick
Click to expand...

I cant boot into normal windows when i enable the Verifier. My pc just freeze. I can only boot in safe mode.
 
Fardarkside,

First things first...you gotta start with the obvious!

1. Make sure you are using the latest Nvidia driver for your video card - They have made some progress with that TDR BSOD
2. Blow out the internals of your system, especially the video card sink and fan and verify the video card fan is working
3. See if the problem persists...if it does, I have a registry tweak you can try.

OH, and while you are in the machine, inspect motherboard and video card for bad capacitors! Go to: Badcaps.net - Badcaps Home look at the images on the right so you know what you are looking for.

**Thanks to Wrench97 for that link!
 
Hi -

Video is a definite contender considering WERCON contains 302 "Live Kernel Events".

These are usually WATCHDOG dumps with a 0x117 bugcheck located in C:\Windows\LiveKernelReports\WATCHDOG

https://www.sysnative.com/forums/bs...rmation/35-video-tdr-timeout-0x116-0x117.html

WERCON also lists 27 BSODs, but no bugchecks.

We need the most recent dump from Driver Verifier.

Boot into SAFEMODE and get it, please - c:\windows\minidump

Regards. . .

jcgriff2
 
Deek said:
Fardarkside,

First things first...you gotta start with the obvious!

1. Make sure you are using the latest Nvidia driver for your video card - They have made some progress with that TDR BSOD
2. Blow out the internals of your system, especially the video card sink and fan and verify the video card fan is working
3. See if the problem persists...if it does, I have a registry tweak you can try.

OH, and while you are in the machine, inspect motherboard and video card for bad capacitors! Go to: Badcaps.net - Badcaps Home look at the images on the right so you know what you are looking for.

**Thanks to Wrench97 for that link!
Click to expand...

Yeah i have the latest driver (320.49) and already checked my fan. Its all good.
 
OK, CAPS?

Here is the reg fix - Run "regedit" (not sure how to get the "run" box in Win8
Navigate to:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ GraphicsDrivers]
Then create a a REG_DWORD file called TdrDelay and set the value to 60
ex. "TdrDelay"=dword:00000060 (60 seconds)


NOTE: TdrDelay is case sensitive, enter it just like above


Then navigate to
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ GraphicsDrivers\DCI]
and Create a Value called
"Timeout"=dword:00000060


Reboot and test

***Please note, this is more of a workaround then a fix, I had a machine that I could not fix the TDR issue on, I had to replace the video card...lets hope this is not the case for you.
 
Deek said:
OK, CAPS?

Here is the reg fix - Run "regedit" (not sure how to get the "run" box in Win8
Navigate to:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ GraphicsDrivers]
Then create a a REG_DWORD file called TdrDelay and set the value to 60
ex. "TdrDelay"=dword:00000060 (60 seconds)


NOTE: TdrDelay is case sensitive, enter it just like above


Then navigate to
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ GraphicsDrivers\DCI]
and Create a Value called
"Timeout"=dword:00000060


Reboot and test

***Please note, this is more of a workaround then a fix, I had a machine that I could not fix the TDR issue on, I had to replace the video card...lets hope this is not the case for you.
Click to expand...

And i use a notebook... Not sure if i can replace my video card. But i did that reg fix. Hope that works. Thanks
 
jcgriff2 said:
Hi -

Video is a definite contender considering WERCON contains 302 "Live Kernel Events".

These are usually WATCHDOG dumps with a 0x117 bugcheck located in C:\Windows\LiveKernelReports\WATCHDOG

https://www.sysnative.com/forums/bs...rmation/35-video-tdr-timeout-0x116-0x117.html

WERCON also lists 27 BSODs, but no bugchecks.

We need the most recent dump from Driver Verifier.

Boot into SAFEMODE and get it, please - c:\windows\minidump

Regards. . .

jcgriff2
Click to expand...

When i try to restart to enable the Verifier, my notebook freezes. So i cant enable Verifier.
 
Fardarkside, on second though, 60 seconds is too long...the default is 2 seconds...I think 10 or 15 sec would be better...it won't hurt anything, but if your GPU is hanging it might take 60 seconds to come back or BSOD...just seems like too long to wait, if it can't render the frame in 15 seconds...well, that just isn't so good.

and jcgriff2 was right, RESTORE POINT! Sometime I forget that not everyone is comfortable with regedit! It's really easy to tank a system.

I'm not sure about the win key X thing, that doesn't seem to work on XPx64, you can always do it via the system restore GUI...again, no idea how to get to that in Win8, sorry
 
Deek said:
Fardarkside, on second though, 60 seconds is too long...the default is 2 seconds...I think 10 or 15 sec would be better...it won't hurt anything, but if your GPU is hanging it might take 60 seconds to come back or BSOD...just seems like too long to wait, if it can't render the frame in 15 seconds...well, that just isn't so good.

and jcgriff2 was right, RESTORE POINT! Sometime I forget that not everyone is comfortable with regedit! It's really easy to tank a system.

I'm not sure about the win key X thing, that doesn't seem to work on XPx64, you can always do it via the system restore GUI...again, no idea how to get to that in Win8, sorry
Click to expand...

Ok.. I found my way to regedit and did it what you told me to do. What about the DRIVER_POWER_STATE_FAILURE? Do you know how to fix it? In the meanwhile, ill try to get those dump files
 
They may be related, can you try to get it to BSOD now?

First thing I would try would be a bios update for the power state BSOD, If you don't know what I am talking about, you could first try going into setup (Bios) during post and disabling APM (Advanced Power Management)

Let me know if I need to elaborate, you seem to know your way around a PC pretty well.

For a bios update, go to the manufacture web site of your laptop, then support, look up you service tag or model and download the firmware/bios update...they will provide instructions, but these days it's just a windows program you fire off.
 
0x116 / 0x117 can occur if the video driver cannot reset in the time allotted (30000 ms).

Based on that, I assume 30000 ms may be the default.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top