crashes !

[martin21]

Hi,

I have the following problem, I work in Windows XP prof. and I have many problems. I get many BOD's (Blue screen Of Death) and many hangs while playing fltsim 2k2. I think it are the XP drivers but i am not sure. I work with :

Windows XP prof. dutch
MSI KT7266 pro 2 (KT266a chipset)
AMD 1500+ at 1333mhz
256MB DDR
Matrox G400 Dual head 32MB (driver 5.72)

Does anybody use's the same use spec's ? Please reply whenether it works right or you have the same problems !
Please help me out.... many thanx

Martin Hamelink
the Netherlands

[farvque]

My system is similar, except I have SDRAM, not DDR Ram. I have some BSOD problems with Windows XP, but far less than with ME or 98.

Here are some things you might want to try:

Your processor or RAM may be overheating. Make sure you have a very good fan and heat synch's on your processor and that your case is well ventilated. You might want to try running with the cover off the case as a test.

I'm not sure from your description, but if your processor is running at a slower Mhz rating than it is rated, you will definitely want to make sure it is running at least at it's rated clock speed. However, you may be confusing two factors, which can cause problems: In your BIOS, there is a setting for your FSB Speed, which is relative to your processor. If you have a 1.4Ghz Processor and your FSB is set to 100, then your processor is running at 1.4Ghz. However if your FSB is set at 133 and you have a processor at 1.4Ghz, then your processor will try to run (i.e., overclock) at 1.4X1.33, which is probably way too fast to keep your system stable. I have my system overclocked at 110Mhz (FSB) using a 1.3Ghz AMD Athlon Processor, which yields a Ghz rating of 1.43 on my processor. If you are uncertain, then get a piece of software called SiSoft Sandra and run tests on your processor. One other thing, if you are really running 1.33Mhz FSB on a 1.4Ghz processor this could potentially ruin your processor!

Another problem could be bad (i.e., cheap) RAM. The best system is susceptible to BSOD if the RAM is not very good. You may want to try an experiment - if your system also supports SDRAM, try replacing the DDR Ram with SDRAM and see what happens. Also, try replacing the DDR RAM with RDR (Rhombus) RAM. RDR Ram is usually compatible with DDR Ram, it is more expensive and much more stable and much faster. In any event, you can run burn tests with SiSoft Sandra to test your RAM to see if it is the problems.

Some other things to try:

Make sure your hard drive is defragged regularly and you have enough free space.
If you have two hard drives, move your swap file (virtual memory settings) to the second drive.
Upgrade (flash) the bios on your motherboard to the latest version.
Close all other processes (including antivirus software) before running FS.
Upgrade to an Ultra DMA (UDMA) 100 Hard Drive.
Disconnect your machine from a network when running FS (reboot first).
Check to see if there is no IRQ conflicts in your device configuration - especially Sound/USB conflicts. Try moving cards to different slots to reassign IRQ's, or if you really know what you are doing, override automatic settings in the BIOS.

All this being said, I have my system as stable as it can get (doing all the above), but I still occasionally get BSOD! - However, they are greatly reduced.

Good Luck

[jkk]

Familiar problems but no solution (wish somebody can help).

My FS2002 works fine until I quit and shut the program.
Then the computer boots with flashing briefly the BOD (too fast to read any of the text. XP starts and runs the _chkdsk_/f_ -program. After logging in The XP wants to send the error report to Microsoft (which I don't let it do).

My computer:
MSI KT7266pro2 (latest XP drivers)
AMD athlon 1,2G (processor temperature 63 deg. Celcius, no overclocking)
256MB DDR
Geforce MX 400 (latest drivers)
XP Home Edition (english) on partition C: (10 GB FAT32) and
FS2002 Pro on partition D: (50 GB NTFS)
I use the sound system onboard the MSI

I even tried the compatibility option to emulate W2K and W98/ME but it did not help (some older programs tend to work better with 'exotic' compatibility setting - like my System Shock 2 - a pre-W2k-era game works only with XP set to emulate windows 2000)

I'm quite happy with my FS2002, at least I can fly without any BODs. It's the constant checkdisk I'm bored with.

This reply may not help but You asked whether someone had the same problems.

Jyrki Kivi
Finland

[jase439]

When you get a BSOD in NT/2000/XP, it is generally indicative of either hardware or driver failure. If you could scribble down the exception being generated (i.e. PAGE_FAULT_IN_NONPAGED_POOL, IRQL_NOT_LESS_OR_EQUAL, etc...), along with any other relevant information - that can sometimes be helpful in tracking the source of the problem down.

[jkk]

My Problem is solved
I finally got the FS2002 working and I got rid of the annoying Blue Screen of Death which emerged every time I shut the program. The error message on BOD was so quick I barely noticed it at all. But it said something about the audio driver and so I updated the onboard AC97 driver (it's a MSI board, so the update was on MSI web page).

This proves (to me at least) that a PC is good gaming platform, just remember allways keep the drivers updated


Thanks everybody,

J. Kivi