hardware error
 

I´ve got a MSI Neo3 + Intel Quad Core Q6600 (not overclocked) and Windows XP 64 Bit Edition.

I´m getting this message after running Prime95 (.27 version - occures for 32 and 64 bit version) + World of Warcraft):

[Oct 26 19:39] Worker starting
[Oct 26 19:39] Setting affinity to run worker on logical CPU #1
[Oct 26 19:39] Resuming primality test of M46218973 using FFT length 2560K
[Oct 26 19:39] Iteration: 10291967 / 46218973 [22.26%].
[Oct 26 19:41] Iteration: 10293661/46218973, ERROR: SUM(INPUTS) != SUM(OUTPUTS), 1.284306450541002e+016 != 1.336507830333977e+016
[Oct 26 19:41] Possible hardware failure, consult the readme.txt file.
[Oct 26 19:41] Continuing from last save file.
[Oct 26 19:41] Waiting five minutes before restarting.

---
I´ve already changed the RAM - it only occures if I have a lot of IO (for instance starting the WOW Game).

Don´t understand whats going on. Is it really a hardware error or some error in the client?

Greetings and thanks
joblack

Have you stress-tested your system before running actual exponent? How did you do it?
How many worker threads are working? How many threads have been assigned per single test?

[quote=Cruelty;146655]Have you stress-tested your system before running actual exponent? How did you do it?
How many worker threads are working? How many threads have been assigned per single test?[/quote]

Yeah works fine as long as I´m not doing something else on the machine (like playing World of Warcraft).

4 worker threads with 1 cpu thread each.

Still I don't know which stress test did you use...
Anyways, check your temperatures and... voltages, as getting errors while playing games might actually indicate some problem with PSU (if you're 100% sure that it's not RAM or CPU that's causing such problems).

[QUOTE=Cruelty;146767]Still I don't know which stress test did you use...
Anyways, check your temperatures and... voltages, as getting errors while playing games might actually indicate some problem with PSU (if you're 100% sure that it's not RAM or CPU that's causing such problems).[/QUOTE]

Or some problem with the games in correctly restoring FPU registers

Luigi

[quote=ET_;146781]Or some problem with the games in correctly restoring FPU registers
Luigi[/quote]

The saving & restoring is done by the operating system (in that case Windows XP 64 Bit) and not by the application.

I´ve formatted my system and installed Windows XP 32 Bit. Now it works without a problem (the same bios configuration).

So it´s a Prime95 (32 Bit or 64 Bit) problem or it is a Windows XP 64 Bit problem. Anyway I suggest don´t use Prime95 with Windows XP 64 (and perhaps Vista 64 Bit).

[QUOTE=joblack;146790]I´ve formatted my system and installed Windows XP 32 Bit. Now it works without a problem (the same bios configuration).

So it´s a Prime95 (32 Bit or 64 Bit) problem or it is a Windows XP 64 Bit problem. Anyway I suggest don´t use Prime95 with Windows XP 64 (and perhaps Vista 64 Bit).[/QUOTE]

Formatting would also have removed anything that was installed before so it could have been a driver or something else running in the background not just Windows or Prime95.

But either way, I have never had any problems with Prime95 and Vista 64bit.

[quote=joblack;146790]The saving & restoring is done by the operating system (in that case Windows XP 64 Bit) and not by the application.

I´ve formatted my system and installed Windows XP 32 Bit. Now it works without a problem (the same bios configuration).

So it´s a Prime95 (32 Bit or 64 Bit) problem or it is a Windows XP 64 Bit problem. Anyway I suggest don´t use Prime95 with Windows XP 64 (and perhaps Vista 64 Bit).[/quote]

I use Prime95 64 bit (24.14) on Windows XP 64, and haven't had any problems. I have played a lot of Warhammer Online at the same time, and still no errors. I happen to be using a Q6600 (not overclocked) also.

I haven't tested my setup with WoW, but plan to after I re-enable my account (Nov 16th).

[quote=joblack;146790]The saving & restoring is done by the operating system (in that case Windows XP 64 Bit) and not by the application.[/quote]Yes, but it used to be that a few device drivers (even XP) were culprits in failing to save/restore FP registers.

As far as I know is the windows xp scheduler doing this work. The device drivers have no direct access to the saved fpu data.

Good. I'm glad that's cleaned up, when/wherever it happened, and is no longer a problem.