Harddrive issues with Win2k

[beatle]

I just installed a WD 600AB to replace my 27 gig Maxtor as my bulk storage drive on my 1.1 tbird/kt7a-raid system. I planned to install both drives and haul all my stuff onto the new WD drive, then remove the Maxtor. I fdisked the drive as one big partition and formatted it as an NTFS partition.

After copying about 150 megs or so, I get a BSOD with the error BAD_POOL_CALLER. Trying again gives me the same error. I can copy things in small amounts, but at around 100-150 megs (such as a few mp3 albums) it would crash the machine. I also got the error KMODE_EXCEPTION_NOT_HANDLED a couple times when copying. In safe mode, I can copy fine.

Looking these up on microsoft's site doesn't yield much useful info. I'm running SP2.

I've tried knocking the interface on the drive down to ATA-33, but that didn't help. It is currently the secondary master. Primary master is an 18 gig ata66 WD. It doesn't help to switch to a diff channel. I am not using the raid portion of my motherboard at all.

The drive checked out fine with the diagnosis program on wd's site. Norton Antivirus came up dry, but locked with a BSOD in the middle of scanning the new drive (same error).

Any suggestions? I've never heard of these errors before or seen behavior like this. I'd rather not reinstall the whole OS.

 

[jmc]

I have an 18 gig WD ata/66 drive and its very noisy, clunks like crazy and I have had the same kinds of things happening (bsods) when copying. I took it off my amd based system and put it on an intel bx chipset and it works better. but is still noisy as hell. Its the last WD I will be buying for a long time. I just bought a new Maxtor 60 gig ata/100 7200 spd drive and I LOVE IT!! What the hell has happened to the WD drives. I work on a few systems in my spare time and in the past year every hard drive I have seen go bad is ALWAYS a western digital.

 

[beatle]

I don't think this is a hardware problem per se, as diagnostics came up with nothing and safe mode works fine.

 

[wyvrn]

I had this exact problem, same error. It was the VIA chipset I was using. Download at least the 4.29 drivers, and install at least Windows SP1, and you should be good to go. 99 to 1 this is the answer to your problem.

 

[beatle]

AFAIK, I'm using the 4.29 drivers. I found the 4.29 install on my comp, however, I don't know where to check to see which drivers are actually loaded. Device manger... where? I'm not seeing any familiar driver numbers when I poke through the different resources.