I bought a K8V-X 64 bit motherboard. It has the VIA K8T800 Chipset. It's super fast, but will not run FS9. It bombs out after a few minutes with a loud noise and a message "memory dump in progress", It then freezes the entie computer.Any suggestions would be helpful..Gary

Check the system event viewer and see what process/application caused the crash. It should show a .dll or file, other than FS9, that caused the crash. Could have been corrupted video card/sound card drivers. The process/application that caused the crash will give you an idea. There are so many possibilities. For instance, say you installed FS9 and updated it to FS9.1. You also installed ActiveCamera but didn't install the upgrade so it will work with FS9.1. Your system will crash everytime. So it's important that you also indicate exactly what the message was after the crash and you can find that in the event viewer.Jim

How does one view the Event Viewer?

Manny,Right click My Computer, select Manage/System Tools/Event Viewer. There are 3 log files available, Application, Security, and System. Hope this helps

I've checked the event timer and found nothing wrong. I used a program called checkit to see if there was a memory problem. I don't know how through the program is but it found no problem. Since FS9 used a lot of memory, could the problem be in the memory somewhere?I also installed Fs2002 and it bombed out the first time I used it, but the second time it did not. Now I'm really confused.Gary

"I've checked the event timer and found nothing wrong."That's unreal! Your computer crashes and no event(s) were recorded? I've never heard of that before but from what you stated it must happen occasionally. In order to be helped, you need to check any error message and write it down. Then maybe someone can figure out what's causing it. Like I said before, there could be several reasons for a crash. Video cards, sound cards, bad memory, memory address conflicts, overheating of the system, corrupted scenery.cfg, duplicate AFCADS, corrupted FS9.cfg, a corrupted or missing FS9 dll, incorrect registry entries, a computer virus, aircraft improperly installed, scenery improperly installed, and/or FS9 improperly updated are some reasons to name just a few. You might try an uninstall and reinstall of FS2K4 and then run it without any addons to see if crashes continue. If crashes continue, then it is more than likely a hardware problem and not FS9. In addition, you stated you checked your installed memory using the program checkit and no problems were found. A memory dump (which you stated originally occurred) does not necessarily mean bad memory. It usually means there was a system conflict somewhere and the system had to shut down. For instance, a PCI card may not be seated properly. You might want to visit the following site to see the various causes of Memory Dumps or do your own google search: http://labmice.techtarget.com/troubleshoot...memorydumps.htmHope this helps.Jim

I had re-installed XP and did all the updates. Then I installed the Creative Sound Card. Then I installed FS9. I ran it and got the error.I guess that means I should uninstall the sound card and try again, right...BTW FS2002 is working correctly now with interruption.Gary

OK, I want everyone to visualize what I see when this happens.Start FS9FS9 runs for about 60 secondsThen Windows blue screen shut down with the following message.MACHINE_CHECK_EXCEPTIONTechnical Info...STOP 0X0000009C (0X00000004), 0X8054FF0, 0XB2000000,0X00070F0FBeginning Dump Of Memory..Hope this helps someone to figure out what's happening..Gary

Hi Gary,I did find this googling your error. Hopefully it will help point you the right direction.http://support.microsoft.com/?kbid=329284

Thanks Don, this should help us to solve this problem hopefully.Gary

Hi Gary, a couple of questions; - What's your memory config (amount and type of modules)? - Which CPU do you have? - OS is XP, which SP? Did you update the OS before installing the drivers? - Which mainboard driver version did you install? At first sight, I could also imagine it's something memory, driver or temperature related. Perhaps download 'memtest86+' from www.memtest.org and let it run a couple of passes. To get the CD-version you'll i.e. require the iso image. FWIW, there is one problem when trying to use the Event Viewer: Often, it doesn't show (should read: can't show) the application which caused the crash and therefore, the Event Viewer's usefulness is somewhat limited. Hope this adds to thoughts, good luck and kind regards Jaap

Jaap,Have to disagree with you concerning the Event Viewer's inability to show which application caused the crash. I've seen several references to FS9 after a crash (FS9.exe caused an exception in sim1.dll module or something similiar). It doesn't make any difference if an application is not shown since you had to have an application open to have caused the event (i.e., the crash). Therefore its usefulness is extremely valuable since you can easily google the event and find a solution or click on the suggested microsoft web site where further information concerning the problem can be found. Back in my days (heh, heh), we didn't have that luxury and had to guess at the problem or call in a tech which sometimes got very expensive. Kind regards,Jim

Hi Jim (and Jaap... how have you been?),Gotta agree with Jaap on this one, Jim. Event Viewer can be useful if the problem is software related. But more often than not anytime a system wants to perform a memory dump the cause is hardware related. The link Don provided above seems to point to a hardware problem as well.To the OP, first thing I'd try is opening the case and giving the innards a good cleaning with some compressed air. If that doesn't help then sticking a house fan into the open left case side (to inject plenty of cool fresh air into the case) is worth a try. And as Jaap requested more info on your system would be helpful.Regards,GregEdited 'cause this keyboard can't spell. :-)

Hi Greg, thanks for the 'assistance'. Doing pretty well although being very busy. How's about you? Hope you're doing well too. Hi Jim, I just wanted to point out that the Event Viewer has limitations. Very often, you'll only see the second last occurance before the FlyTendo went 'down'. Greg specified the (hardware) limitation I should have. Sorry for not having been specific enough. Otherwise, I definitely agree with the EV being a useful tool. Just like I'ld always prefer to see a 'Blue Screen' (w/ some information) above any 'Black Screen of Death' (w/ no infos at all). :-) @ Gary, the 'exclusion method' Greg proposed is probably the best way to go. Once temperature problems can be excluded, you can test the memory config. Etc. If you haven't got any yet, I would warmly recommend to fit 2 additional case fans (1 blowing in - 1 out). Good luck and kind regards everybody Jaap PS, a little hint when cleaning fans with compressed air: Stop/hold the fan, because compressed air will often make it rotate at unspecified speeds and thus perhaps 'burn' the bearing.

PS, Greg, I would like you to try something (provided you have a moment to spare). It's FS related, pretty simple and shouldn't be very time consuming. If you would like to do so, please contact me by mail or PM (and indicate how I can reach you too). Thanks in advance, good luck and kind regards Jaap