Does anyone know what this means. I was on a very long flight from KSFO-RCTP (10+ hours). I was trying to determine the longest range of my PMDG 747 and I got this error 800NM from RCTP. Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.768.3 Locale ID: 1033Additional information about the problem: BCCode: d1 BCP1: FFFFF80003BA6F4A BCP2: 0000000000000002 BCP3: 0000000000000008 BCP4: FFFFF80003BA6F4A OS Version: 6_1_7600 Service Pack: 0_0 Product: 768_1Files that help describe the problem: C:\Windows\Minidump\061410-12448-01.dmp C:\Users\Joseph\AppData\Local\Temp\WER-21777-0.sysdata.xmlRead our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104...mp;clcid=0x0409If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt

Drop your clock to normal and try the flight again - if it happens again, you have eliminated your clock as the problem.

Does anyone know what this means. I was on a very long flight from KSFO-RCTP (10+ hours). I was trying to determine the longest range of my PMDG 747 and I got this error 800NM from RCTP.....

Might be the UIAutomationCore problem? :( (Follow this link if you need to know more).Best of luck,Brian

Might be the UIAutomationCore problem? :( (Follow this link if you need to know more).Best of luck,Brian

I installed the UIAutomationCore.dll. However on my next flight I received the following error about 30 min into the flight around FL 340 above KSFO. Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.768.3 Locale ID: 1033Additional information about the problem: BCCode: 50 BCP1: FFFFF8800568508E BCP2: 0000000000000008 BCP3: FFFFF8800568508E BCP4: 0000000000000001 OS Version: 6_1_7600 Service Pack: 0_0 Product: 768_1Files that help describe the problem: C:\Windows\Minidump\061910-12776-01.dmp C:\Users\Joseph\AppData\Local\Temp\WER-22479-0.sysdata.xmlI even updated DX10 in desperation. Is this a known problem with W7? I bought the system overclocked, and I don't really want to drop the clock speed until I have eliminated everything else. All hardware has been checked, and double checked. My system is 2 mos old. Is anyone else have unresolved Blue Screen problems?Help please...

Download and run Memtest.Check 1 stick at a time.BCCode 50 is usually a ram error.if you get errorsa) drop the clock and retestor:( buy and install new memoryandc) drop the clock and retestVic

Is this a known problem with W7? I bought the system overclocked, and I don't really want to drop the clock speed until I have eliminated everything else. All hardware has been checked, and double checked. My system is 2 mos old. Is anyone else have unresolved Blue Screen problems?Help please...

There can be some aspects of running fsx on W7 (perhaps especially W7 64-bit) which may cause problems. But your immediate problem is that blue screens are not especially friendly things to deal with.I would suggest

There can be some aspects of running fsx on W7 (perhaps especially W7 64-bit) which may cause problems. But your immediate problem is that blue screens are not especially friendly things to deal with.I would suggest

I'll say it one more time - remove the clock ENTIRELY and test again - until you do that you can NOT be sure that the clock is not the problem. If it works, you know the clock is the culprit - if it fails, you can look elsewhere - however - I'd still leave the clock at normal until you resolve the issue or you'll be chasing ghosts.Vic

The clock is not the problem, I use a completely standard PC, Vista 32bit from origin, installed W7 64, and had these BSOD too using FSX. Usually my graphics card just stops and turns itself on again, and sometimes I get the BSOD, usually in a bit more complex area but can happen anywhere here. My PC is a standard one, from Medion, Q6600 at 2.4, NVidia 8600GT at 512MB DDR2, 3GB DDR2, 1 old philips monitor and a new samsung 22".

Download and install Debugging Tools for Windows (x86)!This will let you read your memory dump which tells you (more exactly) what your problem is.A lot of BSOD's are caused by drivers for example.I already solved a couple of issues myself this way.

Dropped the clock, now I am getting bugcheck restarts.

Dropped the clock, now I am getting bugcheck restarts.

Not that I need to, but I want to echo rmk80's comment regarding drivers. On a previous thread I posted a problem about my mouse. What it boiled down to was that I had a couple of conflicting drivers loaded and Windows-7 doesn't seem to have a routine to check for driver conflicts as a new program (or driver update for existing programs) is being installed. If you use the "Express" install for these driver updates, as I had done, you sometimes end up with several drivers that clash with each other for the same internal or peripheral device. Hunting down and deleting unwanted drivers solved my issue. Perhaps you could try this route.

Download and install Debugging Tools for Windows (x86)!This will let you read your memory dump which tells you (more exactly) what your problem is.A lot of BSOD's are caused by drivers for example.I already solved a couple of issues myself this way.

I downloaded another version of debugging tools, and it game me generic driver errors. Debugging tools could not find the error either. For now I have reduced settings, updated the new ATI driver for my 5870. I had a tech review the system and tested hard ware new faults. I even uninstalled my virus software. The bsods go away if I reduce settings but I am still unable to max out all settings. Is this a problem with DX10? Perhaps I should use DX9 going forward?

I have built a new system with all the goodies, been waiting for a while to do this, not a cheap investment and for a while I was getting BSOD everyday, did a lot of reading and all I could find as info was to use a registry cleaner, tried CCcleaner and no joy, so just for the fun of it I downloaded a copy of PC tools Registry Mechanic ver 9, have used this product for a long time, there is a function there that will do a registry compact, after I did that my problems where gone, if you are using W7 Pro, try this it worked for me, no more BSOD. :(

DX10 is people! (soylent green ref)It's garbage. I'm back to dx9 with nearly maxed out sliders and 2048 Rez weather.At altitude I'm getting 45-70 fps in virtual cockpit. I guess dx10 is not ready for sling haul complex addons!