Suddenly can't OC my P4 1.6a

CFW

Member
Oct 9, 1999
48
0
0
I have been running my P4 1.6a on an ASUS P4B266 at 140FSB / 2.24g since february with WIN2K. It has run flawlessly until a week ago. My system suddenly couldn't see my network and the floppy quit working. If I pulled the NIC the floppy drive would work. After a bunch of messing around and a new NIC got it working again with a reinstall of W2K over the old instalation.

Now I have the same problem. But If I set the timing back to stock everthing works fine. Set the FSB to anything over 105 and things start going bad. The sound quits, access to the network quits, try writing to the floppy and it locks up tight. If I have my parallel printer plugged in it will lock up solid as soon as I log on.

Here are a couple things that make me think Software. I can start in safemode with network support at 2.24g no problem. I did a clean install on another disk, that seems to work fine, though I don't have any applications on that instalation to try out. I did run Stability Test for a while and had no problems.

So far I have drained the bios, flashed the bios with a beta bios 1007ddr.004. I guess I need to do a clean install but that is a PITA I wanted to avoid. Any ideas what is going on here
 

jiffylube1024

Diamond Member
Feb 17, 2002
7,430
0
71
It sounds like one of your components doesn't like to be stressed at a high PCI speed. You might want to try setting "turbo 1" in the BIOS (which supposedly locks the PCI and AGP speeds to 37/74 MHz) ... run your machine at stock speed (1.6 GHz) with turbo 1 set ... if that works fine then o/c it around where you were before with turbo 1 enabled.
 

Jwyatt

Golden Member
Mar 22, 2000
1,961
0
76
Running at 140 fsb is only running the pci at 35. So the OCed pci shouldnt be the problem. I would disable everything you can in win 2k and try see if that works well. Then enable them one at a time till you get it back unsable. Its a pain in the arse. You probably have a bad file in there thats causing the problems check them using the command from the run window "sfc /scannow" This will scan all the system files for a bad one. You will need your win2k cd in order to complete this.
 

CFW

Member
Oct 9, 1999
48
0
0
jiffylube1024, I don't seem to have ( or can't find that setting ) in my bios. but I still have problems with the FSB set at 133 that keeps all the busses running stock. The CPU doesn't seem to have any problems at the higher speeds. It will run anything as long as I don't use any accesories like the sound, network or floppy.

Jwyatt, By disabling do you mean just going into the device mgr and disable all the devices, or try unistalling everything? Just disabling sounds pretty easy. As far as a bad system file, I think I have that coverered. I did a second installation on a different partition and am still having problems. In fact the problems started shortly after installing the sound drivers. But why did it work so well for 4 months

SupermanCK, A virus sounds good to me, but if I have one I sure can't find it. I have been running P-cillan on that machine and kept it current. I have run scans and I booted off a Norton Internet security CD and run scans from a cold boot and havn't found anything. But having it start acting up all of a sudden sure makes me suspicious.

Is there anyway to control the IRQ's being setup by WIN2K? It seems I am always sharing some. The bios reports some sharing with either 5 or 9 and I think I can get that cleared up, but WIN2K seems to set up sharing on 21,22,or 23. This is the 1st time I have ever run into these extended IRQ's. My last WIN2K machine put most everything on IRQ11 and it worked OK. Now with IRQ's above 16 you would think you could get by without sharing.
 

CFW

Member
Oct 9, 1999
48
0
0
Got it overclocking again. I disabled all the USB controllers in the device manager thanks Jwyatt. At the moment I don't have any USB devices so it isn't a problem, even though it worked for months with them enabled. I seem to remember reading something about the P4B266-c not overclocking with USB devices plugged in. I didn't think it was supposed to be a problem with the P4B266 with the USB2.0 feature.

I believe this is an IRQ problem, but I don't understand how this new stuff works. My MB manual gives the standard list of IRQ's 1-15 and Priority 1-15 along with the standard Functions like Primary IDE IRQ14 priority 9. But it also list the motherboard resources titled "IRQ assignments for this motherboard" with listings from A-H and listing as shared or used. Anyone have a good link to describe how all this stuff works?