Where can I look up what this error is to maybe point me towards a resolution.

On one specific box I have about 25 valid to 125 that errored out with this message.

Skip

https://www.sidock.si/sidock/results.php?hostid=54582

Code 195 comes from the BOINC wrapper reporting that the science app (CmDock) exited with an error. The clue to that error is in the task output app exit status: 0x8b, indicating it exited due to a SIGSEGV. If this is the only machine experiencing this issue, it most likely points to a hardware problem such as faulty memory or unstable overclocking.

Code 195 comes from the BOINC wrapper reporting that the science app (CmDock) exited with an error. The clue to that error is in the task output app exit status: 0x8b, indicating it exited due to a SIGSEGV. If this is the only machine experiencing this issue, it most likely points to a hardware problem such as faulty memory or unstable overclocking.

It was the only box experiencing this error recently.

I was having another issue on this box occasionally locking up the desktop and over a couple weeks had been lowering the CPU clock multiplier and/or raising the vcore... with little success. Earlier today I bumped the Vdimm from 1.34v to 1.345v (DDR4 3600, CL16) and I've not had the desktop lockups for 7 hours now even with pushing the CPU clock back up just a bit.

With that progress and your info provided above I took SiDock off of NNT for a bit & got 5 new WUs. Those are running now. We'll see come tomorrow if this slight bump in Vdimm also resolves the SiDock errors. They've been running for ~50 minutes so have a ways to go.

Thanx much, Skip

1 of 5 errored out with same error... bumped Vdimm to 1.35v w/ other 4 still running @ ~31% complete.

1 of 5 errored out with same error... bumped Vdimm to 1.35v w/ other 4 still running @ ~31% complete.

SOLVED