-
Competitor rules
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Anyone had rebooting probs with dual core cpu in xp
- Thread starter Phil2008
- Start date
Reboot is more likely a sign of instability. Try running it at stock speeds, see if that helps. You probably need more volts to the cpu or the ram to cure the instability.
The only program I ever found that really hated dual core was an old version of Network General's Sniffer.
Changing to vista will not fix a 'hardware' problem. Try running memtest for 10 hours, see if your getting any memory errors, and what are your temperatures like etc etc.
The only program I ever found that really hated dual core was an old version of Network General's Sniffer.
Changing to vista will not fix a 'hardware' problem. Try running memtest for 10 hours, see if your getting any memory errors, and what are your temperatures like etc etc.
Dual Core Optimiser? What be this?
Although it would surprise me if its true (not saying your making it up... just amazed that maybe microsoft got something right in vista)... but perhaps vista is better able to 'correct' memory errors on the fly that would cause XP to reset.
I'd still reset your processor to stock speeds to see if that gets it stable, and download and run memtest86 overnight... as long a run as possible. 12hours without errors is generally enough to satisfy me that the ram's stable
After that prime95 it for another 12 hours or so.
If that doesnt flag any errors at stock speeds (or cause XP to reboot), then you can wind up the overclock again, repeating both the memtest, and prime tests for each time you increase the clock.
XP shouldnt reset without cause on a dualcore system be it intel or amd, unless something is wrong with the system. The number of times people have complained to me about microsofts sloppy codeing of XP... and I've just run memtest for 10 minutes and found errors.. XP is actually a very good operating system.
I'd still reset your processor to stock speeds to see if that gets it stable, and download and run memtest86 overnight... as long a run as possible. 12hours without errors is generally enough to satisfy me that the ram's stable
After that prime95 it for another 12 hours or so.If that doesnt flag any errors at stock speeds (or cause XP to reboot), then you can wind up the overclock again, repeating both the memtest, and prime tests for each time you increase the clock.
XP shouldnt reset without cause on a dualcore system be it intel or amd, unless something is wrong with the system. The number of times people have complained to me about microsofts sloppy codeing of XP... and I've just run memtest for 10 minutes and found errors
.. XP is actually a very good operating system.