Purple and pink screen of death.
from
Stardock Forums
Something happened to my first attempt to post this and it vanished. But, I got it again.
The first time it happened it was as if my display unsynced - it had narrow horizontal rows of groups of mostly purple and pink
lines of perhaps 2-3 pel vertially by about 160 pel horizontally. There were 8 distinct vertical rows. There were also a lot of
yellow lines and some orange lines.
The second time the lines were almost entirely blue with white speckles.
In both cases the system froze. Only the brute force power off had any affect (a steady push of the power button for 5-10 seconds).
This looks like what would happen if the program got a bad pointer and started storing data in the memory reserved for the display
adapter card.
The first time the debug file had an error message in it that SmartExceptioln was unable to open the file into which it stores the
exception report. The second time the debug file had no indication of errors whatsoever, not even any indications of memory management
errors. However, there was this message:
--------
Debug Message: No AutoSave files in current directory.
-----------
Just in case something can be done with the autosave files I am sending them and the debug file to Cari.
The first time it happened I was left clicking on the main screen to clear either the planet list or ship list (no longer remember
which). This time I was just looking at the screen contemplating my next action (for about 3-5 seconds).
Cheers,
Jack
The first time it happened it was as if my display unsynced - it had narrow horizontal rows of groups of mostly purple and pink
lines of perhaps 2-3 pel vertially by about 160 pel horizontally. There were 8 distinct vertical rows. There were also a lot of
yellow lines and some orange lines.
The second time the lines were almost entirely blue with white speckles.
In both cases the system froze. Only the brute force power off had any affect (a steady push of the power button for 5-10 seconds).
This looks like what would happen if the program got a bad pointer and started storing data in the memory reserved for the display
adapter card.
The first time the debug file had an error message in it that SmartExceptioln was unable to open the file into which it stores the
exception report. The second time the debug file had no indication of errors whatsoever, not even any indications of memory management
errors. However, there was this message:
--------
Debug Message: No AutoSave files in current directory.
-----------
Just in case something can be done with the autosave files I am sending them and the debug file to Cari.
The first time it happened I was left clicking on the main screen to clear either the planet list or ship list (no longer remember
which). This time I was just looking at the screen contemplating my next action (for about 3-5 seconds).
Cheers,
Jack