Is your motherboard BIOS up to date, and are the drivers for your UDMA controller up to date?

Yes and Yes.
 
I am convinced it is a new hard drive problem. So new hard drives have teething problems. I guess it makes sense.

There seems to be a known issue using HPT-366 controller and UDMA-100 harddisk. That is at least for sure an issue using IBM DTLA series, but I haven't tried with other brands. It seems you are having the same problems as I had.

It's true, there is a problem with htp366 and udma100 HD's. I had the same prob with my maxtor but highpoint has fixed this issue in their 1.28 beta drivers. You should try em, there is a fix for the ibm's too. I've been using these drivers for 1 week now and no errors yet.

Rgodart, where can I get these beta drivers?
 
And my board comes with a hpt 370 controller on board not the 366. It is strange because the manual says it is a 366.

Woops.
 
Tiny Wiz, welcome to the NT forums I noticed you are new
 
And thanks for the reply also. I now need to find these drivers.
 
- Card

You can get the drivers on abit's ftp:
 
ftp://ftp.abit.com.tw/pub/beta/
 
You're right, rev 1.2 comes with hpt370 chip (man i wish i had that one instead of my rev 1.0 )

You went to try run your system at stock clock

Well, I can't try the new drivers yet as I've returned the drive. Maby the next time I need abigger hd .
While we are at the HPT controller I might as well ask if anyone has had the same expireance in Win2k pro.
 
Everything is working great except at shutdown.
When I choose "shut down" or "restart" windows closes down and saves ( I forgot what it actually says nevermind ), and when the reboot or shutdown is to take place it turns off my HD for aprox. 2 seconds and starts it upp again. This takes place about 3 times and then it goes to reboot or shutdown.
 
I have tried diffrent drivers and bios revisions.
It only happens in win2k ( have not tried win2k server ).
 
(Pardon my english. It is not my native language.)
 
Any help to this problem would be very apreciated

Tiny Wiz.
 
I had the exact same problem with my last drive right before it died.
I did a scan disk, found no bad sectors it just happened repeatedly. Eventually the hard drive would not boot up at all.
 
Good luck.
 
 
- Card.

I had similar problems with that error on my VP6. Although i was getting every BSOD under the sun, that one was very popular. I traced it down to using crappy ram. Once i got rid of the generic stuff and bought some nice crucial memory the bsod's havnt returned. I see you are overclocking. Try lowering your memory timings (go to cas3 if you are at cas2). I know win2k caches everything thru ram and is very picky when something comes out corupted, it could be possible that this new drive can read data faster than the older one and the memory cant quite keep up.
 
Good luck,
Ultrix

Thank you Ultrix.
 
 
Excellent advice. To answer SHS I had tried it at the default clock speed and still experienced it. But silly me did have the CAS set at 2. I'll adjust it and see what happens.
 
Thanks guys for all the responses.
 
Regards,
 
Card