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: Self-built gaming PC having BSODs and freezes; can't pinpoint cause.

30 Mar 2013   #21
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.

My System SpecsSystem Spec
31 Mar 2013   #22

Windows 7 Home Premium 64 bit

It's been 24+ hours, and still no crashes with Verifier running.
My System SpecsSystem Spec
31 Mar 2013   #23
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:Find your hard-drive manufacturer and run their tests.

Additional Tests:Post a screenshot of Crystal Disk Info summary:
Quote   Quote: Originally Posted by writhziden
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:Use this command with Disk Check:

chkdsk C: /f /r
My System SpecsSystem Spec

01 Apr 2013   #24

Windows 7 Home Premium 64 bit

So far I've done chkdsk, but I'm not sure if/where it created a log file?
My System SpecsSystem Spec
01 Apr 2013   #25

Windows 7 Home Premium 64 bit

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:

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





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



MODULE_NAME: hardware

IMAGE_NAME: hardware



BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner


WhoCrashed showed:

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: hal.dll (hal!HalBugCheckSystem+0x1E3)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008004028, 0xBE000000, 0x800400)
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.
My System SpecsSystem Spec
01 Apr 2013   #26

Windows 7 Home Premium 64 bit

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.
My System SpecsSystem Spec
01 Apr 2013   #27
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:Enable "Round off checking" before the test (see first post below tutorial).All the hardware seeming to be running stable and tests reporting no errors, could mean a bad motherboard.

Note   Note
Remember to finish the hard-drive tests.
My System SpecsSystem Spec
01 Apr 2013   #28

Windows 7 Home Premium 64 bit

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:

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

Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.1.7601.
Locale ID: 1033

Files that help describe the problem

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
BCP2: FFFFF88004C1C2B0
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
My System SpecsSystem Spec
01 Apr 2013   #29
x BlueRobot


Stop 0x124 is almost always a hardware related error, and it may be better to test your graphics card instead first:You can use a program such as CoreTemp or CPUID HWMonitor to monitor your temperatures.
My System SpecsSystem Spec
01 Apr 2013   #30

Windows 7 Home Premium 64 bit

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.
My System SpecsSystem Spec

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

Thread Tools

Similar help and support threads
Thread Forum
Various BSODs and freezes on a newly built Windows 7 PC - 99% hardware
I got various BSODs and freezes on a newly built Windows 7 machine. The problems started immediately before installing windows. I got the first freeze the first time I entered UEFI BIOS. After that I flashed the latest BIOS, after which I managed to install Windows 7. Once I did, I started to get...
BSOD Help and Support
Windows 7 x64 freezes randomly and I can't pinpoint the reason
Hi all. I built this new PC a week ago and it's giving me problems all this time :( It's running perfectly and fast until it suddenly and out of nowhere it freezes up. It doesn't matter what I'm doing or how long the computer has been up, it can happen one minute in or 30 hours in, no matter...
General Discussion
BSODs on a relatively new Custom Built Gaming PC
Computer was built around mid August this year, started crashing around mid-september for seemingly no reason. It's crashed around 7-10 times by now, the most recent one being today while playing Guild Wars 2. Every time it's crashed has been while a game was running except for one time when it...
BSOD Help and Support
Random BSODs cant pinpoint why...
So i bought a new rig and now i am having random bsods - which can occur no matter how loaded my pc is at the moment. I have stress tested gpu and cpu - but everything was ok there no bsods what so ever. Then i memtested ram for 10 hours straight - i got 11 passes and 0 errors. I tried driver...
BSOD Help and Support
I cannot pinpoint the source of my BSODs
Edit: I'm updating my original post with tests I have already done and stuff that has happened. Here is the list. I have had lots of more blue screens, It seems they have become more frequent.... I driver swept my display driver and installed a fresh up to date install I ran memtest for 5...
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 20:39.
Twitter Facebook Google+