P4 1.6A - Overclocking Hell!

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

Nate420

Senior member
Feb 4, 2002
264
0
0
Actually, it was the 2.0 ports that caused the problems for me. I use a Razor Boomslang mouse, which is USB, and never had any probs with it in the 1.0 ports. My HP printer was the device I had in the 2.0 port, but I hardly ever print anything, so it's not an issue for me. I just plug it in when needed.
 

Nightstalker

Junior Member
Oct 8, 2000
11
0
0
Setting the voltage to 1.70 seems to have cured all my problems with this system. I have not been able to reproduce the audio problem since going to the higher voltage. Also the system has been running for two and a half days without a reboot. And that is after hours of RTCW, hours of C&C Renegade on-line, and hours of Serious Sam; The Second Encounter over a lan. Oh yeah, and Seti@Home running 24/7. What do the Turbo 1 and Turbo 2 settings do different then the normal setting? If it is set to normal do the pci/agp settings scale up with the fsb?
 

RalfHutter

Diamond Member
Dec 29, 2000
3,202
0
76
The Turbo 1/2 settings lock the PCI/AGP bus speed regardless of the FSB. The "normal" setting lets the PCI/AGP speed increase as the FSB increases. The setting for Turbo 1 is 36/72Mhz (according to a guy over on Hard who checked it with an ocilliscope), Turbo 2 is a little faster.
 

Nate420

Senior member
Feb 4, 2002
264
0
0
Challenger,

I just sent you a PM to say thanks:D I haven't had a chance to flash yet, but I will this weekend if not before. I'll let ya know how it works for me.
 

f13dfx

Member
Oct 12, 1999
190
0
0
Nightstalker:

Just out of curiousity, what is the FPO Batch # for your NW 1.6a?

Also, does it match the FPO Batch # on the outside of your Retail Box?

Answer my question first, then I'll tell you what you might have and why you aren't able to reach 2.4ghz with ease :)
 

Barrei

Senior member
Mar 21, 2002
514
0
0
Platinum 321 you are plain wrong cause I can overclock my 1.6 williamette to 2050 with no problems sounds like a board problem more then anything.