B4D - someone fumbled a constructor on autopilot and my PC froze.
from 
Stardock Forums
Stardock Forums
I am not sure if the fumble was by me or the game, but it resulted in a hard freeze of my PC.
I had LOTS of constructors on autopilot, flying all over a gigantic galaxy, mostly to tiles next to star bases. During the auto-pilot phase several of the constructors reached their destination with moves left. I moved them onto the star bases to upgrade them until I got to one that I had sent directy to the star base. When I checked to see if I could upgrade it I realized I wanted to look at the other sectors surrounding the one the star base was in to see if I wanted to build an influence upgrade, so I canceled the upgrade. Then it felt like I had lost control so I tried to move the constructor to an adjacent tile. The game gave me a few more move completions, then proceeded into a locked up bit twirl, which, on Win/ME requires you to reboot the PC from a power down/up (cooperative multitasking is wonderful that way, not at all like the excellent preemptive multitasking OS/2 had).
I had LOTS of constructors on autopilot, flying all over a gigantic galaxy, mostly to tiles next to star bases. During the auto-pilot phase several of the constructors reached their destination with moves left. I moved them onto the star bases to upgrade them until I got to one that I had sent directy to the star base. When I checked to see if I could upgrade it I realized I wanted to look at the other sectors surrounding the one the star base was in to see if I wanted to build an influence upgrade, so I canceled the upgrade. Then it felt like I had lost control so I tried to move the constructor to an adjacent tile. The game gave me a few more move completions, then proceeded into a locked up bit twirl, which, on Win/ME requires you to reboot the PC from a power down/up (cooperative multitasking is wonderful that way, not at all like the excellent preemptive multitasking OS/2 had).