| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: Mapping Cancer Markers Forum
Thread: MCM1 x64 tasks fail with error |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 6
|
|
| Author |
|
|
ST240
Cruncher Joined: Feb 15, 2024 Post Count: 14 Status: Offline |
Hi,
All the MCM1 x64 tasks I am receiving are getting an error a few seconds after starting. The x86 version seems to be okay. The error is: Unhandled Exception Detected... - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x00007FF?????88FD write attempt to address 0x?????040 The "?" indicates that these digits can be different for each task. |
||
|
|
bfmorse
Senior Cruncher US Joined: Jul 26, 2009 Post Count: 294 Status: Offline Project Badges: 
|
Try a reboot and select cmos tests then run the memory test.
See if that discovers the source of the problem. Keep us informed and happy crunching (when you can get it to behave properly)😎 |
||
|
|
ST240
Cruncher Joined: Feb 15, 2024 Post Count: 14 Status: Offline |
This is happening on all of my computers. I verified that they are all stable. There are no errors in any tests. Temperatures are low. They all have Windows 10 with the latest updates.
I will see if I can find out what the issue is. :) |
||
|
|
Bryn Mawr
Senior Cruncher Joined: Dec 26, 2018 Post Count: 337 Status: Offline Project Badges: 
|
Zero errors here on Boinc 8.0.4 under Ubuntu 22.04.5 and 24.04.1 running on Ryzen 9 3900
|
||
|
|
ST240
Cruncher Joined: Feb 15, 2024 Post Count: 14 Status: Offline |
Okay, I found the issue. It appears the x64 version of MCM1 does not work if "High-entropy ASLR" is set to "On by default" in Windows 10 Exploit protection settings. MCM1 does work if it is set to "Use default (On)" or "Off by default".
This is strange because "Use default (On)" should be the same as "On by default", unless "Use default (On)" only applies it to some programs. If "High-entropy ASLR" is set to "Use default (On)" or "Off by default", and enabled specifically for MCM1 (wcgrid_mcm1_map_7.61_windows_x86_64.exe) it works fine, which would indicate that MCM1 is compatible with "High-entropy ASLR". But MCM1 does not work when "High-entropy ASLR" is set to "On by default" even if it is disabled specifically for wcgrid_mcm1_map_7.61_windows_x86_64.exe. This would indicate that MCM1 (x64) does not like when "High-entropy ASLR" is enabled for other programs and processes. I have not had issues with any other program when "High-entropy ASLR" is enabled on the system, so maybe there is a bug in the x64 version of MCM1. |
||
|
|
ST240
Cruncher Joined: Feb 15, 2024 Post Count: 14 Status: Offline |
Never mind, wcgrid_mcm1_map_7.61_windows_x86_64 actually doesn't have the extension .exe, so it is just MCM1 that is not compatible with "High-entropy ASLR". It seems that disabling High-entropy for wcgrid_mcm1_map_7.61_windows_x86_64 (no file extension) fixes the issue.
----------------------------------------:) [Edit 1 times, last edit by ST240 at Nov 22, 2024 2:58:16 AM] |
||
|
|
|