Windows XP crash after game install

thunderbird12 · 04-29-2004, 12:06 PM

I purchased the OOTP6 and downloaded the last patch last Friday and was having a blast with it ever since. However, after installing the game, my computer began to act in an unusual fashion. The game ran just fine, but whenever I ran the game, my computer would not reboot properly the next time I started it up... it would just hang with a blank screen and I would have to power it off and turn it on again. Then, it would boot up, but only after running the disk check utility that usually starts up after an improper shutdown. This problem only seemed to occur if I ran the game... if I started the computer, did whatever, and shut it down without ever running the game, it would start up without a problem the next time I powered it on.

Then, last night, my computer would not start up at all. Instead, I was greeted with the error message:

Windows could not start because the following file is missing or corrupt:
\WINDOWS\SYSTEM32\CONFIG\SYSTEM

It appears to be the problem described in this article:

http://support.microsoft.com/?kbid=307545

My initial attempts to restore the system have not been successful, though I haven't had much of a chance to research the problem yet. Hopefully I will have better luck when I get home from work today.

My system is a Dell Inspiron 8100 notebook, with a 1 Ghz processor and 256 MB of RAM. The last time I checked (a couple of weeks ago), I had over 8 GB of available memory. I was running Windows XP home. This is the first time I have had any problems with XP since upgrading about 9 months ago from Windows ME. I perfomed a Windows update about 3 weeks ago, but did not have any problems until installing OOTP6 last Friday.

I am not suggesting that the game did anything malicious to my OS, but the installation of the game did seem to trigger whatever problem I am having now, unless the timing was purely coincidental. Any ideas as to what might have caused this? After quickly checking this forum, I didn't any find any other similar reports of this kind, so this may just be a problem with my particular system.

04-29-2004, 12:06 PM	#1
thunderbird12 Bat Boy Join Date: Apr 2004 Posts: 2	Windows XP crash after game install I purchased the OOTP6 and downloaded the last patch last Friday and was having a blast with it ever since. However, after installing the game, my computer began to act in an unusual fashion. The game ran just fine, but whenever I ran the game, my computer would not reboot properly the next time I started it up... it would just hang with a blank screen and I would have to power it off and turn it on again. Then, it would boot up, but only after running the disk check utility that usually starts up after an improper shutdown. This problem only seemed to occur if I ran the game... if I started the computer, did whatever, and shut it down without ever running the game, it would start up without a problem the next time I powered it on. Then, last night, my computer would not start up at all. Instead, I was greeted with the error message: Windows could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM It appears to be the problem described in this article: http://support.microsoft.com/?kbid=307545 My initial attempts to restore the system have not been successful, though I haven't had much of a chance to research the problem yet. Hopefully I will have better luck when I get home from work today. My system is a Dell Inspiron 8100 notebook, with a 1 Ghz processor and 256 MB of RAM. The last time I checked (a couple of weeks ago), I had over 8 GB of available memory. I was running Windows XP home. This is the first time I have had any problems with XP since upgrading about 9 months ago from Windows ME. I perfomed a Windows update about 3 weeks ago, but did not have any problems until installing OOTP6 last Friday. I am not suggesting that the game did anything malicious to my OS, but the installation of the game did seem to trigger whatever problem I am having now, unless the timing was purely coincidental. Any ideas as to what might have caused this? After quickly checking this forum, I didn't any find any other similar reports of this kind, so this may just be a problem with my particular system.