After an weird encounter of the PMDG 737NGX patch sp1c deleting my texture folder, I had to reinstall my complete FSX. Then I reinstalled all my addons with careful backups. I decided to  play FSX after a while and I loaded it but in the middle of loading, like 30-1 mins of loading, a box popped up saying that FSX has encountered a problem and needs to shut down. I tried again with different methods but still no avail. Here's the data I retrieved from the Windows event viewer

-----------------------------------------------------------------------------------------------------------------------------------------

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: KERNEL32.DLL, version: 6.3.9431.0, time stamp: 0x51bcf71a

Exception code: 0xc0000005

Fault offset: 0x000275ba

Faulting process id: 0x500

Faulting application start time: 0x01cea14a774abfb8

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\WINDOWS\SYSTEM32\KERNEL32.DLL

Report Id: cc2626b9-0d3d-11e3-9b17-8c89a5e2cee0

Faulting package full name: 

Faulting package-relative application ID: 

-----------------------------------------------------------------------------------------------------------------------------------------

There are many individuals having similar issues with Windows 8.1 installed - http://answers.microsoft.com/en-us/windows/forum/windows8_1_pr-gaming/flight-simulator-x-refuses-to-start-action-centre/3246d86a-c3dc-4f87-82a9-871f6734c764 .  Do you have the Uiautomationcore.dll in your main FSX folder.  If so, remove it.  It is not compatible with Windows 8 (it is okay with Windows 7 though)(Source:  NickN, a known computer expert in the fs community).

 

The kernel.dll faulting module indicates a situation that you are nearing an out-of-memory (OOM) situation.  This can be caused by high fsx/display driver settings while flying in commercial scenery areas and/or payware aircraft.  It could also be a tweak in your Fsx.cfg that is causing the error too.  You might try renaming your fsx.cfg to fsx.orig then restart fsx and let the config rebuild.  Once you are at the FSX setup page, you might want to make sure your resolution is set properly and AA/AF is turned on but don't change anything under any of the other tabs.  Go run your flight and see if the problem reoccurs.  If not, there was something amiss in your fsx.cfg. 

 

Look in this forum and look at the recent posts regarding OOM's and check those for possible solutions.

 

Best regards,

Jim

I don't have any sign of a uiautomationcore.dll in my FSX folder. It's strange that I'm out of memory because I have 8 gigs of ram on my PC. Let me try removing FSX.cfg and see what happens.

Nope. No avail. It still says FSX has a fatal error and needs to restart.

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: KERNEL32.DLL, version: 6.3.9431.0, time stamp: 0x51bcf71a

Exception code: 0xc0000005

Fault offset: 0x000275ba

Faulting process id: 0xadc

Faulting application start time: 0x01cea1b83f8b460a

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\WINDOWS\SYSTEM32\KERNEL32.DLL

Report Id: 91db5a8e-0dab-11e3-9b17-8c89a5e2cee0

Faulting package full name: 

Faulting package-relative application ID: 

 

Still the same

Oh, WHY DID I EVER SWITCH TO WINDOWS 8.1?

You need to download and run AppCrashView - http://www.nirsoft.net/utils/app_crash_view.html.  It provides more useful information about your crash.  Just copy the results of the latest crash in the lower pane and paste the results here.  It should have a list of all the crashes you have had recently.  Were they all caused by the kernel.dll? 

 

In regards to your comment about 8 GB's of memory....

 

Virtual Memory The max Virtual Address Space (VAS) limit in FSX (a 32-bit program) is 4GB IF you are running a 64 bit OS (you have Windows 8, 64 bit so you are). Any memory above that will be used by installed hardware and the OS (so this is good as FSX and FSX addons might get to use up to 4GB. On a 32 bit OS (like Windows 8, 32 bit), only 4GB of VAS can be used including space for the OS. So that's not good in that FSX might see/use up to 3GB's and the OS and hardware will use the rest.

 

You can check the amount of VAS being used by your computer while running FSX by running Process Explorer - http://technet.micro...s/bb896653.aspx.  Right click on Process and the Select Columns... Once Select Columns is open, click on Process Memory tab and select Virtual Size, click OK and you should now have a TAB show virtual size for FSX (once it is running) on the main page. You can also see what other apps/processes are running that are taking up VAS.

 

Best regards,

Jim