I have the following running off of my FTW 3090:
3x Dell U2520D daisy-chained on Displayport #1 over MST
1x LG OLED TV on HDMI port
1x AOC Monitor on Displayport #2
1x Valve Index on Displayport #3
Amazingly the card manages to run alls of these at the same time and switch between running various subsets without the need to plug anything in or out. Now this works quite neat for my use case because I can switch between productivity work (3x Dell enabled), video editing (3x Dell & 1x LG), flat gaming (1x LG) and 3D gaming (1x Valve Index and 1x AOC as spectator monitor). If only there were not an almost daily BSOD which appears related to the Displayport MST function that allows me to daisy chain the three Dell. It is not 100% reproducible but very often the Dells don't show up as expected and I switch the fist monitor or other monitors in the daisy chain on or off to fix it. It works half of the time and the monitors get recognized and the other half of the time it crashes. Sometimes it will crash when switching to the Index / AOC use case. Not sure if this should be directed towards EVGA for a BIOS fix or NVidia for a Driver fix. Here's a WinDbg analysis of the BSOD Minidump:
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`65800000 PsLoadedModuleList = 0xfffff804`6642a3b0
Debug session time: Tue Nov 17 09:50:03.569 2020 (UTC + 1:00)
System Uptime: 2 days 3:53:21.563
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8048024a884, The address that the exception occurred at
Arg3: ffff9f0081b16ae8, Exception Record Address
Arg4: ffff9f0081b16320, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.Sec
Value: 3
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on KARA
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 15
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8048024a884
BUGCHECK_P3: ffff9f0081b16ae8
BUGCHECK_P4: ffff9f0081b16320
EXCEPTION_RECORD: ffff9f0081b16ae8 -- (.exr 0xffff9f0081b16ae8)
ExceptionAddress: fffff8048024a884 (nvlddmkm+0x00000000001ea884)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000001ba0
Attempt to read from address 0000000000001ba0
CONTEXT: ffff9f0081b16320 -- (.cxr 0xffff9f0081b16320)
rax=0000000000000000 rbx=ffffdd8a361f9000 rcx=0000000000000000
rdx=0000000000df38e6 rsi=ffffdd8a343c3010 rdi=ffffdd8a361a7000
rip=fffff8048024a884 rsp=ffff9f0081b16d20 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=ffff9f0081b16d60 r12=0000000000000002 r13=0000000000000000
r14=0000000000000001 r15=0000000000000001
iopl=0 nv up ei ng nz ac pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010293
nvlddmkm+0x1ea884:
fffff804`8024a884 448bb0a01b0000 mov r14d,dword ptr [rax+1BA0h] ds:002b:00000000`00001ba0=????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff804664fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8046640f340: Unable to get Flags value from nt!KdVersionBlock
fffff8046640f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000001ba0
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: 0000000000001ba0
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffff9f00`81b16d20 ffffdd8a`361f9000 : ffffdd8a`36196000 00000000`00000000 00000000`00000000 ffffdd8a`36155930 : nvlddmkm+0x1ea884
ffff9f00`81b16d28 ffffdd8a`36196000 : 00000000`00000000 00000000`00000000 ffffdd8a`36155930 00000000`00000001 : 0xffffdd8a`361f9000
ffff9f00`81b16d30 00000000`00000000 : 00000000`00000000 ffffdd8a`36155930 00000000`00000001 00000000`00000001 : 0xffffdd8a`36196000
SYMBOL_NAME: nvlddmkm+1ea884
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xffff9f0081b16320 ; kb
BUCKET_ID_FUNC_OFFSET: 1ea884
FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
Followup: MachineOwner
---------