- Joined
- Apr 29, 2001
Hello. On two occasions, earlier today and two days ago, when setting up my FSB to run at 452 MHz, booting into Vista64 and running Prime95, I would note Everest Ultimate reporting the FSB having gone down to 448MHz. (As I rebooted both times and discovered the BIOS still thinks it's 452MHz, I am confounded.)
I am testing my system right now, at 451MHz:
Q9550 @ 8.5x451
vcore 1.36825v
gtl 0/2 = 0.675
gtl 1/3 = 0.685
CPU PLL = 1.56
NB = 1.4v
FSB Term = 1.30v
CPU Spread spectrum = disabled
C1E = disabled
Speedstep = disabled
Also, when I manually set my FSB Strap at anything other than AUTO, memtest86 reports constant errors. I noted this strapping, when set, brings up other values in "DRAM FREQUENCY" -- given many of these settings are the same, I do not know why 400 or 333MHz might lock up yet 200 won't, assuming "AUTO" chooses 200. Why might that be happening?
Could this be a bad CPU? Or motherboard? Or another BIOS setting I'm overlooking?
Thx!
I am testing my system right now, at 451MHz:
Q9550 @ 8.5x451
vcore 1.36825v
gtl 0/2 = 0.675
gtl 1/3 = 0.685
CPU PLL = 1.56
NB = 1.4v
FSB Term = 1.30v
CPU Spread spectrum = disabled
C1E = disabled
Speedstep = disabled
Also, when I manually set my FSB Strap at anything other than AUTO, memtest86 reports constant errors. I noted this strapping, when set, brings up other values in "DRAM FREQUENCY" -- given many of these settings are the same, I do not know why 400 or 333MHz might lock up yet 200 won't, assuming "AUTO" chooses 200. Why might that be happening?
Could this be a bad CPU? Or motherboard? Or another BIOS setting I'm overlooking?
Thx!