Frquesnt BSOD agrivating customer

[customcomputers]

So, we have an impatient customer who is very tired of this screen-
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8008397028
BCP3: 00000000BC800800
BCP4: 0000000000010137
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\011812-28282-01.dmp
C:\Users\User\AppData\Local\Temp\WER-42198-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


Before we spend many hours trying to troubleshoot this, does anyone have an idea for a quick-fix?

 

[zigzag3143]

So, we have an impatient customer who is very tired of this screen-
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8008397028
BCP3: 00000000BC800800
BCP4: 0000000000010137
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\011812-28282-01.dmp
C:\Users\User\AppData\Local\Temp\WER-42198-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


Before we spend many hours trying to troubleshoot this, does anyone have an idea for a quick-fix?

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress

Some generic advice.

If you are overclocking STOP. Return to the default settings at least for now.
If you are running a RAID update its driver.


You can read more on this error and what to try here... http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[customcomputers]

Cleared the CMOS on first sign of problem and there is no raid.

 

[customcomputers]

thanks for your time anyways-looks like the problem will require the hours...

 

[zigzag3143]

thanks for your time anyways-looks like the problem will require the hours...

Hardware usually does. let us know if we can help

Ken