cpu stress test recommendations

[VJ]

Hello,

I'm looking for a good cpu stress test to test my dual Xeon (Prestonia, 32bit, socket 604).

The reason for this is that yesterday I got a bluescreen stating: "A clock interrupt was not received on a secondary processor within the allocated time interval". According to Supermicro tech support (who replied to my email within an hour!), this blue screen could be the indication of a failing or defect cpu. He recommended either swapping the CPUs and even testing them individually (run the system with only one CPU present).

The blue screen occurred only once so far, but if it occurs again I need to know what steps to take. I'd like to put the system under full load with the CPUs both working hard to see if it will occur again.

Thanks!

Jörg

[TransformX]

This is the search term you're looking for:

http://www.google.co.il/search?q=cpu+burn+in

[VJ]

Yes, I searched, but there are many options and I wondered if people here have favourites...

Supermicro also replied saying that they recommend Passmark, as it allows specific hardware to be tested.

[TransformX]

Sorry, that's where my knowledge ends, let's hope the others know more

[UtwigMU]

Prime95, CPUBurn

[LvR]

Been using OCCT lately

[VJ]

Well, I reinstalled the OS (put back an image of before the failed update) and ran the BurnInTest on CPU and videocard... It passed without a single problem. I'll try some of the other tests in BurnInTest too (harddisks, ...) and use some of the suggested tools as well.

This weekend, I'll do the exact same things I did when the bluescreen occured (I was copying files from a dvdram to harddisk, while dialing a 3G connection on a virtual linux ), and see if it occurs again... Then it I'll update the system and test again... But so far it is looking more positive (I was really fearing a hardware issue).

[Marshmallowman]

I find OCCT test be a very handy stress test as well, gpu and cpu.

[Evildead666]

Prime95 and OCCT are pretty good.

[VJ]

Thanks guys!
I reverted the system to an older configuration (basic installation with drivers) and updated from there on. Then I ran the tests, and the blue screen did not occur anymore...

So I'm more hopefull now that it was just some software glitch...