Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD and reboot


03 Jun 2011   #1

Windows 7 Enterprise x64
 
 
Random BSOD and reboot

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA800628A010
BCP2: FFFFF880072A64E0
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\060311-37081-01.dmp
C:\Users\liy13\AppData\Local\Temp\WER-436303-0.sysdata.xml

System: win 7 64bits
Hardware: T61 with NVS 140 graphics card

I am trying to fix my old T61 ....

I tried to take a look into the dump file, and it seemed that it's about the Nvidia NVS 140m card driver but I am not sure how to fix it. I tried install the latest driver from Lenovo, but the problem still exists.

My System SpecsSystem Spec
.

03 Jun 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by youleelove View Post
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA800628A010
BCP2: FFFFF880072A64E0
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\060311-37081-01.dmp
C:\Users\liy13\AppData\Local\Temp\WER-436303-0.sysdata.xml

System: win 7 64bits
Hardware: T61 with NVS 140 graphics card

I am trying to fix my old T61 ....

I tried to take a look into the dump file, and it seemed that it's about the Nvidia NVS 140m card driver but I am not sure how to fix it. I tried install the latest driver from Lenovo, but the problem still exists.

Even before investigating the below I would remove Symantec, and replace with Microsoft Security essentials at least to test.

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

Virus, Spyware & Malware Protection | Microsoft Security Essentials

"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.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help STOP 0x116: VIDEO_TDR_ERROR troubleshooting - Windows 7 Forums


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\Windows_NT6_BSOD_jcgriff2\060311-37081-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02a19000 PsLoadedModuleList = 0xfffff800`02c5e650
Debug session time: Fri Jun  3 00:57:27.276 2011 (GMT-4)
System Uptime: 0 days 10:32:37.272
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800628a010, fffff880072a64e0, 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+134e0 )

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: fffffa800628a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880072a64e0, 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+134e0
fffff880`072a64e0 48895c2420      mov     qword ptr [rsp+20h],rbx

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`069eb9c8 fffff880`06c99000 : 00000000`00000116 fffffa80`0628a010 fffff880`072a64e0 00000000`00000000 : nt!KeBugCheckEx
fffff880`069eb9d0 fffff880`06c98d0a : fffff880`072a64e0 fffffa80`0628a010 fffffa80`0629ac00 fffffa80`0628e010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`069eba10 fffff880`06d3ff07 : fffffa80`0628a010 00000000`00000000 fffffa80`0629ac00 fffffa80`0628e010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`069eba40 fffff880`06d69b75 : 00000000`ffffffff 00000000`00251f9f 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`069ebb20 fffff880`06d682bb : 00000000`00000102 00000000`00000000 00000000`00251f9f 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`069ebb50 fffff880`06d3b2c6 : ffffffff`ff676980 fffffa80`0628e010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`069ebbf0 fffff880`06d67e7a : 00000000`00000000 fffffa80`06329d50 00000000`00000080 fffffa80`0628e010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`069ebd00 fffff800`02d3532e : 00000000`fffffc32 fffffa80`062a9210 fffffa80`03c3e040 fffffa80`062a9210 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`069ebd40 fffff800`02a8a666 : fffff800`02c0be80 fffffa80`062a9210 fffff800`02c19cc0 fffff880`01225384 : nt!PspSystemThreadStartup+0x5a
fffff880`069ebd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+134e0
fffff880`072a64e0 48895c2420      mov     qword ptr [rsp+20h],rbx

SYMBOL_NAME:  nvlddmkm+134e0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4aa310f2

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`07293000 fffff880`07d9bc00   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Sep 05 21:31:30 2009 (4AA310F2)
    CheckSum:         00B1884B
    ImageSize:        00B08C00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Old drivers
Code:
rixdpx64.sys    11/18/2006 12:07:46 AM        fffff880`06d26000    fffff880`06d7d000    0x00057000    0x455e8712                        
ibmpmdrv.sys    5/31/2007 5:51:31 AM        fffff880`083b9000    fffff880`083c3000    0x0000a000    0x465e9aa3                        
VSTCNXT6.SYS    10/15/2008 8:52:22 PM        fffff880`0941e000    fffff880`094e9000    0x000cb000    0x48f69046                        
VSTAZL6.SYS    10/15/2008 8:53:42 PM        fffff880`08600000    fffff880`08652000    0x00052000    0x48f69096                        
VSTDPV6.SYS    10/15/2008 8:57:45 PM        fffff880`0905b000    fffff880`091cf000    0x00174000    0x48f69189                        
e1e6032e.sys    3/24/2009 2:17:23 PM        fffff880`07246000    fffff880`0728e000    0x00048000    0x49c923b3                        
ADIHdAud.sys    5/18/2009 1:31:55 PM        fffff880`086f8000    fffff880`08778000    0x00080000    0x4a119b8b                        
athrx.sys    6/9/2009 2:06:49 PM        fffff880`0806b000    fffff880`081c3000    0x00158000    0x4a2ea4b9                        
SYMEVENT64x86.SYS    6/24/2009 4:19:12 PM        fffff880`03d12000    fffff880`03d48000    0x00036000    0x4a428a40
How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
My System SpecsSystem Spec
Reply

 Random BSOD and reboot




Thread Tools



Similar help and support threads for2: Random BSOD and reboot
Thread Forum
Random BSOD/reboot BSOD Help and Support
Solved BSOD, Random Reboot, ATHR.SYS BSOD Help and Support
Solved Random Reboot to BIOS -- No BSOD BSOD Help and Support
Random BSOD 0x0000007a - reboot BSOD Help and Support
[REBOOT] Sudden Random Reboot and black screen at start up! BSOD Help and Support
Random reboot and BSOD BSOD Help and Support
Help! Random shutdown/reboot with and without BSOD! BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 03:32 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33