machine died while O/C! is my ram the cause?

Wigwam

Senior member
Dec 26, 2002
943
0
0
Hi,

i posted earlier today about failing to get my rig [2100+ etc as per sig] to work at 200*10.
i then figured i'd try to see what is the cause and booted it at 200*9.5, with the ram timings at spd and at 8-3-3-2.5

it booted up fine and i had mbm5 running to keep an eye on temps.
to test the mem i ran the memory bandwidth and memory cache burn in wizards on sisoft sandra.
it passed 1 round on the bandwidth but when it was doing a cache and memory benchmark [temp was only 53C] i suddenly got a blue screen with:

"A problem has been detected and windows has been shutdown to prevent damage to your computer.
A wait operation, attach process or yield was attempted from a DPC routine.

Techincal Info:
STOP: 0x000000B8 (0x00000000, 0x00000000, 0x00000000, 0x00000000)

i have now put it back down to 166*12 and it finally decided to work again [i had to power off completely first].
Before this i have never had a problem running

technical info: 2100+ auihb at vcore = stock [1.60], ram = twinmos w/winbond BH5 PC3200 running in synch [currently 166MHz at 5-2-2-2] agp = 66mhz stock vmem

do i have dodgy ram that doesnt run at 200MHz even thogh it is supposed to? what else would cause that error

PLEASE HELP
 

MDE

Lifer
Jul 17, 2003
13,199
1
81
That means your CPU isn't stable at that speed. Keep edging up the FSB until it isn't stable, then lower it to the last stable settings.
 

x-kid

Senior member
Jul 25, 2003
284
0
0
are you bumping up your voltages. if not you might need to up them a little bit. also what kind of cooling do you have.
 

Wigwam

Senior member
Dec 26, 2002
943
0
0
no i am keeping it at stock voltage due to hsf limitations

to be perfectly honest i am happy to hear it is the cpu cos i can always wangle that in future with upping volts and better hsf; not much i could do with physical ram probs

as a learning point for me what in the error script tells you that it is cpu error?
 

Wigwam

Senior member
Dec 26, 2002
943
0
0
oh yeah...and how come the cpu runs fine [but hot!] at 2075 MHz via 12.5*166 but has a problem with 200*10? i mean it is currently happy at 12*166 [1992]? so is there more to it than overall speed when assessing voltage needs/instability?
 

MDE

Lifer
Jul 17, 2003
13,199
1
81
It just may not like the high bus speed. You're getting about the speed of a 2600 out of that 2100, not bad in my book :)
 

x-kid

Senior member
Jul 25, 2003
284
0
0
yea usually if you want to run at that high front side bus your gonna up the voltage...and to do that your gonna need to get better cooling
 

Wigwam

Senior member
Dec 26, 2002
943
0
0
thanks - a;; info helps me.
i had assumed it was raw speed limits that determined if you needed to up the vcore or not, not fsb per se - i see i was wrong!
so i guess if i want to play [with my current hsf] i can just slowly up the fsb until it doesnt like it anymore [dropping multi if needed to keep temp down]?