Win7 started crashing today, ok in safe mode

[twicewrapped]

hello,
today my pc started crashing, but stays stable in safe mode. I have looked around other threads, but these symptoms are slightly different.

the crash starts with the screen going purple and distorted, then the system locks and shuts down.
blue screen appears showing crash details.
systems boots up and goes into restore mode. restores successfully using a recent restore point.
using safe mode boot up, all fine.
ran virus scan and check disk. all ok
updated nvidia driver (possible graphics issue, purple screen?) all ok

rebooted full windows, seemed ok. 5minutes later - crash!
arrrgh
any help greatly appreciated!

 

[richc46]

If clean boot does not find the the problem, it is probably a driver
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

 

[twicewrapped]

thanks, will give that a try and report back.

 

[richc46]

Follow clean boot instructions carefully.

 

[richc46]

If you cannot find the solution with clean boot and cant find the driver. Post the BSOD explanation:
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[twicewrapped]

ok, followed the instructions and booted with drivers I recognised, AVG etc. After rebooting, Windows opened fine and I started to open msconfig again, as I did, the screen went purple and I thought it had crashed. But this time after a 2 second blackout, the normal screen returned and a pop up appeared saying the nvidia card had recovered from a failure..
I opened device manager and updated the driver for the video card. Rebooted and windows opened ok. 10 seconds later, purple screen and this time a lock up. no bsod though, it's just locked.
So, i'm guessing either something is conflicting with the Nvidia driver, or the graphics card is faulty?

 

[richc46]

Follow the instructions given and I can give you the precise cause of the problem.

 

[twicewrapped]

worked through all the instructions. problem occurs no matter which services or boot ups I enable or disable. even with all disabled it still crashed..

 

[twicewrapped]

will now do the BSOD post

 

[richc46]

The BSOD report will give us a lot more information.

 

[twicewrapped]

zip attached perfmon didn't work

 

[richc46]

Little more difficult, that hoped. It is BC 124, the most difficult to resolve.
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

As you see there are many possible hardware causes for 124. As a personal choice, because you work in safe mode, I would start with a driver verifier
Enable the Driver Verifier
www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html

Although a pain, it is a likely cause since you did work in safe mode.

 

[zigzag3143]

zip attached perfmon didn't work

These were caused by a TDR_Video_reset attempt. In short the video card sstopped working and the system tried unccessfully to reset it. Usually caused by a driver or card problem

Several of these also reflected a hardware problem which I suspect again was the video card.

Remove and replace the driver as indicated.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\102310-28125-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`01a0d000 PsLoadedModuleList = 0xfffff800`01c4ae50
Debug session time: Sat Oct 23 17:24:23.046 2010 (GMT-4)
System Uptime: 0 days 0:00:44.750
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80039f64e0, fffff88002de1230, 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+10d230 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80039f64e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88002de1230, 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+10d230
fffff880`02de1230 803d39d3b60000  cmp     byte ptr [nvlddmkm+0xc7a570 (fffff880`0394e570)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`025bb9c8 fffff880`03b29ef8 : 00000000`00000116 fffffa80`039f64e0 fffff880`02de1230 00000000`00000000 : nt!KeBugCheckEx
fffff880`025bb9d0 fffff880`03b29c02 : fffff880`02de1230 fffffa80`039f64e0 fffffa80`03becd50 fffffa80`03bd8010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`025bba10 fffff880`03a0ff07 : fffffa80`039f64e0 00000000`00000000 fffffa80`03becd50 fffffa80`03bd8010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`025bba40 fffff880`03a39b75 : 00000000`ffffffff 00000000`00000a59 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`025bbb20 fffff880`03a382bb : 00000000`00000102 00000000`00000000 00000000`00000a59 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`025bbb50 fffff880`03a0b2c6 : ffffffff`ff676980 fffffa80`03bd8010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`025bbbf0 fffff880`03a37e7a : 00000000`00000000 fffffa80`03074010 00000000`00000080 fffffa80`03bd8010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`025bbd00 fffff800`01d21c06 : 00000000`fffffc32 fffffa80`03be4620 fffffa80`01866b30 fffffa80`03be4620 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`025bbd40 fffff800`01a5bc26 : fffff880`009bf180 fffffa80`03be4620 fffff880`009c9f40 fffff880`01238a90 : nt!PspSystemThreadStartup+0x5a
fffff880`025bbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+10d230
fffff880`02de1230 803d39d3b60000  cmp     byte ptr [nvlddmkm+0xc7a570 (fffff880`0394e570)],0

SYMBOL_NAME:  nvlddmkm+10d230

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b07613e

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

edit

Rich we are both right. 4 crashes video TDR, and 2 hardware (124)

 

[twicewrapped]

ok, i used driver sweeper to uninstall the nvidia drivers. rebooted and all was fine (though obviously with basic screen settings).
I used device manager to re-install the nvidia driver for the graphics card and rebooted.
after 2 mins the problem re-occurred, crash!

 

[zigzag3143]

ok, i used driver sweeper to uninstall the nvidia drivers. rebooted and all was fine (though obviously with basic screen settings).
I used device manager to re-install the nvidia driver for the graphics card and rebooted.
after 2 mins the problem re-occurred, crash!

First you shouldnt use device manger to re-install the driver because it uses the driver in its cash which is older. Go to the Mfr site and get the newest

Second Upload the DMP file if avail.

It may be a heat issue, or a video card problem.
download cpu-z, and gpu-z for temps.

Ken J

 

[twicewrapped]

i repeated the driver sweep and downloaded the nvida drivers from their website. same problem occurred.
if it was a heat issue wouldn't the issue occur all the time? i.e. in safe mode and running without the driver installed. both of which had no problems. Same question for possible video card fault..

In the meantime, I will install the temp apps you suggested.

 

[twicewrapped]

ok cpuz installed an running. what am I looking for? gpuz won't work as I have no video driver installed (if I install, the pc crashes)
I ran the pc this morning without the graphic card driver for a few hours, it was fine. Then I downloaded the nvidia drivers and did a clean install. It re-booted and seemed to be ok, but a while later it crashed again.. the driver seems to be causing the issue..