well thats insightful windog, be a lot less vague next time
well thats insightful windog, be a lot less vague next time
BIOS is WAY TOO TIGHT MAN...that memory is screaming out to die on you....
RESET BIOS...find the manual, work out how to reset cmos.....doit...reboot...
and use much gentler timings....
in fact for the first week, let BIOS set the timings using the auto thingy....probably end up 7-3-3-3 or close....
that ram will not do that 5 -2-2-2 stuff.....
good luck
Originally Posted by Advice Trinity by Knoxville
I better re define this.....the memory thing...
if your ram runs really tight timings at 100 fsb (PC1600) it doesntmean it will work thattight at the next bus speed up....
So.....if you set BIOS to use the automatic timing system....(cant remember its damn name now) you'll put PC3200 in and a Duron at 100 fsb and it will knock them down so tight it wil squeak when it walks
then up the cpu and fsb to a 133 (PC2100) and it wil drop them a bit....
then up to a Barton or similar at 166 (PC2700) and it will be slower looser timings again...
and thenfinally to 200 (PC3200) and it will loosen them again.
Much debate about whether a faster timing and slower fsb would be better or vice-a-versa...but on the whole...high fsb and looser timings....
then...AFTER A WEEK OF 100% STABILITY.......tweak ONE setting..and run for a fewdays....etc etc
hope you suss it man
Originally Posted by Advice Trinity by Knoxville
What PCI cards have you got fitted?
a modem disconnected now..
ta zakk i'll try that, but my post reprter doesn't say nout about overclocking probs or temp or whateva
Got some of that bs aswell, and its f0rking up me cpu..Originally Posted by BEANFro Elite
it wont...if the mem is too tight....it wont even see it......soon as the cpu requests anything from the mem, it'll see nowt..
same as having no memory plugged in but probably worse really....cos theres a presence in the slot.
I am NOT tech head...but HAVE done the same damn thing.....
the sad thing is this.......
In doing this very thing I lost my BIOS ..it was corrupted...and Ihad to get it hot flashed....
Originally Posted by Advice Trinity by Knoxville
allow hot flashing man bare dodgy
yeah but i read somewhere that if all goes wrong u could fry yo mobo
use these ram timings: 2.5-3-3-12 @ 166fsb
that should be ok for your system. it will be the ram casuing the problem, generic ram just wont do 2-2-2-x timings... use memtest86 to find the best ones...
Hey, I'm only going to the limit of my knowledge, which I will be the first to acknowledge is near zero!
i put the ram at 15-7-7-7-3.0 100 mhz fsb and it still gives me beef.
i'm telling you, it gets to a certain point and then stops loading...and crashes/freezes.
i did further investigating and have concluded its probabley the mobo's fault.
but i'll try all your suggestions one last time then i'm RMAing the mobo
do you have access to any other memory that u can test the system with?
Do a google search for mup.sys hang.
It's a software problem not hardware you've got (although those timings do sound tight for bargain basement RAM). It is usually accompanied along with a change in hardware.
There are currently 1 users browsing this thread. (0 members and 1 guests)