Error 0x0 and 0x1
From FaHWiki
The 0x0 and 0x1 errors are unknown errors - all errors that are known will end with some other error code and message, but those errors that Pande Group hasn't seen before or did not know about, will end with error 0x0 or 0x1.
One of the common causes of these errors is memory errors. If your RAM has a marginal component or is overclocked or the voltage is low, you're likely to get random errors 0x0 or 0x1. (In some cases, FAH seems to be a more challenging test of memory than the diagnostics, but run them anyway.)
Note: The WU data of an unknown error can not be trusted and by definition you'll never get any credit for it. If the 0x0 and 0x1 error cause is identified and classified as some sort of EUE then you'll start getting credit for such WUs. One possible cause of errors 0x1 and 0x0 is a hardware failure (which is why the software is unable to classify them). If a RAM failure is detected by the OS or for some reason the program wishes to allocate more memory and the OS refuses, the OS will terminate FAHcore_* and the client will no longer be able to communicate with the FAHcore producing Client-core communications error: ERROR 0x1
0x0 errors are Unix Specific and under Linux this error often can be related to Glibc incompatibility.
Note: When using the Gromacs core on Linux, this error is also generated in circumstances where the Windows core would produce a "Gromacs Cannot Continue further" EUE. Unfortunately Pandegroup are currently unsure how WUs are triggering this error. As a result a normal EUE is not triggered, and the whole WU gets dumped and lost. Folding-community: Guha Jayachandran's comment in "Core status 0?"
Under the Gromacs33 (A0) core, this error is returned because even though the cause is known, it has not yet been categorised. The error creates an output in the log similar to this:
Warning: 1-4 interaction between and at distance 0.000 which is larger than the 1-4 table size 8.298 nm
One possible cause for error 0x0 is forgetting to redirect the standard output. If you're running in the background without a command such as './fah5 -verbosity 9 >/dev/null 2>&1 &', the simulation will probably get past 100% and then create an error.
These are ignored for the rest of the simulation This usually means your system is exploding, if not, you should increase table-extension in your mdp file
It should be noted that you yourself cannot increase the table-extension, it is an integral part of the WU
Error 0x1 is not always an "unknown error" When a WU expires, you may receive this error:
Could not transmit unit 02 to Collection server; keeping in queue. + Sent 0 of 1 completed units to the server - Autosend completed Unit 2's deadline (January 14 07:58) has passed. - Warning: Could not delete all work unit files (2): Core returned invalid code - Autosending finished units... Trying to send all finished work units + No unsent completed units remaining. - Autosend completed CoreStatus = 1 (1) Client-core communications error: ERROR 0x1 Deleting current work unit & continuing... - Warning: Could not delete all work unit files (3): Core returned invalid code Trying to send all finished work units + No unsent completed units remaining.
One cause for error 0x1 is the software needed more space that was available in some table. The GPU2 client/core will issue an error 0x1 message if the Aperture setting for the video card is too small.
Check this thread:
Folding-community: Another error 0 on a linux box p1487
0x1 errors are Windows Specific.
If the same WU is failing multiple times at the same spot then this WU is likely faulty and should be removed from circulation. These errors should get reported in the forum (include system specs, and project, run, clone and generation numbers).
- [Early_Unit_End#Reporting_EUEs|Reporting EUEs]]
Reference Links
