I had another one yesterday when attempting a 2d Vatsim flight.
I have done 4 legs offline since with PMDG 738 in VR no errors.
MS Store Version
This is a real head-scratcher since the error happens at different times for different folks…and not at all for some. Having read pretty much all of the posts on what must be one of the longest threads here, I can’t say I’ve noticed any trend as to what may be causing it. Is it more prevalent with this hardware or that? Does it matter if you’re on Steam or MS Store? Is it related to certain addons? Is it as prevalent in the SU10 Beta as it is in SU9? Does DX11 vs DX12 make a difference? Windows 10 vs Windows 11?
Where I’m going with this is perhaps the mods could set up some sort of questionnaire where those having the issue could list their parameters and thereby, over time, see if there are any common factors.
In my case, W11/intel/nVidea/MS Store/highend rig. Never saw the problem until SU9 Hotfix. Joined the SU10 Beta, haven’t seen it since. Go figure, I think some are still getting it in SU10 but not sure about that.
Anyway, food for thought.
You’re not using ReShade by any chance? Some of us managed to get rid of the CTDs with a “reshade tweak”. It’s mentioned a bit further up the thread.
Steam seems less affected? I updated Bios, turned GPU acceleration off and so far OK.
Nope don’t use reshade though we found on inspection post stream my RAM had cached 42gb out if 64?! This is with no rolling cache on too, a clean content.xml and more
Hm that’s a lot. Don’t think I’ve ever seen more than 32GB. Didn’t you report these CTDs a while back? Did you resolve it, and then they suddenly reappeared?
Could ISLC be of use? Intelligent standby list cleaner (ISLC) download latest version 1.0.3.4 | Wagnardsoft. “The application will monitor and clear the memory standby list according to the configured options parameter you set.”
Hopefully someone else can chime in on this. @MichaMMA perhaps.
I have not expierenced a memory error since many month. I had serval CTD 2 weeks ago, since than while holiday, I flew every day 4-5 legs (11hrs)per day without reloading msfs inbetween and had no single CTD. Online services I use every day: Live weather, Bing maps. PG is off as well as MP. Usually I am on west europe server, I changed it to south-east asia 2 weeks ago, even without using it, CTD’s stopped. I am using fenix a320, GSX, P2atc or VATSIM and AIG TC or just the models while on VATSIM. I have a ton of addons installed, but deleted 95% of addons shipped with msfs. Even bushtrips, landing challenges and so on, because I dont use/need it. I am on SUb10 and got a very smooth stable sim, FPS on firdt flight 40 locked, FPS on last flight 40 locked. I7 10700k oc’d, RTX3070, 32GB ram 3200mhz and CPU is watercooled on an average temp about 40-50 degree. Everything ist up to date in windows 11 as well as graphics driver. Wonder why so many people does have crashes. But I am feeling with you.
I am sorey but i am using ISLC since months and that does not stopped my memory could not be read ctds
And now I had this BSD a few hours ago after a pair of hours flying in SU10 1.27.17.0, DX11
-
* -
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: fffff80206f05330, 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_2adba769f8aeb686\nvlddmkm.sys, Win32 error 0n2
Page 185542 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: 1421
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 4157
Key : Analysis.Init.CPU.mSec
Value: 296
Key : Analysis.Init.Elapsed.mSec
Value: 4889
Key : Analysis.Memory.CommitPeak.Mb
Value: 104
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: fffff80206f05330
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: ffff808280c675d0 – (.trap 0xffff808280c675d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=ffff848d0a341000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8023064b918 rsp=ffff808280c67768 rbp=ffff808280c67930
r8=0000000000000000 r9=0000000000000000 r10=ffff848d0a343740
r11=ffff808280c67760 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nvlddmkm+0xdb918:
fffff802`3064b918 415e pop r14
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: NVDisplay.Container.exe
STACK_TEXT:
ffff94814ceacdd8 fffff802064d7e7f : 0000000000000133 0000000000000001 0000000000001e00 fffff80206f05330 : nt!KeBugCheckEx
ffff94814ceacde0 fffff802064d7a91 : 00000ebe2545492e ffff948100000500 0000000000000002 fffff802064d31b8 : nt!KeAccumulateTicks+0x20f
ffff94814ceace50 fffff802064d5c7a : ffff94814ce49200 ffff808280c675d0 ffff94814ce49360 fffff8020642d28b : nt!KiUpdateRunTime+0x61
ffff94814ceaceb0 fffff802064d5a66 : ffff848cebf37400 ffff848cebf374b0 ffff948100000000 0000000000000000 : nt!KeClockInterruptNotify+0x11a
ffff94814ceacf40 fffff8020640d2d0 : 0000000000000000 ffff83edaf48a094 0000000000000057 0000000000000001 : nt!HalpTimerClockIpiRoutine+0x16
ffff94814ceacf70 fffff8020661c8fa : ffff808280c67650 ffff848cebf37400 0000000000000000 0000000000000100 : nt!KiCallInterruptServiceRoutine+0xa0
ffff94814ceacfb0 fffff8020661cec7 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff808280c675d0 fffff8023064b918 : 0000000000000000 ffff808280c67930 ffff848d0a341000 ffff848d0aa16000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff808280c67768 fffff8023064c718 : ffff808280c67930 ffff848d0a341000 ffff808280c67930 fffff8023062d042 : nvlddmkm+0xdb918
ffff808280c67790 fffff8023065b942 : 0000000000000100 0000000000000000 ffff848d0a341000 0000000000000002 : nvlddmkm+0xdc718
ffff808280c677d0 fffff80230609c67 : ffff848d0a341000 ffff848d0aa16000 ffff848d0a341000 ffff848d0aa16000 : nvlddmkm+0xeb942
ffff808280c67830 fffff802064c7c11 : ffff808280c67f00 ffff848ced1f7000 ffff94814ce434c0 ffff94814ce40180 : nvlddmkm+0x99c67
ffff808280c67b00 fffff802064c6c12 : 0000000000000000 ffff808280c67e00 ffff94814ce40180 0000000000000276 : nt!KiExecuteAllDpcs+0x491
ffff808280c67d00 fffff80206622ab5 : 0000000000000000 ffff94814ce40180 ffff948152139c80 0000000000000000 : nt!KiRetireDpcList+0x2a2
ffff808280c67fb0 fffff80206622890 : ffffffffffffffa1 fffff802066220c1 0000000001000010 0000000000000282 : nt!KxRetireDpcList+0x5
ffff8082833e79e0 fffff802066220d5 : 0000000000000000 fffff8020661c9c1 0000000000000002 ffff848d0ed80080 : nt!KiDispatchInterruptContinue
ffff8082833e7a10 fffff8020661c9c1 : 0000000000000002 ffff848d0ed80080 0000000000000000 0000000000000000 : nt!KiDpcInterruptBypass+0x25
ffff8082833e7a20 00007fff82fb111a : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiInterruptDispatch+0xb1
00000028195f8e90 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007fff`82fb111a
SYMBOL_NAME: nvlddmkm+db918
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: db918
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}
And in event viewer like never I had a hundred continuous error before the crash:
- System
|||- Provider
[ Name] nvlddmkm|
| — | — |
|||- EventID 14
[ Qualifiers] 49322|
| — | — |
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x80000000000000
|||- TimeCreated
[ SystemTime] 2022-08-29T15:58:14.5610252Z|
| — | — |
EventRecordID 1621784
Correlation
|||- Execution
[ ProcessID] 4
[ ThreadID] 23608|
| — | — |
Channel System
Computer Silverstone
Security
- EventData
\Device\000000eb
0000(0000) 00000000 00000000
0000000002003000000000000E00AAC0000000000000000000000000000000000000000000000000
And after 4 days, all these problems are related to MS Store version, anyone with a Steam version having these problems?
BSOD is an entirely separate issue from this thread. The module that’s referenced is nvlddmkm, a driver that’s used by Nvidia. You have some type of GPU-related hardware issue causing your BSOD, and it’s not directly caused by MSFS. If you have any GPU overclock, you should remove it.
I don´t have GPU OC at all, thanks for the advice. I think that Microsoft, Asobo and Nvidia etc., are full of bugs.
but this points more to the GPU which caused the BSOD, as @ncbartschi mentioned too. Of course I have no reference, because you use the Su10 BETA,.. but what we know is, that BSODs comes usually not from the game. What you can do is to report these BSOD within the BETA category. Its here bit out of topic ( BSOD and Beta 
).
What I did a few days ago was to uninstall the NVIDIA driver with DDU and then to do a NVCleaninstall as was described in a video here in case if that helps to the rest of errors, and now I did again a DDU and I installed normally without Geforce as always, the last NVIDIA driver and checking to do a clean instal in its own installer.
Maybe that was these recent problems not too much related, of the last days, I am now in a flight of 9 during 3:30hrs apparently a bit more stable, though waiting for the other errors as always. I was achieving flights of 8-9hr again before errors, and a pair of days ago was this, a big step behind in errors.
I will edit probably later regarding this flight of now: it lasted 6 hours before a freeze, better haha.
I’m getting CTDs everytime i spam in EIDW dublin intl airport, parking spot or runway, i tried the default scenario and the mk studios 3d partie, anyone can confirm or check this one?
I’ve seen plenty of reports of this on another forum. Both default and payware EIDW.
There is a forum post about these CTD issues at EIDW which can be found here → CTD/freezing at Dublin (EIDW)
I tried EIDW after I saw the post above and got a CTD, tried again in safe mode with the same result. SU10 and no addon scenery.
Hi, After a few weeks break I wanted to test MSFS again because there was an update. had pushed 2 x CTD without a flight… first was in menu when loading WU. then when setting the settings on runway. I can’t believe how unstable this sim is. The problem is not my computer… P3D ran stably for over 600 hours.. The computer ran stable for over 6 hours Prime… memtest ok.. and 3D mark stress test.. everything runs stable, no crashes… only MSFS i
s extremely unstable