Update 17 - frequent crashes and sometimes BSOD

rootsrat

Volunteer Moderator
Ever since update 17 I get weird crashes in Elite, especially when playing with friend OR when live streaming the game. The most prominent issues are at Thargoid Spire Sites, but also for example at ground Conflict Zones when playing with many friends.

Usually the problem manifests itself in FPS drop below 20 and shortly after either my live stream will freeze or the game will crash. Today it ended up in BSOD when there were 15 of us in a ground conflict zone.

It seems like it's something to do with the net code possibly? (I do have the suggested port forwarding done).

Today's BSOD dmp file reports this:


*******************************************************************************
  • *
  • Bugcheck Analysis *
  • *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000a64, memory referenced
Arg2: 0000000000000009, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80460498ca2, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2046

Key : Analysis.Elapsed.mSec
Value: 8665

Key : Analysis.IO.Other.Mb
Value: 15

Key : Analysis.IO.Read.Mb
Value: 16

Key : Analysis.IO.Write.Mb
Value: 46

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0xd1

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: AV_nvlddmkm!unknown_function

Key : Failure.Hash
Value: {7eea5677-f68d-2154-717e-887e07e55cd3}


BUGCHECK_CODE: d1

BUGCHECK_P1: a64

BUGCHECK_P2: 9

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80460498ca2

FILE_IN_CAB: 111123-6359-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

READ_ADDRESS: fffff8043771d468: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000000a64

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: EliteDangerous

DPC_STACK_BASE: FFFFF80436062FB0

TRAP_FRAME: fffff80436060e10 -- (.trap 0xfffff80436060e10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80460498ca2 rsp=fffff80436060fa0 rbp=fffff804360610c9
r8=fffff804360611c0 r9=fffff804360611c0 r10=fffff80436061530
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nvlddmkm+0xb8ca2:
fffff804`60498ca2 8bb9640a0000 mov edi,dword ptr [rcx+0A64h] ds:00000000`00000a64=????????
Resetting default scope

STACK_TEXT:
fffff804`36060cc8 fffff804`36e27da9 : 00000000`0000000a 00000000`00000a64 00000000`00000009 00000000`00000000 : nt!KeBugCheckEx
fffff804`36060cd0 fffff804`36e23434 : 00000000`00000020 fffff804`6049b6fd 00000000`003f0070 00000000`00000020 : nt!KiBugCheckDispatch+0x69
fffff804`36060e10 fffff804`60498ca2 : fffff804`610f3ee0 fffff804`6057c3c5 00000000`00000038 00000000`00000001 : nt!KiPageFault+0x474
fffff804`36060fa0 fffff804`610f3ee0 : fffff804`6057c3c5 00000000`00000038 00000000`00000001 fffff804`610f3ee0 : nvlddmkm+0xb8ca2
fffff804`36060fa8 fffff804`6057c3c5 : 00000000`00000038 00000000`00000001 fffff804`610f3ee0 fffff804`36061000 : nvlddmkm+0xd13ee0
fffff804`36060fb0 00000000`00000038 : 00000000`00000001 fffff804`610f3ee0 fffff804`36061000 ffff9206`f8752018 : nvlddmkm+0x19c3c5
fffff804`36060fb8 00000000`00000001 : fffff804`610f3ee0 fffff804`36061000 ffff9206`f8752018 fffff804`604a2fa5 : 0x38
fffff804`36060fc0 fffff804`610f3ee0 : fffff804`36061000 ffff9206`f8752018 fffff804`604a2fa5 00000000`00000000 : 0x1
fffff804`36060fc8 fffff804`36061000 : ffff9206`f8752018 fffff804`604a2fa5 00000000`00000000 00000000`00000000 : nvlddmkm+0xd13ee0
fffff804`36060fd0 ffff9206`f8752018 : fffff804`604a2fa5 00000000`00000000 00000000`00000000 fffff804`360610c9 : 0xfffff804`36061000
fffff804`36060fd8 fffff804`604a2fa5 : 00000000`00000000 00000000`00000000 fffff804`360610c9 fffff804`610f3ee0 : 0xffff9206`f8752018
fffff804`36060fe0 00000000`00000000 : 00000000`00000000 fffff804`360610c9 fffff804`610f3ee0 fffff804`36061080 : nvlddmkm+0xc2fa5


SYMBOL_NAME: nvlddmkm+b8ca2

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: b8ca2

FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}

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


All my drivers, applications and OS (Win 11) are up to date. My spec as follows:

MOBO - Asus ROG Maximus XI Hero (Wi-Fi) CODBO4 Edition
PSU - Corsair HX1000i Platinum (od widzów!)
CPU - Intel Core i7 9700K @ 4.90 GHz
RAM - 32GB Corsair Vengeance LPX DDR4 3200MHz
GFX - GeForce RTX 3080 GAMING OC 10G

Elite is installed on an M2.

Never had these issues before Update 17. No issues with other game, both playing multiplayer and live streaming.

Here's an example from yesterday - we've had an event where there were 15-20 people in Maelstrom, no issues for a few good hours, until we moved to a Spire Site - timestamp link, so I think you need to click on it. As soon as I dropped into the Spire Site - stream crashed.

Note the drop in FPS, massive stuttering and then crash. Today was exactly the same, albeit at a different spire site. We then moved into a conflict zone and after a while performance dropped and I got the BSOD with the error reported in the above dmp.

Source: https://www.twitch.tv/videos/1973789792?t=04h39m10s


Is anyone else experiencing something similar?
 
Last edited:
What did the event viewer say?
Some time ago my PC was simply resetting/booting Itself during game. I recall an event ID code something like 1102. Some kind of scheduling task that was failing. So had to dive into windows and fix this.

Flimley
 
Last edited:

rootsrat

Volunteer Moderator
@rootsrat
Don't forget to check your system for other things that can cause that kinda problem as well.
Well, these issues are the only constant. I did a few driver updates along the way to bring everything up to speed in attempt to combat these issues. I don't believe this is anything to do with my system, as literally everything else works perfectly fine, as it always has. It's only after U17 these things started happening with Elite.

What did the event viewer say?

Flimley
Nothing, there were no errors, warnings or criticals before the BSOD.

If you look in the dmp log however there is this:

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000a64, memory referenced
Arg2: 0000000000000009, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80460498ca2, address which referenced memory

followed by

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: EliteDangerous

It looks to me like Elite process was trying to access something that doesn't exist and my system returned a BSOD.
 
Hmmm. Have you also checked any windows updates for known issues. I only mention this as one recent update in October caused some users pc's to reset. Including mine. Although I'm running windows 10. But after scanning ( using DISM.exe) a corrupt file was found and repaired

Flimley
 
Last edited:

rootsrat

Volunteer Moderator
This smells like hardware failure, an app shouldn't be able to BSOD a machine no matter how badly it's coded.
Hmmm. Have you also checked any windows updates for known issues. I only mention this as one recent update in October caused some users pc's to reset. Including mine. Although I'm running windows 10. But after scanning a corrupt file was found and repaired

Flimley
Could be either, although if anything I'd suspect faulty windows update.

I'll reinstall the game and we'll see.
 
Oh man. Run the scan in safe mode also. But guessing you know this. 😁

if it persists after fix. @Ned Flandalorian could be into something as checking the DIMMS slots for issues. Could bear fruit.
 
Last edited:

rootsrat

Volunteer Moderator
On my ancient machine, when it starts doing that it means it's time to evict the dust bunnies and reseat all components. Usually buys me another year. I do wonder how much longer I can keep doing that. 😄
To be fair inside-out cleaning is long overdue on my machine :D
 

rootsrat

Volunteer Moderator
D1 BSODs are frequently memory errors.
Yeah, that much was clear from the dmp log. But this never happens on any other game, streaming or not, the log states it was ED process that tried to access it and it only ever happens when I play Elite.

So... everything points to Elite process rather than faulty hardware. Hence I posted here to see if anyone else had similar issue.

I will still run some checks when I get the time just to be sure.
 
AFAIK, ED does give systems a good workout. I'd start with cleaning and reseating the RAM, also remove any eventual overclocking. Maybe also worth to try without XMP/EXPO.

If it somehow was the game I think that we'd have seen more complaints.
 
Yeah, that much was clear from the dmp log. But this never happens on any other game, streaming or not, the log states it was ED process that tried to access it and it only ever happens when I play Elite.

So... everything points to Elite process rather than faulty hardware. Hence I posted here to see if anyone else had similar issue.

I will still run some checks when I get the time just to be sure.
That could simply mean that ED is trying to access a problem area that nothing else on your system does. ED is an older game, so it's probably not utilizing resources the same way as newer applications.
 
Back
Top Bottom