Prime95 v 30.3b6 64bit enable more verbose logging?

[Bitter]

I'm trying to pin down some issues in a computer and prime95 has been great at causing the failure but I haven't had a detailed enough log to know which worker is failing each time. What's happening is either the whole PC reboots with a windows event error about bug check or prime95 crashes and closes. Either time the results.txt only tells me at what point in testing the problem happened and what the rounding error was, but not which worker had the failure. I would like to know which worker is failing each time to pin down if I have a bad core in the CPU or if it's a more general failure. Only once in many hours of testing have I been present to see a worker fail. It fails at different points and different times so it's my issue, not a Prime95 issue.

How do I get a more verbose log from Prime95 running Windows 10?

[ixfd64]

You can set Debug=1 in your prime.txt file, although this is mainly for troubleshooting connection issues. Checking the Event Viewer logs will probably be more helpful.

[Bitter]

Originally Posted by ixfd64

You can set Debug=1 in your prime.txt file, although this is mainly for troubleshooting connection issues. Checking the Event Viewer logs will probably be more helpful.

Event viewer has only informed me that it wasn't a planned reboot and that I failed a bug check, pretty generic faults that don't point me to which worker thread failed. I was hoping if it was the same worker each time it could indicate a specific CPU core that was at fault and warranty the CPU.



I'll try setting the debug switch anyway. Are there any other ways to log or to incrementally save the text output in the Prime95 worker window?

[Prime95]

Originally Posted by Bitter

Are there any other ways to log or to incrementally save the text output in the Prime95 worker window?

I'm afraid you are out of luck.

FWIW, a bad CPU core is really rare. The most common culprit is RAM. Try a small FFT torture test (more CPU-only testing, little RAM testing).

[Bitter]

Originally Posted by Prime95

I'm afraid you are out of luck.

FWIW, a bad CPU core is really rare. The most common culprit is RAM. Try a small FFT torture test (more CPU-only testing, little RAM testing).

I know it's rare but with how Ryzen boosts it's possible that one isn't stable at boost speeds I suppose. It runs small FFT without fail, pretty sure the whole thing fits in the 16MB L3 cache so no RAM is tested. I have a smaller set of RAM that's the same speed to swap in for overnight testing I'm going to try out but I have a funky feeling about the board/cpu since I noticed more than normal vdroop on the SOC voltage readings and it doesn't like the post after changing that voltage up to compensate for the droop, sometimes beeping out a memory error code sometimes just not posting at all.

[VBCurtis]

If it's passing a test that fits in cache, but fails work that doesn't fit in cache, you have a really strong indication that RAM is not good while CPU is good.
It's possible the motherboard is bad, too- there is such a thing as a RAM channel being bad on a board, for instance.

[retina]

Originally Posted by Bitter

Event viewer has only informed me that it wasn't a planned reboot and that I failed a bug check, pretty generic faults ...

At the risk of simply reiterating what the previous posters said: Check your RAM. Or perhaps if you are lucky, your RAM timing settings. Slow it down, get it stable, then bring it up slowly till it fails, back it off a small amount, and done.