RoboDK 5.6.5.23784 can terminate while generating a robot program for a Yaskawa GP50 project on Windows 11. The recorded application exception is 0xc0000005. The evidence does not establish a root cause, but it defines a repeatable isolation and diagnostic-capture procedure.
Identify the Failure Signature
| Field | Observed value |
|---|---|
| Application | RoboDK Win 64 bit |
| Application version | 5.6.5.23784 |
| Operating system | Windows 11 |
| Robot model | Yaskawa GP50 base model |
| Trigger | Generate a robot program from a Python script, including with F6
|
| Exception code | 0xc0000005 |
| Error offset | 0x000000000a02d9 |
| Faulting executable and module | C:\RoboDK\bin\RoboDK.exe |
The observed sequence is a loading indicator followed by an abrupt application exit. Windows Event Viewer reports both a .NET runtime error and an application error, with RoboDK.exe named as the faulting application and module.
Separate Project and Computer Effects
The crash occurred with the hexagon drawing example and with a default Python script, so the evidence does not isolate the problem to one script. A fresh installation did not correct the affected computer, while the same workflow worked on another PC. These results support investigating computer-specific state, but they do not prove which setting or local component causes the exception.
The issue was not reproduced with the supplied workflow in another environment. Preserve and provide the RDK project that triggers the failure because project state remains part of the diagnostic evidence even when multiple scripts produce the crash.
Reset Settings and Capture the Debug Log
- Open Tools > Options and select Set Default settings.
- Repeat program generation from the Python script by selecting Generate robot program or pressing
F6. - If RoboDK still crashes, close it and launch
C:/RoboDK/RoboDK-Debug.bat. - Reproduce the program-generation crash once more.
- Immediately after the crash, preserve
C:/RoboDK/bin/RoboDK.debug.txtand provide it through an official RoboDK support channel together with the failing RDK project.
Resetting default settings did not resolve the reported case, so do not treat that action as a confirmed fix. Its diagnostic value is to test whether saved RoboDK configuration contributes to the failure.
Verify the Result
After any corrective change, reopen the same GP50 project and generate the same robot program. Consider the change verified only if generation completes without RoboDK exiting and no matching 0xc0000005 application error appears in Windows Event Viewer. If the failure remains, retain the debug log, project file, RoboDK build number, and Event Viewer fields so the failing and working PCs can be compared without changing multiple variables at once.
FAQ
Why does RoboDK crash when generating a Yaskawa GP50 program?
The recorded failure uses exception code 0xc0000005 in RoboDK 5.6.5.23784, but the available evidence does not establish the root cause. The workflow works on another PC and fails with more than one Python script, indicating that the investigation should include computer-specific state and the RDK project.
Where is the RoboDK debug log after a program-generation crash?
Launch RoboDK with C:/RoboDK/RoboDK-Debug.bat, reproduce the crash, and then collect C:/RoboDK/bin/RoboDK.debug.txt immediately afterward.
Will resetting RoboDK default settings fix error 0xc0000005?
Reset settings through Tools > Options > Set Default settings and retest. This did not fix the reported case, so capture the debug log and failing RDK project if the crash continues.
