Windows 7 Blue screen of death crashes!!

Welcome!

It looks like all of them were caused by your nVidia driver nvlddmkm.sys. Try uninstalling your nVidia drivers and installing the latest version.

You may need to try many different drivers until you get satisfactory results.

Good luck!

~JK

Code:

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


Loading Dump File [C:\Users\Jonathan\Desktop\032910-25490-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0300d000 PsLoadedModuleList = 0xfffff800`0324ae50
Debug session time: Mon Mar 29 06:30:10.491 2010 (GMT-4)
System Uptime: 0 days 23:50:16.458
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.......
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8004447410, fffff88004e4fb10, 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+5e4b10 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8004447410, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004e4fb10, 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+5e4b10
fffff880`04e4fb10 4053            push    rbx

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`09194b48 fffff880`03f0def8 : 00000000`00000116 fffffa80`04447410 fffff880`04e4fb10 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`09194b50 00000000`00000116 : fffffa80`04447410 fffff880`04e4fb10 ffffffff`c000009a 00000000`00000004 : dxgkrnl+0x5cef8
fffff880`09194b58 fffffa80`04447410 : fffff880`04e4fb10 ffffffff`c000009a 00000000`00000004 00000000`00000001 : 0x116
fffff880`09194b60 fffff880`04e4fb10 : ffffffff`c000009a 00000000`00000004 00000000`00000001 fffffa80`04447410 : 0xfffffa80`04447410
fffff880`09194b68 ffffffff`c000009a : 00000000`00000004 00000000`00000001 fffffa80`04447410 fffff880`03ee1867 : nvlddmkm+0x5e4b10
fffff880`09194b70 00000000`00000004 : 00000000`00000001 fffffa80`04447410 fffff880`03ee1867 fffff880`04e4fb10 : 0xffffffff`c000009a
fffff880`09194b78 00000000`00000001 : fffffa80`04447410 fffff880`03ee1867 fffff880`04e4fb10 fffffa80`07bf5000 : 0x4
fffff880`09194b80 fffffa80`04447410 : fffff880`03ee1867 fffff880`04e4fb10 fffffa80`07bf5000 00000000`00000000 : 0x1
fffff880`09194b88 fffff880`03ee1867 : fffff880`04e4fb10 fffffa80`07bf5000 00000000`00000000 ffffffff`c000009a : 0xfffffa80`04447410
fffff880`09194b90 fffff880`04e4fb10 : fffffa80`07bf5000 00000000`00000000 ffffffff`c000009a ffffffff`ff676980 : dxgkrnl+0x30867
fffff880`09194b98 fffffa80`07bf5000 : 00000000`00000000 ffffffff`c000009a ffffffff`ff676980 fffffa80`07bdd010 : nvlddmkm+0x5e4b10
fffff880`09194ba0 00000000`00000000 : ffffffff`c000009a ffffffff`ff676980 fffffa80`07bdd010 00000000`00000000 : 0xfffffa80`07bf5000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+5e4b10
fffff880`04e4fb10 4053            push    rbx

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+5e4b10

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a6f0977

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

Often times the driver Windows Update finds is not the same as the latest one released by the manufacturer.

I can't tell you that the latest driver is going to work, or the oldest one you can find. Different drivers work for different people, for whatever reason.