Announcement

Collapse

PMDG Forum Rules

1) SIGN YOUR POSTS. Since 1997, we have asked users to sign their real name, first and last, to all posts in the PMDG forum. We do this in order to keep conversations personal and familiar. You took the time to be here, we want to get to know you. This is one of the few rigid rules that we enforce regularly. We do so because we feel that forums in which users must engage one another personally are generally warmer, more collegial and friendly. Posts that are unsigned will be quietly removed without comment by the moderators, so to make your life easy- we recommend enabling your forum signature so that you never need to remember. Do this by clicking the username pull-down at the top right, then selecting "User Settings." You will find the signature editor on the ACCOUNT tab, about half way down the page. Look for "Edit Post Signature." Be sure to click the "Show Signatures" box.

2) BE NICE. We are all simmers here and no matter our differences of opinion, we share a common love of aviation, computing and simulation. Treat everyone else in the forum with respect even when you disagree. If someone frustrates you, walk away from the conversation or ask for a moderator to get involved. Speaking of Moderators, they prefer not to be treated as "The Thought Police" but if any behavior infringes on the enjoyment of another user or is otherwise considered to be unacceptable in the moderator's judgment, it will be addressed in keeping with our view of ensuring that this forum remains a healthy environment for all simmers.

3) BE LAWFUL: Any behavior that infringes upon the law, such as discussion or solicitation of piracy, threats, intimidation or abuse will be handled unsympathetically by the moderators. Threats and intimidation may, at the moderator's discretion, be provided to law enforcement for handling.

4) BE FACTUAL: When you post, always be factual. Moderators will remove posts that are determined not to be factually accurate.

5) RESPECT COPYRIGHTS: Posting of copyrighted material such as flight manuals owned by Boeing or various airlines is not allowed in this forum. If you have questions related to copyrighted material, please contact a forum moderator for clarification.

6) RESPECT PMDG: We love to hear what you like about our products. We also like to hear what you think can be improved, or what isn't working. Please do tell us and we will always treat your feedback with value. Just be sure to treat the team respectfully, as they do put a significant amount of effort into building and maintaining these great simulation products for you.

7) RESPECT PMDG DEVELOPERS: All of the developers will spend some time here. Given the ratio of developers-to-users, it simply isn't possible for us to answer every post and private message individually. Please know that we do try to read everything, but developer workload is simply too high to manage personal contact with tens-of-thousands of users simultaneously. In most cases, members of the development team will stick to conversations in the forum and will not answer private messages.

8) RESPECT OTHER DEVELOPERS: PMDG has always advocated for a strong development community and we have many friends within this community. Every developer offers something unique that helps to make the simming community larger and more vibrant. We insist that you treat our friends respectfully.

9) RESPECT MODERATORS: Moderators have a tough job, and none of them enjoy having to stomp out negativity. If a moderator has to weigh in to keep a thread peaceful, please respect that effort and refrain from giving the moderator any grief.

10) If you require official support for any of our products please open a support ticket through the support portal, https://support.precisionmanuals.com

11) This forum is designed primarily as a vehicle for the PMDG development team to interact with our customers, and for customers to interact with one another in a manner that is positive, supportive and assists in the general advancement of understanding the simulation and helping to make this and future simulations better. Any other use of this forum is not permitted, including but not limited to discussion of pricing policies, business practices, forum moderating policies, advertising of non-PMDG products, promotion of events, services or products that are not approved in advance by PMDG or any other topic deemed unacceptable by any forum administrator

12) HAVE FUN: This is the whole point of it all.
See more
See less

MSO20win32client.dll CDT

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Anton Vind
    replied
    As you can see on the Faulting module path, it is caused by Microsoft Office. I had a lot of these crashed caused by this .dll, but since February I haven't had a single crash for some mysterious reason. Maybe I updated something that made it stop.

    Leave a comment:


  • DDowns
    replied
    I haven't seen this one in months, but there was a rash of exactly same reports earlier this year, or maybe last year (past 18 mos are a blurr). Google machine has a lot of hits on this, going to Microsoft tech support is one of them: https://social.technet.microsoft.com...ffice2016ITPro

    Leave a comment:


  • Swaluver88
    replied
    Nice to see that they made an RTX 3030 lol

    Anyways I believe this is due to Microsoft office strictly. Isk what causes p3d to ctd. Try to uninstall office fly a flight with 777 then reinstall office.

    Leave a comment:


  • NBL1936
    started a topic MSO20win32client.dll CDT

    MSO20win32client.dll CDT

    I have had this happen 2x now, both with PMDG 777. BOTH times on SHORT final. I will also be posting to P3D forums.
    My system is brand new: NVIDIA RTX 3030 with 12 G VRAM; Intel Octacore i7, 2T SSD for Flight sim drive. All Windows applications, including OFFICE have been updated as of yesterday.

    The error as shown on Event Viewer is:
    Log Name: Application
    Source: Application Error
    Date: 9/19/2021 3:39:17 PM
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: DESKTOP-4E7IL52
    Description:
    Faulting application name: Prepar3D.exe, version: 5.2.22.27615, time stamp: 0x60db69bf
    Faulting module name: mso20win32client.dll, version: 0.0.0.0, time stamp: 0x613aac42
    Exception code: 0xc0000005
    Fault offset: 0x00000000000379e1
    Faulting process id: 0xd00
    Faulting application start time: 0x01d7ad5efbedbe75
    Faulting application path: F:\Flight Sim Files & Programs\P3D v5\Prepar3D.exe
    Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll
    Report Id: 1aa37a25-5b55-42e1-8c1c-76285305c588
    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>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-09-19T20:39:17.2401429Z" />
    <EventRecordID>6833</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-4E7IL52</Computer>
    <Security />
    </System>
    <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>5.2.22.27615</Data>
    <Data>60db69bf</Data>
    <Data>mso20win32client.dll</Data>
    <Data>0.0.0.0</Data>
    <Data>613aac42</Data>
    <Data>c0000005</Data>
    <Data>00000000000379e1</Data>
    <Data>d00</Data>
    <Data>01d7ad5efbedbe75</Data>
    <Data>F:\Flight Sim Files &amp; Programs\P3D v5\Prepar3D.exe</Data>
    <Data>C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll</Data>
    <Data>1aa37a25-5b55-42e1-8c1c-76285305c588</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    </EventData>
    </Event>


    Ideas?

    Solutions?

    Dave Robinette
Working...
X