P95 PrimeNet causes BSOD; small FFTs, large FFTs, and blend test don't
 

Hi.

So I have an interesting problem... I can get my overclocked computer 8 hour+ stable in Small FFTs, Large FFTs, and the Blend torture tests. Oddly enough, however, if I try to use PrimeNet... I will get a near instantaneous BSOD citing "Secondary Processor Interrupt". I can only get this to go away by dropping from 4.8 to 4.5 GHz, which is massive. Likewise I have never had a processor crash in any other program, including the Intel Burn Test. Does anyone know why it would be so unstable for this one specific program when in all other operating circumstances it is rock solid?

Lastly, sorry if this isn't exactly the place for this kind of question, I will admit that I found this forum by basically googling "Prime95 forums".

Haswell?

Sandy Bridge, 3930K

[QUOTE=KarateF22;357351]Oddly enough, however, if I try to use PrimeNet... I will get a near instantaneous BSOD citing "Secondary Processor Interrupt". I can only get this to go away by dropping from 4.8 to 4.5 GHz, which is massive.[/QUOTE]

I'm sorry but I've not heard from anyone else having a similar problem. I can't even come up with a plausible explanation why network activity would trigger a hardware failure.

[QUOTE=Prime95;357362]I'm sorry but I've not heard from anyone else having a similar problem. I can't even come up with a plausible explanation why network activity would trigger a hardware failure.[/QUOTE]

Which torture test does PrimeNet most resemble? Or does it cycle through each of them over its execution? Are there any subroutines that are only utilized in PrimeNet?

[QUOTE=KarateF22;357363]Which torture test does PrimeNet most resemble? [/QUOTE]

In-place large FFT torture test with an FFT size somewhere between 3072K and 4096K.

See if you can set up a custom torture test with those parameters. When you say near instant, are you talking minutes, seconds, or less?

[QUOTE=TheMawn;357444]See if you can set up a custom torture test with those parameters. When you say near instant, are you talking minutes, seconds, or less?[/QUOTE]

0-2 seconds after it finishes downloading the data on any core. As for testing the custom settings, I will be able to Sunday... am currently out of town.

I understand the desire to get as much out of the system as one can. You are pushing your system to the limits so naturally bad things can (and do) happen. As for finding the reason I think we already know what it is: overclocking and generally stressing the system. And you also already know the solution: reduce the clock.

But considering the utility function of gain vs loss, I think you have already lost much more than you can ever gain from now by overclocking. BSODs and general errored results cause a lot of work to be wasted and requires a significant amount of overclocking to be able to recover such losses, let alone actually getting ahead on the deal.

My suggestion is just to set it to 4.3GHz (or whatever you found stable less some comfort margin) and start getting good results immediately. Waiting another few days for more tests to complete, and other various bits of farting around, will take a lot of catching up (if you can ever catch up).

I would normally agree with what retina says here, but in this case if it can run the prime95 torture test without error for 8 hours reliably, and the same program is dumping a bsod in just a couple of seconds talking to primenet, something else is wrong.

You may discover in the end, that the cpu IS overclocked a little to high too give consitsently accurate results. Still, something else is wrong here.

Posting the prime.log file might be useful.