BSOD when gaming, error 101

Dreadedmike · 14 Mar 2012

Dreadedmike said:

the step where i search for "nvlddmkm.sy_" i find no results.
on both options you have posted i cannot find the file nvlddmkm.sy_

I have found the nvlddmkm.sy_ file and have done what you said, shall i run a test and see if i get BS?

After trying to start my furmark test i get an error from furmark saying it requires an OpenGl 2.0 Compliant Graphics Controller

I also looked at Nvidia Control Panel and all the tabs are gone except for "Stereoscopic 3D"
?????

Dreadedmike · 14 Mar 2012

Dreadedmike said:

the step where i search for "nvlddmkm.sy_" i find no results.
on both options you have posted i cannot find the file nvlddmkm.sy_

I have found the nvlddmkm.sy_ file and have done what you said, shall i run a test and see if i get BS?

After trying to start my furmark test i get an error from furmark saying it requires an OpenGl 2.0 Compliant Graphics Controller

I also looked at Nvidia Control Panel and all the tabs are gone except for "Stereoscopic 3D"
?????

repeated steps and i am about to test, sorry for such carelessness on instructions

SmurofNeves · 14 Mar 2012

Have you remembered to restart your PC..??

Dreadedmike · 14 Mar 2012

Yes i did restart PC, followed all steps and still got B SOD on test, are you sure this is not a hardware problem, i worry for my PSU, because this only has happened on high performance games in SLI mode.
Heres the dmp again.

P.S getting tired here, will be back up in a few hours to continue on the problem thank you so far for your support guys hopefully i can get this fixed

writhziden · 16 Mar 2012

Problem Devices:

Code:

Photosmart Plus B209a-m	ROOT\MULTIFUNCTION\0000	This device is disabled.
Photosmart 2600 series	ROOT\MULTIFUNCTION\0001	This device is disabled.
Photosmart Plus B209a-m	ROOT\IMAGE\0000	This device is disabled.

Security Software:

Code:

teatimer.exe	c:\program files (x86)\spybot - search & destroy\teatimer.exe	3964	4	200	1380	3/14/2012 2:57 AM	1.6.4.26	2.04 MB (2,144,088 bytes)	12/26/2011 10:45 PM
msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	132	8	200	1380	3/14/2012 2:56 AM	3.0.8402.0	12.48 KB (12,784 bytes)	4/27/2011 6:21 PM
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	3004	8	200	1380	3/14/2012 2:57 AM	3.0.8402.0	281.52 KB (288,272 bytes)	4/27/2011 6:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	3872	8	200	1380	3/14/2012 2:57 AM	2.1.1116.0	1.37 MB (1,436,736 bytes)	6/15/2011 3:35 PM

Spybot can cause problems on systems. I would recommend removing it. If you want the same functionality from a security product, you are welcome to start a thread in System Security - Windows 7 Forums

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\Dreadedmike\Windows_NT6_BSOD_jcgriff2\031412-29187-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0361d000 PsLoadedModuleList = 0xfffff800`03862670
Debug session time: Wed Mar 14 01:54:56.765 2012 (UTC - 6:00)
System Uptime: 0 days 0:08:23.655
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800cb804e0, fffff8800fd4baa4, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+ca1aa4 )

Followup: MachineOwner
---------

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800cb804e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fd4baa4, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+ca1aa4
fffff880`0fd4baa4 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0d999a48 fffff880`02c76000 : 00000000`00000116 fffffa80`0cb804e0 fffff880`0fd4baa4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0d999a50 fffff880`02c49867 : fffff880`0fd4baa4 fffffa80`078b8000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0d999a90 fffff880`02c75e0f : fffffa80`ffffd84d 00000000`00000000 fffffa80`0cb804e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0d999b40 fffff880`02d44ec1 : fffffa80`09baad50 00000000`00000080 00000000`00000000 fffffa80`0991e010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0d999bc0 fffff800`03934fee : fffff880`0cc0d550 fffffa80`0989f040 fffffa80`06cef040 fffff800`03691757 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0d999c00 fffff800`0368b5e6 : fffff800`0380fe80 fffffa80`0989f040 fffff800`0381dcc0 fffff880`01220cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`0d999c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+ca1aa4
fffff880`0fd4baa4 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+ca1aa4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f4e68c4

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------

H2SO4 said:

These are all stop 0x116 VIDEO_TDR_FAILURE conditions.

It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash. As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds. If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling.

The above quote was taken from https://www.sevenforums.com/crashes-d...tml#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining STOP 0x116: VIDEO_TDR_ERROR troubleshooting and proceed through each step. Let us know if you need further help.

Dreadedmike · 18 Mar 2012

Sorry for no replies again, went on vacation, but I never usually get 0x116 blue screens, only when running a stress test, the frequent blue screens i get are 0x101, and i just got another when loading up minecraft, here is the mini-dump.

writhziden · 18 Mar 2012

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\Dreadedmike\Windows_NT6_BSOD_jcgriff2\031812-19796-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03660000 PsLoadedModuleList = 0xfffff800`038a4650
Debug session time: Sun Mar 18 08:58:35.177 2012 (UTC - 6:00)
System Uptime: 0 days 11:53:31.011
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff88002f65180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f65180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

Debugging Details:
------------------


OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0789edd8 fffff800`03733b39 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`02f65180 : nt!KeBugCheckEx
fffff880`0789ede0 fffff800`036e6907 : 00000000`00000000 fffff800`00000002 00000000`00002711 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`0789ee70 fffff800`03621895 : fffff800`03647460 fffff880`0789f020 fffff800`03647460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0789ef70 fffff800`036d9273 : 00000000`8a4c973d fffff800`03851e80 fffff800`03851e80 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0789efa0 fffff800`036e1bf6 : fffff800`03851e80 fffff880`00000001 00000000`00000000 fffff880`0789f238 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0789f130 fffff800`036fc571 : 00000000`00000000 00000000`00000002 00000000`00000001 fffff960`001caa88 : nt!KeFlushMultipleRangeTb+0x266
fffff880`0789f200 fffff800`036fefa8 : 00000000`00000002 fffff880`0789f380 fffff900`c0636000 fffff880`0789fb00 : nt!MiFlushTbAsNeeded+0x1d1
fffff880`0789f310 fffff800`03807f86 : 00000000`00001360 fffff880`041a5cc0 00000000`00000021 00000000`00000002 : nt!MiAllocatePagedPoolPages+0x4cc
fffff880`0789f430 fffff800`036fccd0 : 00000000`00001360 fffff880`041a5cc0 00000000`00000021 fffff900`c0636000 : nt!MiAllocatePoolPages+0x906
fffff880`0789f570 fffff800`0380a90e : 00000000`00000000 00000000`0000cccc 00000000`00000020 00000000`00001360 : nt!ExpAllocateBigPool+0xb0
fffff880`0789f660 fffff960`000c70c4 : fffff900`c0084370 00000000`00000000 fffff880`0789fa00 fffff880`07010101 : nt!ExAllocatePoolWithTag+0x82e
fffff880`0789f750 fffff960`00074aa2 : fffff880`0789fa80 fffff900`c00c0010 fffff900`c304b470 fffff960`fffffffe : win32k!AllocThreadBufferWithTag+0x24
fffff880`0789f780 fffff960`00074015 : fffff900`c25d0cd8 fffff880`00000028 fffff900`c2445720 fffff880`0789fcd0 : win32k!EngTextOut+0x4aa
fffff880`0789fb10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!GreExtTextOutWLocked+0x1d29


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------

Run these hardware checks to determine which hardware is causing the 0x101 error:

If you are overclocking any hardware, please stop.
Monitor temperatures during the following tests.

Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
- Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.

Dreadedmike · 18 Mar 2012

Alright i will run the tests later tonight thank you

writhziden · 18 Mar 2012

You're welcome. Best of luck!