Think I'll definitely give this new Marvell AQtion V3.1.10 driver a try.

Looks like it passed WHQL on 11 August 2024 - so it should be solid for both the old and new OWC Thunderbolt Pro docks

In reply to a post by Pheasant:

Think I'll definitely give this new Marvell AQtion V3.1.10 driver a try.

I guess its worth a try, but I’d be surprised if an Ethernet driver makes a difference. As there are a serious number of ports on that dock, I wonder if something else is triggering the BSOD, perhaps the eSATA as I’ve not seen that for years.

Good point - I'll disconnect everything and reconnect one by one...

Think I'll take a closer look at this particular dock too. Just recalled that I had noticed some time ago, that it was flapping on the ethernet switch logs. Never the best of signs really.

I have a couple of identical docks here (in our home office and for the kids laptops) and they are fine. Possibly the easiest thing would be to connect to one and see if it BSODs there.

A process of elimination for the next few days.

Edited by Pheasant (Tue 31-Dec-24 19:12:05)

The new v3 Marvell driver is in play - works fine with the plain OWC dock now - I’ve tested two docks just to make sure it wasn’t a hardware fault with one dock. All good. Sort off….

As soon as I reconnect Dell monitor via Thunderbolt into dock…near instant BSOD!

This Dell UltraSharp monitor (with its own dock, Thunderbolt, USB and Gig Ethernet port!) has worked flawlessly with all manner of machines plugged into the OWC dock and correspondingly with it….Including this Thinkpad in it original 23H2 Windows11 build!! So will have a closer look at the windows system logs to see what is going on with 24H2 and this BSOD.

TBC!

OK now getting somewhere. Machine will BSOD when Dell UltraSharp U4021QW monitor is connected via Thunderbolt ports, via OWC dock:

This is the same BSOD error when previously attempting an in-line upgrade from 23H2 to 24H2 or doing a clean install of 24H2 from the Lenovo Recovery media for this machine.

WinDbg debug output, following analysis as follows:

*******************************************************************************
* *
* 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: ffff9581fd9db008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80648f654a6, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1484

Key : Analysis.Elapsed.mSec
Value: 4878

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

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

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

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Bugcheck.Code.LegacyAPI
Value: 0xd1

Key : Bugcheck.Code.TargetModel
Value: 0xd1

Key : Dump.Attributes.AsUlong
Value: 21808

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_WiManHio!unknown_function

Key : Failure.Hash
Value: {ba8258fc-371d-0c3a-2d7a-10fe19f59a3e}

Key : Hypervisor.Enlightenments.ValueHex
Value: 7417df84

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 1

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 55447806

Key : Hypervisor.Flags.ValueHex
Value: 34e10fe

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 3f7


BUGCHECK_CODE: d1

BUGCHECK_P1: ffff9581fd9db008

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80648f654a6

FILE_IN_CAB: 010825-22218-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump

FAULTING_THREAD: ffffe1890f6c4040

READ_ADDRESS: fffff806b57c34b0: 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
ffff9581fd9db008

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffffdd8c6858f760 -- (.trap 0xffffdd8c6858f760)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffdd8c6858f9a8 rbx=0000000000000000 rcx=ffffdd8c6858f9a8
rdx=ffff9581fd9db008 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80648f654a6 rsp=ffffdd8c6858f8f8 rbp=0000000000000000
r8=000000000000001c r9=000000000000001c r10=1fffff00c91e9668
r11=004b014c402e0073 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
WiManHio+0x254a6:
fffff806`48f654a6 0f1002 movups xmm0,xmmword ptr [rdx] ds:ffff9581`fd9db008=????????????????????????????????
Resetting default scope

STACK_TEXT:
ffffdd8c`6858f618 fffff806`b4e8dce9 : 00000000`0000000a ffff9581`fd9db008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffdd8c`6858f620 fffff806`b4e88fa8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffdd8c`6858f760 fffff806`48f654a6 : fffff806`48f64e93 00000000`00000000 ffffe189`0f6c1310 ffffdd8c`6858faa0 : nt!KiPageFault+0x468
ffffdd8c`6858f8f8 fffff806`48f64e93 : 00000000`00000000 ffffe189`0f6c1310 ffffdd8c`6858faa0 00000000`00000000 : WiManHio+0x254a6
ffffdd8c`6858f900 00000000`00000000 : ffffe189`0f6c1310 ffffdd8c`6858faa0 00000000`00000000 00000000`00000000 : WiManHio+0x24e93


SYMBOL_NAME: WiManHio+254a6

MODULE_NAME: WiManHio

IMAGE_NAME: WiManHio.sys

STACK_COMMAND: .process /r /p 0xffffe189044d8040; .thread 0xffffe1890f6c4040 ; kb

BUCKET_ID_FUNC_OFFSET: 254a6

FAILURE_BUCKET_ID: AV_WiManHio!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ba8258fc-371d-0c3a-2d7a-10fe19f59a3e}

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

Further update following testing. A direct Thunderbolt connection between the laptop and monitor is fine. Can actually use the (Realtek chipped) gigabit Ethernet port on the monitor too.

However then connecting the monitor back to the OWC dock as it was originally, will induce an instant BSOD.

So to recap:
- OWC dock on its own is fine, in-built 10GbE connection is working fine
- Dell monitor on its own is fine, in-built GbE connection is working fine

- OWC dock + Dell monitor = BSOD with 24H2 (however used to work fine on Win 11 23H2)

I just had a scary moment with 24H2, I was finally offered the update this morning and started the update but after it rebooted and started the update it sat there for a good 20 minutes with just a black screen and a mouse cursor and no hard disk activity. I started to worry and was close to doing a hard reboot but for one reason or another decided to connect up one of the spare HDMI ports in addition to the normal DP port I use and the DP port then come to life and the disk light started flashing and the update continued on to a successful completion. All very strange that the update hung until one of the HDMI ports was connected up.