P4 1.6A OC problem, help!

WhiteMouse

Senior member
May 30, 2000
623
0
0
I have P4 1.6A, Shuttle AB30 MB, 512M PC133 DIMM (yeah, I know, I know ...). But, whenever I set FSB @133, besides the cold boot problem, it also reports hard disk config changed :confused:

Step by step testing, all at Default Vcore:

1. Only installed floppy, and GF2 video card, ignore the HD warning, (or set them as None in BIOS to remove the warning), boot to DOS @133FSB, ran MemDoc burn-in test memory for 24 hours, no error at all. I guess that means my CPU and memory sticks (even mixed brand and chips) have no problem at all to handle 2.2G @ 133fsb.

2. Installed HD and CD, and XP, now have to see the boot HD warning every time. Booted to XP at the first time. Then, after a little BIOS changing, I cannot boot into XP at all. Always reboot after the XP splash window. Switch back to 100fsb will boot to XP smoothly.

So, besides changing a motherboard, is there anything I can do?

Thanks!
 

o1die

Diamond Member
Jul 8, 2001
4,785
0
71
If you have set the fsb jumper to 133 (assuming the board has one) and you still have the problem, I would rma the board. It may not be providing enough voltage for the system to run at 133. When I had a similar problem last year, I rma'd both the board and cpu so the shop could test both. If you have a generic power supply that's not amd approved, that could also cause problems.
 

Nate420

Senior member
Feb 4, 2002
264
0
0
Whitemouse...I'd probably rma the board like o1die said.


o1die....

I understand your point about a cheap PSU being a problem, but since when is AMD's approval relevant to an Intel system? :D (just bustin your balls)
 

Duvie

Elite Member
Feb 5, 2001
16,215
0
71
2 things since shuttle as such a stellar record for quality....

1) do you know for certain that the shuttle board implements a 1/4 pci divider or lock pci/agp speeds at a certain speed??? could it be the pci is way out of spec...ie 44mhz????

2) Check your 12v rail...I believe harddrives may run off of it as well as the p4 cpu...like mentioned above maybe power supply is not supplying enough amps and wattage to run everything...if you have several ide devices and sort, unplug a few beside main harddrive and see if that helps...


also go ahead and clear cmos and set board back to factory defaults in case you have set something incorrectly in the bios...
 

nealh

Diamond Member
Nov 21, 1999
7,078
1
0
try upping the Vcore before doing anything else and keep the memory timings at default and see if you can boot winxp

If you run the cpu at default speed does this happen??
 

WhiteMouse

Senior member
May 30, 2000
623
0
0
Thanks for all your help. I played during the weekend. Here's what I found.

1. The 12V (+/-) are little low, they are all at 11.5 level. But how come there is NO hd warning in default 100 FSB? And even I did not install any HD or CDROM, there is still the warning, if FSB is above 115. However, seems that HD warning is just a warning, since I can boot into XP, see below for details. I can just press F1 to ignore the warning, or even disable it in BIOS.

2. The default Vcore is 1.4V, but I read somewhere P4 1.6A default Vcore should be 1.5V?

3. The cold start problem only happens after I clean CMOS and unplug the power cord. Otherwise, it will post. :)

4. Set Vcore as 1.5V, I can boot into XP. But both BIOS and Sis Sandra show the VCore as 1.46V. :confused:

5. There is no anwser from Shuttle tech support. So I do not know if PCI is locked in 33 when fsb is 133. Sis Sandra does not show AGP speed or PCI speed while FSB is not 100 :|

6. Sis Sandra does show memory bandwidth, which Shuttle AB30 does not lock at all. Dependes on BIOS memory setting: PC100 or PC133, it's simply multiplying the FSB. So when FSB is 133, my PC133 memory running at 133x1.33 = PC176 :Q The memory banchmark confirmed that too.

7. XP blue screen is not because of overclock. It's CMedia audio driver's problem. I reinstalled XP twice before I found that out! :disgust:

8. Running Sis Sandra stress burn-in (memory banchmark only since I found it always uses 100% CPU, so it can raise CPU temp quicker), passed 100s loops w/o any problem. But running overnight crashed XP.

I will test more, any other suggestions?