P3D v5.1 CTD - Faulting module name: mso20win32client.dll

[Martyson]

@ Bingobango ,

Just to verify the current problem is:
“When I do P3D doesn’t work at all / doesn’t load up”?

[Bingobango]

Just had this crash again for the first time in 2 weeks - I was purposely avoiding any payware airports but found it crashed again on touch down at FSDT JFK - the sim froze for 5 seconds then the sound went then CTD with the MSO20WIN32 faulting module in windbg preview. The only other system change I made before the flight was installing Aerosoft A330 pro with RAAS installed also. I have uninstalled RAAS as I read that this may have something to do with it but I don't have much hope that it solve the issue.

For me it only seems to happen on touch down or on approach to pay ware airports when traffic is near by.
I was thinking a memory issue but I have 16GB and I'm only running P3D with Active sky, PMDG/FSLABS320 on line with VPILOT.



ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000000000000c8

STACK_TEXT:
00000010`62e8ef08 00007ff8`c890f149 : 0000014a`3bce5f30 00000010`62e8f378 00000000`00000001 00007ff8`c8a757d0 : mso20win32client+0x4f23d
00000010`62e8ef10 0000014a`3bce5f30 : 00000010`62e8f378 00000000`00000001 00007ff8`c8a757d0 00000149`e480dab0 : mso20win32client+0x4f149
00000010`62e8ef18 00000010`62e8f378 : 00000000`00000001 00007ff8`c8a757d0 00000149`e480dab0 00001d70`00000001 : 0x0000014a`3bce5f30
00000010`62e8ef20 00000000`00000001 : 00007ff8`c8a757d0 00000149`e480dab0 00001d70`00000001 0000014a`3be1e080 : 0x00000010`62e8f378
00000010`62e8ef28 00007ff8`c8a757d0 : 00000149`e480dab0 00001d70`00000001 0000014a`3be1e080 00007ff8`c890f07c : 0x1
00000010`62e8ef30 00000149`e480dab0 : 00001d70`00000001 0000014a`3be1e080 00007ff8`c890f07c 0000014a`3bce6e60 : mso20win32client+0x1b57d0
00000010`62e8ef38 00001d70`00000001 : 0000014a`3be1e080 00007ff8`c890f07c 0000014a`3bce6e60 0000014a`3be1e080 : 0x00000149`e480dab0
00000010`62e8ef40 0000014a`3be1e080 : 00007ff8`c890f07c 0000014a`3bce6e60 0000014a`3be1e080 00000000`00000000 : 0x00001d70`00000001
00000010`62e8ef48 00007ff8`c890f07c : 0000014a`3bce6e60 0000014a`3be1e080 00000000`00000000 00007ff9`3d369761 : 0x0000014a`3be1e080
00000010`62e8ef50 0000014a`3bce6e60 : 0000014a`3be1e080 00000000`00000000 00007ff9`3d369761 0000014a`3be1e080 : mso20win32client+0x4f07c
00000010`62e8ef58 0000014a`3be1e080 : 00000000`00000000 00007ff9`3d369761 0000014a`3be1e080 00007ff8`c890ed8a : 0x0000014a`3bce6e60
00000010`62e8ef60 00000000`00000000 : 00007ff9`3d369761 0000014a`3be1e080 00007ff8`c890ed8a 0000014a`3be1e010 : 0x0000014a`3be1e080


SYMBOL_NAME: mso20win32client+4f23d

MODULE_NAME: mso20win32client

IMAGE_NAME: mso20win32client.dll

STACK_COMMAND: ~0s ; .ecxr ; kb

FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_c0000005_mso20win32client.dll!Unknown

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {56ee7c02-6b0d-a165-40e7-fd12cf95be3c}

Followup: MachineOwner
---------

0:000> lmvm mso20win32client
Browse full module list
start end module name
00007ff8`c88c0000 00007ff8`c8f5f000 mso20win32client T (no symbols)

[Bingobango]

Just had this crash again for the first time in 2 weeks - I was purposely avoiding any payware airports but found it crashed again on touch down at FSDT JFK - the sim froze for 5 seconds then the sound went then CTD with the MSO20WIN32 faulting module in windbg preview. The only other system change I made before the flight was installing Aerosoft A330 pro with RAAS installed also. I have uninstalled RAAS as I read that this may have something to do with it but I don't have much hope that it solve the issue.

For me it only seems to happen on touch down or on approach to pay ware airports when traffic is near by.
I was thinking a memory issue but I have 16GB and I'm only running P3D with Active sky, PMDG/FSLABS320 on line with VPILOT.



ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000000000000c8

STACK_TEXT:
00000010`62e8ef08 00007ff8`c890f149 : 0000014a`3bce5f30 00000010`62e8f378 00000000`00000001 00007ff8`c8a757d0 : mso20win32client+0x4f23d
00000010`62e8ef10 0000014a`3bce5f30 : 00000010`62e8f378 00000000`00000001 00007ff8`c8a757d0 00000149`e480dab0 : mso20win32client+0x4f149
00000010`62e8ef18 00000010`62e8f378 : 00000000`00000001 00007ff8`c8a757d0 00000149`e480dab0 00001d70`00000001 : 0x0000014a`3bce5f30
00000010`62e8ef20 00000000`00000001 : 00007ff8`c8a757d0 00000149`e480dab0 00001d70`00000001 0000014a`3be1e080 : 0x00000010`62e8f378
00000010`62e8ef28 00007ff8`c8a757d0 : 00000149`e480dab0 00001d70`00000001 0000014a`3be1e080 00007ff8`c890f07c : 0x1
00000010`62e8ef30 00000149`e480dab0 : 00001d70`00000001 0000014a`3be1e080 00007ff8`c890f07c 0000014a`3bce6e60 : mso20win32client+0x1b57d0
00000010`62e8ef38 00001d70`00000001 : 0000014a`3be1e080 00007ff8`c890f07c 0000014a`3bce6e60 0000014a`3be1e080 : 0x00000149`e480dab0
00000010`62e8ef40 0000014a`3be1e080 : 00007ff8`c890f07c 0000014a`3bce6e60 0000014a`3be1e080 00000000`00000000 : 0x00001d70`00000001
00000010`62e8ef48 00007ff8`c890f07c : 0000014a`3bce6e60 0000014a`3be1e080 00000000`00000000 00007ff9`3d369761 : 0x0000014a`3be1e080
00000010`62e8ef50 0000014a`3bce6e60 : 0000014a`3be1e080 00000000`00000000 00007ff9`3d369761 0000014a`3be1e080 : mso20win32client+0x4f07c
00000010`62e8ef58 0000014a`3be1e080 : 00000000`00000000 00007ff9`3d369761 0000014a`3be1e080 00007ff8`c890ed8a : 0x0000014a`3bce6e60
00000010`62e8ef60 00000000`00000000 : 00007ff9`3d369761 0000014a`3be1e080 00007ff8`c890ed8a 0000014a`3be1e010 : 0x0000014a`3be1e080


SYMBOL_NAME: mso20win32client+4f23d

MODULE_NAME: mso20win32client

IMAGE_NAME: mso20win32client.dll

STACK_COMMAND: ~0s ; .ecxr ; kb

FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_c0000005_mso20win32client.dll!Unknown

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {56ee7c02-6b0d-a165-40e7-fd12cf95be3c}

Followup: MachineOwner
---------

0:000> lmvm mso20win32client
Browse full module list
start end module name
00007ff8`c88c0000 00007ff8`c8f5f000 mso20win32client T (no symbols)

[Berniman]

I have Microsoft 365 Personal and no problems to report.

Dear Martyson.

what Office 365 Version do you have? I have Office 365 as well.

Thanks and regards

Bernie

[JorgenSA]

Something in your system is doing something bad. Look at this:

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

This means that something - most likely an incompatible or badly programmed add-on - is attempting to write to an area of RAM where it has no access rights.

This problem is going to remain until you remove the source from your system.

Jorgen

[Martyson]

I have Microsoft 365 Personal and no problems to report.

Dear Martyson.

what Office 365 Version do you have? I have Office 365 as well.

Thanks and regards

Bernie

@ Berniman ,
Bernie,

MSO 16.0.13530.20418 64 bit

Note:
Just to verify.
Did you test with your first install of P3D without Add-ons?

[Martyson]

@ Bingobango ,

You mentioned:
“Just had this crash again for the first time in 2 weeks - I was purposely avoiding any payware airports but found it crashed again on touch down at FSDT JFK - the sim froze for 5 seconds then the sound went then CTD with the MSO20WIN32 faulting module in windbg preview. The only other system change I made before the flight was installing Aerosoft A330 pro with RAAS installed also. I have uninstalled RAAS as I read that this may have something to do with it but I don't have much hope that it solve the issue.

For me it only seems to happen on touch down or on approach to pay ware airports when traffic is near by.
I was thinking a memory issue but I have 16GB and I'm only running P3D with Active sky, PMDG/FSLABS320 on line with VPILOT. “


My Office version is : MSO 16.0.13530.20418 64 bit

I have Vpilot but have not used it for a year or so.

I own FSDT JFK but uninstalled it some months ago.

I use DD New York now.

I do not use Aerosoft A330

I stopped using RAAS (PMDG 747) long ago.

Do you use GSX with FSDT ?

Are you overclocking?


You mentioned:
“For me it only seems to happen on touch down or on approach to pay ware airports when traffic is near by.”

Which Traffic ?
Default traffic?
Payware Traffic?
Freeware Traffic?

[Berniman]

I have Microsoft 365 Personal and no problems to report.

Dear Martyson.

what Office 365 Version do you have? I have Office 365 as well.

Thanks and regards

Bernie

@ Berniman ,
Bernie,

MSO 16.0.13530.20418 64 bit

Note:
Just to verify.
Did you test with your first install of P3D without Add-ons?

No... I didn't... should I de-Install everything? That will take ages :-(

[Martyson]

@ Berniman ,

You mentioned:
“No... I didn't... should I de-Install everything? That will take ages”

That would be your call.
You know your flight sim setup best.

Which Office version are you using?

When did this problem first start on your setup?

[Bingobango]

sorry for late response - work

I found it doesn't make a difference if traffics around - I was on last night and it happened on touch down at uk2000 Man offline with 0 traffic and with nothing in event viewer.

I did have the MSO20WIN32CLIENT.DLL in event viewer in the past, i found that after CTD that ms office one click was a process running in the background - you would stop the process but it would always come back = I denied its permissions and delated the mso20 dll, no i still have ctd but with nothing in event viewer or crash dumps.

in terms of trends

- mostly only happens at pay ware airports - but did happen on approach in to default vhhh last week
- never after take off, cruise or decent - only on touch down or on approach
- happens with all pay ware aircraft that have - pmdg 747 - fslabs a320 - asa330 pro
- now online or offline

its seems to also happen 1 in 10 flights maybe -

For example i did a return flight to VIE from UK2000 LHR TO FLYTAMPA VIE with FSLABS A320 - online with lots of traffic - Active sky running - VAS ascars running and nothing happened.

I've searched the web tried different things - done clean installs etc I've ran out of ideas?