BSOD and Black Screen Issue

[Meteorology]

Hello,

I have been having an issue with random blue screens. I recently updated my chipset drivers and graphics drivers. I haven't had any blue screens since then (granted it's only been a couple days since), but still.

I am running Windows 7 64-bit.

However, today and yesterday I've had a problem with my monitor suddenly going black, and my computer crashing basically. Yesterday it did it and a weird "ERRRRRRRRRRRRR" sound came out of my speakers also. It did the same thing today, only without the sound. It's done it twice today. It did give me an error message on the desktop after I rebooted after one of the crashes today, it says the "Problem Event Name" was a BlueScreen, however there was no blue screen.... the monitor went black, then I had to manually turn my computer off:

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

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA80053064E0
BCP2: FFFFF8800F819970
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\052011-18876-01.dmp
C:\Users\JP Fowler\AppData\Local\Temp\WER-32042-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I have also attached my minidump folder.

Thank you for your time

 

[zigzag3143]

Hello,

I have been having an issue with random blue screens. I recently updated my chipset drivers and graphics drivers. I haven't had any blue screens since then (granted it's only been a couple days since), but still.

I am running Windows 7 64-bit.

However, today and yesterday I've had a problem with my monitor suddenly going black, and my computer crashing basically. Yesterday it did it and a weird "ERRRRRRRRRRRRR" sound came out of my speakers also. It did the same thing today, only without the sound. It's done it twice today. It did give me an error message on the desktop after I rebooted after one of the crashes today, it says the "Problem Event Name" was a BlueScreen, however there was no blue screen.... the monitor went black, then I had to manually turn my computer off:

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

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA80053064E0
BCP2: FFFFF8800F819970
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\052011-18876-01.dmp
C:\Users\JP Fowler\AppData\Local\Temp\WER-32042-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I have also attached my minidump folder.

Thank you for your time

Half of these point to your video drivers the other half to Avast.


I would remove Avast and replace with Microsoft Security essentials

http://files.avast.com/files/eng/aswclear5.exe

http://www.microsoft.com/security_essentials/


I would also then re-install the video driver using this just to be sure

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

Or Phyxion.net - 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\Minidump\052011-18876-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.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`0361d000 PsLoadedModuleList = 0xfffff800`03862650
Debug session time: Fri May 20 19:09:37.095 2011 (GMT-4)
System Uptime: 0 days 0:23:47.141
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80053064e0, fffff8800f819970, ffffffffc000009a, 4}

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+7e4970 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80053064e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f819970, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+7e4970
fffff880`0f819970 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`037fbb88 fffff880`0fd39000 : 00000000`00000116 fffffa80`053064e0 fffff880`0f819970 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`037fbb90 fffff880`0fd0c867 : fffff880`0f819970 fffffa80`073c8000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`037fbbd0 fffff880`0fd38e0f : fffffa80`ffffd84d 00000000`00000000 fffffa80`053064e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`037fbc80 fffff880`01462ec1 : fffffa80`04fc2730 00000000`00000080 00000000`00000000 fffffa80`072b1410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`037fbd00 fffff800`0393932e : 00000000`0341ddfb fffffa80`06decb60 fffffa80`04879890 fffffa80`06decb60 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`037fbd40 fffff800`0368e666 : fffff800`0380fe80 fffffa80`06decb60 fffff800`0381dcc0 fffff880`01219384 : nt!PspSystemThreadStartup+0x5a
fffff880`037fbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+7e4970
fffff880`0f819970 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+7e4970

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9e7f64

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

 

[Meteorology]

OK - I did all of that. However, when I was uninstalling all my NVIDIA drivers, prior to running the driver-sweeper and installing the new ones, I removed the NVIDIA Chipset drivers. When I downloaded the latest driver software from the NVIDIA website, the chipset drivers were never reinstalled with that package. My computer is running fine, and the graphics are fine also.

Does it intentionally not install the chipset drivers in the graphics driver package? Do I need to get the chipset drivers from somewhere else? (I couldn't find an NVIDIA chipset driver package anywhere). They may have installed, but there is no NVIDIA chipset driver uninstall option in Add/Remove Programs anymore.

 

[Meteorology]

After doing all that, I got another blue screen today. And yesterday the black screen issue happened.

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

Additional information about the problem:
BCCode: 24
BCP1: 00000000001904FB
BCP2: FFFFF88003362388
BCP3: FFFFF88003361BE0
BCP4: FFFFF880012C6694
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\052211-20280-01.dmp
C:\Users\JP Fowler\AppData\Local\Temp\WER-25864-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I've attached my new minidump folder.

 

[zigzag3143]

After doing all that, I got another blue screen today. And yesterday the black screen issue happened.

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

Additional information about the problem:
BCCode: 24
BCP1: 00000000001904FB
BCP2: FFFFF88003362388
BCP3: FFFFF88003361BE0
BCP4: FFFFF880012C6694
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\052211-20280-01.dmp
C:\Users\JP Fowler\AppData\Local\Temp\WER-25864-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I've attached my new minidump folder.

Still the majority of these point to your video subsystem.


"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

 

[Meteorology]

That's definitely a possibility. I own a gaming community (and thus of course I play a lot of online games). When I play Battlefield: Bad Company 2, my GPU temperature sometimes reaches 110°C. Yes, Celsius.