Self-built gaming PC having BSODs and freezes; can't pinpoint cause.

[x BlueRobot]

Driver Verifier will be mostly causing the freezes, since it 'stressing' the drivers, in order to hopefully pinpoint a faulty driver which needs to be either updated or removed. Driver Verifier will produce a BSOD if a driver is found.

You may stop Driver Verifier after 24 hours, and try to keep the computer on as long as possible, if you need to shut down then try and shut down in Windows.

 

[Dem0nGam3r]

It's been 24+ hours, and still no crashes with Verifier running.

 

[x BlueRobot]

Disable Driver Verifier for now, there doesn't seem to be any driver related issues, as of yet.

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

 

[Dem0nGam3r]

So far I've done chkdsk, but I'm not sure if/where it created a log file?

 

[Dem0nGam3r]

I just got a blue screen a few minutes ago, and it's an error I've never seen before until this crash. I've attached the file itself and posted the info about the crash from WhoCrashed and WinDbg below. What do y'all make of it?

-------------------------------------------------------------------------------------------------------

WinDbg showed:

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: fffffa8008004028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

STACK_TEXT:
fffff800`00ba8a98 fffff800`0302aa3b : 00000000`00000124 00000000`00000000 fffffa80`08004028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`031ed633 : 00000000`00000001 fffffa80`07852490 00000000`00000000 fffffa80`078524e0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`0302a700 : 00000000`00000728 fffffa80`07852490 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`0302a052 : fffffa80`07852490 fffff800`00ba8e70 fffffa80`07852490 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`03029f0d : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`0301de88 : fffff880`0ae6e880 00000000`00f71a51 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`030d552c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`030d5393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 fffff880`059231e6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00b9c9b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USBPORT!USBPORTSVC_LogEntry+0xa


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

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

---------------------------------------------------------------------------------------------------

WhoCrashed showed:

[FONT=Segoe UI, Arial]On Mon 4/1/2013 6:44:32 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]hal.dll[/FONT] (hal!HalBugCheckSystem+0x1E3)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008004028, 0xBE000000, 0x800400)
Error: [FONT=Segoe UI, Arial]WHEA_UNCORRECTABLE_ERROR[/FONT]
file path: C:\Windows\system32\hal.dll
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
------------------------------------------------------------------------------------------------------------------------------------------------
[/FONT]

 

[Dem0nGam3r]

I got ANOTHER crash just now, where the computer randomly restarted; no freeze, no BSOD. Seriously, I can't get a grip on what in the world is going on. Does ANYONE have ANY idea about what this can be? Any general highly probable cause? To me it's looking like CPU or MOBO at this point, more likely MOBO, but I don't really know.

 

[x BlueRobot]

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.

In such a situation, it is best to use these steps:

• http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

Enable "Round off checking" before the test (see first post below tutorial).

• 
  http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

All the hardware seeming to be running stable and tests reporting no errors, could mean a bad motherboard.

   Note

Remember to finish the hard-drive tests.

 

[Dem0nGam3r]

Thanks, will do. I was about to use Prime95 before but it sounded like it may be risky, seeing how it pushes the components to their max. But if it's safe and won't cause further damage, I'll try it.

I'd like to quickly mention (in the hopes it could somehow be relevant to the other crashes) that every time I play a certain game (Arma II, mostly happens on multi-player), my screen goes black, the game crashes to my desktop and I can't maximize it but when I attempt to I can hear the sounds from the game and the program still works, but the visuals won't come back and I can only hear myself play from the desktop screen. After these crashes (it happens the same way every time I try to play the game), the reliability center logs the crash as "video hardware error" and under the report it says:

Description:
A problem with your video hardware caused Windows to stop working correctly.

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

Files that help describe the problem
WD-20130327-2058.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: 117
BCP1: FFFFFA800BA5A360
BCP2: FFFFF88004C1C2B0
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

 

[x BlueRobot]

Stop 0x124 is almost always a hardware related error, and it may be better to test your graphics card instead first:

• http://www.sevenforums.com/tutorials/160729-nvidia-amd-video-card-test-occt.html

You can use a program such as CoreTemp or CPUID HWMonitor to monitor your temperatures.

 

[Dem0nGam3r]

Um, sorry to ask but what should I configure the settings to be on OCCT? The how-to is a little vague and just says "your desired settings". I need to know what to set the resolution and shader complexity to, and whether to tick "fullscreen" or "error check". I'm assuming 1920x1080 @ 60Hz for resolution and maybe 8 for shader complexity with both other options ticked all running for an hour? I just want to be sure I don't fry my card or something, (even though I doubt that's possible, the PSU tab basically self-declares itself as highly dangerous and I just want to be sure everything is safe) but don't want to make the test too tame, either.

I'll be using HWMonitor and GPU-Z to monitor the heat levels.

 

[x BlueRobot]

Do the GPU Stress Test (GPU:OCCT), and then set the Shader Complexity to 3 as shown in the tutorial to be safe, set the resolution to your current screen resolution, and then enable Error Check to allow the program to log any errors. Run the test for 1 hour.

The passes is for the GPU Memory Test if your graphics card supports this option and is a separate test.

 

[Dem0nGam3r]

I started the test a few minutes ago, but the card tops 80C in a matter of a couple minutes and looks like it would continue rising in temperature if I let it keep running. Either the temperature readings are off or my GPU has an overheating problem by the looks of it. I attached the results of a five minute run and a 3 minute run and it really seems like it shouldn't get that hot so quickly. What do you make of it?

I just checked the GPU fan with the PC off and I noticed the fan's quite dusty, and the frontal fan ent is very dusty as well. I still don't think that quite accounts for the rapid increase in GPU heat. I need to clean this puppy out, though. Stupid dusty-arse Texas.

 

[x BlueRobot]

You need to clean all the fans and the heatsinks, the temperature shouldn't increase so rapidly, seems to be most probably a overheating issue so far, although I'm not sure wherever the heat may have damaged your hardware as of yet.

 

[Dem0nGam3r]

If it is overheating, I would expect it to rise in heat rapidly whilst in games, which it doesn't seem to do (stays at about 60C-70C). Also, how does overheating explain the crashes when I'm idling on my desktop? Not to mention the USB error and such, as they seem unrelated to a graphics issue (although I read that crashes normally just point to the last major driver running before the crash; so maybe the USB thing is irrelevant?). I'll clean the dust out ASAP anyways, though. It's kind of rainy today so I might have to wait a day or two.

 

[x BlueRobot]

60*C to 70*C is still quite hot, and report back after you have cleaned your computer.

 

[TwoCables]

If it is overheating, I would expect it to rise in heat rapidly whilst in games, which it doesn't seem to do (stays at about 60C-70C). Also, how does overheating explain the crashes when I'm idling on my desktop? Not to mention the USB error and such, as they seem unrelated to a graphics issue (although I read that crashes normally just point to the last major driver running before the crash; so maybe the USB thing is irrelevant?). I'll clean the dust out ASAP anyways, though. It's kind of rainy today so I might have to wait a day or two.

60-70 for a video card like yours in video games isn't all that hot.

 

[Dem0nGam3r]

@BlueRobot Will do.

@TwoCables Yeah, I didn't think so, that's why overheating doesn't seem to fit. The only time it's ever (that I know of) gotten up to 80C is with OCCT. But hopefully once I clean out the dust it'll run a bit cooler. Currently and through most of today the card has idled in the mid 50's range, peaking during ArmaIII alpha at 76C. Running the OCCT test for the amount I did couldn't have damaged the card, could it have?

It's hard to ignore the quick rise in heat from OCCT, regardless of the game temperatures.

By the way guys, on GPU-Z I noticed that the maximum GPU power consumption was 101.5% (averaging in the 30%-40% range), is that normal? What does the power consumption tab even indicate, the power being drawn from the PSU (lordy I hope not!), or the maximum amount of power that can be utilized by the GPU? Just thought I'd ask in case it's relevant.

 

[TwoCables]

@BlueRobot Will do.

@TwoCables Yeah, I didn't think so, that's why overheating doesn't seem to fit. The only time it's ever (that I know of) gotten up to 80C is with OCCT. But hopefully once I clean out the dust it'll run a bit cooler. Currently and through most of today the card has idled in the mid 50's range, peaking during ArmaIII alpha at 76C. Running the OCCT test for the amount I did couldn't have damaged the card, could it have?

Not a chance. Overclockers run these kind of programs for 12-24 hours (some go longer) just to test the stability of their overclock!

It's hard to ignore the quick rise in heat from OCCT, regardless of the game temperatures.

Yeah, but OCCT is designed to work the GPU much harder than anything else.

By the way guys, on GPU-Z I noticed that the maximum GPU power consumption was 101.5% (averaging in the 30%-40% range), is that normal? What does the power consumption tab even indicate, the power being drawn from the PSU (lordy I hope not!), or the maximum amount of power that can be utilized by the GPU? Just thought I'd ask in case it's relevant.

I'm not sure, personally. I've never really gotten this far into GPU-Z.

 

[Dem0nGam3r]

@TwoCables Thank you for the very neat, categorical answers!

No game I play, at any time, tops 80C (most barely reach and rarely top 70). I've been playing games all day today and the max peak heat is at 77C.

Do you guys think I can rule out an overheating issue, or is that still very likely the problem? If I don't do the stress test should I still do the memory test? I personally no longer think the card is overheating; I've gotten crashes idling on the desktop before and once while playing Ace of Spades (which while playing I barely top 60C) in the past (I've also played more demanding games for hours without crashing, as well as crashed while watching online videos and loading browser tabs). I would think overheating would at least be consistent, crashing only when under high load.

I compared my graphics heat level to a friend's (he has a GTX 570) and his temperatures are equal and sometimes higher than mine in the same games, and his idle temp is 10C higher than mine most of the time (not to mention he lives in Great Britain, whilst I in TX, USA; needless to say, there's a HUGE difference in climate).

I still cling to it being a MOBO or very hard-to-pinpoint software issue. All along I've wondered if it's software, because it seems like if a hardware component was defective/damaged I would see at least some kind of hit in overall performance, but it continues to operate flawlessly...until it doesn't.

 

[TwoCables]

@TwoCables Thank you for the very neat, categorical answers!

No game I play, at any time, tops 80C (most barely reach and rarely top 70). I've been playing games all day today and the max peak heat is at 77C.

Do you guys think I can rule out an overheating issue, or is that still very likely the problem? If I don't do the stress test should I still do the memory test? I personally no longer think the card is overheating; I've gotten crashes idling on the desktop before and once while playing Ace of Spades (which while playing I barely top 60C) in the past (I've also played more demanding games for hours without crashing, as well as crashed while watching online videos and loading browser tabs). I would think overheating would at least be consistent, crashing only when under high load.

I compared my graphics heat level to a friend's (he has a GTX 570) and his temperatures are equal and sometimes higher than mine in the same games, and his idle temp is 10C higher than mine most of the time (not to mention he lives in Great Britain, whilst I in TX, USA; needless to say, there's a HUGE difference in climate).

I still cling to it being a MOBO or very hard-to-pinpoint software issue. All along I've wondered if it's software, because it seems like if a hardware component was defective/damaged I would see at least some kind of hit in overall performance, but it continues to operate flawlessly...until it doesn't.

You're welcome!

If it were overheating, then your performance would suffer. I've seen it before several times, so that's how I came to find this out.

Forgive me for the following because I was gone for a while and I couldn't follow along, but did you end up testing your memory one stick at a time in one slot at a time?