BSOD error 0x0000016 - nvlddmkm.sys

So far I've tried unistallign and reinstalling the nvidia drivers, installing beta versions of them, downgrading some drivers because someone told me that the realtek and nvidia drivers are not compatible. Reinstalling directx and reinstalling windows at least a dozen times.

Code:

OS Version:                6.1.7600 N/A Build 7600

Update to Service Pack 1 (SP1)

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site

Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH



Antivirus Software? Good and Free system security combination.

Code:

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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03088e50
Debug session time: Wed Feb 22 15:38:31.878 2012 (UTC - 7:00)
System Uptime: 0 days 0:04:16.813
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800679e4e0, fffff88010081ae4, 0, 2}

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+1aeae4 )

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

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

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

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


FAULTING_IP: 
nvlddmkm+1aeae4
fffff880`10081ae4 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  ²ñÌ


CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`043b4988 fffff880`040c0cbc : 00000000`00000116 fffffa80`0679e4e0 fffff880`10081ae4 00000000`00000000 : nt!KeBugCheckEx
fffff880`043b4990 fffff880`040c09c6 : fffff880`10081ae4 fffffa80`0679e4e0 fffffa80`08aafd50 fffffa80`088f4410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`043b49d0 fffff880`04167f07 : fffffa80`0679e4e0 00000000`00000000 fffffa80`08aafd50 fffffa80`088f4410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`043b4a00 fffff880`04191b75 : 00000000`ffffffff 00000000`00003f74 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`043b4ae0 fffff880`041902bb : 00000000`00000102 00000000`00000000 00000000`00003f74 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`043b4b10 fffff880`041632c6 : ffffffff`ff676980 fffffa80`088f4410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`043b4bb0 fffff880`0418fe7a : 00000000`00000000 fffffa80`08aafd50 00000000`00000080 fffffa80`088f4410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`043b4cc0 fffff800`03160166 : 00000000`fffffc32 fffffa80`08a41060 fffffa80`06720040 fffffa80`08a41060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`043b4d00 fffff800`02e9b486 : fffff800`03035e80 fffffa80`08a41060 fffff800`03043c40 fffff880`01247a90 : nt!PspSystemThreadStartup+0x5a
fffff880`043b4d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+1aeae4
fffff880`10081ae4 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+1aeae4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f2128ab

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.

Heya thanks for the help! I downloaded service pack 1 and havent gotten a single blue screen...... but I have gotten tons of other screens =(. Instead of blue screens I now regularly get red, green, white and yellow screens anytime I launch starcraft 2 or star wars the old republic. ALTHOUGH I was able to play starcraft 2 for a little bit.

The first time I launched SC2 it crashed, second time it ran perfectly, third time perfectly. I stopped playing for a bit and I downloaded star wars the old republic because I wanted to try other games out. Thats when the solid color crashes started, and ever since then I havent been able to play any games with high end graphics. Is it my video card? My ram? I was able to play starcraft I dont understand why it would just **** up like that!

To test out your hardware, do the following steps:

• 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.[/indent]
  
  
  • 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.
    
    
    
  • 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.

I fixed it! It was as simple as pressing a red button. You see the power supply on my computer was simply giving too much voltage! Thanks for your help its much appreciated!

You're welcome. Glad you found the problem. :)