Blue screen error, cannot use brand new pc.

On the blue screen it tells me it is an uncorrectable hardware error, after restart, windows gave me the following error msg:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8010155030
BCP3: 00000000FE000000
BCP4: 000000000040014A
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini052209-01.dmp
C:\Users\Administrator\AppData\Local\Temp\WER-30843-0.sysdata.xml
C:\Users\Administrator\AppData\Local\Temp\WER8220.tmp.version.txt


This problem happens seemingly at random. During idol, during games or movies. I'd like to not have to send it back to the manufacturer after waiting a month yet having it only a few days.

Sys specs:
Win 64 Ultimate
4.0 ghz (Factory overclocked) i7 cpu
12g ram
quad sli nvidia 295's
Sound Blaster X-FI sound card.

If there is a way I can correct this issue, i'm all ears.

A stop 0x124 is indeed a hardware error report.

It's a bit like having your new car's engine develop a problem whereby it's stopping randomly while you're driving. Do you really want to be pulling out the spanners and troubleshooting yourself, possibly at the risk of voiding the warranty, or do you take it back to the dealer?

no I do not. But that's why I asked what it would take to fix this particular error. So I'd know if it was something I could do or not. But since I have no clue what a spanner is, that would be a good lead to the no.

So can you tell me what kinda hardware error it is? Faulty equipment, non compatible hardware, or something most likely just not set up right?

When I recived this pc, It wouldn't even boot. I had to mess with the bios to get it to boot. It still doesn't even reconize the raid-0 solid state disks. It does some kinda canning for disks, no disks found 2x, then boots from from the disks it couldnt find lol.

RandyBev said:

no I do not. But that's why I asked what it would take to fix this particular error. So I'd know if it was something I could do or not. But since I have no clue what a spanner is, that would be a good lead to the no.

So can you tell me what kinda hardware error it is? Faulty equipment, non compatible hardware, or something most likely just not set up right?

When I recived this pc, It wouldn't even boot. I had to mess with the bios to get it to boot. It still doesn't even reconize the raid-0 solid state disks. It does some kinda canning for disks, no disks found 2x, then boots from from the disks it couldnt find lol.

Click to expand...

A spanner is what you'd (probably) call a wrench

I wrote up some basic info about 0x124 stop errors here, and some of it may be interesting to you:

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

However, personally I would not troubleshoot a brand new machine (under warranty) that's experiencing this symptom. I'd take/send it back instead.

Well because im in Hawaii, it would take literally a month or more before I saw this system again. Therefore, I'd like to do all I can to determine the nature of the stop error before sending it back. There are many things I can do on my own, and If it saves me a month because "X" cable was loose, or a drive wasn't slaved right, I can fix these things.

I'm going to go ahead and print the stop error and take a look at that write up and see if I can figure out whats causing it before sending it back.
UNCORRECTABLE HARDWARE ERROR
*** STOP: 0x00000124
(0x0000000000000000
0xFFFFFA80109195E2
0X00000000B2000000
0X0000000080000106)

Upon further investigation, i found that under my IDE ATA/ATAPI controllers heading, i have 3 entries each for channels 1 and 0 each. one of each (a one and a zero) seem to be faulty.

This device cannot start. (Code 10)

Looking at the driver for both, it appeares to be a sys32 driver, could this be the culprit? A Win 32 driver loaded for Win 64?

Are the faulty IDE channel(s) marked with a yellow ! or a red x? If so, uninstall them by right clicking and selecting "Uninstall". Then reboot and see what happens.

Since it's gonna be a while before you send it back, you can try the "old" method of replacing all of the drivers - one by one - to see if that fixes it. I'd start with the motherboard/chipset drivers, then the video drivers, then the LAN, sound, and the rest.

System32 is where all the drivers are installed - 32 or 64 bit. Installing a 32 bit driver on a 64 bit system shouldn't be possible - but even if it was, you'd receive all sorts of warning messages before the install would finish.