I did set it to system managed size and it still will not work. Clearly there is a RAM issue, did you see my above post earlier to look for any errors or mistakes in my configuration?

 

Is there anything I can even do anymore or is it just over for this computer / FSX?

did you see my above post earlier to look for any errors or mistakes in my configuration?

 

No. Where? (Post #).

I just ran Malwarebytes the other night

 

That program works but it only gets rid of the most serious threats. Super Anti-Spyware gets rid of everything. No indications you ran CCleaner.

 

Reviewing my posts and don't see where I recommended employing the /3GB switch. Did you? http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=9583842&linkID=9240617.

 

Did you delete or rename your FSX.cfg, restart FSX and let the config rebuild?

 

Lastly, look in your Event Viewer and it will provide even more information related to your crashes - http://support.microsoft.com/kb/308427. Don't look at the last error. Look at them all since the crashes started. The link has further details on how to properly use the Event Viewer.

 

Best regards,

Jim

I did not employ the /3GB switch, I will try that now. What exactly do you want me to do with the recorded crashes from event viewer? Post them?

Config and all is at post 12.

 

On that AutoDesk Article it says on step 12 on startup make sure that you select the 3GB option or it will revert to the 2GB. Where do i change that function?

 

This is the most seen error of mine:

 

Event Type: Error

Event Source: Application Error

Event Category: None

Event ID: 1000

Date: 12/30/2012

Time: 11:45:35 AM

User: N/A

Computer: DESKTOP

Description:

Faulting application fsx.exe, version 10.0.61637.0, faulting module unknown, version 0.0.0.0, fault address 0x53128acb.

 

For more information, see Help and Support Center at http://go.microsoft....ink/events.asp.

Data:

0000: 41 70 70 6c 69 63 61 74 Applicat

0008: 69 6f 6e 20 46 61 69 6c ion Fail

0010: 75 72 65 20 20 66 73 78 ure fsx

0018: 2e 65 78 65 20 31 30 2e .exe 10.

0020: 30 2e 36 31 36 33 37 2e 0.61637.

0028: 30 20 69 6e 20 75 6e 6b 0 in unk

0030: 6e 6f 77 6e 20 30 2e 30 nown 0.0

0038: 2e 30 2e 30 20 61 74 20 .0.0 at

0040: 6f 66 66 73 65 74 20 35 offset 5

0048: 33 31 32 38 61 63 62 0d 3128acb.

0050: 0a .

 

 

Also this one on one occasion:

Event Type: Error

Event Source: Application Error

Event Category: None

Event ID: 1001

Date: 12/30/2012

Time: 11:45:49 AM

User: N/A

Computer: DESKTOP

Description:

Fault bucket -960410262.

 

For more information, see Help and Support Center at http://go.microsoft....ink/events.asp.

Data:

0000: 42 75 63 6b 65 74 3a 20 Bucket:

0008: 2d 39 36 30 34 31 30 32 -9604102

0010: 36 32 0d 0a 62..

 

.All of the events related to FSX have an event ID of 1000 or 1001.

Okay Firehawk, I think that this will be the most important piece of information yet. This is the "Error Signatute" that would be sent to Microsoft if I say to "Send Error Report"

 

Does this give us any information?

 

AppName: fsx.exe AppVer: 10.0.61637.0 ModName: Terrain.dll

ModVer:10.0.61637.0 Offeset: 0000e88b

 

Using the guide posted by Summer1, I think this was the major problem, that ever since I reset my fsx.CFG, it turned up my sliders beyond my system's reach, as it was barely able to hold onto what I used previously.

I turned them down below what I previously had to ensure stability.

 

I'm beginning a test flight immediately and will return with any findings of significance.

Crashed again, I believe there must be a missing file, what is the next step from here?

 

Should I reinstall FSX since I clearly have a faulty terrain.dll or do something else?

Try running stock FSX.cfg settings for a while. If you can get an hour flight in then try bumping up your settings. Cheers jja

I highly recommend you download a (free) copy of the Memtest 86+ utility and run it through at least 10 passes (that'll take a few hours). That will exercise all of your memory and give you a good idea as to whether your memory is behind these problems. If you get any errors at all, you have either a bad stick of RAM or some setting adjustments to do to make it run correctly. The design bit error rates would allow you to run 24/7 for months with error-free performance .

 

Regards