A KUKA controller running KSS 7.1 and WinXPe 2.2 can accept a RoboDK connection and return the current robot position while still failing configuration and program transfer. In the observed case, the controller-side C3 Bridge Interface Server terminated with exception 0xc0000096, and RoboDK separately reported that C:/KukaShared could not be found or created.
Separate the confirmed behavior from the unknown cause
| Item | Observed result |
|---|---|
| Robot/controller | KR5sixx R850 with KSS 7.1 and WinXPe 2.2 |
| RoboDK | Version 5.9.4 using the kukabridge driver |
| Basic communication | Connection succeeds and current robot position is available |
| C3 Bridge 1.7.1.0 | Server terminates during KUKA Driver Auto Configuration |
| C3 Bridge 1.8.1.0 | The same failures remain after retesting |
| C3Easy 1.0.2.0 | Also causes the C3 Bridge Interface Server to terminate |
| Program transfer | Fails for remote path C:/KukaShared
|
The evidence confirms the failing application and exception, but it does not establish whether the privileged instruction originates from operating-system compatibility, the controller platform, or another component. Do not treat basic position feedback as proof that configuration and file-edit functions are operational.
Troubleshoot the C3 Bridge exception
The exception Privileged Instruction. (0xc0000096)
occurred in the application at location 0x00b20092C3 Bridge version 1.8 added support for most features on older platforms, so updating from 1.7.1.0 is the first supported compatibility check. However, the reported controller produced the same result with 1.8.1.0; an upgrade alone therefore did not resolve this specific KSS 7.1 and WinXPe 2.2 installation.
- Record the controller, operating-system, RoboDK, C3 Bridge, and C3Easy versions shown in the table.
- Reproduce the failure with C3 Bridge 1.8.1.0 and capture the complete exception text, including
0xc0000096and location0x00b20092. - If automatic configuration still terminates the server, stop relying on that operation and apply the required KUKA driver configuration changes manually.
Handle the C:/KukaShared transfer failure
RoboDK reports Remote path not found or can't be created C:/KukaShared even though the directory exists, is shared, grants Full Control to Everyone and KUKA03\target, and is reachable through the controller FTP server using an anonymous account. Those tests verify directory existence and access through other mechanisms; they do not verify that C3 Bridge can edit files.
The available evidence links program transfer to the C3 Bridge problem and identifies controller-side denial of file editing as a possible condition on some control systems. When automatic editing fails, manually enter all required driver configuration changes using the documented KUKA driver configuration process, then repeat the transfer test.
Verify the recovery
First confirm that the bridge remains running while the configuration operation executes. Then retry Send Program(s) to robot and verify that RoboDK no longer reports the remote-path error. Directory sharing and anonymous FTP access are supporting checks, but successful bridge-based configuration and program transfer are the decisive verification results.
FAQ
What does KUKA C3 Bridge error 0xc0000096 mean in this case?
It is the privileged-instruction exception that terminates the C3 Bridge Interface Server during automatic configuration. The evidence does not identify the underlying compatibility or operating-system cause.
Does C3 Bridge 1.8.1.0 fix KSS 7.1 configuration crashes?
Not in the reported KSS 7.1 and WinXPe 2.2 installation. The same configuration, C3Easy, and transfer failures remained after replacing version 1.7.1.0 with 1.8.1.0.
Why does RoboDK reject C:/KukaShared when FTP works?
FTP access and share permissions do not prove that C3 Bridge can edit controller files. If the bridge cannot perform automatic edits, enter the required KUKA driver configuration changes manually and retest program transfer.
