Check your clock speed and multiplier. I have a kt3-Ultra2-BR from MSI and had my FSB set right, but an incorrect multiplier for over two years.
Can you say slow burn? By forcing the system to run at 334 fsb instead of 333mhz for years, it slowley burned the system up.
I started getting random reboots without an error message, exactly as you described. No memory dumbs or error logs. Took me three weeks to figure it out.
I decreased the clock multiplier and brought the clock cycle down to keep the cpu at 1ghz instead of it's native 1200ghz support. It's been stable for 4 months, but I lost 200mhz, and trying to bump the chip back to 1200mhz just causes the problem to start again.
Even worse, the fsb was wrecked through the inadvertant overclock, and now randomly bumps back to 334.5 according to Sandra.
Now I just bide my time to an upgrade.
__________________
Seen on an employer evaluation:
"The wheel is turning but the hamsters dead"
____________________________
Is arch13 really a porn diety ? find out after the film at 11.
-Nanofever
|