BSOD on startup

I have been having troubles now for almost a month, originally when I tried to play a graphically intensive game, I would get artifacts and then it would freeze up. I have been playing around with a few different drivers and now the problem has worsened. I can only run in safe mode when any nvidia driver is installed because on startup I get a flickering black screen at the log on point then there is a freeze, followed by a BSOD 0x116 nvlddmkm.sys.

I have also opened up the back and there doesn't seem to be any dust build up.

• Asus g51j - Notebook - latest bios (208)
• Windows 7x64 OEM
• 15 months old
• gtx 260m gpu
• drivers tried: 258.96, 260.89, 260.99, 266.58, 267.34, 267.76
• Each time i have uninstalled and used driver sweeper.

Any help would be greatly appreciated!

mrtom said:

I have been having troubles now for almost a month, originally when I tried to play a graphically intensive game, I would get artifacts and then it would freeze up. I have been playing around with a few different drivers and now the problem has worsened. I can only run in safe mode when any nvidia driver is installed because on startup I get a flickering black screen at the log on point then there is a freeze, followed by a BSOD 0x116 nvlddmkm.sys.

I have also opened up the back and there doesn't seem to be any dust build up.

• Asus g51j - Notebook - latest bios (208)
• Windows 7x64 OEM
• 15 months old
• gtx 260m gpu
• drivers tried: 258.96, 260.89, 260.99, 266.58, 267.34, 267.76
• Each time i have uninstalled and used driver sweeper.

Any help would be greatly appreciated!

These were caused by a video problem. Could be driver, card, power, or heat.

I would start with re-installing JUST the driver (no other utilities).

If that doesnt help download cpu-z, and gpu-z to keep an eye on the temps.

If that isnt the answer we can start investigating the power.

In the mean time I would test the ram

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

AND run a system file check

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information SFC /SCANNOW Command - System File Checker

Let us know the results from the report at the end.



Ken J

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\diagtoolreports\032611-58827-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;srv*e:\symbols
*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.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`04002000 PsLoadedModuleList = 0xfffff800`04247e90
Debug session time: Sat Mar 26 14:57:02.258 2011 (GMT-4)
System Uptime: 0 days 0:01:05.131
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa8004be7010, fffff8800f611354, 0, 0}

Unable to load image 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+156354 )

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

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa8004be7010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f611354, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+156354
fffff880`0f611354 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`07308400 fffff880`048e15f7 : fffffa80`04be7010 102906c9`a00038bf 00000000`00000000 fffffa80`06fdc901 : watchdog!WdDbgReportRecreate+0xa3
fffff880`07308920 fffff880`048e2075 : fffff8a0`03b5cffc fffff8a0`03c04740 fffff8a0`03a083c1 00000000`00154c3b : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`07308970 fffff880`048e2ce2 : fffffa80`04be7010 fffffa80`04be7010 fffffa80`06ed4830 fffffa80`06fdc010 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d
fffff880`07308a10 fffff880`04989f07 : fffffa80`04be7010 00000000`00000000 fffffa80`06ed4830 fffffa80`06fdc010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`07308a40 fffff880`049b3b75 : 00000000`ffffffff 00000000`00000fae 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`07308b20 fffff880`049b22bb : 00000000`00000102 00000000`00000000 00000000`00000fae 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`07308b50 fffff880`049852c6 : ffffffff`ff676980 fffffa80`06fdc010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`07308bf0 fffff880`049b1e7a : 00000000`00000000 fffffa80`06ed4830 00000000`00000080 fffffa80`06fdc010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`07308d00 fffff800`0431fcce : 00000000`fffffc32 fffffa80`06fadb60 fffffa80`036632f0 fffffa80`06fadb60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`07308d40 fffff800`04073fe6 : fffff800`041f4e80 fffffa80`06fadb60 fffff800`04202cc0 fffff880`01442384 : nt!PspSystemThreadStartup+0x5a
fffff880`07308d80 00000000`00000000 : fffff880`07309000 fffff880`07303000 fffff880`07307ee0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+156354
fffff880`0f611354 ??              ???

SYMBOL_NAME:  nvlddmkm+156354

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d27c6da

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys

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

I ran the memory test overnight and had 11 passes with no errors