MSFS Application Error - memory could not be read

I have done all that in the past but it will still come back eventuality. When I first starting getting this error back in July it seemed always to happen on approach. I decided to Turn AI off and any third party AI. The error went away. I started getting them again a few weeks later even in the menus. I have since turned everything back on. I will wait for a fix from Asobo.

Yeah clearly. It’s so funny to see article telling you that if you want to have good performances in MSFS2020, you need to turn of live traffic, weather, disable mods, remove traffic on airports, remove copilot voice, reduce graphics to low etc etc.
I’m sure one day the next official tip will be to not launch at all MSFS2020, to close your eyes and imagine your are flying planes


2 Likes

@FreeBirdJosh thanks for letting me know! I will enjoy the time it works then I guess :smiley: hope they are going to fix it for good!

1 Like

image

There we go again. According to the details, it seems to be related to communication with the GPU for with nvlddmkm is apparently responsible. Will try updating/reinstall drivers.

I have done that multiple times recently and in the past even with DDU etc., nothing worked.

I wrote some weeks ago that for me was solved because I found some hardware unstable and then was going better all the PC and FS20, and I had some similar problem in other game, wrong, a shame, now worse than never, this is unsupportable, in my years of PC never had these severe unsolvable problems and so long in time. Weird weird.

For me this started yesterday
 :frowning:

Ah, ok, go ahead, good luck, all the best, who knows, all the cases are not the same, may the force be with you.

1 Like

Now that a fix appears to have been found for the ntdll.dll CTD, and I’m sure that any sufferers here will be very grateful, are the devs now going to concentrate on finding a solution for this one please?

3 Likes

I wouldn’t hold my breath as this thread has been active since April, and only recently got a surge of 3-400 users (that probably posted in the wrong thread). Meanwhile though, there’s been compelling evidence in another forum that there could be a correlation between the CTDs and what one ate for breakfast. Pending further investigations.

It’s not fair to blame GSX for all CTD’s.

But neither is automatically assuming that GSX does not cause any CTD’s due to recent developments.

MSFS Error - Memory

I get this with or without GSX.
It started a few days ago, happens randomly in all kinds of situation (on ground, in flight, 3rd party or vanilla, etc) but on every single flight.

I am on the current BETA, with latest NVidia drivers on a rather powerful system running Win11 latest build and all updates installed.

I never had this issue before but it made MSFS unusalbe for me.

Did you check the event viewer? I saw that in my case it was GPU driver related. When digging further, it seemed that these issues started in July. So I reverted back to the Nvidia driver 512.96 (version before July), so far so good

will give it a try.
indeed I updated the GPU driver last week, so worth a shot, i guess

1 Like

I just had again this, with all whistles and bells I am having this BSD sometimes, PAGE_FAULT_IN_NONPAGED_AREA, this time in DX11 (the other time was in DX12 and prior a “memory could not be read”), NVIDIA 3080ti, 12900k, 32GB Ram, SU10 beta, this time after 3 hours approx. crossing the Atlantic, mostly only water photogrammetry.


  •                                                                         *
    
  •                    Bugcheck Analysis                                    *
    
  •                                                                         *
    

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffc6c526abea00, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff80240fd66d2, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

Debugging Details:

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_47917a79b8c7fd22\nvlddmkm.sys, Win32 error 0n2
Page 788b50 not present in the dump file. Type “.hh dbgerr004” for details

KEY_VALUES_STRING: 1

Key  : AV.Type
Value: Read

Key  : Analysis.CPU.mSec
Value: 1374

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 3384

Key  : Analysis.Init.CPU.mSec
Value: 296

Key  : Analysis.Init.Elapsed.mSec
Value: 2642

Key  : Analysis.Memory.CommitPeak.Mb
Value: 112

Key  : Bugcheck.Code.DumpHeader
Value: 0x50

Key  : Bugcheck.Code.KiBugCheckData
Value: 0x50

Key  : Bugcheck.Code.Register
Value: 0x50

Key  : Dump.Attributes.AsUlong
Value: 1800

Key  : WER.OS.Branch
Value: co_release

Key  : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key  : WER.OS.Version
Value: 10.0.22000.1

FILE_IN_CAB: MEMORY.DMP

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x1800

BUGCHECK_CODE: 50

BUGCHECK_P1: ffffc6c526abea00

BUGCHECK_P2: 0

BUGCHECK_P3: fffff80240fd66d2

BUGCHECK_P4: 2

READ_ADDRESS: ffffc6c526abea00 Paged pool

MM_INTERNAL_CODE: 2

IMAGE_NAME: nvlddmkm.sys

MODULE_NAME: nvlddmkm

FAULTING_MODULE: fffff80240810000 nvlddmkm

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: HWiNFO64.EXE

TRAP_FRAME: fffffd0704545ed0 – (.trap 0xfffffd0704545ed0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff910e5f56858c rbx=0000000000000000 rcx=ffff910e5f56858c
rdx=000035b6c7556474 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80240fd66d2 rsp=fffffd0704546068 rbp=0000000000000010
r8=0000000000000800 r9=0000000000000800 r10=fffff80240812f50
r11=ffffc6c526abf200 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
nvlddmkm+0x7c66d2:
fffff80240fd66d2 0f100411 movups xmm0,xmmword ptr [rcx+rdx] ds:ffffc6c526abea00=???
Resetting default scope

STACK_TEXT:
fffffd0704545c28 fffff802174978d3 : 0000000000000050 ffffc6c526abea00 0000000000000000 fffffd0704545ed0 : nt!KeBugCheckEx
fffffd0704545c30 fffff80217275cf6 : fffff80200000004 0000000000000000 fffffd0704545e30 0000000000000000 : nt!MiSystemFault+0x1d3613
fffffd0704545d30 fffff802174269f5 : ffff910e5f979d60 0000000000000000 0000000000000000 fffffd0700000002 : nt!MmAccessFault+0x2a6
fffffd0704545ed0 fffff80240fd66d2 : fffff802408a05d6 ffff910e6043e000 fffff80240de6bc8 ffff910e00000020 : nt!KiPageFault+0x335
fffffd0704546068 fffff802408a05d6 : ffff910e6043e000 fffff80240de6bc8 ffff910e00000020 0000000000000000 : nvlddmkm+0x7c66d2
fffffd0704546070 fffff80240f5114b : ffff910e5f567c50 ffff910e5f567c50 ffff910e6043e000 0000000000000000 : nvlddmkm+0x905d6
fffffd07045460a0 fffff80240de6860 : ffff910e5f567c50 000000000010a4cc ffff910e0010a4c8 0000000001000000 : nvlddmkm+0x74114b
fffffd0704546120 fffff80240de7a09 : ffff910e6043e000 0000000000000040 ffff910e6050e080 ffff910e5f566000 : nvlddmkm+0x5d6860
fffffd0704546170 fffff80240de6a58 : 0000000000000000 00000000000ee030 ffff910e5f566000 ffff910e6043e000 : nvlddmkm+0x5d7a09
fffffd07045461d0 fffff80240de73d9 : ffff910e5f566000 ffff910e6043e000 fffffd0704546330 0000000000000000 : nvlddmkm+0x5d6a58
fffffd0704546270 fffff802409e9d50 : 00000000000ee030 0000000000000000 ffff910e5f566000 fffffd07045463c0 : nvlddmkm+0x5d73d9
fffffd07045462e0 fffff8024099fd61 : 0000000000000000 fffff80240b5b1a3 00000a7b46d8dda0 ffff910e5f566000 : nvlddmkm+0x1d9d50
fffffd0704546380 fffff802409a0c79 : ffff910e60563b50 0000000000000000 0000000000000000 fffff80240a3833d : nvlddmkm+0x18fd61
fffffd0704546410 fffff80240b5893e : 0000000000000000 fffffd0704546560 ffff910e60563000 fffff802172b0898 : nvlddmkm+0x190c79
fffffd0704546460 fffff80240c32673 : 0000000000000000 0000000000000000 fffffd0704546930 fffffd0704546930 : nvlddmkm+0x34893e
fffffd0704546790 fffff80240989032 : 0000000000000004 fffffd0700000001 0000000000000000 fffff802410e7a80 : nvlddmkm+0x422673
fffffd07045467f0 fffff80240995ae8 : 0000000000000b0c 0000000000000013 ffff910e00000001 ffff910e68224d18 : nvlddmkm+0x179032
fffffd07045468c0 fffff80240995d45 : 00000000b2000000 00000000b2000000 fffffd0704546b80 fffff802408cdc48 : nvlddmkm+0x185ae8
fffffd0704546af0 fffff80240995e04 : fffff802412891d0 00000000b2000000 00000000c1d00055 fffffd0704546e58 : nvlddmkm+0x185d45
fffffd0704546b40 fffff802408a656e : ffff910e65b6a8f8 ffff910e6043e000 fffffd0704546ef8 0000000000000000 : nvlddmkm+0x185e04
fffffd0704546c80 fffff802408a62c0 : fffffd0704546ef8 fffffd0704546de9 0000000000000000 0000000000000000 : nvlddmkm+0x9656e
fffffd0704546d50 fffff80241070d82 : fffffd0704546ef8 fffffd0704546de9 0000000000000000 fffffd0704546ed0 : nvlddmkm+0x962c0
fffffd0704546da0 fffff80241618c63 : fffff80241070d0a 0000000000000000 ffff910e627a3000 ffffc3868eaae300 : nvlddmkm+0x860d82
fffffd0704546e50 fffff80241617af5 : ffff910e627a3000 fffff80241764b60 ffffc3868eaae300 fffff8024166d0ff : nvlddmkm+0xe08c63
fffffd0704546f70 fffff8024161403f : ffffc3868eaae300 ffff910e627a3000 fffffd0704547120 0000000000000000 : nvlddmkm+0xe07af5
fffffd0704546fb0 fffff8024166bb98 : ffff910e627a3000 fffffd0704547120 ffffc3868eaae300 ffff910e611f2000 : nvlddmkm+0xe0403f
fffffd0704546ff0 fffff8024166c38f : 00000000c000000d fffffd0704547140 ffff910e627a3000 0000000000000001 : nvlddmkm+0xe5bb98
fffffd0704547040 fffff802415ee9de : 00000000c000000d fffffd0704547329 fffffd0704547598 00000000c000000d : nvlddmkm+0xe5c38f
fffffd07045472a0 fffff80232bf9f97 : 0000000000000008 0000000000000000 0000000000000001 000000004e562a2a : nvlddmkm+0xdde9de
fffffd0704547390 fffff80232abd831 : ffff910e6148c000 0000000000000001 ffff910e6148c000 0000000000000001 : dxgkrnl!DXGADAPTER::DdiEscape+0x107
fffffd0704547470 fffff8021742a375 : ffff910e6e3fa080 ffff910e6e3fa080 0000000000000000 0000000000000000 : dxgkrnl!DxgkEscape+0x8e1
fffffd0704547a20 00007ff9209e4f54 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000000ae6cb38 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff9`209e4f54

SYMBOL_NAME: nvlddmkm+7c66d2

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 7c66d2

FAILURE_BUCKET_ID: AV_R_(null)_nvlddmkm!unknown_function

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f899ea14-805d-2454-345d-ba405310c43d}

Followup: MachineOwner

Which NVidia driver are you on? I had similar issues caused by nvlddmkm, and reverted back the the Nvidia driver 512.96 (from May). I could see in the event viewer that these crashes started in July, so I took a driver from well before July.

So far so good, but not extensively tested yet.

EDIT: This didn’t solve it in the end, after a couple of days, another CTD. Same error.

2 Likes

I am now with 516.94 since past week or so. Curious, in this report says “PROCESS_NAME: HWiNFO64.EXE when the other day said PROCESS_NAME: FlightSimulator.exe” posted the 22-08-22, I am going to try the same flight without HWINFO64 monitoring in background.


  •                                                                         *
    
  •                    Bugcheck Analysis                                    *
    
  •                                                                         *
    

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffb3938ebc8200, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff806950366d2, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

Debugging Details:

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_47917a79b8c7fd22\nvlddmkm.sys, Win32 error 0n2
Page 189750 not present in the dump file. Type “.hh dbgerr004” for details

KEY_VALUES_STRING: 1

Key  : AV.Type
Value: Read

Key  : Analysis.CPU.mSec
Value: 1639

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 3621

Key  : Analysis.Init.CPU.mSec
Value: 421

Key  : Analysis.Init.Elapsed.mSec
Value: 3982

Key  : Analysis.Memory.CommitPeak.Mb
Value: 103

Key  : Bugcheck.Code.DumpHeader
Value: 0x50

Key  : Bugcheck.Code.KiBugCheckData
Value: 0x50

Key  : Bugcheck.Code.Register
Value: 0x50

Key  : Dump.Attributes.AsUlong
Value: 1800

Key  : WER.OS.Branch
Value: co_release

Key  : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key  : WER.OS.Version
Value: 10.0.22000.1

FILE_IN_CAB: MEMORY.DMP

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x1800

BUGCHECK_CODE: 50

BUGCHECK_P1: ffffb3938ebc8200

BUGCHECK_P2: 0

BUGCHECK_P3: fffff806950366d2

BUGCHECK_P4: 2

READ_ADDRESS: ffffb3938ebc8200

MM_INTERNAL_CODE: 2

IMAGE_NAME: nvlddmkm.sys

MODULE_NAME: nvlddmkm

FAULTING_MODULE: fffff80694870000 nvlddmkm

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: FlightSimulator.exe

TRAP_FRAME: ffff970a40c8dee0 – (.trap 0xffff970a40c8dee0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffbe0e6679c58c rbx=0000000000000000 rcx=ffffbe0e6679c58c
rdx=fffff5852842bc74 rsi=0000000000000000 rdi=0000000000000000
rip=fffff806950366d2 rsp=ffff970a40c8e078 rbp=0000000000000010
r8=0000000000000800 r9=0000000000000800 r10=fffff80694872f50
r11=ffffb3938ebc8a00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nvlddmkm+0x7c66d2:
fffff806950366d2 0f100411 movups xmm0,xmmword ptr [rcx+rdx] ds:ffffb3938ebc8200=???
Resetting default scope

STACK_TEXT:
ffff970a40c8dc38 fffff8066ac978d3 : 0000000000000050 ffffb3938ebc8200 0000000000000000 ffff970a40c8dee0 : nt!KeBugCheckEx
ffff970a40c8dc40 fffff8066aa75cf6 : fffff80600000004 0000000000000000 ffff970a40c8de40 0000000000000000 : nt!MiSystemFault+0x1d3613
ffff970a40c8dd40 fffff8066ac269f5 : ffffbe0e659b5490 0000000000000000 0000000000000000 ffff970a00000001 : nt!MmAccessFault+0x2a6
ffff970a40c8dee0 fffff806950366d2 : fffff806949005d6 ffffbe0e6667a000 fffff80694e46bc8 ffffbe0e00000020 : nt!KiPageFault+0x335
ffff970a40c8e078 fffff806949005d6 : ffffbe0e6667a000 fffff80694e46bc8 ffffbe0e00000020 0000000000000000 : nvlddmkm+0x7c66d2
ffff970a40c8e080 fffff80694fb114b : ffffbe0e6679ae38 ffffbe0e6679ae38 ffffbe0e6667a000 0000000000000000 : nvlddmkm+0x905d6
ffff970a40c8e0b0 fffff80694e46860 : ffffbe0e6679ae38 000000000010a4cc ffffbe0e0010a4c8 0000000001000000 : nvlddmkm+0x74114b
ffff970a40c8e130 fffff80694e47a09 : ffffbe0e6667a000 0000000000000040 ffffbe0e66797080 ffffbe0e6679a000 : nvlddmkm+0x5d6860
ffff970a40c8e180 fffff80694e46a58 : 0000000000000000 00000000000429c8 ffffbe0e6679a000 ffffbe0e6667a000 : nvlddmkm+0x5d7a09
ffff970a40c8e1e0 fffff80694e473d9 : ffffbe0e6679a000 ffffbe0e6667a000 ffff970a40c8e340 0000000000000000 : nvlddmkm+0x5d6a58
ffff970a40c8e280 fffff80694a49d50 : 00000000000429c8 0000000000000000 ffffbe0e6679a000 ffff970a40c8e3d0 : nvlddmkm+0x5d73d9
ffff970a40c8e2f0 fffff806949ffd61 : 0000000000000000 fffff8069491c48d 0000030915c6a75c ffffbe0e6679a000 : nvlddmkm+0x1d9d50
ffff970a40c8e390 fffff80694a00c79 : ffffbe0e667768e8 0000000000000000 ffffbe0e667768e8 fffff80694a49766 : nvlddmkm+0x18fd61
ffff970a40c8e420 fffff80694ba1a42 : ffffbe0e66773000 ffffbe0e667768e8 0000000000000000 ffff970a40c8e529 : nvlddmkm+0x190c79
ffff970a40c8e470 fffff80694cc1345 : ffffbe0e66773000 ffffbe0e6667a000 0000000000000000 0000000000000003 : nvlddmkm+0x331a42
ffff970a40c8e4c0 fffff80694b89cf1 : ffffbe0e68ee6014 ffffbe0e68ee6014 0000000000000004 ffffbe0e66773000 : nvlddmkm+0x451345
ffff970a40c8e4f0 fffff80694b2c544 : 0000000000000004 ffffbe0e68ee6014 ffff970a40c8e670 0000000000000000 : nvlddmkm+0x319cf1
ffff970a40c8e560 fffff80694b2f351 : ffffbe0e66680000 0000000000000000 ffffbe0e79907000 ffffbe0e6667a000 : nvlddmkm+0x2bc544
ffff970a40c8e5c0 fffff80694c92673 : 0000000000000000 ffffbe0e79907018 ffff970a40c8e7b0 ffff970a40c8e7b0 : nvlddmkm+0x2bf351
ffff970a40c8e610 fffff806949e9032 : 0000000000000004 ffff970a00000001 0000000000000000 fffff80695147380 : nvlddmkm+0x422673
ffff970a40c8e670 fffff806949f5ae8 : 0000000000000490 0000000000000013 ffffbe0e00000001 ffffbe0e778649c8 : nvlddmkm+0x179032
ffff970a40c8e740 fffff806949f5d45 : 00000000b2000000 00000000b2000000 ffff970a40c8ea00 fffff8069492dc48 : nvlddmkm+0x185ae8
ffff970a40c8e970 fffff806949f5e04 : fffff806952e91d0 fffff8066b26a46d 0000000000000040 0000000000000001 : nvlddmkm+0x185d45
ffff970a40c8e9c0 fffff8069496c84d : ffffbe0e877c0b90 fffff806952e85d0 0000000000000000 ffff970a40c8eef8 : nvlddmkm+0x185e04
ffff970a40c8eb00 fffff806949697a2 : 0000000000000000 0000000000000000 ffff970a40c8ed70 0000000000000001 : nvlddmkm+0xfc84d
ffff970a40c8eb60 fffff8069490652c : ffff970a40c8eef8 ffff970a40c8ed00 ffff970a40c8ed70 ffff970a40c8eef8 : nvlddmkm+0xf97a2
ffff970a40c8ec80 fffff806949062c0 : ffff970a40c8eef8 ffff970a40c8ede9 0000000000000000 0000000000000000 : nvlddmkm+0x9652c
ffff970a40c8ed50 fffff806950d0d82 : ffff970a40c8eef8 ffff970a40c8ede9 0000000000000000 ffff970a40c8eed0 : nvlddmkm+0x962c0
ffff970a40c8eda0 fffff80695678c63 : fffff806950d0d0a 0000000000000000 ffffbe0e65b66000 ffff970a40c8f7e0 : nvlddmkm+0x860d82
ffff970a40c8ee50 fffff80695677af5 : ffffbe0e65b66000 fffff806957c4b60 ffff970a40c8f7e0 fffff806956cd0ff : nvlddmkm+0xe08c63
ffff970a40c8ef70 fffff8069567403f : ffff970a40c8f7e0 ffffbe0e65b66000 ffff970a40c8f120 0000000000000000 : nvlddmkm+0xe07af5
ffff970a40c8efb0 fffff806956cbb98 : ffffbe0e65b66000 ffff970a40c8f120 ffff970a40c8f7e0 ffffbe0e671ff000 : nvlddmkm+0xe0403f
ffff970a40c8eff0 fffff806956cc38f : 00000000c000000d ffff970a40c8f140 ffffbe0e65b66000 0000000000000001 : nvlddmkm+0xe5bb98
ffff970a40c8f040 fffff8069564e9de : 00000000c000000d ffff970a40c8f329 ffff970a40c8f598 00000000c000000d : nvlddmkm+0xe5c38f
ffff970a40c8f2a0 fffff806836c9f97 : 0000000000000008 0000000000000000 ffff970a00000002 000000004e562a2a : nvlddmkm+0xdde9de
ffff970a40c8f390 fffff8068358d831 : ffffbe0e676a1000 0000000000000001 ffffbe0e676a1000 0000000000000001 : dxgkrnl!DXGADAPTER::DdiEscape+0x107
ffff970a40c8f470 fffff8066ac2a375 : 0000022ba64cf880 ffffbe0e6e068080 0000000000000000 0000022b98230d10 : dxgkrnl!DxgkEscape+0x8e1
ffff970a40c8fa20 00007ff83c3a4f54 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000fe3317cb78 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff8`3c3a4f54

SYMBOL_NAME: nvlddmkm+7c66d2

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 7c66d2

FAILURE_BUCKET_ID: AV_R_(null)_nvlddmkm!unknown_function

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f899ea14-805d-2454-345d-ba405310c43d}

Followup: MachineOwner

That was the version I was running as well
 so worth trying downgrading I would suggest.

Thanks, I think I was in that driver too, I have been always in the last ones and having these problems maybe since the beginning of this thread in April.

You could try this one: CTD due to NVLDDMKM (at least %99 of the time) FIX!

Not a fan of it, but worth trying maybe?

1 Like

Thanks, I will check that. Edit: I was there a lot of time ago regarding the forum info “last visit”, but there are new posts.

Edit: nothing, I have disabled HWIFO64 monitoring, and I had a frozen a few minutes after take off, for me this is worse than ever, I am with the redwing 1049 and PMS 750 only installed and in community, usually in the past I was able to flight 8 hours and more and then sim CTD etc., and I was moaning for that
 Maybe I try other plane like the Salty 747 or the Just Flight BAE146.

Edit: With the Salty 748 is exactly the same., and another BSD this time:


  •                                                                         *
    
  •                    Bugcheck Analysis                                    *
    
  •                                                                         *
    

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8043df05330, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_47917a79b8c7fd22\nvlddmkm.sys, Win32 error 0n2
Page 18a150 not present in the dump file. Type “.hh dbgerr004” for details




*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***


*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***


*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***


*** Type referenced: TickPeriods ***



KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 1312

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 3528

Key  : Analysis.Init.CPU.mSec
Value: 342

Key  : Analysis.Init.Elapsed.mSec
Value: 16364

Key  : Analysis.Memory.CommitPeak.Mb
Value: 97

Key  : Bugcheck.Code.DumpHeader
Value: 0x133

Key  : Bugcheck.Code.KiBugCheckData
Value: 0x133

Key  : Bugcheck.Code.Register
Value: 0x133

Key  : Dump.Attributes.AsUlong
Value: 1800

Key  : WER.OS.Branch
Value: co_release

Key  : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key  : WER.OS.Version
Value: 10.0.22000.1

FILE_IN_CAB: MEMORY.DMP

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x1800

BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8043df05330

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: fffffd04c145ee20 – (.trap 0xfffffd04c145ee20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffb301e60a9202
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8043d47f55b rsp=fffffd04c145efb0 rbp=000000000010a4c8
r8=0000000000000000 r9=000000000010a4c8 r10=fffff80468322f50
r11=000000000000000c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KzLowerIrql+0x1b:
fffff804`3d47f55b 4883c420 add rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffa080d28acdd8 fffff8043d4b71ef : 0000000000000133 0000000000000001 0000000000001e00 fffff8043df05330 : nt!KeBugCheckEx
ffffa080d28acde0 fffff8043d4b6e01 : 000014189481f13b fffff80400000500 0000000000000002 fffff8043d4b2528 : nt!KeAccumulateTicks+0x20f
ffffa080d28ace50 fffff8043d4b4fea : ffffa080d2849200 fffffd04c145ee20 ffffa080d28493b0 fffff8043d51c7fb : nt!KiUpdateRunTime+0x61
ffffa080d28aceb0 fffff8043d4b4dd6 : ffffb301c594d400 ffffb301c594d4b0 ffffa08000000000 0000000000000000 : nt!KeClockInterruptNotify+0x11a
ffffa080d28acf40 fffff8043d4913d0 : 0000000000000000 fffff6bb86f4d3b7 0000000000000000 00000000ffffffff : nt!HalpTimerClockIpiRoutine+0x16
ffffa080d28acf70 fffff8043d61994a : fffffd04c145eea0 ffffb301c594d400 0000000000000000 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa0
ffffa080d28acfb0 fffff8043d619f17 : ffffffff00000001 fffffd04c145ed68 fffffd04c145ee70 0000000000000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffd04c145ee20 fffff8043d47f55b : ffffb30100000000 00000000ffffffff 0000000000000000 fffff804683fb68f : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffd04c145efb0 fffff804683ca883 : ffffb301e5e28a58 000000000010a0f4 ffffb301e5e28a58 fffff804683b9a69 : nt!KzLowerIrql+0x1b
fffffd04c145efe0 fffff804683fb5b7 : ffffb301e5e28a58 000000000010a4c8 0000000000000020 fffff804683fba07 : nvlddmkm+0xaa883
fffffd04c145f010 fffff804683fb99a : ffffb301e5e28000 ffffb301e5e28a58 000000000010a4c8 ffffb301e5e28a58 : nvlddmkm+0xdb5b7
fffffd04c145f070 fffff804683fc718 : ffffb301e5e28000 ffffb301e570e690 ffffb301e5e28000 0000000000000000 : nvlddmkm+0xdb99a
fffffd04c145f0f0 fffff804684e8de0 : 0000000000000001 fffff804683d610f 0000000000000040 0000000000000020 : nvlddmkm+0xdc718
fffffd04c145f130 fffff80468964a4d : ffffb301e5e97080 ffffb301e5e28000 fffffd04c145f1f8 ffffb301e5e9a000 : nvlddmkm+0x1c8de0
fffffd04c145f170 fffff80468964b27 : ffffb301e600ff00 000000000010a000 ffffb301e5e28000 0000000000000001 : nvlddmkm+0x644a4d
fffffd04c145f1a0 fffff804688f7a92 : ffffb301e5e28000 ffffb301e5e97080 ffffb30100000000 ffffb301e5e28000 : nvlddmkm+0x644b27
fffffd04c145f1e0 fffff804688f4276 : ffffb301e5e28000 ffffb301e5e28000 fffffd04c145f340 ffffb301cfd7d000 : nvlddmkm+0x5d7a92
fffffd04c145f240 fffff8046840b23b : 0000000000000000 fffff804687965eb 0000000000000000 000000000000000f : nvlddmkm+0x5d4276
fffffd04c145f280 fffff8046840a714 : ffffb301e5e28000 000000000000000f ffffb301f9ea000f 0000000000000000 : nvlddmkm+0xeb23b
fffffd04c145f2c0 fffff8046840afc5 : ffffb301f9eab1d0 ffffb301e5e98000 ffffb301e5e98001 ffffb301e5e99600 : nvlddmkm+0xea714
fffffd04c145f330 fffff8046840ba9a : ffffb301e5e28000 0000000000000000 ffffb301e5e28000 fffffd04c145f500 : nvlddmkm+0xeafc5
fffffd04c145f3a0 fffff804683b9c67 : ffffb301e5e28000 ffffb301e5e98000 ffffb301e5e28000 ffffb301e5e98000 : nvlddmkm+0xeba9a
fffffd04c145f400 fffff8043d4a74a1 : fffffd04c145fab0 ffffb301c5cee000 ffffa080d28434c0 ffffa080d2840180 : nvlddmkm+0x99c67
fffffd04c145f6d0 fffff8043d4a64a2 : 0000000000000008 fffffd04c145f9d0 ffffa080d2840180 0000000000000170 : nt!KiExecuteAllDpcs+0x491
fffffd04c145f8d0 fffff8043d61bcbe : 0000000000000000 ffffa080d2840180 ffffa080d284c640 ffffb301f0491080 : nt!KiRetireDpcList+0x2a2
fffffd04c145fb80 0000000000000000 : fffffd04c1460000 fffffd04c1459000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e

SYMBOL_NAME: nvlddmkm+aa883

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: aa883

FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup: MachineOwner