possible causes for memtest freezing?

[mkln]

hi, i was just trying to diagnose a system problem am was wondering what the possible causes for failure of memtest would be (other than faulty memory). i have tried changing hard drives for the system, changed the memory, changed cabling, and memtest will just stall; the 'wall time' will freeze, but there is still a flashing cursor and the '+' in the memtest name (top left corner) will continue to flash as well. memtest does not report any errors, but it will freeze at random times; once it froze w/in 3 mins, and another after 30 mins. could the processor or mobo be the cause of the problem? if so, how would i be able to distinguish one problem from another w/o having another mobo to test with? (temps are fine btw).

thanks in advance to any helpful advice

 

[Rike]

Assuming your memory is not the problem, which is assuming a lot, it could be . . .
1. Bad OC on your CPU
2. Not enough volts on the NB
3. Overheating NB

If you haven't already checkout this sticky at the top of the CPU & OC forum. It's very helpful.

 

[mkln]

thanks for the reply

i have tried orthos in windows and the system will freeze before anything else happens; orthos will not even fail.

1) on stock clocks, the system will freeze
2) bios is locked (the system i am troubleshooting is a POS system - celeron 356 - from Bestbuy)
3) temps seem to be fine.

thanks for the link, but the system just seems quite unstable to the point that no tests can be run successfully; it even froze during an install of windows and basically any installation, which lead me to believe a memory or HDD issue. i have since swapped the HDD and memory for known working ones and still the issue arises. i have yet to change the PSU though, but i believe that is is more likely that the CPU or mobo are the cause of the problem. is there anything short of actually changing the mobo/CPU that i can do in order to diagnose which one is the problem?

thanks again

 

[Rike]

The chances of it being a bad CPU are not very good, especially if it has never been OCed. Based on what you've said, I'd guess the mobo is the problem. I had it happen on a build once and it's maddening. It could be the psu, but I'm betting mobo. And the only way to really know is to either swap out the mobo or swap in all other known working parts.

 

[mkln]

i suppose getting another mobo is the only solution then. thanks again