Can somebody please take a look at the event viewer log and maybe give me some sort of insight?

I am guessing it is the sound.dll causing it but that is a guess and no idea how to rectify it.

 

Log Name:      Application
Source:        Application Error
Date:          04/11/2017 11:51:20
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      nicks-pc
Description:
Faulting application name: Prepar3D.exe, version: 4.1.7.22841, time stamp: 0x59d67e95
Faulting module name: sound.dll, version: 4.1.7.22841, time stamp: 0x59d67e1a
Exception code: 0xc0000005
Fault offset: 0x00000000000208ad
Faulting process id: 0x2a8c
Faulting application start time: 0x01d35556d9423a00
Faulting application path: D:\p3d v4\Prepar3D.exe
Faulting module path: D:\p3d v4\sound.dll
Report Id: d2bebd44-da46-41ff-839c-3536e2e95661
Faulting package full name:
Faulting package-relative application ID:
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="2017-11-04T11:51:20.687022700Z" />
    <EventRecordID>116769</EventRecordID>
    <Channel>Application</Channel>
    <Computer>nicks-pc</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.1.7.22841</Data>
    <Data>59d67e95</Data>
    <Data>sound.dll</Data>
    <Data>4.1.7.22841</Data>
    <Data>59d67e1a</Data>
    <Data>c0000005</Data>
    <Data>00000000000208ad</Data>
    <Data>2a8c</Data>
    <Data>01d35556d9423a00</Data>
    <Data>D:\p3d v4\Prepar3D.exe</Data>
    <Data>D:\p3d v4\sound.dll</Data>
    <Data>d2bebd44-da46-41ff-839c-3536e2e95661</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

2 hours ago, easymo3 said:

Can somebody please take a look at the event viewer log and maybe give me some sort of insight?

The following link here at AVSIM might help -

I really think the problem depends on the sound device you have installed.  Do you have a dedicated sound card installed like a Creative Soundblaster?  Is internal sound enabled in your BIOS?  If you have both enabled, the P3DV4 sound module may see a conflict.  I have a Soundblaster sound card and have disabled the on-board sound setting in my BIOS so only the Soundblaster card is used.  The following link provides information on how to disable on-board sound - https://www.wikihow.com/Disable-Onboard-Sound

On 04/11/2017 at 2:48 PM, Jim Young said:

The following link here at AVSIM might help -

I really think the problem depends on the sound device you have installed.  Do you have a dedicated sound card installed like a Creative Soundblaster?  Is internal sound enabled in your BIOS?  If you have both enabled, the P3DV4 sound module may see a conflict.  I have a Soundblaster sound card and have disabled the on-board sound setting in my BIOS so only the Soundblaster card is used.  The following link provides information on how to disable on-board sound - https://www.wikihow.com/Disable-Onboard-Sound

Thank you very much, for your insight.

I will look into this issue.