Can anyone PLEASE help me?

[cbalow 2]

Ken,

 

For what it is worth, I completely re-installed UT and CT again.  1 file @ a time.  Bingo, no issues.  I have not tried reinstalling CO, or  NE yet.

 

The only difference for me was I had 1 process going @ a time.  I installed CO,NE,UT,CT all at the same time so I was flying through the install process having 2 or 3 files unzipping at a time while having another file or 2 installing.  My guess is something was not installed correctly.

 

I am going to take this approach with CO and NE and if it works, I will believe it was simply my impatience that caused my grief.  (aka, ID10T error)

 

Else..... I will visit Newegg.com and buy MORE POWER!!!!   :rolleyes:   (or just follow the other suggestions.)

[CaptainKen 0]

Well bad news for me - I installed Nebraska from the downloads, and once again I am crashing 0n Nebraska.  If I don't use the megascenery, the fsx doesn't crash.  But if I use it, then I crash.  Now what?  I downloaded several sectors at the same time, and installed several of them simultaneously as well.  I'm so darn frustrated.

 

I tried and tried again, having five "crashes" in a period of about 15 minutes.  All "error codes looked the same.  I'll post one here incase anyone has any ideas.  Here it is:

Version=1
EventType=APPCRASH
EventTime=130180475612924000
ReportType=2
Consent=1
UploadTime=130180475623554000
ReportIdentifier=2b3b7481-ea67-11e2-b5a1-00038a000015
IntegratorReportIdentifier=2b3b7480-ea67-11e2-b5a1-00038a000015
WOW64=1
Response.BucketId=600423621
Response.BucketTable=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.61472.0
Sig[2].Name=Application Timestamp
Sig[2].Value=475e17d3
Sig[3].Name=Fault Module Name
Sig[3].Value=util.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.61472.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=475e180d
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00022d5a
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=fb8b
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=fb8bd1bf7dcc44d047c58f37f56ad727
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=fa63
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=fa63c80ebf2b9d98cfa9fc211d9a92ad
UI[2]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
UI[3]=Microsoft Flight Simulator® has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[7]=C:\Windows\syswow64\GDI32.dll
LoadedModule[8]=C:\Windows\syswow64\USER32.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\syswow64\LPK.dll
LoadedModule[15]=C:\Windows\syswow64\USP10.dll
LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[17]=C:\Windows\syswow64\ole32.dll
LoadedModule[18]=C:\Windows\system32\apphelp.dll
LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[20]=C:\Windows\system32\UxTheme.dll
LoadedModule[21]=C:\Windows\system32\WINMM.dll
LoadedModule[22]=C:\Windows\system32\samcli.dll
LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[24]=C:\Windows\system32\MSACM32.dll
LoadedModule[25]=C:\Windows\system32\VERSION.dll
LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[27]=C:\Windows\system32\sfc.dll
LoadedModule[28]=C:\Windows\system32\sfc_os.DLL
LoadedModule[29]=C:\Windows\system32\USERENV.dll
LoadedModule[30]=C:\Windows\system32\profapi.dll
LoadedModule[31]=C:\Windows\system32\dwmapi.dll
LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[35]=C:\Windows\syswow64\urlmon.dll
LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[43]=C:\Windows\syswow64\iertutil.dll
LoadedModule[44]=C:\Windows\syswow64\WININET.dll
LoadedModule[45]=C:\Windows\system32\MPR.dll
LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll
LoadedModule[50]=C:\Windows\system32\mscms.dll
LoadedModule[51]=C:\Windows\system32\DDRAW.dll
LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[54]=C:\Windows\syswow64\IMM32.dll
LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[57]=C:\Windows\syswow64\NSI.dll
LoadedModule[58]=C:\Windows\system32\msi.dll
LoadedModule[59]=C:\Windows\AppPatch\AcXtrnal.DLL
LoadedModule[60]=C:\Windows\system32\SHUNIMPL.DLL
LoadedModule[61]=C:\Windows\system32\SortServer2003Compat.dll
LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[63]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\language.dll
LoadedModule[64]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLL
LoadedModule[65]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[66]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ablscpt.dll
LoadedModule[67]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\flight.dll
LoadedModule[68]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ai_player.dll
LoadedModule[69]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\acontain.dll
LoadedModule[70]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\controls.dll
LoadedModule[71]=C:\Windows\system32\DINPUT8.dll
LoadedModule[72]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsui.dll
LoadedModule[73]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\atc.dll
LoadedModule[74]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\facilities.dll
LoadedModule[75]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\demo.dll
LoadedModule[76]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\main.dll
LoadedModule[77]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fe.dll
LoadedModule[78]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\util.dll
LoadedModule[79]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simprop.dll
LoadedModule[80]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g2d.dll
LoadedModule[81]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[82]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[83]=C:\Windows\system32\d3d9.dll
LoadedModule[84]=C:\Windows\system32\d3d8thk.dll
LoadedModule[85]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g3d.dll
LoadedModule[86]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\panels.dll
LoadedModule[87]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\multiplayer.dll
LoadedModule[88]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ui.dll
LoadedModule[89]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sound.dll
LoadedModule[90]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sim1.dll
LoadedModule[91]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simscheduler.dll
LoadedModule[92]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\visualfx.dll
LoadedModule[93]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\window.dll
LoadedModule[94]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\terrain.dll
LoadedModule[95]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\weather.dll
LoadedModule[96]=C:\Windows\system32\DSOUND.dll
LoadedModule[97]=C:\Windows\system32\POWRPROF.dll
LoadedModule[98]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\symmap.dll
LoadedModule[99]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dll
LoadedModule[100]=C:\Windows\system32\MSIMG32.dll
LoadedModule[101]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\xuipc.dll
LoadedModule[102]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\livingwater.dll
LoadedModule[103]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fs-traffic.dll
LoadedModule[104]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\gps.dll
LoadedModule[105]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[106]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[107]=C:\Windows\system32\RICHED20.DLL
LoadedModule[108]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[109]=C:\Windows\system32\rsaenh.dll
LoadedModule[110]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[111]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[112]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[113]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[114]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[115]=C:\Windows\system32\wbemcomn.dll
LoadedModule[116]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[117]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[118]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[119]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[120]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[121]=C:\Windows\system32\dxgi.dll
LoadedModule[122]=C:\Windows\system32\d3d11.dll
LoadedModule[123]=C:\Windows\system32\aticfx32.dll
LoadedModule[124]=C:\Windows\system32\atiu9pag.dll
LoadedModule[125]=C:\Windows\system32\atiumdag.dll
LoadedModule[126]=C:\Windows\system32\atiumdva.dll
LoadedModule[127]=C:\Windows\system32\atiuxpag.dll
LoadedModule[128]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[129]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[130]=C:\Windows\system32\d3d10_1.dll
LoadedModule[131]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[132]=C:\Windows\SysWOW64\dxdiagn.dll
LoadedModule[133]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[134]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[135]=C:\Windows\system32\winbrand.dll
LoadedModule[136]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[137]=C:\Windows\system32\WINSTA.dll
LoadedModule[138]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[139]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll
LoadedModule[140]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[141]=C:\Windows\SysWOW64\wer.dll
LoadedModule[142]=C:\Windows\System32\Wpc.dll
LoadedModule[143]=C:\Windows\System32\wevtapi.dll
LoadedModule[144]=C:\Windows\System32\msxml6.dll
LoadedModule[145]=C:\Windows\system32\SAMLIB.dll
LoadedModule[146]=C:\Windows\system32\netutils.dll
LoadedModule[147]=C:\Windows\system32\uiautomationcore.dll
LoadedModule[148]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[149]=C:\Windows\system32\OLEACC.dll
LoadedModule[150]=C:\Windows\System32\MMDevApi.dll
LoadedModule[151]=C:\Windows\System32\PROPSYS.dll
LoadedModule[152]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[153]=C:\Windows\system32\HID.DLL
LoadedModule[154]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[155]=C:\Windows\system32\wdmaud.drv
LoadedModule[156]=C:\Windows\system32\ksuser.dll
LoadedModule[157]=C:\Windows\system32\AVRT.dll
LoadedModule[158]=C:\Windows\system32\msacm32.drv
LoadedModule[159]=C:\Windows\system32\midimap.dll
LoadedModule[160]=C:\Windows\system32\dinput.DLL
LoadedModule[161]=C:\Windows\System32\wship6.dll
LoadedModule[162]=C:\Windows\System32\wshtcpip.dll
LoadedModule[163]=C:\Program Files (x86)\FSDiscover!\FSDiscoverFSX.dll
LoadedModule[164]=C:\Windows\system32\OPENGL32.dll
LoadedModule[165]=C:\Windows\system32\GLU32.dll
LoadedModule[166]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[167]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\iFly737NG.dll
LoadedModule[168]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[169]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FeelThere\E170\EJetH.dll
LoadedModule[170]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\A2A_Feel.dll
LoadedModule[171]=C:\Windows\SysWow64\XAudio2_6.dll
LoadedModule[172]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\AccuFeelMenu.dll
LoadedModule[173]=C:\Windows\system32\msadp32.acm
LoadedModule[174]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[175]=C:\Windows\SysWOW64\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[176]=C:\Windows\SysWOW64\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[177]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[178]=C:\Windows\system32\Secur32.dll
LoadedModule[179]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[180]=C:\Windows\system32\WINNSI.DLL
LoadedModule[181]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[182]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Cessna.DLL
LoadedModule[183]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Cessna172.DLL
LoadedModule[184]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Cessna182s.DLL
LoadedModule[185]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\CessnaWAlpha.DLL
LoadedModule[186]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Bendix_King_Radio.DLL
LoadedModule[187]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\VAGauge.GAU
LoadedModule[188]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\VAInfo.GAU
LoadedModule[189]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
LoadedModule[190]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Bell_206B.DLL
LoadedModule[191]=C:\Windows\system32\msimtf.dll
LoadedModule[192]=C:\Windows\system32\msls31.dll
LoadedModule[193]=C:\Windows\system32\d2d1.dll
LoadedModule[194]=C:\Windows\system32\DWrite.dll
LoadedModule[195]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[196]=C:\Windows\system32\MLANG.dll
LoadedModule[197]=C:\Windows\system32\ntmarta.dll
LoadedModule[198]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[199]=C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll
LoadedModule[200]=C:\Windows\system32\explorerframe.dll
LoadedModule[201]=C:\Windows\system32\DUser.dll
LoadedModule[202]=C:\Windows\system32\DUI70.dll
LoadedModule[203]=C:\Windows\system32\EhStorShell.dll
LoadedModule[204]=C:\Windows\system32\ntshrui.dll
LoadedModule[205]=C:\Windows\system32\srvcli.dll
LoadedModule[206]=C:\Windows\system32\cscapi.dll
LoadedModule[207]=C:\Windows\system32\slc.dll
LoadedModule[208]=C:\Windows\System32\StructuredQuery.dll
LoadedModule[209]=C:\Windows\SysWOW64\actxprxy.dll
LoadedModule[210]=C:\Program Files (x86)\Internet Explorer\ieproxy.dll
LoadedModule[211]=C:\Windows\SysWOW64\thumbcache.dll
LoadedModule[212]=C:\Windows\system32\SearchFolder.dll
LoadedModule[213]=C:\Windows\system32\SHDOCVW.dll
LoadedModule[214]=C:\Windows\System32\drprov.dll
LoadedModule[215]=C:\Windows\System32\ntlanman.dll
LoadedModule[216]=C:\Windows\System32\davclnt.dll
LoadedModule[217]=C:\Windows\System32\DAVHLPR.dll
LoadedModule[218]=C:\Windows\system32\wkscli.dll
LoadedModule[219]=C:\Windows\system32\PortableDeviceApi.dll
LoadedModule[220]=C:\Windows\system32\PortableDeviceTypes.dll
LoadedModule[221]=C:\Windows\system32\LINKINFO.dll
LoadedModule[222]=C:\Windows\system32\NetworkExplorer.dll
LoadedModule[223]=C:\Windows\system32\EhStorAPI.dll
LoadedModule[224]=C:\Windows\system32\zipfldr.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Flight Simulator®
AppPath=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
 

[Jim Young 2,356]

Sorry to hear you are still having problems with the util.dll (faulting module).  I just looked at your topic again and noticed there is nothing here about your system specs or whether you have Windows 64 bit installed (sorry if I missed those details - lot to read). Your crash report indicates you do have Windows 7 installed though but, if you have the 32 bit version vs the 64 bit version it could mean a lot about your problem.  You are running out of memory or your system cannot handle the resources FSX is throwing at it.  The util.dll is related to memory for FSX and the util.dll in the Windows Operating System folder is part of the Microsoft.net packages.  When you disable Nebraska, FSX doesn't throw a lot of requests for resources at the Windows OS.  If you set your fsx.cfg like mine to have a LOD_Radius of 6.5 and a Texture_Max_Load setting of 2048 (like mine), then your system may not be able to handle it.  In any case, there is nothing wrong with Nebraska.  If there was a corrupt texture or file, FSX would simply disregard it and render what is there.  But you cannot install a corrupted Nebraska.  I have Nebraska installed (my former home State) and it works great. 

 

You may also have a corrupted Fsx.cfg too that could bring down FSX.  Any Bufferpool setting is dangerous and could bring down your system if you do not know what it's doing.  Affinity Mask settings will also take down FSX.

 

I have looked over this topic and there have been tons of suggestions, one of which should have worked but obviously not.  You just have to realize that when you enable Nebraska, you will immediately be taking up a lot of system resources to run FSX.  If any fsx.cfg setting is wrong or you have a wrong overclock or you have a bad BIOS setting, it will crash FSX when you load Nebraska.  It's the trigger that is causing the crashes.  You now have to figure out how you can get more resources for fsx to run. 

 

I just did some extensive research on the Internet and most crashes are fixed when you uninstall/reinstall FSX or do a clean installation of Windows 7 and then reinstall FSX.  Why does this happen?  It happens because somewhere in your current situation you set up a bad tweak or you put a bad setting in the BIOS or you didn't set your Virtual Memory (Page File) correctly.  There are so many causes for crashes.

 

Hope you can find a solution.

 

Best regards,

Jim

[CaptainKen 0]

As always Jim, thanks for your input.  I ASSUME that because I have high FPS (20 - 50) that the computer has all the resources it needs.  Is this correct?  I have windows 7, 64 bit.  I have 2 HTI Radeon HD 5670 graphics cards.  The computer is quad core.  The processor is an Intel® Core Extreme CPU Q 6850 @ 3.00 GHz.  I have 8.00 GB Ram.  It says that I have 2303 MB total graphics memory.  The primary Hard disk has 345 GB Free.  Megascenery is installed on an external hard drive (WD, 2 TB).  The following specs apply to the graphics:  2303MB total available memory; 1024 MB Dedicated graphics memory; 0MB dedicated system memory.  Primary monitor resolution is 1680 x 1050.  Secondary monitor resolution is 1289 x 1024.  The direct x version is direct X 10.  However, that "box" inside fsx is not checked - that preview direct x or whatever it is.

 

Ok that's the specs.  The above is all literally "Greek" to me - I know nothing of what it means.  Regarding Bios, and overclocking.  I know nothing about them, I never messed with them, etc.  I tired to copy and paste, here, a copy of my fsx cfg file, but it won't let me.  It looks ok to me (haha), but again I know little about it. 

 

I don't know if I should re-try loading Nebraska, or, delete and reinstall fsx.  I should mention that today, flying in Colorado (another recent "potentially corrupt" megascenery purchase.  Also, through your analysis, please remember - I have 10 megascenery areas ( the original purchase of mine) that were absolutely fine.

 

I do consider you more expert than myself, but I can't help thinking if I had a memory/resources problem that none of the megascenery would work. 

 

Anyhow, thanks for your input, and I look forward to reading more from you on this.

 

Ken

[Jim Young 2,356]

 

 

Megascenery is installed on an external hard drive (WD, 2 TB).

 

Sounds like the same MyBook 2TB HDD that I have.  I use mine for the backups.  I have never tried to run anything on an external HHD connected to a USB port.  It all depends I suppose on the speed of the USB port.  There are two types of USB Ports, one is 3.0 and the other 2.0 (which is of course has slower transfers).  I would move the Nebraska folder over to your HHD then go into the Scenery Library and edit the location of the scenery.  See if this fixes the problem.  An external HDD is normally used for backup and storage.  This may be your problem.  According to the WD website, the external HDD should be used for backup and storage.  You can get a 1TB HDD for about $70 and maybe cheaper with sales.  You would want to get one that spins at the rate of 7200 rpm's.

 

Your Q6850 is about 3 times slower than the Intel i7 2600K so it's not the top of the line http://www.cpubenchmark.net/cpu.php?cpu=Intel+Core2+Extreme+Q6850+%40+3.00GHz.  You have to be careful with it and don't try to put a lot of demands on it.  It should still run FSX okay but you will run into some fps issues at commercial airports.  You should make sure your Fsx.cfg settings are as suggested by the MegaSceneryEarth developers - http://www.megasceneryearth.com/support/MegaSceneryEarth-How-To-Optimize-Graphics-Settings.htm. 

 

The monitor looks fine.  The two ATI graphics cards are great too.  Shouldn't cause a problem with FSX.

 

Installing FSX on Windows 7 64 bit was smart as a 64 bit system will handle memory for your applications better than a 32 bit OS.  But FSX can only use up to a max of 4 GB as this is all Windows will allow for a 32 bit application.  The rest of your memory would be used for Windows to keep it running.

 

I now have 35 States installed.  When I first started buying and installing the States several months ago, I really had no problems running FSX for a while.  I don't recall how many States I had installed before FSX started to get slower and slower in loading and I encountered a couple of freezes (but think those were from my weather program).  That's when I decided I had to disable every State and just use the ones I plan on flying over.  I discussed that earlier here so no need to reiterate the method I used to do this. 

 

So, to summarize, it appears your external HDD may be causing the fatal errors.  It just cannot keep up with the demands of FSX to render a texture.

 

Hope this helps.

 

Best regards,

Jim

[CaptainKen 0]

WOW - SO much information you present.  Thank you Jim.  OK - this all makes sense - maybe its time to upgrade - IF I went that route, should I bite the bullet and get a whole new system?  Or might it be worth my while to just upgrade the processor (if that's even possible)?  As you should be able to tell, I value your input highly - so please give me your opinion.  I am not broke - but of course, laying out a couple of grand for a new system isn't what anyone "wants" to do - but your opinion (and anyone else reading this forum) is so welcomed.  IF I bought the bullet, I am leaning strongly toward a system I saw advertised in PC Pilot magazine - it is a machine built solely for fsx (so they say).  It is called the Fusion Hornet and is made by someone called Chillblast.  But I'd welcome your opinion here too.

 

I get a little muddled with some of the terminology - but if I understood your last post, you think maybey I should move the Nebraska to the COMPUTER versus the external wd.  I'll give it a try and see what happens - le you know shortly.   

[cbalow 2]

Ken,

 

I am with you.  I really don't think it is an in game performance thing.  However, I am starting to believe it IS in installation performance thing.  I thought I had Utah resolved, but in depth testing has revealed that I have not fixed the issue.

 

I have literally been reviewing the results 1 tile at a time. (I have a good process going, thank goodness for multiple monitors)   I am finding that if I find a tile that fails, (not file, but tile) I can re-install just that tile and it will fix it 80% of the time.  Interestingly enough, I find that the ones I cannot resolve are where the airport lies across more than 1 tile.  I am also doing this @ ground level.  Maybe @ FL300 they won't fail because I can zoom out in map view and be perfectly fine (no CTD).  

 

I am slowly making progress and confident that I will be able to run without issue at some point, I have decided that I will not be doing this for every state I purchase, so unless I can find a system resolution, no more MSE2.0 states for me.

 

Now, with that said, Jim just brought to my attention another system config thing to check.  I dramatically increased my bufferpool size per another forum thread, before I started having these issues.  It appeared to have no impact (positive or negative) so I figured it was one of those irrelevant things.  But I now have another rabbit hole I can go down   :rolleyes:   

[Jim Young 2,356]

I reviewed the Fusion Hornet and it looks like a decent system - http://www.chillblast.com/Chillblast-Fusion-Hornet.html.  The i5 3570K CPU is a little more than 2 x's faster than the CPU you have now -  http://www.cpubenchmark.net/cpu.php?cpu=Intel+Core+i5-3570K+%40+3.40GHz&id=828.  If you could get a system with an i7 3770K, it would be better http://www.techpowerup.com/reviews/Intel/Core_i5_3570K_and_i7_3770K_Comparison/11.html.  The i7 3770K costs about $107 more than the 3570. Not much more and it is more future-proof.  FSX uses the CPU more than the GPU to operate so the CPU is important.  In the previous versions of flightsims, it was the GPU that was most important.  I like the rest of the specs of the Chillblast Fusion Hornet though.

 

 

 

I get a little muddled with some of the terminology - but if I understood your last post, you think maybey I should move the Nebraska to the COMPUTER versus the external wd. I'll give it a try and see what happens - le you know shortly.

 

That's exactly correct.  Move the folder over to your HDD then go into the Scenery Library and show where the Nebraska folder is now located.

 

Hope this helps!

 

Best regards,

Jim

 

 But I now have another rabbit hole I can go down   :rolleyes:   

:LMAO: Love it!  You can easily try out whether to use the Bufferpool setting or not by simply "commenting" out Bufferpool (you would not have to delete the entry) as follows:

 

//[bUFFERPOOLS]

//UsePools=1
//Poolsize=8388608

//RejectThreshold=126976

 

When you place the slashes (//) in front of the item, that item will not be loaded when you start up FSX.  So you can try FSX with the Bufferpools disabled in this way and then try it by removing the slashes.

 

Best regards,

Jim
 

[macermacer 0]

So it just shuts down...Odd

[CaptainKen 0]

In an effort to keep you updated, I'll write more:  1.  I moved the scenery from the external to the internal.  Crashed as expected, where expected.  Nothing going but the default Cessna.  THEN I decided to try a flight with the megascenery I got the first time.  I flew from Pit (pa) to LAG (NY)  I used Megascenery for Pa, none for NJ (I don't have it) and then Mega in NY.  All the scenes switched, no issues at all.  No stuttering, no crash, etc.  I also flew this "Loaded" - That is, I had VoxAtc running (a resource hog), and FS discover running.  The frames were great all throughout the flight.  I had no issues at all.  It has to be the new scenery - it has to be.

 

However, I still appreciate ALL of the input from the forum.  And thanks for the info on the processor Jim.  If I do go that route, I'll but the I7, FOR SURE. 

 

Cbalow - I wish I knew what to tell you - you are in the same boat as me, I guess.  We just got bad disks (admitted by the mfr.).  They are sending me new ones for Nebraska and Indiana.  When I spoke to them by phone, they were the only ones I knew that were bad.  I got an email - they are on their way.  But I know for sure Colorado is bad too.  I'm not sure about Iowa and Ohio, because I haven't used that are since all the trouble began.  But if I can still fly as is, then be so be it.  I'll just have to avoid the new scenery in those states.  But it just hurts inside, if you know what I mean.  I'll continue to post any new "progress" in determining either the depth of the problem, or any hint toward resolving these issues.,

 

Ken

[Jim Young 2,356]

Hi Ken,

 

Thanks for your comments.  I'm not familiar with the DVD series as I downloaded all of my 35 States.  You're the first to report MSE V2 corruption so that's why I thought it was all strange.  When I downloaded the scenery I found corruption but Windows wouldn't even let me open up the program so I had to go back to the developer and advise him that such and such .zip file was corrupted.  They found the corruption and placed corrected versions on their download site.  Meanwhile, while waiting for them to fix the one file, I went ahead and installed everything else.  Just those corrupted tiles would not show up.

 

Hope you can get this issue resolved soon.

 

Best regards,

Jim

[CaptainKen 0]

Final Post - Got new disks today from Megascenery folks.  Installed them.  They are working like a gem.  No crashes.  So, I believe it is safe to say it was corrupted files from bad disks.  My Heartfelt thanks to all who in any way tried to help me fix this problem.  I think this should be categorized as "answered" on the forum.

 

Ken

[Jim Young 2,356]

Great news that the problem has been resolved.  Thanks for posting the solution.

 

Best regards,

Jim

[cbalow 2]

Glad to hear Ken.  I however am giving up.  I have downloaded and reinstalled Colorado 2x times and Utah several times.  I still get consistent CTD at the same location.   I might contact them and see if they will send me discs.  For I think the issue is somewhere in the download and installation.