A7V333 + XP2400 = Lame Hard Drive?

[ranger235]

Howdy - I have an A7V333 rev 1.1 mobo that I've been running an overclocked 1900+ in for about a year. I just went out and bought a 2400+ and slapped it in the other day - everything ran fine for about the first 3 minutes, then the mouse quit working. I restarted, but it wouldn't go past the boot screen - the HDD light was flickering like once every 2 seconds, but no other activity. I tried to reinstall the system, but it took about 2 hours and then wouldn't load when it was all done. It was like the hard drive was trying to write but couldn't. It's a 40gb Maxtor drive, and I'm using bios 1015. I swapped back to the 1900 and all is fine again - is this a shot processor? Do I need to update the IDE controllers to run a 2400? I've never heard of this before - I even tried using a brand new Maxtor 40gb, but it did the same thing - anybody got any ideas? The rest of the system is 512mb of Corsair pc3200 (1 stick, middle slot), 550w Enermax psu, Sony CD burner.

[SteveW]

Originally posted by ranger235
Howdy - I have an A7V333 rev 1.1 mobo that I've been running an overclocked 1900+ in for about a year. I just went out and bought a 2400+ and slapped it in the other day - everything ran fine for about the first 3 minutes, then the mouse quit working. I restarted, but it wouldn't go past the boot screen - the HDD light was flickering like once every 2 seconds, but no other activity. I tried to reinstall the system, but it took about 2 hours and then wouldn't load when it was all done. It was like the hard drive was trying to write but couldn't. It's a 40gb Maxtor drive, and I'm using bios 1015. I swapped back to the 1900 and all is fine again - is this a shot processor? Do I need to update the IDE controllers to run a 2400? I've never heard of this before - I even tried using a brand new Maxtor 40gb, but it did the same thing - anybody got any ideas? The rest of the system is 512mb of Corsair pc3200 (1 stick, middle slot), 550w Enermax psu, Sony CD burner.

What BIOS are you running?

1016 has shown to provide the best results with T'bred processors in these boards.

** EDIT: I see you are running 1015 BIOS - you might want to give 1016 a shot.

[ranger235]

Thanks Steve - that did the trick. I found this thread (honest! I did a search first!) http://www.amdforums.com/showthread....hreadid=205620 that sounded like the same problem - I checked my DDR voltage jumpers but they were in the Asus default position already. I upgraded to bios 1016 and set the memory timings back to "optimal" and bang - runs like a deere now. I even set the memory back to "turbo" since without any instability - so it was just a bios thing?

[SteveW]

Originally posted by ranger235
Thanks Steve - that did the trick. I found this thread (honest! I did a search first!) http://www.amdforums.com/showthread....hreadid=205620 that sounded like the same problem - I checked my DDR voltage jumpers but they were in the Asus default position already. I upgraded to bios 1016 and set the memory timings back to "optimal" and bang - runs like a deere now. I even set the memory back to "turbo" since without any instability - so it was just a bios thing?

wellnowthat'sprettykickass!!!!

Glad it was so easy.

The A7V333 mobo's seem to really like BIOS 1016, especially when running T'bred's and Bartons.

Works like PFM - Pure xxxxing Magic!!!!!!

I found this out a few months back when having problems with a Plextor burner - I contacted Plextor tech support and they said I had an IDE controller/driver/BIOS problem. The only change I had made to my system since doing good CD burns was a BIOS upgrade - so I flashed it back to 1016 and it's ran fine since.

"I don't know Clark - she falls down a well and her eyes went crossed. Get's kicked in the head by a mule and they go straight again."

- Cousin Eddie

[ranger235]

Yikes! I decided to tempt fate and set the multiplier to 13 and fsb to 166 = 2158mhz!! Sandra reads it as 2166mhz - I don't know what that means, but it's been running stable at those settings with mem set to turbo for 5 hours now - now that'skickass!!! Thanks again bud - workin better than I could have hoped!

[SteveW]

Originally posted by ranger235
Yikes! I decided to tempt fate and set the multiplier to 13 and fsb to 166 = 2158mhz!! Sandra reads it as 2166mhz - I don't know what that means, but it's been running stable at those settings with mem set to turbo for 5 hours now - now that'skickass!!! Thanks again bud - workin better than I could have hoped!

333 x 13 and Turbo huh?

Bingo!!!!

That combination on the A7V333 will cost you an extra $5 please.

A7V333 + 1016 BIOS = PFM

(Take it easy will ya, yer gettin me in trouble with the moderator - we have speed limits around here)

[ranger235]

okay, okay - so I ain't going to get windburn going that fast...at least it's running! I had my doubts for a while. I'm gonna give it while and start raising it up some more. I can't see why 2.4ghz or even 2.4ghz wouldn't be possible - Bwaahahaha!