This link has exactly my issue (and there's a visual): http://forum.avsim.net/topic/387736-fsx-crashes-when-i-fly-with-737ngx/#entry2491604

 

The main issues still remains - the OP has NOT determined if the cause of the error is the OS, the hardware or FSX? So what good would a upgrade of ANYTHING do if you still havent identified the issue?

 

Using your logic, I guess he could go out and buy a whole new system and new software but I do think it's a bit much

 

Exactly! My system is fine! Again, everything 'runs', it's just the level of uncertainty and paranoia of the error. I'm really surprised no one has heard (so far) of the known W7 64 bit error

I'm really surprised no one has heard (so far) of the known W7 64 bit error

 

To what "known W7 64 bit error" are you referring? Like many here, I have just such a system and it runs almost flawlessly with multiple add-ons.

 

You're also ignoring the meat of the post you quote: "the OP has NOT determined if the cause of the error is the OS, the hardware or FSX?". This is exactly on point. As others have tried to suggest, if nothing else, you've now got a mess (multiple installs and registry issues) which MUST be cleaned up before you proceed. Your system is NOT fine. If it was, you'd be like most of us here - running FSX without major issues.

 

Step one is obvious - clean things up.

 

Scott

Scott hit it on the head. Clean things up first. And, there are MANY possible "w7 64bit errors" - that image the other link posted has a lot more information. Usually, if you scroll down that dialog box it will list the "faulting module" that ca give you a clue. But now that you've messed around - don't bother - just clean it up and start over and then we can deal with any possible errors.

 

Keep us posted.

 

Vic

Step one is obvious - clean things up.

 

That's what I'm going to do. Remove every trace, I'm then going to use this: http://www.simforums.com/forums/topic34141_post198187.html#198187 and this: http://www.simforums.com/forums/topic29041.html to setup. Sound good, Scotty?

 

Keep us posted.

 

I definitely will, thanks for your help vg!! :Peace:

c0000005 is a memory error I have seen in other posts. To quote firehawk44 "Each one shows the Exception Code 0000005 (Memory_Access_Violation). This exception almost shows up in every FSX CTD and it happens when FSX is looking for a texture, a gauge, an effect to load or render and cannot find it."

Okay...I have every trace of FSX removed from comp (so I believe). Is there anyway to be sure? I'm going to try and install tonight after I finish typing a paper....

:p0317: