Jon Speelman
Chieftain
Hi,
I'm playing BtS3.13 (with the Bhuic patch re the Glance screen)
I've had a problem in the last few days that when I exit to the desktop (after it's handled perfectly well during the game itself) the machine reboots itself - and then comes back to life from a "serious System Crash - event 1003.
Originally, I could just ALT F4 with no prob. Then I started using "Exit to Desktop" but that caused the same problem . So I then started first to exit to the Main Meniu and then the the desktop. This normally works, espcially if I pause for a few seconds but sometimes causes the reboot as well.
I presume that this is a graphics card issue -the card is an ATI Radeon HD 2900; or something to do with memory pages and purged this once (ie set virtual mem to 0 and rebooted before resetting) but this didn' help at all.
If so, I can take it up with the manufacturer sicne it's a new machine - just about a month old. But I was checking in case other people had had the same problem and it was a memory leak or something and not hardware?
Thanks,
Jon
I'm playing BtS3.13 (with the Bhuic patch re the Glance screen)
I've had a problem in the last few days that when I exit to the desktop (after it's handled perfectly well during the game itself) the machine reboots itself - and then comes back to life from a "serious System Crash - event 1003.
Originally, I could just ALT F4 with no prob. Then I started using "Exit to Desktop" but that caused the same problem . So I then started first to exit to the Main Meniu and then the the desktop. This normally works, espcially if I pause for a few seconds but sometimes causes the reboot as well.
I presume that this is a graphics card issue -the card is an ATI Radeon HD 2900; or something to do with memory pages and purged this once (ie set virtual mem to 0 and rebooted before resetting) but this didn' help at all.
If so, I can take it up with the manufacturer sicne it's a new machine - just about a month old. But I was checking in case other people had had the same problem and it was a memory leak or something and not hardware?
Thanks,
Jon