I might get some people rolling their eyes when they read this, as this is regarding the old FS9, but please help! I have been out of flightsimming for almost 2 years, but my gf is letting me use her new computer for it until I can buy my own. I keep getting a blue screen and i've done many searches, tried tons of advice, but I'm still getting it on occasion. At first I thought it was some saitek drivers for my x52, but I got rid of them, and it still happened. I have C++ (installed with PMDG aircraft). I already ran a RAM Diagnostic with no errors found. Can't figure it out guys.Windows 7 64-bitFS9.1 with 64 bit patch to the executable as suggested in the W7 avsim forums.GT520 (yes I know not the latest) with Nvidia Inspector settings at 8xS as suggested by Ryan in his pinned topic (285.62 driver)PMDG 744, 744F, MD-11, Level D 767 all up to date, fresh installs, all for FS98GB RAM DDR3here is the error info:Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033Additional information about the problem: BCCode: 7f BCP1: 0000000000000008 BCP2: 0000000080050031 BCP3: 00000000000406F8 BCP4: FFFFF8800F2C4500 OS Version: 6_1_7601 Service Pack: 1_0 Product: 768_1Files that help describe the problem: C:\Windows\Minidump\012212-11216-01.dmp C:\Users\Onnarashii\AppData\Local\Temp\WER-23259-0.sysdata.xml Would setting properties for FS9 to run in WinXP SP3 make this go away? But then wouldn't that cancel out the 64-bit patch to the .exe? Also, would that inhibit the amount of RAM allowed to be used? If anyone could help, or just point me where to go for better help, that would be awesome. As I've said, I have done searches and tried to find a solution already.Thanks!

Could be your graphics card overheating. I'd recommend downloading a program that'll let you monitor the temp.

Could be your graphics card overheating. I'd recommend downloading a program that'll let you monitor the temp.

Actually, I just got through a flight with no errors randomly. Temp via nvidia inspector immediatley after closing flight sim was 35c, so I dont belive thats the problem, but ill check it in the middle of playing later.I am wondering if running in XP compatibility will cure all this, but then wouldn't I lose the extra RAM ability of the 64-bit W7 that I have?

compatibility won't affect memory, win7x64 still has plenty to give fsx its 4gb.You haven't overclocked this computer, have you?Afother thing that can easily cause bluescreens is simply a loose connection somewhere. It wouldn't hurt to unplug & reseat all cables/cards in the PC. That SHOULD solve any potential connection issues.

compatibility won't affect memory, win7x64 still has plenty to give fsx its 4gb.You haven't overclocked this computer, have you?Afother thing that can easily cause bluescreens is simply a loose connection somewhere. It wouldn't hurt to unplug & reseat all cables/cards in the PC. That SHOULD solve any potential connection issues.

Ok that's good to know. I will try ur suggestion. And no, no overclock. Just using fs9 right now, so I don't need to do that until I buy my computer with an i5 2500k and use fsx. Thanks

There's nothing wrong with overclocking in case anyone misunderstands my post. It's the single best system mod for fsx performance and also a common source of bluescreens when done incorrectly.

Edited January 23, 201214 yr by MrKen

I have just done two flights, PMDG MD-11 and the 747F, TNCA-EHAM, and KSDF-KDFW, while running in WinXP SP3 compatibility mode. No blue screens! Hopefully that was the issue. Thanks for the input guys

Blue screens are not something to immediately worry about! The solution cuold be really simple! It could be as MrKen said, cables or parts not seated properly, overheating GPU. CPU... Possibly even a virus. I've been running 4.5 GHz for 3 months, never had BSOD's, until last week I got two of them. Than I scanned my pc for virusses and it found the extremely dangerous "Exploit:Java/Blacole.XX". It found 4 of these same virusses. Scan your pc. After I did this, the BSOD's stopped. Until yesterday when I tried overclocking further to 4.7 GHz. Obviously my CPU needs a lot of voltage because I'm still getting BSOD with 1.37V. Currently, running great at 4.5 and 1.35V. So again, scan your pc!If this doesn't solve it, then some part of your pc might be faullty.

Edited January 23, 201214 yr by arjenfsx

Have you tried opening the minidump with debugger?Can you remember what the blue screen said where the error was?You should also review the event logs which might tell what triggured the error.

Have you tried opening the minidump with debugger?Can you remember what the blue screen said where the error was?You should also review the event logs which might tell what triggured the error.

They've gone away since i've been opening in compatibility mode for WinXP SP3. I think it's over with. Thanks for the tips though, everybody. I'll use them if it happens on my future computer

I would never have associated that with bsod

Have you tried opening the minidump with debugger?Can you remember what the blue screen said where the error was?You should also review the event logs which might tell what triggured the error.

ok, so have to bring this thread back up, cause after doing a 7 hours of flying into a 9 hr flight on level d 767, I paused and saved. next day i reloaded from where I left off, 10 minutes in, Blue Screen. Restarted, loaded md-11F to do KSDF-KDFW, on final, Blue Screen. And this is after a week of no blue screens. I did a system restore to when I wasn't having problems. Really worried that it is the physical RAM. How do you open with a debugger? Event logs have so many events, nothing really stands out to me. Not completely computer illiterate, but definitely don't know troubleshooting tools very well, or understand these errors. If it happens again, I will post the error codes, but they seemed very similar to the ones I posted at the beginning of this topic.Thanks!

ok, so have to bring this thread back up, cause after doing a 7 hours of flying into a 9 hr flight on level d 767, I paused and saved. next day i reloaded from where I left off, 10 minutes in, Blue Screen. Restarted, loaded md-11F to do KSDF-KDFW, on final, Blue Screen. And this is after a week of no blue screens. I did a system restore to when I wasn't having problems. Really worried that it is the physical RAM. How do you open with a debugger? Event logs have so many events, nothing really stands out to me. Not completely computer illiterate, but definitely don't know troubleshooting tools very well, or understand these errors. If it happens again, I will post the error codes, but they seemed very similar to the ones I posted at the beginning of this topic.Thanks!

The error code at the beginning of this topic is vague at best. We need more. What is it the error codes have in common?Just to give an idea of how vague your error code is: http://answers.microsoft.com/en-us/windows/forum/windows_7-system/blue-screen-windows-7-bccode-7f/f9b0636d-7bf3-4108-8b70-b8cfee538058

Edited January 29, 201214 yr by ZachLW

Microsoft's instructions can be a bit cryptic but try this..http://msdn.microsoft.com/en-us/windows/hardware/gg463009Try to trigger a BSOD,and remember the heading of the BSOD .ie,SYSTEM_POINTER_PENDING, or IRQL_NOT_LESS_OR_EQUAL are some of the typical BSOD's you might see,Also refer to the event viewer to see what might be the faulting .dll

Microsoft's instructions can be a bit cryptic but try this..http://msdn.microsoft.com/en-us/windows/hardware/gg463009Try to trigger a BSOD,and remember the heading of the BSOD .ie,SYSTEM_POINTER_PENDING, or IRQL_NOT_LESS_OR_EQUAL are some of the typical BSOD's you might see,Also refer to the event viewer to see what might be the faulting .dll

Ok, so dll causes this usually? That'll help. There's so many little events, that I can't make heads or tails of it, but if its a dll then that will narrow it down. Thanks!

The error code at the beginning of this topic is vague at best. We need more. What is it the error codes have in common?Just to give an idea of how vague your error code is: http://answers.microsoft.com/en-us/windows/forum/windows_7-system/blue-screen-windows-7-bccode-7f/f9b0636d-7bf3-4108-8b70-b8cfee538058

Wow, had no idea it was vague lol. Good to know. Would sending the .dmp file mentioned in the report to a Microsoft support guy be of any help? Just learned what those files are.