Random BSOD **Please Help**

This is a new system that I built and I can't get this figured out. I have updated all the drivers and DL all the updates to my OS. I have tested and replaced the ram just to be sure and it is still occurring. I have attached several of my minidumps to this post.

Mainboard : Gigabyte GA-MA78GM-US2H
Chipset : AMD 780
Processor : AMD Phenom 7750 @ 1350 MHz
Physical Memory : 4096 MB (2 x 2048 DDR2-SDRAM )
Video Card : NVIDIA GeForce 8800 GT
Hard Disk : WDC Raptors 75 Gig Running Raid AMD (148 GB)
Hard Disk : WDC (1000 GB)
DVD-Rom Drive : NEC DVD_RW ND-3520A ATA Device
DVD-Rom Drive : ASUS DVD-E616P2 ATA Device
DVD-Rom Drive : UHIP A3K1UZ0HE SCSI CdRom Device
Network Card : Realtek Semiconductor RTL8168/8111 PCI-E Gigabit Ethernet NIC
Operating System : Windows (TM) Vista Ultimate 64 bit Professional 6.00.6001 Service Pack 1
DirectX : Version 10.00

Thank in advance for any help!!

Hi -

The most recent dump w/ timestamp = Thu May 7 13:50:37.045 2009 (GMT-7)
System up-time = 0 days 0:26:30.798

bugcheck = 0x124 (0x0, 0xa800672f030, 0xb4442000, 0x135)

0x124 = WHEA_UNCORRECTABLE_ERROR - a fatal hardware error occurred. WHEA = Windows Hardware Error Architecture

1st parm = 0x0 = machine check exception

The dumps show May 2 - 7. Are there any that fall outside this date range?

I have some more recent ones but they are at home I can load them up tonight if it helps.

Here is MSDN page on 0x124 -
Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR

I think ESET updated eamon.sys since early Feb 2009. Check ESET for program updates.

ESET
eamon.sys Fri Feb 06 05:14:25 2009 (498C37B1)

Can you boot & run OK in safemode - any BSODs there?

Safemode would give us more of an indication of software v. hardware at fault here.

These 2 drivers stood out in the dump -

GVTDrv64.sys Tue Sep 05 00:10:02 2006 (44FD22CA) - GIGABIT
AtiPcie.sys Mon Nov 06 08:59:54 2006 (454F6A0A)

Vista SP1 is 2008 >

I will try it tonight and see what happens...will it still create minidumps if it crashes in safe mode?

Yes, it should.

These are the most recent dumps....I'm currently using it in safe mode waiting to see if it crashes on me.

No crashes in safe mode as of yet....

I still have not had any crashes in safe mode....does this point that more then likely it is a driver issue?

ronin72 said:

I still have not had any crashes in safe mode....does this point that more then likely it is a driver issue?

Click to expand...

No. 0x124 is a hardware-triggered error.

By running in safe mode you may be avoiding whatever the hardware is complaining about in normal mode, but that doesn't necessarily make it a driver issue.

As a suggestion, have a look at this:

http://www.vistax64.com/general-discussion/224976-please-help-bsod-stop-0x00000124.html#post1036629

Thanks I read it and thanks for taking the time to reply.

So at this point since i have updated all my drivers should I start removing pieces of hardware and see what could be causing the error??

ronin72 said:

Thanks I read it and thanks for taking the time to reply.

So at this point since i have updated all my drivers should I start removing pieces of hardware and see what could be causing the error??

Click to expand...

You could first try interpreting the information in the 3rd and 4th bugcheck parameters (as per that other post I linked to). Between them, they constitute the MCi_Status register - a 64-bit bitmask - and that's the actual error message from the hardware. Sometimes, it's relatively straightforward.

the only problem with this is that I can't seem to get microsoft debugginh tools for windows to work....it will never load the correct symbols.

That is the main reason I posted on here.

I also attached the mini dump from this morning....I apologize if I seem like a moron, but this is something pretty new to me I have never had this many issues with a new build.

I went and downloaded MCAT installed it and not sure how to run it now....it said it installed, but I can't find instructions on now to run the program??

The latest dump bugcheck - 0x124 - WHEA

Debug session time: Sun May 17 08:20:28.303 2009 (GMT-7)
System Uptime: 0 days 9:15:07.979

There are a few drivers that you should look into/ update -

Ok...I will try and update those drivers when I get home tonight...but I though from what H2SO4 was saying that this had to be a hardware issue and not drivers? I'm not trying to start a flame war here but I just don't want any of you experts wasting your time with me if it's something else.

ronin72 said:

Ok...I will try and update those drivers when I get home tonight...but I though from what H2SO4 was saying that this had to be a hardware issue and not drivers? I'm not trying to start a flame war here but I just don't want any of you experts wasting your time with me if it's something else.

Click to expand...

There's no flame war at all. JCGriff and I are good friends

We can't directly tell what's causing your 0x124 (MCE) events. That would require physical access to the machine and quite possibly hardware troubleshooting toys as well. If the hardware is no longer under warranty, and you're stuck with having to troubleshoot it yourself, then there's no particular "absolutely prescribed" way to go about it. The "complainer", for lack of a better term, is the hardware, and that message is being passed on by the OS in the form of a STOP 0x124, but it is theoretically possible that updating a driver will keep the relevant hardware out of the zone where it feels the need to complain. I mentioned updating drivers in that write-up I did in the other post, and I agree 120% with what JCGriff is suggesting you do.

You should also check the MCi_STATUS register contents. Unfortunately, you don't need the debugging tools because there's nothing to debug in this instance and JCGriff has already dug out the numbers for you in this post:

http://www.vistax64.com/general-discussion/227040-random-bsod-please-help.html#post1042622

Here they are again:

bugcheck = 0x124 (0x0, 0xa800672f030, 0xb4442000, 0x135)

I've highlighted parameters 3 and 4 which between them make up the contents of the MCi_STATUS register. If you concatenate them together, this is the resultant binary bitmask:

1011010001000100001000000000000000000000000000000000000100110101
3210987654321098765432109876543210987654321098765432109876543210
___6_________5_________4_________3_________2_________1

And this is what that number is trying to say to you:

63: VAL - MCi_STATUS register valid
61: UC - Error uncorrected
60: EN - Error enabled
58: MCi_ADDR register valid (58)
54:53: Yellow - Status tracking is provided for the structure posting the event; the current status is yellow (above threshold).

There are a few other bits in there but I think 54&53 are sufficient to understand the nature of the complaint. This is what the Intel docs have to say about the "yellow" cache status:

"A processor that supports enhanced cache error reporting contains hardware
that tracks the operating status of certain caches and provides an indicator
of their “health”. The hardware reports a “green” status when the number of lines that incur repeated corrections is at or below a pre-defined threshold, and a “yellow” status when the number of affected lines exceeds the threshold. Yellow status means that the cache reporting the event is operating correctly, but you should schedule the system for servicing within a few weeks."

It sounds to me like your processor or memory are malfunctioning, or at least that's the error contained in the MCE message delivered by the hardware.

Yeah, almost all the hardware(CPU, RAM, MB) is still under warranty less then 60+ days old and the video card while about a year old was working in fine in my old system.

I have tested the ram and I also replaced both sticks with other ram that I bought from a local store and it still gave me the same BSOD issues, so I don't think it's the ram.

That only leaves the CPU and MB.

I will try and updating the Drivers JCGriff mentioned and see how that goes if all fails I will RMA the board first since I think that is the most likely culprit, I would just like to confirm it before hand.