WinXP Pro Freezes during drive to drive copy process

[MrJustice]

Brand new custom build:

If I copy large files from a hard disk to any other device (another hard disk, USB drive, fire wire drive) my system will freeze at some point of the copy.
After a reboot I get the report that the "System has recovered from a serious error"
Here are the codes:

BCCode : 9c BCP1 : 00000004 BCP2 : 8054D5F0 BCP3 : B2000000
BCP4 : 00070F0F OSVer : 5_1_2600 SP : 2_0 Product : 256_1

I have also attached the mini dump (no idea how to read it)

Specs:
Abit AN8
Athlon 64 X2 4400
2GB Kingston DDR400
ATI All In Wonder X1300
300GB Maxtor IDE (Master)
Liteon DL DVD+R (Slave)
120 GB Maxtor IDE (Master-system drive)
120 GB WD USB 2.0 external drive
This is any large file x-fer between any drive type (4GB or more)

 

[howard_hopkinso]

Hello and welcome to Techspot.

Your minidump crashes with a bugcheck of 9C.

You have a hardware problem of some kind.

0x0000009C: MACHINE_CHECK_EXCEPTION

This is a hardware issue: an unrecoverable hardware error has occurred. The parameters have different meanings depending on what type of CPU you have but, while diagnostic, rarely lead to a clear solution. Most commonly it results from overheating, from failed hardware (RAM, CPU, hardware bus, power supply, etc.), or from pushing hardware beyond its capabilities (e.g., overclocking a CPU).

FOLLOWUP_IP:
nt!KdPitchDebugger+ef4
8054d5f0 0100 add [eax],eax

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KdPitchDebugger+ef4

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1e

FAILURE_BUCKET_ID: 0x9C_IA32_AuthenticAMD_nt!KdPitchDebugger+ef4

BUCKET_ID: 0x9C_IA32_AuthenticAMD_nt!KdPitchDebugger+ef4

Followup: MachineOwner

Regards Howard :wave: :wave:

 

[MrJustice]

Hello and welcome to Techspot.

Your minidump crashes with a bugcheck of 9C.

You have a hardware problem of some kind.

0x0000009C: MACHINE_CHECK_EXCEPTION

This is a hardware issue: an unrecoverable hardware error has occurred. The parameters have different meanings depending on what type of CPU you have but, while diagnostic, rarely lead to a clear solution. Most commonly it results from overheating, from failed hardware (RAM, CPU, hardware bus, power supply, etc.), or from pushing hardware beyond its capabilities (e.g., overclocking a CPU).

FOLLOWUP_IP:
nt!KdPitchDebugger+ef4
8054d5f0 0100 add [eax],eax

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KdPitchDebugger+ef4

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1e

FAILURE_BUCKET_ID: 0x9C_IA32_AuthenticAMD_nt!KdPitchDebugger+ef4

BUCKET_ID: 0x9C_IA32_AuthenticAMD_nt!KdPitchDebugger+ef4

Followup: MachineOwner

Regards Howard :wave: :wave:

Ok. First step is is RAM I suppose..I downloaded Memtest and I removed 1 stick of RAM and I am running the first test on it right now. Does memtest give me some type of report when it is done?

 

[howard_hopkinso]

Memtest will run untill you tell it to stop.

I recommend at least 7 full passes.

If you haven`t seen any errors by then, chances are you won`t get any.

Please be aware that some faulty ram can pass Memtest.

Regards Howard

 

[MrJustice]

Memtest will run untill you tell it to stop.

I recommend at least 7 full passes.

If you haven`t seen any errors by then, chances are you won`t get any.

Please be aware that some faulty ram can pass Memtest.

Regards Howard

Great, thanks for the fast replies. It ran 10 passes on the first stick, no errors. On to the second stick by its self and guess what..the system wont even boot! Cannot post, just sits there. So I went back to the error free stick, leaving out the potential "bad stick" and booted back into windows and have started my large file x-fer again. I will report with my findings. 21 min to go on the copy.

 

[MrJustice]

Well, things have taken a turn for the worse. Went down to one stick of Ram (1GB) and attempted the file x-fer again. MAde it to 38.8 of the 39GB and it froze. Tried to reboot and my bios splash screen looks like this:


It just sits there and does nothing :blackeye:

I think the board is bad...