Windows 7: BSOD After Win7 Welcome Screen

wantuzus · 21 Feb 2012

This tragedy happen during I surfing internet, then my monitor blackout suddenly. Then I restart, there was BSOD appearnya about 10 sec before reboot after Win7 welcome screen. After the, my Boot sequence have 3 redline many blocks vertically. I format the HD and try to reinstall win7 from scratch. The BSOD scenario happen (Same attribute). I don't have idea to settle this problem. Please help me

Herewith attached minidump memory file but for the perfmon /report i can't generate because its keep appears error "The system cannot find the path specified"

My PC OS
Win7 32 Bit
Memory Kingston 2GB
Processor Pentium Dual CoreE2180 2 Ghz

zigzag3143 · 21 Feb 2012

Quote:

"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

**Capt.Jack Sparrow** · 21 Feb 2012

Hello and Welcome!

Seems like the crashes are VIDEO_TDR_FAILURE 0x116 which mostly referring to Video card or driver. Follow this article STOP 0x116: VIDEO_TDR_ERROR troubleshooting .

Follow this guide and do a complete nVidia driver Cleanup nVidia Driver Cleanup Guide | Captain Debugger also run all the stress test mentioned in the above guide.

Bugcheck:

Code:

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 86afe008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 914bca80, 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:
------------------

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

FAULTING_IP: 
nvlddmkm+aca80
914bca80 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:  
8e782b74 91e02c26 00000116 86afe008 914bca80 nt!KeBugCheckEx+0x1e
8e782b98 91e03a45 914bca80 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
8e782bbc 91e3392c 00000000 00000102 85568008 dxgkrnl!TdrIsRecoveryRequired+0xb8
8e782c34 91e5d944 fffffcfb 00000531 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8e782c5c 91e5e065 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
8e782c98 91e3a8f0 8e782c90 82c38ebf 85568008 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
8e782d28 91e5f3c9 85568008 82c38ebf 85568008 dxgmms1!VidSchiScheduleCommandToRun+0xaa
8e782d3c 91e5f485 85568008 00000000 868c6948 dxgmms1!VidSchiRun_PriorityTable+0xf
8e782d50 82df1d16 85568008 91979440 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8e782d90 82c93159 91e5f406 85568008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+aca80
914bca80 55              push    ebp

SYMBOL_NAME:  nvlddmkm+aca80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a0c7fdb

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner

wantuzus · 21 Feb 2012

Quote: Originally Posted by Capt.Jack Sparrow

Hello and Welcome!

Seems like the crashes are VIDEO_TDR_FAILURE 0x116 which mostly referring to Video card or driver. Follow this article STOP 0x116: VIDEO_TDR_ERROR troubleshooting .

Follow this guide and do a complete nVidia driver Cleanup nVidia Driver Cleanup Guide | Captain Debugger also run all the stress test mentioned in the above guide.

Bugcheck:

Code:

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 86afe008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 914bca80, 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:
------------------

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

FAULTING_IP: 
nvlddmkm+aca80
914bca80 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:  
8e782b74 91e02c26 00000116 86afe008 914bca80 nt!KeBugCheckEx+0x1e
8e782b98 91e03a45 914bca80 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
8e782bbc 91e3392c 00000000 00000102 85568008 dxgkrnl!TdrIsRecoveryRequired+0xb8
8e782c34 91e5d944 fffffcfb 00000531 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8e782c5c 91e5e065 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
8e782c98 91e3a8f0 8e782c90 82c38ebf 85568008 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
8e782d28 91e5f3c9 85568008 82c38ebf 85568008 dxgmms1!VidSchiScheduleCommandToRun+0xaa
8e782d3c 91e5f485 85568008 00000000 868c6948 dxgmms1!VidSchiRun_PriorityTable+0xf
8e782d50 82df1d16 85568008 91979440 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8e782d90 82c93159 91e5f406 85568008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+aca80
914bca80 55              push    ebp

SYMBOL_NAME:  nvlddmkm+aca80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a0c7fdb

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner

TQVM Dude

.

Hurray. My PC was running normal. I change the bios setting, disable PCIE Graphics Card to onboard graphics. Seem my external Graphic Card was caused the problem as you told. Is possible My Graphic card was broken since before My CPU was broken before because of lightning ? I already change 2 MOBO before this. Is there any method can fix the broken graphic card ?

wantuzus · 22 Feb 2012

Quote: Originally Posted by zigzag3143

Quote:

"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

Thank you bro

zigzag3143 · 22 Feb 2012

Quote: Originally Posted by wantuzus

Quote: Originally Posted by zigzag3143

Quote:

"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

Thank you bro

My pleasure, let us know if we can help.