BSOD - When Installing Windows XP

rlculver · 7 Jun 2007 at 10:40

will the volatge change damage any thing

Admiral Huddy · 7 Jun 2007 at 10:51

rlculver said:
will the volatge change damage any thing

not unless you set it something stupid.... PC3200 memory won't work to well with anything less than 2.7 volts.. If you have anything less than this then you will get BSODs. What is the current setting?

I had this problem with my nForce 2 when i had one running PC3200 and lot of others that i've dealt with since.

z0mbi3 · 7 Jun 2007 at 10:57

Admiral Huddy said:
as Jaffa Cake said it's a little too hot but this wouldn't cause the system to BSOD.. it would just cut out when it reaches a certain "fail safe" limit.

Running too hot could cause it to BSOD. Depending on the cooler and the dust inside the PC it could be time for a re-application.

split · 7 Jun 2007 at 14:03

mattbill said:
Found this about the AMD XP Athlon on good'old wikipedia.

Specifications:
Barton (130 nm)

L1-Cache: 64 + 64 KiB (Data + Instructions)
L2-Cache: 512 KiB, fullspeed
MMX, 3DNow!, SSE
Socket A (EV6)
Front side bus: 166/200 MHz (333/400 MT/s)
VCore: 1.65 V
First release: February 10, 2003
Clockrate: 1833 - 2333 MHz (2500+ to 3200+)
166 MHz FSB: 1833 - 2333 MHz (2500+ to 3200+)
200 MHz FSB: 2100, 2200 MHz (3000+, 3200+)

3000+ appears to be 200 fsb, as standard.

is his cpu definately the 3000+?
could be a 2500+ or 3200+ overclocked, and you are positive its not overclocked? I would say if you reverted back to defaults and its changed the fsb, its a sign it has been OC'd.

If it has been OC'd could be ram n cpu speeds not in sync etc.

The wilki missed a bit. I shall go find that page and add to it.
AMD did a sly on the 3000+.
There was 2 models, though the 200FSB was rarer.

Model 10 "Barton"

AXDA3000DKV4E 3000+ 2100MHz 10.5x200
AXDA3000DKV4D 3000+ 2167MHz 13x166

It's the E and the D that give it away...(last digit)

Max FSB:
C = 266MHz
D = 333MHz
E = 400MHz

He's prolly fixed it now, but I couldn''t refuse

Admiral Huddy · 11 Jun 2007 at 16:16

SO how did it go?

Fob · 11 Jun 2007 at 16:34

Had that mobo there is a bug in the BIOS if you have too much memory installed.

I had 4 250MB modules and the same thing happened to me.

If you change the BIOS setting to CPU Menu instead of Auto and check the rest of the settings like onboard sound etc.

It should just boot up at standard settings, cant remember exact details.