Hello,
I am experiencing frequent system crashes since I upgraded to Windows 8.1
I am pasting below WhoCrashed report.
Could you please help me solve this issue?
I suspect the culprit is NVIDIA graphics driver, but it's always up do date to the latest version.
Thanks and regards,
Marco
System Information (local)
computer name: MARCO-PC
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: G75VW, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17130569728 total
VM: 2147352576, free: 1918095360
*** * Crash Dump Analysis*
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 20/12/2013 05:54:22 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122013-21671-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x14DCA0)
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 be caused by a 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 Fri 20/12/2013 05:54:22 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module:
nvlddmkm.sys (nvlddmkm+0x1A08D9)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 331.82
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 331.82
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 be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 331.82 , NVIDIA Corporation).
Google query: NVIDIA Corporation DPC_WATCHDOG_VIOLATION
On Wed 27/11/2013 10:33:27 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112713-28906-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x14DCA0)
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 be caused by a 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 Thu 21/11/2013 12:51:24 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112113-21359-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x14DCA0)
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 be caused by a 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.