Ive just finished building a new Athlon X2 AM2 system (3800+, 2GB DDR2 667, XP Pro) and have been running various burn in programs to stress test it to make sure it was stable.
The problem Ive been having is in regards to running Prime95. Now since this is a dual core cpu Im using, I have to run two instances of Prime95 to stres both cores simultaneously. When I run them like that, one of the instances will fail around 2-3 hours into the process. The funny thing is, its not always the same core, either seem to fail, just not both. I then tried a program called Ortheos that is a gui made for prime95 and designed for use with dual core cpus. When I ran it the first time, it made it to 3 hours and then one of the instances halted for a rounding error as it had before. I ran it a second time and this time it ran for close to 5 hours.
I ran yet another program called 'hot cpu burn-in' and it would run for 4-5 hours before crashing the entire system with a blue screen refering to a memory dump.
Also, I did run memtest overnight and no errors were found for the ram. I did try to watch the temps, and I never did see it push over 45C, but I cant watch it all the time, so it would be nice if there was some way to log the temps so I could look back at it at the moment the test failed.
Any ideas on what I might do to fix this or another program I could run to verify the results? If its nto overheating, then maybe its just a bad cpu, but Id like to make sure. Thanks
The problem Ive been having is in regards to running Prime95. Now since this is a dual core cpu Im using, I have to run two instances of Prime95 to stres both cores simultaneously. When I run them like that, one of the instances will fail around 2-3 hours into the process. The funny thing is, its not always the same core, either seem to fail, just not both. I then tried a program called Ortheos that is a gui made for prime95 and designed for use with dual core cpus. When I ran it the first time, it made it to 3 hours and then one of the instances halted for a rounding error as it had before. I ran it a second time and this time it ran for close to 5 hours.
I ran yet another program called 'hot cpu burn-in' and it would run for 4-5 hours before crashing the entire system with a blue screen refering to a memory dump.
Also, I did run memtest overnight and no errors were found for the ram. I did try to watch the temps, and I never did see it push over 45C, but I cant watch it all the time, so it would be nice if there was some way to log the temps so I could look back at it at the moment the test failed.
Any ideas on what I might do to fix this or another program I could run to verify the results? If its nto overheating, then maybe its just a bad cpu, but Id like to make sure. Thanks