Good day all.

 

Started getting CTD and trying to figure out the reason. I am guessing vPilot but not sure. Addons used: vPilot, OpusFSX, PMDG 772.

Any help is appreciated.

Thank you

 

See the end of this message for details on invoking 

just-in-time (JIT) debugging instead of this dialog box.

 

************** Exception Text **************

System.Runtime.InteropServices.COMException (0xC000014B): Exception from HRESULT: 0xC000014B

   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

   at Microsoft.FlightSimulator.SimConnect.SimConnect.RequestDataOnSimObjectType(Enum RequestID, Enum DefineID, UInt32 dwRadiusMeters, 

 

SIMCONNECT_SIMOBJECT_TYPE type)

   at cg.v()

   at bs.f(Object A_0, EventArgs A_1)

   at System.Windows.Forms.Timer.OnTick(EventArgs e)

   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

 

************** Loaded Assemblies **************

mscorlib

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5477 (Win7SP1GDR.050727-5400)

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

vPilot

    Assembly Version: 1.0.5260.20091

    Win32 Version: 1.0.0.0

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

Ninject

    Assembly Version: 3.2.0.0

    Win32 Version: 3.2.2.0

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

System.Windows.Forms

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)

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

System

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

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

System.Drawing

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

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

System.Core

    Assembly Version: 3.5.0.0

    Win32 Version: 3.5.30729.5420 built by: Win7SP1

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

Anonymously Hosted DynamicMethods Assembly

    Assembly Version: 0.0.0.0

    Win32 Version: 2.0.50727.5477 (Win7SP1GDR.050727-5400)

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

System.Xml

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)

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

System.Configuration

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)

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

zwvtsdu-

    Assembly Version: 1.0.5260.20091

    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

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

Accessibility

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

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

System.Management

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

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

Microsoft.DirectX.AudioVideoPlayback

    Assembly Version: 1.0.2902.0

    Win32 Version: 5.04.00.2904

    CodeBase: 

 

 

ll

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

Microsoft.DirectX

    Assembly Version: 1.0.2902.0

    Win32 Version: 5.04.00.2904

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

92kd8e0q

    Assembly Version: 1.0.5260.20091

    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

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

Microsoft.FlightSimulator.SimConnect

    Assembly Version: 10.0.61259.0

    Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421)

    CodeBase: 

 

 

ct.dll

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

SharpDX.DirectInput

    Assembly Version: 2.6.0.0

    Win32 Version: 2.6.0

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

SharpDX

    Assembly Version: 2.6.0.0

    Win32 Version: 2.6.0

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

System.Web.Services

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

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

iiocizdr

    Assembly Version: 1.0.5260.20091

    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

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

msvcm80

    Assembly Version: 8.0.50727.4940

    Win32 Version: 8.00.50727.4940

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

4u4eyogl

    Assembly Version: 1.0.5260.20091

    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

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

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

    <system.windows.forms jitDebugging="true" />

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

 

Version=1

EventType=APPCRASH

EventTime=130468341382903057

ReportType=2

Consent=1

UploadTime=130493340650370680

ReportIdentifier=2437bd32-f037-11e3-8d6d-e03f498675dd

IntegratorReportIdentifier=2437bd31-f037-11e3-8d6d-e03f498675dd

WOW64=1

Response.BucketId=2264211002

Response.BucketTable=1

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=atkexComSvc.exe

Sig[1].Name=Application Version

Sig[1].Value=0.0.0.0

Sig[2].Name=Application Timestamp

Sig[2].Value=00000000

Sig[3].Name=Fault Module Name

Sig[3].Value=StackHash_0a9e

Sig[4].Name=Fault Module Version

Sig[4].Value=0.0.0.0

Sig[5].Name=Fault Module Timestamp

Sig[5].Value=00000000

Sig[6].Name=Exception Code

Sig[6].Value=c0000005

Sig[7].Name=Exception Offset

Sig[7].Value=74b371fc

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=6.1.7601.2.1.0.256.48

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=1033

DynamicSig[22].Name=Additional Information 1

DynamicSig[22].Value=0a9e

DynamicSig[23].Name=Additional Information 2

DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789

DynamicSig[24].Name=Additional Information 3

DynamicSig[24].Value=0a9e

DynamicSig[25].Name=Additional Information 4

DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789

UI[2]=C:\Program Files (x86)\ASUS\AXSP\1.01.02\atkexComSvc.exe

UI[5]=Check online for a solution (recommended)

UI[6]=Check for a solution later (recommended)

UI[7]=Close

UI[8]=atkexComSvc.exe stopped working and was closed

UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.

UI[10]=&Close

LoadedModule[0]=C:\Program Files (x86)\ASUS\AXSP\1.01.02\atkexComSvc.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\syswow64\ADVAPI32.DLL

LoadedModule[5]=C:\Windows\syswow64\msvcrt.dll

LoadedModule[6]=C:\Windows\SysWOW64\sechost.dll

LoadedModule[7]=C:\Windows\syswow64\RPCRT4.dll

LoadedModule[8]=C:\Windows\syswow64\SspiCli.dll

LoadedModule[9]=C:\Windows\syswow64\CRYPTBASE.dll

LoadedModule[10]=C:\Windows\system32\VERSION.DLL

LoadedModule[11]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.DLL

LoadedModule[12]=C:\Windows\syswow64\GDI32.dll

LoadedModule[13]=C:\Windows\syswow64\USER32.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\system32\MSIMG32.DLL

LoadedModule[18]=C:\Windows\syswow64\OLE32.DLL

LoadedModule[19]=C:\Windows\syswow64\OLEAUT32.DLL

LoadedModule[20]=C:\Windows\system32\IMM32.DLL

LoadedModule[21]=C:\Windows\syswow64\MSCTF.dll

LoadedModule[22]=C:\Windows\system32\olepro32.dll

LoadedModule[23]=C:\Windows\system32\asio.dll

LoadedModule[24]=C:\Windows\system32\MFC42.DLL

LoadedModule[25]=C:\Windows\system32\ODBC32.dll

LoadedModule[26]=C:\Windows\system32\odbcint.dll

LoadedModule[27]=C:\Program Files (x86)\ASUS\AXSP\1.01.02\PEbiosinterface32.dll

LoadedModule[28]=C:\Program Files (x86)\ASUS\AXSP\1.01.02\ATKEX.dll

LoadedModule[29]=C:\Windows\syswow64\CLBCatQ.DLL

LoadedModule[30]=C:\Windows\system32\CRYPTSP.dll

LoadedModule[31]=C:\Windows\system32\rsaenh.dll

LoadedModule[32]=C:\Windows\system32\RpcRtRemote.dll

LoadedModule[33]=C:\Windows\system32\SXS.DLL

State[0].Key=Transport.DoneStage1

State[0].Value=1

FriendlyEventName=Stopped working

ConsentKey=APPCRASH

AppName=atkexComSvc.exe

AppPath=C:\Program Files (x86)\ASUS\AXSP\1.01.02\atkexComSvc.exe

Error 7/27/2014 5:03:48 PM Application Error 1000 (100)

 

Log Name:      Application

Source:        Application Error

Date:          7/27/2014 5:03:48 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      Owner-PC

Description:

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

Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86

Exception code: 0xe06d7363

Fault offset: 0x0000c42d

Faulting process id: 0x%9

Faulting application start time: 0x%10

Faulting application path: %11

Faulting module path: %12

Report Id: %13

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2014-07-27T22:03:48.000000000Z" />

    <EventRecordID>6463</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Owner-PC</Computer>

    <Security />

  </System>

  <EventData>

    <Data>fsx.exe</Data>

    <Data>10.0.61637.0</Data>

    <Data>46fadb14</Data>

    <Data>KERNELBASE.dll</Data>

    <Data>6.1.7601.18409</Data>

    <Data>53159a86</Data>

    <Data>e06d7363</Data>

    <Data>0000c42d</Data>

  </EventData>

</Event>

The faulting module - StackHash (then four digits/letters indicating memory address where crash occurred) is common but it was caused when running atkexComSvc.exe.  This program belongs to the ASUS AI Suite. To get rid of it is nearly impossible.  It remains on my system and the only way I know of to get rid of it is to reformat the HDD and reinstall Windows.  It's a program filled with so many bugs, like memory leaks, etc., that ASUS should be totally ashamed they developed the program.  It's an ASUS related Motherboard Utility.  What it does I have no idea but I disabled the ASUS Com Service and my computer works great again.  I think it is needed if you have ASUS AI Suite installed which is also impossible to uninstall (and you definitely do not need to have the ASUS AI Suite installed).  I finally got mine uninstalled and I feel sorry for anyone who has it installed.  It causes so many problems.  You might want to Google atkexComSvc.exe and read up about it.  I do not know how many man hours I spent researching this and the ASUS HM Com Services.  I do know it is not required to run Windows.  Some say it has something to do with your fans but I have it disabled and my fans work great w/o the services. It may be some kind of communication device between Windows and your Motherboard for a service that ASUS thinks is neat, really cool and everyone should have it.  Just disable those ASUS com services and see if this fixes the problem (believe your Event Viewer will get upset they cannot find the service whenever Windows starts up).  If you look at the processes running on your system (ctrl-alt-del), you will see these two Com Services are eating memory like it's going out of style.  Unfortunately, ASUS techs have no idea these services are leaking memory and could care less (or at least I see no fix has ever been issued).  ASUS continues to install this Malware (my definition) on systems when individuals install the ASUS AI Suite.
 
I don't know if vPilot uses Simconnect but the top error is a Microsoft Visual C++ generated error (Microsoft Visual C++ is doing the job it was installed to do - find problems and let you know). Exception from HRESULT: 0xc000014B error - The 0xc000014B is a "broken pipe" exception. A pipe is a communication channel between two applications (such as FSX and an addon program like ASN or OPUS). SimConnect offers addons the possibility to use pipes to communication with FSX. A "broken pipe" is a situation where one of the pipes no longer exists, while the other tries to communicate using the pipe. A typical scenario would be fsx crashing and then ASN or OPUS tried to use the pipe (communications channel) and the “pipe” was broken. The 014B exception would then occur. 

 

All of FSX addons make sure that Simconnect is properly installed to run their application.  You can disable vPilot (not sure how to do that; maybe not start it up?) and see if that fixes the problem.  If so, I would reinstall the application using Administrative Privileges (right click and select run as Administrator).  Same goes with OPUS.  I doubt the problem lies with the PMDG 772 but they did install a program call RAASPRO and there's an entry placed in the dll.xml.  It could be corrupted.  Just so many possibilities and you can only start uninstalling things like vPilot, OPUS, PMDG, etc., until the problem goes away.

 

The last crash shows the kernelbase.dll as the faulting module.  As stated in the AVSIM CTD Guide, there is no known fix but some have fixed this problem by updating or reinstalling their video card drivers.  That's a longshot fix but might be worth a try.  I checked the version you have and it is the same as on my system. 

 

Hope this helps.

 

Best regards,

Thank you for response. 

 

That is so said. Before I built this PC I did research and all hardware, fans, video card and especially ASUS motherboard I have was highly recommended.

Windows was reinstalled 3 times already. Windows 7 is located in its dedicated SSD drive, DSX is on its own larger SSD drive. HDD drive is a back up, where I installed other software like vPilot, OpusFSX. PFPX... If I reformat HDD I am not sure it will make any difference. I don't have CTD all the time, usually it happens after landing on taxi. I will do more flying to see if I have any other errors. I wonder if I am able to get ird of  atkexComSvc.exe, if not, what the possible solution could be? Another brand motherboard? 

 As to disable ASUS com services... Which one are ASUS services? I was unable to find them:

 

 

I will try to reinstall those addons you have mentioned above.

 

Thank you for help

If you have the ASUS Com Service disabled in Services, then it should not be showing up in your Task Manager/Processes. I'm just saying that your crash report indicates the module is being loaded. You might click on your Start button and then type msconfig in the search box and then look up in the Menu and click on msconfig. When open, click on the Services tab and then check the box, "Hide all Microsoft Services" and see if you see ASUS Com Service and ASUS HM Com Service. Make sure there are no check marks next to the names if you see them. If you do not see them, then I suspect you have a virus as this app has been used by malicious users to gain access to systems. That likelihood is unlikely but I mention it as a precaution.

 

There is nothing wrong with your ASUS Motherboard. It is a great board and I have it too and I have only owned ASUS MB's. It's the program(s) they install with ASUS AI Suite (which is not needed to make your motherboard work) that causes problems.

 

If the problem is occurring occasionally, then I would try to live with it until you have to reinstall Windows (you don't have to reformat your HDD).

 

Best regards,

Thank you Jim.

 

I did have ASUS Com Service enabled. I just disabled it, will see what happens. I contacted a couple of add-on developers as well and they said that they were working on some issues as well on they end especially vPilot. I was also told that AUSU had released Bios update and that should help as well. Will keep testing.

 

Thank you for help. 

If you have the ASUS Com Service disabled in Services, then it should not be showing up in your Task Manager/Processes. I'm just saying that your crash report indicates the module is being loaded. You might click on your Start button and then type msconfig in the search box and then look up in the Menu and click on msconfig. When open, click on the Services tab and then check the box, "Hide all Microsoft Services" and see if you see ASUS Com Service and ASUS HM Com Service. Make sure there are no check marks next to the names if you see them. If you do not see them, then I suspect you have a virus as this app has been used by malicious users to gain access to systems. That likelihood is unlikely but I mention it as a precaution.

 

 

Jim.

 

I did everything what you suggested, so far no more CTD.  I am wondering if you have experience with these error messages:

 

6DOF Error<div style=": rgb246, 246, 246;">  and  Exception from HRESULT: 0xC00000B0<div style=" 

 

Those errors do not cause CTD, but I see those error when I use OpusFSX. There is monitor window withing Opus wich detect all errors and this is the only place where those error apper when Opus crashes.  know this topic is not about OpusFSX here but developer said that those error are nothing to do with OpusFSX. He said that it is FSX issue. If I do not run OpusFSX I do not get those errors. I asked other simmers how had same triple monitor setup and using Opus and they do not have these errors. It could be something withing my FSX or PC or something else. I wonder if you can suggest anything I may need to look at. 

 

Thank you. 

I would say your problem is somehow connected to your triple monitors. HRESULT: 0xC00000B0 is a Microsoft.net error. Make sure you have Microsoft.net versions 2.0, 3.0, 3.5, and any of the latest installed. They are not backward compatible so, if OPUS requires Microsoft.net 3.5, and you only have 4.5 installed, this could be a problem. As the developer of OPUS rightly stated, if something is wrong with your installation of FSX/Acceleration, then a problem could occur with any addon. FSX requires Microsoft.net 1.1 or 2.0 to run properly. Same goes with Microsoft Visuals which are used by developers to make sure you product is installed properly. FSX requires Microsoft Visuals 2005 w/SP1 and 2008. See the AVSIM CTD Guide for more guidance on Microsoft Visuals and Microsoft.net including links to the proper versions.

 

Best regards,

I installed FSX+ Acceleration based on NickN bible (from simforum) and PMDG recommendations, both are the same. I did it carefully so I think I did it right. 

 

This is what I have in PC:

 

 

If I understood correctly I have to have all those NET.Framework be installed, not just a latest one? I do not have Microsoft.net versions 2.0, 3.0, 3.5 for some reason.

 

"FSX requires Microsoft.net 1.1 or 2.0 to run properly" - Does this mean I need NET Framework 1.1 or 2.0 installed as well? 

 

One more thing. I installed .NET Framework Setup Verification Tool. In one of the section I found this:

By default, the .NET Framework setup verification tool will only list versions of the .NET Framework that it detects are installed on the computer that it is being run on.  As a result, the tool will not list all of the above versions of the .NET Framework.  This product filtering can be overridden by running the .NET Framework setup verification tool with the following command line switch:

 

netfx_setupverifier.exe /q:a /c:"setupverifier2.exe /a"

I cannot figure out where do I have to make this change: netfx_setupverifier.exe /q:a /c:"setupverifier2.exe /a"

 

I cannot find window to enter that command to override filters.

 

 

 

Thank you for help. 

 

If I understood correctly I have to have all those NET.Framework be installed, not just a latest one? I do not have Microsoft.net versions 2.0, 3.0, 3.5 for some reason.

As we have stated in the AVSIM CTD Guide, you must have those versions installed. They are not backward compatible. They are normally installed when you install FSX, Acceleration, an Orbx product, etc., etc., but, if you move your FSX installation from a backup, they will be missing and that appears what you have done. The AVSIM CTD Guide shows you exactly where to look in your Windows installation to find out whether you have all of the versions installed (C:\Windows\Microsoft.net\Framework\then the versions).

 

netfx_setupverifier.exe /q:a /c:"setupverifier2.exe /a"

 

I cannot figure out where do I have to make this change: netfx_setupverifier.exe /q:a /c:"setupverifier2.exe /a"

Not sure if you really need to run this program but use the Windows "Run" Command (Click on the Start button and in the search box type Run and then lookup in the Menu and click on Run. Copy and paste the command there.

 

Best regards,

So far I was able to install .NET 1.1 only. I tried to install 2.0 and I got a message that version 2.0 was already part of OS. I then tried to install version 2.0 SP1, and I got error message sating that I cannot install SP1 on VIsta system. I do not have Vista, I have W7 professional. When I tried version 2 SP2 and version .NET V3.0 I was getting error message stating that I must use Turn Windows Features on or off... I was unable to figure what I had to turn on in Windows Feature window:

 

I have got a response in another forum:

 

"...versions 2.0..3.0 are not missing, since about .net 3.0 they have been included in the installation package ie. 2.0 as well as service packs.
So seeing you have 1.0 and 3.5, it should include the previous versions, 2.0 and 3.0, as well as any service packs.
(ref.)http://www.microsoft.com/en-au/download/details.aspx?id=21

You won't be able to just install these separately without removing 3.5 and possibly 4.5 first, in programs and features, as you found out, it's saying they are already installed.   What effect it may have on other things by removing these is hard to say, hmm.

Opus may be looking for a specific 2.0 version which is now updated.( by later versions 3.5 etc. )
Have you tried reinstalling opus? If the installer cannot find the correct version it needs, it should install what is needed."

 

I am wondering if does this mean I am OK and I have all those versions inside of 3.5 and 4.5 or I still have to have them installed separately?

Thx 

OK. I have another CTD today after installation ORBX FTX Vector:

 

Version=1

EventType=APPCRASH

EventTime=130528649407085133

ReportType=2

Consent=1

UploadTime=130528649409065246

ReportIdentifier=b295207a-2710-11e4-9501-e03f498675dd

WOW64=1

Response.BucketId=247846989

Response.BucketTable=17

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=fsx.exe

Sig[1].Name=Application Version

Sig[1].Value=10.0.61637.0

Sig[2].Name=Application Timestamp

Sig[2].Value=46fadb14

Sig[3].Name=Fault Module Name

Sig[3].Value=KERNELBASE.dll

Sig[4].Name=Fault Module Version

Sig[4].Value=6.1.7601.18409

Sig[5].Name=Fault Module Timestamp

Sig[5].Value=53159a86

Sig[6].Name=Exception Code

Sig[6].Value=e06d7363

Sig[7].Name=Exception Offset

Sig[7].Value=0000c42d

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=6.1.7601.2.1.0.256.48

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=1033

UI[2]=F:\FSX\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]=F:\FSX\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.762_none_0c178a139ee2a7ed\MFC80.DLL

LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\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\syswow64\USERENV.dll

LoadedModule[30]=C:\Windows\syswow64\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.18201_none_ec80f00e8593ece5\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\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.42_none_0e9c2a8d74fd3ce6\MFC80ENU.DLL

LoadedModule[60]=F:\FSX\language.dll

LoadedModule[61]=F:\FSX\API.DLL

LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\MSVCP80.dll

LoadedModule[63]=F:\FSX\ablscpt.dll

LoadedModule[64]=F:\FSX\flight.dll

LoadedModule[65]=F:\FSX\ai_player.dll

LoadedModule[66]=F:\FSX\acontain.dll

LoadedModule[67]=F:\FSX\controls.dll

LoadedModule[68]=C:\Windows\system32\DINPUT8.dll

LoadedModule[69]=F:\FSX\fsui.dll

LoadedModule[70]=F:\FSX\atc.dll

LoadedModule[71]=F:\FSX\facilities.dll

LoadedModule[72]=F:\FSX\demo.dll

LoadedModule[73]=F:\FSX\main.dll

LoadedModule[74]=F:\FSX\fe.dll

LoadedModule[75]=F:\FSX\util.dll

LoadedModule[76]=F:\FSX\simprop.dll

LoadedModule[77]=F:\FSX\g2d.dll

LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll

LoadedModule[79]=C:\Windows\system32\d3dx10_34.dll

LoadedModule[80]=F:\FSX\d3d9.dll

LoadedModule[81]=C:\Windows\system32\d3dx9_43.dll

LoadedModule[82]=F:\FSX\g3d.dll

LoadedModule[83]=F:\FSX\panels.dll

LoadedModule[84]=F:\FSX\multiplayer.dll

LoadedModule[85]=F:\FSX\ui.dll

LoadedModule[86]=F:\FSX\sound.dll

LoadedModule[87]=F:\FSX\sim1.dll

LoadedModule[88]=F:\FSX\simscheduler.dll

LoadedModule[89]=F:\FSX\visualfx.dll

LoadedModule[90]=F:\FSX\window.dll

LoadedModule[91]=F:\FSX\terrain.dll

LoadedModule[92]=F:\FSX\weather.dll

LoadedModule[93]=C:\Windows\system32\DSOUND.dll

LoadedModule[94]=C:\Windows\system32\POWRPROF.dll

LoadedModule[95]=F:\FSX\symmap.dll

LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\gdiplus.dll

LoadedModule[97]=C:\Windows\system32\MSIMG32.dll

LoadedModule[98]=F:\FSX\xuipc.dll

LoadedModule[99]=F:\FSX\livingwater.dll

LoadedModule[100]=F:\FSX\fs-traffic.dll

LoadedModule[101]=F:\FSX\gps.dll

LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll

LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll

LoadedModule[104]=C:\Windows\system32\d3d9.dll

LoadedModule[105]=C:\Windows\system32\d3d8thk.dll

LoadedModule[106]=C:\Program Files\NVIDIA Corporation\Display\NvSmartMax.dll

LoadedModule[107]=C:\Windows\system32\WTSAPI32.dll

LoadedModule[108]=C:\Windows\system32\ntmarta.dll

LoadedModule[109]=C:\Windows\syswow64\WLDAP32.dll

LoadedModule[110]=C:\Windows\system32\CRYPTSP.dll

LoadedModule[111]=C:\Windows\system32\rsaenh.dll

LoadedModule[112]=C:\Windows\syswow64\WINTRUST.dll

LoadedModule[113]=C:\Windows\syswow64\CRYPT32.dll

LoadedModule[114]=C:\Windows\syswow64\MSASN1.dll

LoadedModule[115]=C:\Windows\syswow64\CLBCatQ.DLL

LoadedModule[116]=C:\Windows\system32\wbem\wbemprox.dll

LoadedModule[117]=C:\Windows\system32\wbemcomn.dll

LoadedModule[118]=C:\Windows\system32\RpcRtRemote.dll

LoadedModule[119]=C:\Windows\system32\wbem\wbemsvc.dll

LoadedModule[120]=C:\Windows\system32\wbem\fastprox.dll

LoadedModule[121]=C:\Windows\system32\NTDSAPI.dll

LoadedModule[122]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL

LoadedModule[123]=F:\FSX\dxgi.dll

LoadedModule[124]=C:\Windows\system32\d3d10.dll

LoadedModule[125]=C:\Windows\system32\d3d10core.dll

LoadedModule[126]=C:\Windows\system32\d3d11.dll

LoadedModule[127]=C:\Windows\system32\d3dx10_43.dll

LoadedModule[128]=C:\Windows\system32\d3dx11_43.dll

LoadedModule[129]=C:\Windows\system32\MSVCR100.dll

LoadedModule[130]=C:\Windows\system32\D3DCOMPILER_43.dll

LoadedModule[131]=C:\Windows\system32\dxgi.dll

LoadedModule[132]=C:\Windows\system32\nvd3dum.dll

LoadedModule[133]=C:\Windows\syswow64\PSAPI.DLL

LoadedModule[134]=C:\Windows\system32\bcrypt.dll

LoadedModule[135]=C:\Windows\system32\D3DCompiler_34.dll

LoadedModule[136]=C:\Windows\SysWOW64\bcryptprimitives.dll

LoadedModule[137]=C:\Windows\system32\WindowsCodecs.dll

LoadedModule[138]=C:\Windows\system32\d3d10_1.dll

LoadedModule[139]=C:\Windows\system32\d3d10_1core.dll

LoadedModule[140]=C:\Windows\SysWOW64\dxdiagn.dll

LoadedModule[141]=C:\Windows\system32\winbrand.dll

LoadedModule[142]=C:\Windows\system32\WINSTA.dll

LoadedModule[143]=C:\Windows\SysWOW64\gameux.dll

LoadedModule[144]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll

LoadedModule[145]=C:\Windows\SysWOW64\XmlLite.dll

LoadedModule[146]=C:\Windows\SysWOW64\wer.dll

LoadedModule[147]=C:\Windows\System32\Wpc.dll

LoadedModule[148]=C:\Windows\System32\wevtapi.dll

LoadedModule[149]=C:\Windows\System32\msxml6.dll

LoadedModule[150]=C:\Windows\system32\SAMLIB.dll

LoadedModule[151]=C:\Windows\system32\netutils.dll

LoadedModule[152]=F:\FSX\uiautomationcore.dll

LoadedModule[153]=C:\Windows\system32\OLEACC.dll

LoadedModule[154]=C:\Windows\System32\MMDevApi.dll

LoadedModule[155]=C:\Windows\System32\PROPSYS.dll

LoadedModule[156]=C:\Windows\system32\AUDIOSES.DLL

LoadedModule[157]=C:\Windows\system32\RICHED20.DLL

LoadedModule[158]=C:\Windows\system32\HID.DLL

LoadedModule[159]=C:\Windows\system32\XInput9_1_0.dll

LoadedModule[160]=C:\Windows\system32\wdmaud.drv

LoadedModule[161]=C:\Windows\system32\ksuser.dll

LoadedModule[162]=C:\Windows\system32\AVRT.dll

LoadedModule[163]=C:\Windows\system32\msacm32.drv

LoadedModule[164]=C:\Windows\system32\midimap.dll

LoadedModule[165]=C:\Windows\system32\dinput.DLL

LoadedModule[166]=C:\Windows\System32\wship6.dll

LoadedModule[167]=C:\Windows\System32\wshtcpip.dll

LoadedModule[168]=F:\FSX\PMDG\DLLs\PMDG_Interface.dll

LoadedModule[169]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll

LoadedModule[170]=F:\FSX\RAASPRO\RAASPRO.dll

LoadedModule[171]=C:\Windows\system32\Secur32.dll

LoadedModule[172]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll

LoadedModule[173]=C:\Windows\system32\IPHLPAPI.DLL

LoadedModule[174]=C:\Windows\system32\WINNSI.DLL

LoadedModule[175]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll

LoadedModule[176]=C:\Windows\system32\DNSAPI.dll

LoadedModule[177]=C:\Windows\System32\netprofm.dll

LoadedModule[178]=C:\Windows\System32\nlaapi.dll

LoadedModule[179]=C:\Windows\system32\dhcpcsvc6.DLL

LoadedModule[180]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll

LoadedModule[181]=C:\Windows\system32\dhcpcsvc.DLL

LoadedModule[182]=C:\Windows\system32\rasadhlp.dll

LoadedModule[183]=C:\Windows\System32\npmproxy.dll

LoadedModule[184]=C:\Windows\System32\fwpuclnt.dll

LoadedModule[185]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll

LoadedModule[186]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll

LoadedModule[187]=C:\Windows\system32\MSDART.DLL

LoadedModule[188]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll

LoadedModule[189]=C:\Program Files (x86)\Common Files\System\Ole DB\OLEDB32R.DLL

LoadedModule[190]=C:\Windows\system32\comsvcs.dll

LoadedModule[191]=C:\Windows\system32\ATL.DLL

LoadedModule[192]=C:\Windows\SysWOW64\msjetoledb40.dll

LoadedModule[193]=C:\Windows\SysWOW64\msjet40.dll

LoadedModule[194]=C:\Windows\SysWOW64\mswstr10.dll

LoadedModule[195]=C:\Windows\SysWOW64\msjter40.dll

LoadedModule[196]=C:\Windows\SysWOW64\MSJINT40.DLL

LoadedModule[197]=C:\Windows\SysWOW64\mstext40.dll

LoadedModule[198]=C:\Windows\system32\mlang.dll

LoadedModule[199]=C:\Windows\system32\RAASAUDIO32.DLL

LoadedModule[200]=C:\Windows\system32\X3DAudio1_6.dll

LoadedModule[201]=C:\Windows\SysWow64\xactengine3_4.dll

LoadedModule[202]=C:\Windows\SysWow64\XAudio2_4.dll

LoadedModule[203]=F:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll

LoadedModule[204]=F:\FSX\Modules\FSUIPC4.dll

LoadedModule[205]=F:\FSX\VistaMare\ViMaCoreX.dll

LoadedModule[206]=F:\FSX\VistaMare\bin\VMCX_AP.dll

LoadedModule[207]=F:\FSX\VistaMare\bin\ViMaNET_AP.dll

LoadedModule[208]=F:\FSX\as_srv\as_btstrp.dll

LoadedModule[209]=C:\Windows\system32\mscoree.dll

LoadedModule[210]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll

LoadedModule[211]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll

LoadedModule[212]=C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\f8be9e33457f57805b4068f90099e428\mscorlib.ni.dll

LoadedModule[213]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsec.dll

LoadedModule[214]=C:\Windows\syswow64\imagehlp.dll

LoadedModule[215]=C:\Windows\system32\ncrypt.dll

LoadedModule[216]=C:\Windows\system32\GPAPI.dll

LoadedModule[217]=C:\Windows\system32\cryptnet.dll

LoadedModule[218]=C:\Windows\system32\SensApi.dll

LoadedModule[219]=C:\Windows\system32\WINHTTP.dll

LoadedModule[220]=C:\Windows\system32\webio.dll

LoadedModule[221]=C:\Windows\system32\credssp.dll

LoadedModule[222]=F:\FSX\as_srv\as_connect.dll

LoadedModule[223]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll

LoadedModule[224]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System\2ee90c95adb50b0e75b814fcb9d87f8e\System.ni.dll

LoadedModule[225]=F:\FSX\Modules\VAInterface.dll

LoadedModule[226]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll

LoadedModule[227]=C:\Windows\SysWOW64\ieframe.dll

LoadedModule[228]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll

LoadedModule[229]=C:\Windows\SysWOW64\mshtml.dll

LoadedModule[230]=C:\Windows\system32\msimtf.dll

LoadedModule[231]=C:\Windows\system32\msls31.dll

LoadedModule[232]=C:\Windows\system32\d2d1.dll

LoadedModule[233]=C:\Windows\system32\DWrite.dll

LoadedModule[234]=C:\Windows\system32\D3D10Warp.dll

LoadedModule[235]=C:\Windows\SysWOW64\uiautomationcore.dll

LoadedModule[236]=C:\Windows\system32\srvcli.dll

LoadedModule[237]=C:\Windows\system32\wkscli.dll

LoadedModule[238]=C:\Windows\SysWow64\XAudio2_7.dll

LoadedModule[239]=C:\Windows\system32\napinsp.dll

LoadedModule[240]=C:\Windows\system32\pnrpnsp.dll

LoadedModule[241]=C:\Windows\System32\winrnr.dll

LoadedModule[242]=C:\Windows\system32\icmp.Dll

LoadedModule[243]=C:\Windows\system32\LINKINFO.dll

LoadedModule[244]=C:\Windows\system32\SearchFolder.dll

LoadedModule[245]=C:\Windows\system32\ntshrui.dll

LoadedModule[246]=C:\Windows\system32\cscapi.dll

LoadedModule[247]=C:\Windows\system32\slc.dll

LoadedModule[248]=C:\Windows\system32\explorerframe.dll

LoadedModule[249]=C:\Windows\system32\DUser.dll

LoadedModule[250]=C:\Windows\system32\DUI70.dll

LoadedModule[251]=C:\Program Files\Microsoft Office 15\root\Office15\GROOVEEX.DLL

LoadedModule[252]=C:\Program Files\Microsoft Office 15\root\Office15\MSVCP100.dll

LoadedModule[253]=C:\Program Files\Microsoft Office 15\root\Office15\ATL100.DLL

LoadedModule[254]=C:\Program Files\Microsoft Office 15\root\Office15\1033\GrooveIntlResource.dll

LoadedModule[255]=C:\Windows\system32\EhStorShell.dll

LoadedModule[256]=C:\Program Files (x86)\Kaspersky Lab\Kaspersky PURE 3.0\shellex.dll

LoadedModule[257]=C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll

LoadedModule[258]=C:\Windows\System32\StructuredQuery.dll

LoadedModule[259]=C:\Windows\system32\mssprxy.dll

LoadedModule[260]=C:\Windows\SysWOW64\thumbcache.dll

LoadedModule[261]=C:\Windows\system32\SHDOCVW.dll

LoadedModule[262]=C:\Windows\system32\NetworkExplorer.dll

LoadedModule[263]=C:\Program Files (x86)\Internet Explorer\ieproxy.dll

LoadedModule[264]=C:\Windows\System32\drprov.dll

LoadedModule[265]=C:\Windows\System32\ntlanman.dll

LoadedModule[266]=C:\Windows\System32\davclnt.dll

LoadedModule[267]=C:\Windows\System32\DAVHLPR.dll

LoadedModule[268]=C:\Windows\system32\PortableDeviceApi.dll

LoadedModule[269]=C:\Windows\SysWOW64\actxprxy.dll

LoadedModule[270]=C:\Windows\system32\EhStorAPI.dll

LoadedModule[271]=F:\FSX\GAUGES\PMDG_777X.DLL

LoadedModule[272]=C:\Windows\system32\NETAPI32.dll

LoadedModule[273]=C:\Windows\system32\WSOCK32.dll

LoadedModule[274]=F:\FSX\GAUGES\PMDG_777X_3.DLL

LoadedModule[275]=F:\FSX\Gauges\PMDG_777X_2.dll

LoadedModule[276]=C:\Windows\system32\snmpapi.dll

LoadedModule[277]=F:\FSX\VistaMare\bin\ViMaIScnX_AP.dll

LoadedModule[278]=C:\Windows\system32\d3dx9_31.dll

LoadedModule[279]=C:\Windows\SysWOW64\msjtes40.dll

LoadedModule[280]=C:\Windows\system32\VBAJET32.DLL

LoadedModule[281]=C:\Windows\system32\expsrv.dll

LoadedModule[282]=C:\Program Files (x86)\Common Files\System\ado\msadrh15.dll

LoadedModule[283]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Drawing\bce52f0521c930a2e305badb3ea07128\System.Drawing.ni.dll

LoadedModule[284]=C:\Windows\system32\msadp32.acm

State[0].Key=Transport.DoneStage1

State[0].Value=1

FriendlyEventName=APPCRASH

ConsentKey=APPCRASH

AppName=Microsoft Flight Simulator®

AppPath=F:\FSX\fsx.exe

ReportDescription=Stopped working

 

I ran system test  suggested by Microsoft, No any integrity violations were found. 

Log Name:      Application

Source:        Application Error

Date:          8/18/2014 2:49:08 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      Owner-PC

Description:

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

Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86

Exception code: 0xe06d7363

Fault offset: 0x0000c42d

Faulting process id: 0x1560

Faulting application start time: 0x01cfbb0fc58742b7

Faulting application path: F:\FSX\fsx.exe

Faulting module path: C:\Windows\syswow64\KERNELBASE.dll

Report Id: b70e0f2e-2710-11e4-9501-e03f498675dd

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2014-08-18T19:49:08.000000000Z" />

    <EventRecordID>7900</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Owner-PC</Computer>

    <Security />

  </System>

  <EventData>

    <Data>fsx.exe</Data>

    <Data>10.0.61637.0</Data>

    <Data>46fadb14</Data>

    <Data>KERNELBASE.dll</Data>

    <Data>6.1.7601.18409</Data>

    <Data>53159a86</Data>

    <Data>e06d7363</Data>

    <Data>0000c42d</Data>

    <Data>1560</Data>

    <Data>01cfbb0fc58742b7</Data>

    <Data>F:\FSX\fsx.exe</Data>

    <Data>C:\Windows\syswow64\KERNELBASE.dll</Data>

    <Data>b70e0f2e-2710-11e4-9501-e03f498675dd</Data>

  </EventData>

</Event>

Kernelbase.dll errors are usually associated with system drivers. Many have fixed this error by reinstalling their video card drivers.

 

Best regards,

Kernelbase.dll errors are usually associated with system drivers. Many have fixed this error by reinstalling their video card drivers.

 

Best regards,

 

Thank you. Will give it a try.