Seemingly Random BSOD or Black Screen + Windows Failed Update

[Arkileo]

Sometimes I can run for up to around 6 hours without any of these happening, but when it does happen there are sure to be more to follow. Computer restarts offer a temporary fix. Audio always continues to play uninterrupted throughout any of these (Excluding BSOD, of course.)

Ranked in order of frequency (Most common at top):
-Random screen freeze (Usually while browsing the internet, never seems to happen in games.) When it unfreezes my cursor takes the shape of what it should when I hover over something, but it won't change back (Ex. Changes to the I symbol when it goes over the address bar, but keeps the shape no matter where I put the cursor.)
-Screen goes black and the "DVI NO SIGNAL" message appears on the screen, computer sounds to be running normally. It usually returns to normal after a few minutes, when I have the patience to wait. This happened once while I was away from the computer, so it wasn't triggered by an action of mine.
-Screen goes completely black, no messages, and it restarts. OR I get a BSOD. I was thinking that maybe the black screen is actually a BSOD that fails to show me the actual blue screen. They both create dump files.

In addition to these things, the Windows Update "Windows 7 Service Pack 1 for x64-based Systems (KB976932)" Has been failing to install since about 2 months before the crashing started. The error code is 80073712. All other updates install successfully, I was considering the possibility that these two problems are related somehow.

Thanks for reading and for any help that could be offered.
Dump Files below.

 

[koolkat77]

I would start with a Clean Reinstall - Factory OEM Windows 7 to eliminate a possible hardware issue.


From the dumps that were uploaded, it does seem like it be a hardware problem:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80074ed8f8, 0, 0}

Probably caused by : GenuineIntel

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80074ed8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031a86b0 fffff800`034cc979 : fffffa80`074ed8d0 fffffa80`06737680 00000000`00000008 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a8bd0 fffff800`033ae677 : fffffa80`074ed8d0 fffff800`034275f8 fffffa80`06737680 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a8c00 fffff800`03316c85 : fffff800`03489380 fffffa80`0764ac48 fffffa80`0764ac40 fffffa80`06737680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a8c40 fffff800`0328fb21 : fffff880`010cae00 fffff800`03316c60 fffffa80`06737680 00000538`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a8c70 fffff800`0352147a : 00000538`00000000 fffffa80`06737680 00000000`00000080 fffffa80`06723040 : nt!ExpWorkerThread+0x111
fffff880`031a8d00 fffff800`03260da6 : fffff880`02f64180 fffffa80`06737680 fffff880`02f6efc0 00000538`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a8d40 00000000`00000000 : fffff880`031a9000 fffff880`031a3000 fffff880`037a7500 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

1: kd> !errrec fffffa80074ed8f8
===============================================================================
Common Platform Error Record @ fffffa80074ed8f8
-------------------------------------------------------------------------------
Record Id     : 01ce7cb27efd3f45
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/9/2013 14:42:31 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80074ed978
Section       @ fffffa80074eda50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x000000000001067a
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80074ed9c0
Section       @ fffffa80074edb10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 7a 06 01 00 00 08 04 00 - bd e3 08 0c ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa80074edb10

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80074eda08
Section       @ fffffa80074edb90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xf200004000000800

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try

 

[Arkileo]

A Clean reinstall didn't work, still getting crashes just as frequently. Am I right in assuming that the piece of hardware causing this is my CPU? Judging by "GenuineIntel" and how often it says processor. If so, I might just buy a new one.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 124[/COLOR], {[COLOR="Blue"]0[/COLOR], [COLOR="SeaGreen"]fffffa80074ed8f8[/COLOR], 0, 0}

Probably caused by : GenuineIntel

1: kd> [COLOR="SeaGreen"]!errrec fffffa80074ed8f8[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa80074ed8f8
-------------------------------------------------------------------------------
Record Id     : 01ce7cb27efd3f45
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/9/2013 14:42:31 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80074ed978
Section       @ fffffa80074eda50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x000000000001067a
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80074ed9c0
Section       @ fffffa80074edb10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 7a 06 01 00 00 08 04 00 - bd e3 08 0c ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa80074edb10

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80074eda08
Section       @ fffffa80074edb90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR="Red"]BUSL0_SRC_ERR_M_NOTIMEOUT_ERR[/COLOR] (Proc 0 Bank 0)
  Status      : 0xf200004000000800

The first parameter or argument has the value of 0x0, which is a Machine Check Exception, which means the CPU has detected a hardware problem and the address points to a processor error because the CPU has found one, so it could be a different form of hardware which is causing the issue.

As a result, of the the black screens, then firstly I would stress testing the graphics card for any problems:

• http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

 

[Arkileo]

What exactly should I be looking for? It runs pretty smoothly, getting up to around 93 degrees and leveling off, other than that nothing really happens.

 

[x BlueRobot]

Did you notice any artifacts or weird distortions? How long did you run the test for, and how long did it take for the temperature to reach 93*C?

 

[Arkileo]

I ran it for about 45 minutes this time without seeing any distortions or artifacts or anything out of the ordinary.
It hit 90°C at about 2 minutes (starting at 48°C) and increased very slowly, jumping and falling everywhere in the low 90s. At about 30 minutes it started jumping around anywhere between and including 93°C to 96°C. For the next 15 minutes it stayed pretty much the same.

I also thought it might be worth mentioning that the small clip at the end of the PCIe x16 slot is broken off, so the GPU is hanging sideways in its slot without anything but the actual connectors holding it there, so the card isn't completely perpendicular to the motherboard as a result. It dips a little bit. One card or another has been in there the same way without any problems for the past 3 years, however.
TL;DR: is it possible that my problem is caused by a bad connection? Maybe the connection has deteriorated over time?

 

[x BlueRobot]

The temperature rose very fast for such a short period of time, I would check for any overheating issues as well, open the case and then clean the fans and heatsinks with a can of compressed air.

I would definitely check the connection, have you tried placing the card in a different PCIe slot?

 

[Arkileo]

I sprayed everything, and the temperature holds at about 88°C, but it still hit that mark after about 2 minutes.
Unfortunately my motherboard only has one PCIe slot.
I also propped the GPU up with a coin, so hopefully it's closer to the way it's supposed to be plugged in.

Also, my screen froze earlier and I decided to try running furmark immediately after. The framerate was 4 instead of the usual 10 or 11, the temperature held at about 72°C, but what was most odd was that the GPU load was at 1%, instead of the usual 99%.

 

[x BlueRobot]

Strange, and does your motherboard or CPU have a onboard graphics card to switch to?

 

[Arkileo]

It does, or did. My monitor wasn't getting signal from it when I hooked it up a minute ago.

 

[x BlueRobot]

Do you know if it's part of the motherboard or the CPU?

 

[Arkileo]

Didn't know they could be part of the CPU. But the CPU is Intel, and the built-in graphics are Nvidia, so I'd think it would be part of the motherboard.

 

[x BlueRobot]

It'll be part of the motherboard, I asked because since the onboard graphics card doesn't seem to be working and the PCIe slot is partially broken, then the motherboard could be at fault here.

 

[Arkileo]

Is there a motherboard diagnostic tool I could run or something?

 

[x BlueRobot]

There's not unfortunately, but when you attempted to use the onboard graphics card, did you make sure it was enabled in the BIOS? Did you remove the PCIe card?

 

[Arkileo]

My bad, didn't realize I couldn't have my other card plugged in. Figured it wouldn't matter as long as it wasn't connected to the monitor.
I'll run it for awhile with the built-in to see what happens. But sometimes it can take a few hours before the problems start to appear.

Also, I've recently had a few occurrences where the drivers for my card GPU crashed and then recovered immediately after. These are the newest drivers, though. I updated to the current version after windows started crashing.

 

[x BlueRobot]

The driver crashing, can be a result of the card too, and post back if you have any problems.