Windows 7: Unknown Bugcheck : Bugcheck c00002e3 - System is randomly Shutting OFF

momotrdr · 03 Feb 2012

T61
4GB Kingston T61 specific Ram
2.5GHz
6459CTO
T9300 (965 Chipset)

Fresh, Full licensed copy of Win 7 Ultimate loaded onto system, without issues.

All device drivers from the Lenovo site have been loaded successfully without incident. Device Manager showing Zero issues.

System randomly will just simply shut down, NO BSOD, just shut off.

Only diagnostic that I can get the system to repeat this behavior is the Lenovo Thinkvantage Toolbox diagnostic program.

System will shut down during either the multicore processor test, or the advanced memory pattern test.

Parameters of bugcheck: 0x96ce1ab8, 0xc0000189, 0x0, 0x0

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Files that help describe the problem
020309-31496-01.dmp
sysdata.xml
WERInternalMetadata.xml

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.
Extra information about the problem
BCCode: c00002e3
BCP1: 96CE1AB8
BCP2: C0000189
BCP3: 00000000
BCP4: 00000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Running the Windows Debugger utility I was able to retrieve this info from the mini-dump file:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\owner\Desktop\020309-31496-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x82c13000 PsLoadedModuleList = 0x82d53230
Debug session time: Fri Feb 3 11:10:12.063 2012 (UTC - 8:00)
System Uptime: 0 days 0:00:29.811
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
.....

momotrdr · 03 Feb 2012

I'm unable to figure out how to successfully use or read the information in the DMP file, so the answer may be right in front of me, but I'm unable to understand it.

Anyone tech savvy with Win 7 (32-bit) version to know what's up?

momotrdr · 03 Feb 2012

Given that I did get this system from a seller off of Craigslist, I'm wondering if any of these codes in my original post seem to indicate the presence of a virus on the HDD?

I didn't install the OS myself, however, I inspected it right after he loaded OS7. Then I went home and loaded all the Thinkpad specific drivers on....

the system shutting down didn't start right after that, however, a couple of days later. So, just not sure if one has something to do with the other. I don't like recommendations that are suggesting to simply "Format and reload" the OS Again!

I feel like this is a cop out way, and not truly the best way to go about resolving the core issue.

Fingers crossed there are some really good windows techs on this board.

momotrdr · 03 Feb 2012

Tried following the User Posting message instructions for the posting to this thread BTW and it doesn't download the app.

momotrdr · 03 Feb 2012

Help Anyone know what this problem could be?

writhziden · 04 Feb 2012

Please follow the http://www.sevenforums.com/crashes-d...tructions.html so we have more information to better assist you. Also, when you respond so many times to your own thread, many of us helping assume that you already received help because we see so many replies.

Please follow the instructions and we will do our best to troubleshoot your problem with you.

I see you are having trouble downloading the app to follow the instructions. Have you tried another computer? We really need the crash reports as they contain the best information for determining the cause of the crashes.

momotrdr · 04 Feb 2012

Done.

Please help.

writhziden · 04 Feb 2012

Code:

Loading Dump File [K:\Kingston\BSODDmpFiles\momotrdr\Windows_NT6_BSOD_jcgriff2\011712-31309-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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x8283c000 PsLoadedModuleList = 0x829854d0
Debug session time: Tue Jan 17 16:08:28.966 2012 (GMT-7)
System Uptime: 0 days 0:58:27.963
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
......
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 87cdd510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 8c43b990, 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+c990
8c43b990 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:  
88d88b74 8bbc707b 00000116 87cdd510 8c43b990 nt!KeBugCheckEx+0x1e
88d88b98 8bbbb937 8c43b990 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
88d88bbc 8cd9692c 00000000 00000102 87cff560 dxgkrnl!TdrIsRecoveryRequired+0xb8
88d88c34 8cdc0944 fffffcfb 00036d8d 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
88d88c5c 8cdc1065 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
88d88c98 8cd9d8f0 88d88c90 87def6f8 87dee410 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
88d88d28 8cdc23c9 87cff560 82873509 87cff560 dxgmms1!VidSchiScheduleCommandToRun+0xaa
88d88d3c 8cdc2485 87cff560 00000000 87d05610 dxgmms1!VidSchiRun_PriorityTable+0xf
88d88d50 82a44fda 87cff560 a5fec9df 00000000 dxgmms1!VidSchiWorkerThread+0x7f
88d88d90 828ed1f9 8cdc2406 87cff560 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+c990
8c43b990 55              push    ebp

SYMBOL_NAME:  nvlddmkm+c990

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4aa310b9

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

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

Quote: Originally Posted by H2SO4

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 http://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.

Also, update all drivers, BIOS, and firmware that you can at Lenovo Support - Download Drivers and Software (US).

momotrdr · 04 Feb 2012

writhziden!
Thank you so much!

This at least points me in the right direction. I just had no idea what was up. If it's perhaps a driver problem, then just maybe I didn't buy a P.O.S. used laptop, right? Well fingers crossed anyways.

I'll repost here either way, once I re-verify that I've updated all drivers.

Thanks again,
mike

writhziden · 04 Feb 2012

Quote: Originally Posted by momotrdr

writhziden!
Thank you so much!

This at least points me in the right direction. I just had no idea what was up. If it's perhaps a driver problem, then just maybe I didn't buy a P.O.S. used laptop, right? Well fingers crossed anyways.

I'll repost here either way, once I re-verify that I've updated all drivers.

Thanks again,
mike

Lenovo appears to have very good support for drivers. I was rather impressed with what they had to offer for a fairly old computer. I think if you get those drivers up to date, you will find things run a lot more smoothly.

Windows 7: Unknown Bugcheck : Bugcheck c00002e3 - System is randomly Shutting OFF

Unknown Bugcheck : Bugcheck c00002e3 - System is randomly Shutting OFF problems?