FSB crashing OS

BlueD0T

Distinguished
Mar 18, 2003
13
0
18,510
I just upgraded to an ATHLON XP 2600+ SOCKET A (2.1 GHz) (266 MHz BUS) from 800 MHz Duron, on a GigaByte GA-7DXE (BIOS ver F3) (AMD AMD-761) mobo. I have 2 sticks of Micron Technology DDR-SDRAM PC2100 - 256 Mbytes.

When I first installed the processor the BIOS recognized it as a unknown processor running at 1.6ghz so after it booted it used the BIOS update tool that came on the gigabyte CD to flash it to the newest none beta version (BIOS ver F5) it then sow the processor as a AMD 1900+ (in the BIOS and winXP) (I then realized that I forgot the set to mobo jumper from the 100mhz FSB to 133mhz bus) then after setting the jumper to 133mhz FSB, the BIOS sow the processor as a AMD 2600+ (yeah) but as soon as windows XP pro starts to load the computer just restarts. (I let it restart then it come up as windows did not load good last time would you like to start in safe mode, so I do start in safe mode and it does the same thing.)

So I set the jumper back the 100 MHz and it loads fine.. So then I update the bios to F6a (a beta version) and it boots alittle further than before but still just restarts.

My CPU temps are fine and the chip looked fine before I installed it and the chip said it was a 2600+ on the chip. I also updated to the newest mobo drivers. Im running win xp pro sp2.

CPU-Z see’s it as:
Code Name Thoroughbred
Specification AMD Athlon(tm) XP 1900+
Family / Model / Stepping 6 8 1
Extended Family / Model 7 8
Package Socket A
Core Stepping B0
Technology 0.13 µ
Supported Instructions Sets MMX, Extended MMX, 3DNow!, Extended 3DNow!, SSE
CPU Clock Speed 1615.9 MHz
Clock multiplier x 16.0
Front Side Bus Frequency 101.0 MHz
Bus Speed 202.0 MHz


Anyone got any advice? Is it a bad CPU? Bad mobo? User error?

Thanks,
BlueD0T
 
Make sure the Mobo is supplying the correct Voltage to the CPU (I beleive it is the 1.5 / 1.6 Vcore area - not sure))

<font color=blue><font color=red>Blow</font color=red> Dry <font color=red>my ass</font color=red> and call me <font color=red>Eden</font color=red>!</font color=blue>
 
My first instinct with a reboot situation is to blame the power supply. (Especially since upping the MHz that much would really increase the power draw of the CPU.) Can you read your voltages in BIOS?

<pre><b><font color=red>"Build a man a fire and he's warm for the rest of the evening.
Set a man on fire and he's warm for the rest of his life." - Steve Taylor</font color=red></b></pre><p>
 
BIOS says:

FSB@133
Vcore - 1.52
3.3V - 3.23
5V - 5.05
12V - 12.30

FSB@100
Vcore - 1.53
3.3V - 3.23
5V - 5.07
12V - 12.30

Windows FSB@100
Vcore - 1.50 to 1.52 (it moves every few sec)
3.3V - 3.23
5V - 5.02 to 5.05 (it moves every few sec
12V - 12.30

General Information :
Real Frequency : 1615.9 MHz
Performance Rating : 1900 PR
Multiplier : 16x

Front Side Bus Information :
Front Side Bus Speed : 101 MHz
Bus Speed : 202 MHz (DDR)

Initial Frequencies :
Frequency : 2133 MHz
Front Side Bus Speed : 133 MHz

Thermal Information :
Core Power : 49.46 W (approx.)

Processor Performance Information :
Throttle Mode AC : None
Throttle Mode DC : Adaptive
Current Configuration : None
Throttle : 1615 MHz


hardware--------------------
hard drives (2) 20gb 7200
memory (2) 256mb PC2100
geforce 2 MX 32mb (i plan to upgrade soon a new mid level card so a can play doom3)
Creative SB live
(1) 10/100 nic card
(1) DVD Burner
(1) DVD reader
(4) case fans
Power Supply CWT-375atx12 (its 375w with 2 fans)


I really dont know what all this power stuff means. but the number seem right. and a 375w should be fine right? is their any wat to test it with out having a bigger power supply?
 
It's tough to say where the problem is. It could be either the motherboard or cpu. I would increase the cpu voltage gradually if your board permits this, and see if that helps. My new barton 2600 is set at 1.63 volts. I would also try just one stick of memory.
 
I had several AMD 761 boards(Asus, I speced out first two, they bought others later without asking my advice), that had same problem. WOuld not run stable at 133, and in fact toasted at least one stick of memory trying to run 133. Believe I tracked it down to a voltage problem on the dimm socket. Had to get each board stable seperately, started around 120mhz FSB clocked it up until I started crashing again, and then went back down 2mhz, believe 127 tended to be the happy medium.

WOuld give memory related BSOD's even on Windows setup, much less crashes in windows.