A strange Blue Screen of Death

[Mroma1228]

Hi everyone,
I've experience a BSoD recently with the followig error message: DPC_WATCHDOG_VIOLATION

I am running windows 10 on a 5 years old Lenovo V570. Originally coming with windows 7.

Attempting to fix the issue, I have reinstalled windows, totally wiping the hard drive. The BSoD is still there, crashing the PC every 2min. However, over a complete night of crash and reboot, I have done the windows updates (all I think).

I am now working on the safemode with networking, which is working perfectly fine.

A few more detail:
-before I reinstalled windows, the error message was different (I cant remember which one though)

-I have also tried to uninstalled driver marked with an exclamation mark (!) and then reboot, it hasnt work.


I know the PC is old, but I would like to find a way to make it work a little bit longer.

Thanks

 

[Colif]

can you download and run whocrashed: http://www.resplendence.com/whocrashed
it will create a summary of bsod and may tell us cause

copy/paste results in here


See if this helps: http://answers.microsoft.com/en-us/windows/forum/windows_10-update/bluescreen-error-dpcwatchdogviolation/100cb707-0716-40d4-88a8-7bf9dd8f836d

have you run updates on this site? not many win 10 things there but the win 8 drivers should be ok - lenova link

 

[Mroma1228]

Hi Colif,

Here is the WhoCrashed output.
Those happened after I've reinstalled win10, but they were the same error code before
I will chek the links you've sent me.

My main interrogation is why the error code changed?
And how am I still able to use my PC perfectly on the safemode?

Thanks


System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-CT7JHM9
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: 1066C3U, LENOVO, Emerald Lake
CPU: GenuineIntel Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 6352449536 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 2016-10-23 10:06:32 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\102316-26375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0x9F (0x3, 0xFFFFBC8B72B90060, 0xFFFFD380D0E38960, 0xFFFFBC8B7317BC60)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 2016-10-23 10:06:32 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFBC8B72B90060, 0xFFFFD380D0E38960, 0xFFFFBC8B7317BC60)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 2016-10-23 10:02:33 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\102316-29234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 2016-10-23 7:45:35 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\102316-20343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 2016-10-23 7:32:48 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\102316-30546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Colif]

there are 255 possible error codes, luckily there are more common ones and I don't have to remember how to fix everything...

Driver power state failure means a driver isn't designed to cope with the new power states in win 10 and creates that error
DPC Watchdog violation isn't as easy to explain - one common solution is this: http://www.thewindowsclub.com/dpc_watchdog_violation-blue-screen-in-windows-10

NTOSKRNL is crucial part of windows 10, if it crashes, so does win 10. One of its jobs is to deal with driver requests.
Unfortunately for me I cannot really tell what driver is causing problems just from that report. What I would do is follow the posting instructions on this page and post a question there as they will answer question faster than I can: http://www.tenforums.com/bsod-crashes-debugging/

 

[Mroma1228]

Thanks, I will follow your links