3 hard disks CORRUPTED

[bum]

Few months back, got a 120GB seagate pata hdd. Windows played up alot. Ran seatools diagnostic. Primary drive failed. Got a new one (it was still under waranty). Repeate all that. Tested my new drive last night, failed.

Here's a diagram of the exact same seatools result I got will all 3 drives



My main issue is with each new hdd having blue screens. First they're occasional but the more I used a drive the more they pop up. NAd that aint normal on Win XP Home sp1. I'm guessing that 3 consecutive dodgy hard disks is just about impossible, so the problem has to be somewhere els. Anyone got any idea what the hell is causing my comp to screw up so badly?

[Kalium]

Make sure all your drivers are up to date. I had a similar problem once, it was due to my IDE controller drivers being out of date.

Also, be sure you have 48-bit addressing enabled in Windows, and that your current BIOS version supports it. Flashing your BIOS may be in order.

[Scintilla]

My main issue is with each new hdd having blue screens. First they're occasional but the more I used a drive the more they pop up. NAd that aint normal on Win XP Home sp1.

It is if your computer is running too hot.

I used to get blue screens all the time at The College when my computer was sitting on my desk with not much clearance behind it for airflow, running with the side panel on (before I wised up and started running it without), and I was working in Photoshop for long periods of time.
Cakewalk Professional 8 would also trigger it occasionally.

[bum]

My main issue is with each new hdd having blue screens. First they're occasional but the more I used a drive the more they pop up. NAd that aint normal on Win XP Home sp1.

It is if your computer is running too hot.

I've had my comp encode video for hours on end without a single blue screen, yet starting up, opening mpc, trillian and firefox (which togeather use very little cpu power) has sometimes caused a bsod.

[bum]

Make sure all your drivers are up to date. I had a similar problem once, it was due to my IDE controller drivers being out of date.

My board has a via chipset, so I got the latest via4in1 drivers, anything els I need?

Also, be sure you have 48-bit addressing enabled in Windows, and that your current BIOS version supports it. Flashing your BIOS may be in order.

How do I make sure I've got 48bit addressing enabled?