Message boards :
Number crunching :
A handful of STATUS_ACCESS_VIOLATIONs
Message board moderation
Author | Message |
---|---|
MossyRock Send message Joined: 9 Jul 13 Posts: 19 Credit: 19,863,818 RAC: 22 |
Until a few days ago, my Ryzen 7 1700 system has been running Seti@Home tasks with no errors. https://setiathome.berkeley.edu/show_host_detail.php?hostid=8298163 Now, I'm getting about one or two failures a day with the exit status of "-1073741819 (0xC0000005) STATUS_ACCESS_VIOLATION". These failures are for tasks that ran on the CPU cores, not the GPU. https://setiathome.berkeley.edu/results.php?hostid=8298163&offset=0&show_names=0&state=6&appid= Everything on the system is at stock settings. The CPU never goes above 55 C. These failures began right after we had a power surge and a power outage which destroyed my CyberPower UPS. Right now the system is running on just a surge protector strip until I receive a replacement UPS. I would think that if the power surge damaged my system then I would be seeing symptoms much worse than this. Any ideas on what may be causing this? Thanks. |
Brent Norman Send message Joined: 1 Dec 99 Posts: 2786 Credit: 685,657,289 RAC: 835 |
Looking at your log, I would do memory and disk checks. |
MossyRock Send message Joined: 9 Jul 13 Posts: 19 Credit: 19,863,818 RAC: 22 |
MemTest86, Prime95, chkdsk, Samsung magician - all show no hardware problems. |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13736 Credit: 208,696,464 RAC: 304 |
I would think that if the power surge damaged my system then I would be seeing symptoms much worse than this. Do you have a multi-meter? If so, i'd check the rails to see how close to specification they are. While a power surge will usually result in the death of a device, it's not unusual for it to result in the death of one or 2 components that result in poor regulation as opposed to complete failure. Grant Darwin NT |
MossyRock Send message Joined: 9 Jul 13 Posts: 19 Credit: 19,863,818 RAC: 22 |
Will using HWMonitor suffice? Here are the min/max readings I got from running HWMonitor for about 12 hours: 3.3v: 3.312 to 3.344 +5: 4.992 to 5.016 12v: 12.144 to 12.250 Looks stable to me. |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
Could system file corruption be causing the problem? Other applications may not use the same API calls as SETI and so may show normal operation despite other applications still having issues. I'd run a CHKDSK /F and let that run after reboot. If that doesn't solve, then if you have UAC enabled, open an elevated CMD prompt and perform an SFC /SCANNOW. If both those come back clean, I'd re-install of BOINC to refresh folder and file permissions. Then a project reset to force BOINC to re-download the SETI executables. This should definitely come after checking system files. This way, we're working backward from the OS to the application. |
MossyRock Send message Joined: 9 Jul 13 Posts: 19 Credit: 19,863,818 RAC: 22 |
CHKDSK /F and SFC/SCANNOW found nothing. I think I'm chasing a phantom here. No new workunits have crashed. I'll reinstall BONIC from scratch when the next release comes out. Thanks for all your help. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.