Kuka alarm 13 connection closed by realtime system error 10053

[JMinnesota]

Hello,
My KR60HA with a KRC2 controller brought up
"Kuka alarm 13 connection closed by realtime system error 10053"
then the keyboard was non-responsive after that.
I shut off the power, and turned it back on, and it seemed to start up correctly after that.

Have you seen this error before?
Any suggestions about what might be causing it?
Thanks!

[SkyeFire]

Which KSS version are you running? 

That error isn't one I'm familiar with, but at a guess I'd say that something killed the virtual network communication between the VxWorks realtime-os "virtual machine" and the Windows XP sides of the controller. 

This kind of thing can happen sometimes for no apparent reason, but it's pretty rare. Odds are you'll never see it again.  However, if you do, it could be an indication of something that needs to be addressed.  My first response in that case would be to wipe the controller clean and do a fresh install of XP and KSS from the install disks.  If it happens again after tha, I'd either replace the HD, RAM, and/or Motherboard, or just go whole-hog and replace the entire PC rack unit.

[JMinnesota]

This is what the Help -> Info window says on the robot:

KRC
V5.2.14
GUI Version:
1.2.32.0 B73

Kernel system version:
 KS V6.74_38 (krc1adm@pc40225) Tue Feb
 28 11:15:00 WN 2006 RELEASE

[optimus_prime]

Normally from loose connection of MFC-DSE Card with motherboard n vibrations...
Ensure Virus free environment....

[markopo]

Hello.
I've got this same problem on one of our robot. Til today there was changed HD, but problem still stays and time-to-time I have to reboot machine and everything works fine to next rebooting.
My question is that is problem with CARD or whole connection to robot (inc. wires, plugs etc.) ?
Marek