[QUOTE=KarateF22;357351]Lastly, sorry if this isn't exactly the place for this kind of question,[/QUOTE]It's the right place.

[quote]I will admit that I found this forum by basically googling "Prime95 forums".[/quote]Did you try Googling "BSOD Secondary Processor Interrupt" or "Sandy Bridge Secondary Processor Interrupt"?

When I try those and some variations, almost every find is talking about a _clock_ interrupt, as in "A clock interrupt was not received on a secondary processor". Does your message mention "clock"?

[quote]I can get my overclocked[/quote]Hmm... , "clock interrupt", "overclocked" Coincidence?

As for it happening only if you use PrimeNet ... I don't know.

Well, this just gets even more curious. Just deleted my current version of p95 and installed a new (presumably identical) one. Now PrimeNet is fine, though it will only utilize 6 of 12 available workers (though they each have their affinity set to use 2 threads). That said, it doesn't seem to be fully stressing the CPUs anymore using PrimeNet, while previously it had 12 workers running on full and fully stressed CPUs. I... don't even really have anything I could possibly say to justify why this would suddenly be the case.

*EDIT* Nevermind on the number of workers, found the setting to increase that number higher. Now fully stresses CPU. No longer crashes CPU either... which confuses me as presumably its an identical program.


tl;dr Deleting then reinstalling Prime95 magically fixed everything.

[QUOTE=KarateF22;357646]Deleting then reinstalling Prime95 magically fixed everything.[/QUOTE]

That doesn't make sense (if you are SURE the versions of Prime95 were identical).

Have you checked your HD's SMART data? You might have a failing hard drive.

If not, the temporal correlation with network activity might be worth thinking about. Could you have a bad NIC and/or bus?

[QUOTE=chalsall;357653]That doesn't make sense (if you are SURE the versions of Prime95 were identical).

Have you checked your HD's SMART data? You might have a failing hard drive.

If not, the temporal correlation with network activity might be worth thinking about. Could you have a bad NIC and/or bus?[/QUOTE]

I won't argue that it doesn't make sense, unfortunately I wasn't smart enough to keep the old version... though to be fair it was because I did not think it would work.

My HD appears to be fine, just did a check and there were no errors.

Hey yeah! Where the hell is our damn NIC stress tester?

[QUOTE=TheMawn;357665]Hey yeah! Where the hell is our damn NIC stress tester?[/QUOTE]

MTR (My Trace Route) is mine.