Difference between revisions of "Unrecoverable error for result "result" (There are no child processes to wait for. (0x80) - exit code 128 (0x80)"
(Adding FAQ 69) |
(adding table) |
||
Line 8: | Line 8: | ||
With ATI GPU usage, the drivers needed to run Milkyway and Collatz are converted from a amdxxxxx.dll to ATIxxxxx.dll these changes occur with the newer and latest driver updates. a copy and rename in the system32 folder is all that it takes to fix this problem. | With ATI GPU usage, the drivers needed to run Milkyway and Collatz are converted from a amdxxxxx.dll to ATIxxxxx.dll these changes occur with the newer and latest driver updates. a copy and rename in the system32 folder is all that it takes to fix this problem. | ||
+ | |||
+ | |||
+ | {| class="wikitable" style="text-align: center;" | ||
+ | ! Original writer | ||
+ | ! Original FAQ | ||
+ | ! Date | ||
+ | |- | ||
| Jorden | | Jorden | ||
− | | | + | | [http://boincfaq.mundayweb.com/index.php?language=1&view=69 69] |
− | + | | 21-12-2006 | |
− | | | + | |- |
− | + | |} | |
− | |||
− | | | ||
− | |||
− | |||
− | | |
Revision as of 22:27, 29 August 2016
If you encounter an error called Unrecoverable error for result "result" (There are no child processes to wait for. (0x80) - exit code 128 (0x80)), your DirectX version is out of date.
Please update your DirectX version through Windows Update, or get it from here. (August 2009 redistributable edition, multi-language, 103.3MB)
One other possible cause for this is when the programmer of the application has used .NET technology to make his application. Then you need to install .NET on your computer. It's only available to Windows computers and then only to Windows 2000 and above.
So if you encounter this error after you updated your DirectX to the latest available version, post about it on that project's forums and ask if they used .NET to make their application.
With ATI GPU usage, the drivers needed to run Milkyway and Collatz are converted from a amdxxxxx.dll to ATIxxxxx.dll these changes occur with the newer and latest driver updates. a copy and rename in the system32 folder is all that it takes to fix this problem.
Original writer | Original FAQ | Date |
---|---|---|
Jorden | 69 | 21-12-2006 |