Crash Of Which I Don't Remember.


Well-Known Member
I was looking through my Event Viewer when i saw a BlueScreen event in it. It happened at 10:00 AM on 5/15/12 by what it says, but I don't remember this happening. There was a DMP file so I will upload. My computer has been acting funny so this my explain this whole thing.

The scary part was that this .dmp mentioned hal.dll! (i can read dmp's but not professionally)

Please Help Me With This Thing I Don't Know About Happening! (my computer has been opening stuff by itself!)

View attachment View attachment


Well-Known Member
Sorry For The Bump!


Noob Whisperer
The bad news is:
[COLOR=#ff0000][U][B]BugCheck 124[/B][/U][/COLOR], {0, 872664dc, 0, 0}
[COLOR=#ff0000][U][B]Probably caused by : hardware
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: 00000000, Machine Check Exception
[COLOR=#ff0000][U][B]Arg2: 872664dc, Address of the WHEA_ERROR_RECORD structure.[/B][/U][/COLOR]
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_AuthenticAMD
8e587cc4 832df105 872664c0 83377c28 83377c20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8e587ce4 832dff2f 83377c20 872664c0 83377c50 nt!WheapProcessWorkQueueItem+0x56
8e587d00 8327e06b 83377c20 00000000 85ba3a70 nt!WheapWorkQueueWorkerRoutine+0x1f
8e587d50 8341ead1 00000001 a582ed38 00000000 nt!ExpWorkerThread+0x10d
8e587d90 832d0209 8327df5e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
FOLLOWUP_NAME:  MachineOwner
[COLOR=#ff0000][U][B]MODULE_NAME: hardware
IMAGE_NAME:  hardware[/B][/U][/COLOR]
And the worse news is;
Common Platform Error Record @ 872664dc
Record Id     : 01cd32a30908e3c1
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 5/15/2012 14:00:19
Flags         : 0x00000002 PreviousError

Section 0     : Processor Generic
Descriptor    @ 8726655c
Section       @ 87266634
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

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

Section 1     : x86/x64 Processor Specific
Descriptor    @ 872665a4
Section       @ 872666f4
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 52 0f 10 00 00 08 04 00 - 09 20 80 00 ff fb 8b 17
                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  @ 872666f4

Section 2     : x86/x64 MCA
Descriptor    @ 872665ec
Section       @ 87266774
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

[COLOR=#ff0000][U][B]Error         : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)[/B][/U][/COLOR]
  Status      : 0xb200001000020c0f
Could be your processor (check for proper seating, thermal paste compound and cooling) or possibly your board (check for leaking or swollen capacitors and any evidence of corrosion anywhere front or back). And double check and make sure your power supply is healthy and up to the task. And or course if you are currently overclocking anything, best revert settings back to normal / standard
In any event if you are running the latest BIOS version for your board as well as the latest Chipset drivers from the MoBo manufacturer you may want to try;
Some test you might consider running to see if you can possibly zero in on anything specific.
Run sfc /scannow to verify the system files integrity.
Run Chkdsk
Run the correct Hard Drive Diagnostics Tool for your HDD.
Run Memtest86+ overnight, after your computer has been off for about an hour or two so it has a cold start. Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test.
Note!! Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Test RAM sticks individually. When you find a good one then test it in all slots. Post back with the results.
Memtest86+ 4.20 Download.
Guide to using Memtest86+
CPU - Stress Test with Prime95. Run the "Blend" and "Small FFTs" tests.
Video Card - Stress Test with Furmark.
Good luck


Well-Known Member
I did just put a new Video Card in this Christmas, and it was my first ever hardware installing i've ever done on the inside. My CPU was put in by Pro's so yeah, and my ram i am replacing this summer. Ill start backing up tonight.


Noob Whisperer
Does the installation, in any way, coincide with the occurrences of the BSODs you are now experiencing? I suppose it is possible that the new Video Card could be imposing demands on the Power Supply that is incapable of meeting.


Well-Known Member
I have only 1 BSOD at the time, and the power outage that day did something weird that morning (shut off all computers and game consoles. all clocks though remained ontime). I'm afraid to run the stress test on the grounds that it might kill my graphics card. I hope the fact that i stupidly accidently left the film on it for a month when i put it in, is fine now. (don't insult me, im a noob). Ill try some of the other Diagnostics, i already have an updated bottable copy of Memtest86. DskChk i will also run.

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.