Computer Crash
 

I realize it may just be a coincidence, but I've had intermittent computer crashes (BSOD) since downloading 5.1b, all of them either during or shortly after playing the game on my Windows XP SP2 system. I've not had it happen while using other programs (unless FOF is up at the same time). The BSOD message is "Kernal-Stack-Inpage-Error" and indicates a dump of physical memory. (I am not a computer whiz, so I don't really know what any of that means!)

Microsoft reports that one possibility is a problem with "inconsistent data sectors on my hard drive," but checking my hard drive has not revealed any problems. Another Microsoft-recommended effort at fixing the problem is to uninstall new software, but the only "new" software I have are the FOF2004 upgrades, as well as updates of Ad-Aware and Spybot. I really do not want to uninstall FOF2004 -- which is my alltime favorite sports sim (and I've been playing them since 1965!) -- if it is highly unlikely to be the problem.

Any thoughts or suggestions. :confused:

bored and trying to help you...found this on some forum

Stop Error 0x00000077
Stop error number:

(0x00000077)


Descriptive text:

KERNEL_STACK_INPAGE_ERROR


Usual cause:

The requested page of kernel data from the paging file could not be read into memory.



To troubleshoot Stop error 0x00000077
Using a current version of your virus-protection software, check for viruses on your computer. If you find a virus, perform the steps required to eliminate it from your computer. See your antivirus software documentation for these steps.

If the computer is formatted with NTFS, restart your computer, and then run Chkdsk /f /r on the system partition. If you cannot start the system due to the error, use the Command Console and run Chkdsk /r.

Run any system diagnostics supplied by your computer manufacturer, especially the memory check.

Disable BIOS memory options such as caching or shadowing.

dola

here's a link to the MS support DB on it

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

also

http://support.microsoft.com/default...b;en-us;315266

no problem. damn MS and SP2 for being a janky piece of garbage!

Thanks. I'm going to try to follow-up on these approaches. With any luck, one of them will lead to the identification of the problem so I can get it corrected.