BSOD. DPC_watchdog_violation + driver_power_state_failure.

[kamui00]

View attachment SysnativeFileCollectionApp.zip

Hi everyone,


This problem has been persisting for the past 4-5 days when my computer suddenly crashed while playing City Skylines. I have an Nvidia GeForce GTX 670MX running on Windows 10.

The 1st BSOD I had was the DPC_watchdog_violation:
I proceed to go on Device Manager and locate the IDE ATA/ATAPI Controllers, then change it from iaStorA.sys to storachi.sys. Next, I updated all my current drivers, including my graphics card driver (I now have Nvidia v. 385.41 driver). Also, I did a disk check just to be safe, and it doesn't seem that there is any bad parts on the chkdsk c:. Finally, I saved everything and restarted. Then, the other BSOD message appeared.

Driver_Power_State_Failure BSOD: At this point I'm certain it is my graphics card + drivers somehow being incompatible to each other. According to most guides out there, everyone is recommending to do the above, updating + restarting. I've done a clean update on my graphics drivers. I rolled it back to the previous versions (v382.05 and v385.28), still have issues. No matter which driver I use for my graphics card, it will eventually crash.

My laptop doesn't seem to crash if I disable the Graphics card, but of course, I can't play any games if I have it disabled.

I've also tried pressing the power button without being plugged to the battery (to discharge it). No success.

My PC info:
Laptop
MSI GT70
- Windows 10 64 bit
- 12 GB RAM
- Age of the system: ~4 years old. Purchased in 2013
- VGA: Nvidia GeForce GTX 670MX / 3GB GDDR5



Any help or advice is greatly appreciated.

Thank you in advance.

 

[philc43]

Hello kamui00,

Can you confirm if the graphics card was disabled when you ran the file collection program? The DxDiag logfile shows error code 22 for the NVIDIA GeForce GTX 670MX device.

All the recent mini-dump files for the BSOD are related to the DPC watchdog violation. The errors are all zeroed_stack_0x133 so it is not possible to determine which driver(s) were involved.

I would suggest you run Driver Verifier according to the following instructions: Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista

Please post the mini-dumps when you get any new BSOD events.

 

[kamui00]

Hello kamui00,

Can you confirm if the graphics card was disabled when you ran the file collection program? The DxDiag logfile shows error code 22 for the NVIDIA GeForce GTX 670MX device.

All the recent mini-dump files for the BSOD are related to the DPC watchdog violation. The errors are all zeroed_stack_0x133 so it is not possible to determine which driver(s) were involved.

I would suggest you run Driver Verifier according to the following instructions: Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista

Please post the mini-dumps when you get any new BSOD events.

Yes, the Nvidia graphics card was disabled when I ran the collection program at that time. As soon as I enable it, the system will crash + BSOD will appear almost for sure. Sometimes, I would just have a few minutes on the start-up to restart into safe-mode in order to disable it, and then do what I have to do.



I ran the verifier and then the collection file:

View attachment SysnativeFileCollectionApp.zip

 

[philc43]

There is nothing recorded in the logs as being triggered by Driver Verifier. Did you run it in normal mode with the graphics card disabled?

 

[kamui00]

I followed all the instructions on the "Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista" guide, but the verifier doesn't seem to do anything after I restart it (unless it is doing it silently in the background). I still left the PC running for ~24 hrs and see if it does something.
Yes, the Nvidia graphics card wasn't disabled, but it eventually had a "Code 43" error, disabling it by itself. I ran the collection file 24hrs after the verifier.

 

[jcgriff2]

Driver Verifier runs in the background. There is no message or anything to indicate that it is running. Some system slow up as Verifier uses lots of system resources,

You can check to see if Driver Verifier is running or not.

Bring up an Admin CMD prompt and type or copy/paste:

 [FONT=Lucida Console][SIZE=3]verifier /query[/SIZE] [/FONT]

Regards. . .

jcgriff2