swiftscout21
Newcomer
2 messages
joined Nov 2014
[Crash dump directory: C:\Windows\Minidump
Crash dumps are currently active on your machine.
Your computer hit a snag on Thu 13.11.2014. 13:19:16 GMT
crash dump file: C:\Windows\Minidump\111314-35459-01.dmp
It looks like the culprit here might be: nvlddmkm.sys (nvlddmkm+0x158288)
Bugcheck code: 0x116 (0xFFFFFA8007D05010, 0xFFFFF8800F42E288, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: Nvidia Windows kernel moda driver, version 344.65
company: Nvidia Corporation
description: Nvidia Windows kernel moda driver, version 344.65
Bug check description: Basically, the system tried to reset the display driver after a timeout, but things just didn't go as planned.
A third-party driver seems to be the likely reason for this system error. You might want to see if there's a newer update available for: nvlddmkm.sys (Nvidia Windows kernel moda driver, version 344.65 , Nvidia Corporation).
Google query: nvlddmkm.sys Nvidia Corporation VIDEO_TDR_ERROR
Your computer went down on Thu 13.11.2014. 13:19:16 GMT
crash dump file: C:\Windows\memory.dmp
This issue was likely triggered by: dxgkrnl.sys (dxgkrnl!TdrResetFromTimeout +0 x214)
Bugcheck code: 0x116 (0xFFFFFA8007D05010, 0xFFFFF8800F42E288, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft ® Windows ® Operating system company
company: Microsoft Corporation
description: DirectX Graphics kernel bug
Bug check description: This means the attempt to reset the display driver following a timeout was unsuccessful.
Since the crash happened within a standard Microsoft module, it’s possible your system configuration isn't quite right—or perhaps another driver on the system is causing a conflict that we can't pinpoint just yet.
I wonder what's actually going on here...