https://boinc.bakerlab.org/rosetta/results.php?hostid=1188956

As you can see, my PC gave many many errors on plenty of WUs, and then suddenly stopped and went back working properly. I updated it's graphics card drivers and BOINC version to "fix" the error. (There were graphics errors, black boxes in the titles... etc. which gave me a clue as to what the problem could be.)

The weird part is, that while it gave Rosetta errors, it only gave 1 or 2 Collatz Conjecture errors (GPU Only)... EVEN though the problem was fixed AFTER a GRAPHICS driver update and BOINC update...

Can anyone understand the info that came back with the WUs and pin point the problem? All failed WUs failed right at the start, suggesting a software rather than a hardware problem (heat... etc)

Thanks.

---

Setting up folding (abrelax) ...


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x0094700B write attempt to address 0xFFFFFF7A

Engaging BOINC Windows Runtime Debugger...

This is the information from the task page. I do not know what has caused this error but it seems like rosetta can't access/write the files it needs.
Have you tried resetting the project?

PS. It looks like WU are still failing on that machine, last computution error was reported today.

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x0094700B write attempt to address 0xFFFFFF7A

This is actually an Access Violation: The application tried to access memory out of the range that's owned by it.
This could by a driver issue, but usually it's an faulty pointer in a process. This could be faulty WUs (which I acrually doubt, since I have had only three compute errors in the last 400 WUs). This could as well be a hardware problem (CPU or memory failing).

Hard to tell, even harder to give any advice. If it was my computer, I would run some stress tests (Prime95 for CPU and Memory, Furmark for Graphics Card). Maybe this gives a hint...

Good luck!

Joe

---

357381146 357381134 & 357381125 all tasks start with lrm_jorj_combined_tlrm_jorj_combined_torsion. All tasks end with Compute error. I'm thinking lrm_jorj_combined_tlrm_jorj_combined_torsion is a bad bad batch of tasks.

---

Have a crunching good day!!

357381146 357381134 & 357381125 all tasks start with lrm_jorj_combined_tlrm_jorj_combined_torsion. All tasks end with Compute error. I'm thinking lrm_jorj_combined_tlrm_jorj_combined_torsion is a bad bad batch of tasks.

Yes I had a couple of those as well last night.
Error:
ERROR: Unable to open weights. Neither ./dslf_weights.wts nor dslf_weights.wts nor minirosetta_databasescoring/weights/dslf_weights.wts exist
ERROR:: Exit from: ....srccorescoringScoreFunctionFactory.cc line: 178
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

As well I had this task with a compute error:
cs-only-2-sen15_8-6_20161_233_1
Error:
ERROR: rsd_type_list.size()
ERROR:: Exit from: ....srccorefragmentFrame.cc line: 62
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

But Chilean got access violations, wich I rather consider to be hardware related.

cu Joe

---

Seems to be running fine overall, except for the 2 errors I've gotten so far since the big incident. The PC is slightly overclocked (3.2 -> 3.3). I'll put it back to default.

---

Seems to be running fine overall

Did you do some stress-testing with Prime 95? I use it for testing the system stability of my OCed computer.

But if the errors go away with standard clocks, you'll know as well. ;)

cu Joe

---