BSOD help!

Montycat · 31 Jan 2010

Ok, I've been getting nvlddmkm.sys BSODs 5-90 minutes into playing Mass Effect 2 on my new computer. Any ideas on what's wrong with my computer?

**Pauly** · 31 Jan 2010

Before we start scouring the dumps have you updated your gfx drivers or removed and re-installed them yet, if not then thats where i would start, go to nvidia website and obtain the latest for your hardware

All dumps report 0x116 error, have a look here for a bit more info, defo a gfx issue http://www.carrona.org/bsodindx.html#0x00000116

zigzag3143 · 31 Jan 2010

Montycat said:

Ok, I've been getting nvlddmkm.sys BSODs 5-90 minutes into playing Mass Effect 2 on my new computer. Any ideas on what's wrong with my computer?

Hi and welcome all of these crashes are virtually identical. All were probably caused by your video driver. The system attempted to re-start but the car did not restart quickly enough

I would
Download and install a fresh driver and run a \
system file check
type cmd in search>right click and run as admin>sfc /scannow

If you are overclocking stop
I would also download Gpu-z to keep track of the video card temps

Good luck

Ken

Code:

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


Loading Dump File [C:\Users\K\Desktop\New folder\013010-19250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82844000 PsLoadedModuleList = 0x8298c810
Debug session time: Sun Jan 31 01:57:24.213 2010 (GMT-5)
System Uptime: 0 days 1:01:01.102
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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

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

FAULTING_IP: 
nvlddmkm+e2a30
9650aa30 55              push    ebp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8da5bb74 96fc2adb 00000116 85729510 9650aa30 nt!KeBugCheckEx+0x1e
WARNING: Stack unwind information not available. Following frames may be wrong.
8da5bb98 96fc38fa 9650aa30 00000000 00000002 dxgkrnl+0x8cadb
8da5bbbc 928c092c 00000000 00000102 881d5008 dxgkrnl+0x8d8fa
8da5bc34 928eaa32 fffffcfb 000393f0 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8da5bc5c 928eb153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
8da5bc98 928c78f0 8da5bc90 88220748 88220b48 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
8da5bd28 928ec4b7 881d5008 828803f1 881d5008 dxgmms1!VidSchiScheduleCommandToRun+0xaa
8da5bd3c 928ec573 881d5008 00000000 881e3d48 dxgmms1!VidSchiRun_PriorityTable+0xf
8da5bd50 82a5266d 881d5008 bdcbd71f 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8da5bd90 829040d9 928ec4f4 881d5008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+e2a30
9650aa30 55              push    ebp

SYMBOL_NAME:  nvlddmkm+e2a30

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4c0972

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

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