Whats the likely culprit?

Soldato
Joined
8 Nov 2006
Posts
9,237
While I am running memtest and generally mucking about am looking for suggestions as to what could be the cause of my problems.

The problem is, a couple of days ago, my pc stopped running at anything other than default speeds. If I tried to up the FSB to anything above 200MHz, it gets to the memory test at boot and then restarts/resets itself.

Ok, so the most likely culprits are mobo and memory. I unplugged one set of memory and coule boot at 333MHz fsb. So it must be the other set? Swapped the two sets around and booted fine at 333MHz fsb.

Try it with all 4 back in, get a short squeek from something, and resets self and I am back to where I started. So, with all four sticks in, everything runs fine at default, btu can not up my fsb. With either set of sticks will boot fine at 333 fsb.

So what is likely my problem? motherboard? Memory? PSU maybe? Will be running memtest on memory in mean time, but help appreciated.

PS - Have done things like upped voltage to me, etc, with no luck - it was running fine for about a month.
 
Am currently running memtest on the other pc. I have never used it before, so unfamiliar with how it works. Is the pass field at the top the total of the tests?
 
I have tested each set of memory independantly, and tested in both sets of slots using memtest, and no failures.

I have tried another PSU, and had the same problem.

Is there anything else I can test? Is it likely the motherboard?
 
Am I going to be out of luck RMAing the motherboard? Essentially I have not been overclocking it, as I had the FSB at 333MHz, but given the explanations I have given, are they going to turn around and say "Sorry, it runs on its default settings."?
 
it runs at what its meant to so it technically cant be rma'd, but if it doesnt work with higher fsb stock chips it can be.

its probably PSU seeing as how its a hiper (someone had to say it)
 
Last edited:
Would this still be the case if I get the same problem when I set everything to it's default manually?

Even if the only change I make is taking the cpu frequency setting from auto to manual without actually changing the frequency from 200, I get the same problem.
 
Back
Top Bottom