[SOLVED] SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M Leading to RtlpCopyRangeListEntry

S

stevepaulquinn

Contributor
Joined
Feb 22, 2022
Posts
9
Hi Folks

I've got a remote customer with a HP ZBook G3 running Windows 10 Pro x64 21H2.

Normally I like to touch and test computers before I send them in the field.
This one was essentially drop shipped from the refurbishers. Never again. It's been a long road pushing through many BSOD issues.

The Windows Memory Diagnostic application shows no errors but I'm not comfortable with the results. I prefer MemTest.
I'm having a hard time getting her system to boot with a MemTest key I just shipped her.
I'll have to guide her blind through the BIOS I think, oh yay.

Assuming it's not memory ...
From some forum recommendations, I've run DDU and am running the official HP Provided NVidia driver now.
I'm unsure it that is the wisest choice. It's hard to find concrete proof as to which graphics drivers to use.

It seems debugging these BSOD memory dumps is a real black art and I truly appreciate what your team is doing for the community
I followed along on your excellent tutorial here
Debugging Stop 0x7E - SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

I'm hitting a road block landing on RtlpCopyRangeListEntry
ExceptionAddress: fffff8023474eb2c (nt!RtlpCopyRangeListEntry+0x000000000000002c)

Here's more details
OS was factory installed from Refurbishers :-(
sfc /scannow completed
DISM /Online /Cleanup-Image /RestoreHealth completed
BIOS is 01.54 Rev.A Released Dec 17, 2021
Driver verifier is not enabled
Kaspersky Internet Security. BSOD issues were before installation
Macrium Reflect
No over clocking

I'd be so grateful if someone can help me find the smoking gun.

Sorry for the rambling

Take care

Steve Quinn
 

Attachments

Rich (BB code): 
4: kd> !devnode ffff9583f7bd4520
DevNode 0xffff9583f7bd4520 for PDO 0xffff9583f611b060
  Parent 0xffff9583e989cca0   Sibling 0000000000   Child 0xffff9583f7bcf7a0  
  InterfaceType 0  Bus Number 0
  InstancePath is "PCI\VEN_10DE&DEV_0FBC&SUBSYS_80D5103C&REV_A1\4&1516f031&0&0108"
  ServiceName is "HDAudBus"
  State = DeviceNodeStarted (0x308)
  Previous State = DeviceNodeStarted (0x308)
  StateHistory[03] = DeviceNodeAwaitingQueuedDeletion (0x30e)
  StateHistory[02] = DeviceNodeStarted (0x308)
  StateHistory[01] = DeviceNodeEnumerateCompletion (0x30d)
  StateHistory[00] = DeviceNodeEnumeratePending (0x30c)
  StateHistory[19] = DeviceNodeStarted (0x308)
  StateHistory[18] = DeviceNodeEnumerateCompletion (0x30d)
  StateHistory[17] = DeviceNodeEnumeratePending (0x30c)
  StateHistory[16] = DeviceNodeStarted (0x308)
  StateHistory[15] = DeviceNodeEnumerateCompletion (0x30d)
  StateHistory[14] = DeviceNodeEnumeratePending (0x30c)
  StateHistory[13] = DeviceNodeStarted (0x308)
  StateHistory[12] = DeviceNodeEnumerateCompletion (0x30d)
  StateHistory[11] = DeviceNodeEnumeratePending (0x30c)
  StateHistory[10] = DeviceNodeStarted (0x308)
  StateHistory[09] = DeviceNodeEnumerateCompletion (0x30d)
  StateHistory[08] = DeviceNodeEnumeratePending (0x30c)
  StateHistory[07] = DeviceNodeStarted (0x308)
  StateHistory[06] = DeviceNodeStartPostWork (0x307)
  StateHistory[05] = DeviceNodeStartCompletion (0x306)
  StateHistory[04] = DeviceNodeStartPending (0x305)
  Flags (0x6c010028)  DNF_REENUMERATE, DNF_IDS_QUERIED,
                      DNF_DEVICE_GONE, DNF_NO_LOWER_DEVICE_FILTERS,
                      DNF_NO_LOWER_CLASS_FILTERS, DNF_NO_UPPER_DEVICE_FILTERS,
                      DNF_NO_UPPER_CLASS_FILTERS

The issue is possibly related to your sound card controller driver by Nvidia, I would suggest checking for a possible update from the support page of the computer.
 
Rich (BB code): 
4: kd> .cxr 0xffffd88d5036ea10
rax=ffffdb060a768640 rbx=ffffdb060a768640 rcx=0000000000000028
rdx=0000000000000000 rsi=00000010100fffd8 rdi=ffffdb05ee38acf0
rip=fffff8023474eb2c rsp=ffffd88d5036f410 rbp=ffffd88d5036f560
 r8=0000000000000fff  r9=00000000000006d0 r10=00000000656c5252
r11=0000000000001001 r12=0000000000000001 r13=0000000000000005
r14=ffff9583e9871750 r15=ffffdb05ee6fcb90
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050282
nt!RtlpCopyRangeListEntry+0x2c:
fffff802`3474eb2c 0f1006          movups  xmm0,xmmword ptr [rsi] ds:002b:00000010`100fffd8=????????????????????????????????

The reason why the nt!RtlpCopyRangeListEntry throws an exception is because an invalid parameter is being passed to it. The range is the I/O resources handled by the device's arbiter. The !arbiter command doesn't dump correctly because this is only a Minidump but I thought I'll try it anyway to explain what is happening.

Rich (BB code): 
4: kd> !arbiter

DEVNODE ffff9583e7ac7cc0 (HTREE\ROOT\0)
  Interrupt Arbiter "RootIRQ" at fffff80234c44340
    Allocated ranges:
Error reading RangeList ffffdb05ee39ea80
    Possible allocation:
Error reading RangeList ffffdb05ee39ec30
  BusNumber Arbiter "RootBusNumber" at fffff80234c441e0
    Allocated ranges:
Error reading RangeList ffffdb05ee39eb40
    Possible allocation:
Error reading RangeList ffffdb05ee39eae0
  Port Arbiter "RootPort" at fffff80234c44760
    Allocated ranges:
Error reading RangeList ffffdb05ee39edb0
    Possible allocation:
Error reading RangeList ffffdb05ee39ed20
  Memory Arbiter "RootMemory" at fffff80234c44600
    Allocated ranges:
Error reading RangeList ffffdb05ee39ed80
    Possible allocation:
Error reading RangeList ffffdb05ee39e960
  ffff9583e7ac8a20: Could not read device node

Rich (BB code): 
4: kd> knL
  *** Stack trace for last set context - .thread/.cxr resets it
 # Child-SP          RetAddr           Call Site
00 ffffd88d`5036f410 fffff802`3474eab1 nt!RtlpCopyRangeListEntry+0x2c << Crash here!
01 ffffd88d`5036f440 fffff802`35cc0a0c nt!RtlCopyRangeList+0x41
02 ffffd88d`5036f470 fffff802`35cc114d pci!ArbTestAllocation+0x3c
03 ffffd88d`5036f4d0 fffff802`3473d3be pci!ArbArbiterHandler+0x5d
04 ffffd88d`5036f510 fffff802`3473c0c6 nt!IopCallArbiter+0xca << Arbiter is used to manage resources between PnP devices
05 ffffd88d`5036f570 fffff802`3473e3ea nt!PnpReleaseResourcesInternal+0x122
06 ffffd88d`5036f640 fffff802`3473e53a nt!IopReleaseResources+0xe
07 ffffd88d`5036f670 fffff802`34732e28 nt!IopLegacyResourceAllocation+0xb6
08 ffffd88d`5036f730 fffff802`3475ce8d nt!IopReleaseDeviceResources+0xa4 << Release resources allocated to the device
09 ffffd88d`5036f7c0 fffff802`34732c38 nt!PnpSurpriseRemoveLockedDeviceNode+0xc9
0a ffffd88d`5036f820 fffff802`34732933 nt!PnpDeleteLockedDeviceNode+0x88
0b ffffd88d`5036f860 fffff802`3473107e nt!PnpDeleteLockedDeviceNodes+0xf7
0c ffffd88d`5036f8e0 fffff802`3472be3b nt!PnpProcessQueryRemoveAndEject+0x1da << Eject the device and remove the device node
0d ffffd88d`5036f9c0 fffff802`3464903e nt!PnpProcessTargetDeviceEvent+0xeb
0e ffffd88d`5036f9f0 fffff802`342b86c5 nt!PnpDeviceEventWorker+0x2ce
0f ffffd88d`5036fa70 fffff802`34355a05 nt!ExpWorkerThread+0x105
10 ffffd88d`5036fb10 fffff802`343fea08 nt!PspSystemThreadStartup+0x55
11 ffffd88d`5036fb60 00000000`00000000 nt!KiStartSystemThread+0x28

You can use a third-party debugger extension such as !stack -p from CodeMachine to display the parameters passed to the functions on the call stack. There is manual methods of getting the same information, however, using !stack -p is far easy and more efficient. Anyway, there is a couple of functions which take a device node as a parameter, as shown in the following output:

Rich (BB code): 
4: kd> !stack -p
Call Stack : 18 frames
## Stack-Pointer    Return-Address   Call-Site       
00 ffffd88d5036f410 fffff8023474eab1 nt!RtlpCopyRangeListEntry+2c 
    Parameter[0] = 00000010100fffd8
    Parameter[1] = (unknown)       
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
01 ffffd88d5036f440 fffff80235cc0a0c nt!RtlCopyRangeList+41 
    Parameter[0] = ffffdb05ee38ac60
    Parameter[1] = ffffdb05ee38acf0
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
02 ffffd88d5036f470 fffff80235cc114d pci!ArbTestAllocation+3c 
    Parameter[0] = ffff9583e9871750
    Parameter[1] = ffffd88d5036f540
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
03 ffffd88d5036f4d0 fffff8023473d3be pci!ArbArbiterHandler+5d 
    Parameter[0] = (unknown)       
    Parameter[1] = (unknown)       
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
04 ffffd88d5036f510 fffff8023473c0c6 nt!IopCallArbiter+ca 
    Parameter[0] = ffffdb05ee6fcb90
    Parameter[1] = 0000000000000000
    Parameter[2] = ffffdb06012d97a8
    Parameter[3] = (unknown)       
05 ffffd88d5036f570 fffff8023473e3ea nt!PnpReleaseResourcesInternal+122 
    Parameter[0] = ffff9583f7bd4520
    Parameter[1] = (unknown)       
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
06 ffffd88d5036f640 fffff8023473e53a nt!IopReleaseResources+e 
    Parameter[0] = ffff9583f7bd4520
    Parameter[1] = (unknown)       
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
07 ffffd88d5036f670 fffff80234732e28 nt!IopLegacyResourceAllocation+b6 
    Parameter[0] = 00000000ffffffff
    Parameter[1] = ffff9583e7c02e30
    Parameter[2] = ffff9583f611b060
    Parameter[3] = 0000000000000000
08 ffffd88d5036f730 fffff8023475ce8d nt!IopReleaseDeviceResources+a4 
    Parameter[0] = ffff9583f7bd4520
    Parameter[1] = 0000000000000000
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)       
09 ffffd88d5036f7c0 fffff80234732c38 nt!PnpSurpriseRemoveLockedDeviceNode+c9 
    Parameter[0] = ffff9583f7bd4520
    Parameter[1] = 0000000000000000
    Parameter[2] = 0000000000000000
    Parameter[3] = (unknown)



 
Thanks Blue Robot. Your BSOD Kung Foo is legendary. I'll look closer your analysis today. The customer is a very busy accountant working 12-14 hours daily until April 2022. I'm a little gun shy to play around with drivers as she is an hour away and so busy. I did log in last night and validated she is running the most recent HP provided Nvidia Video and Audio driver. :-(

She is still getting BSOD's daily but I've missed any new dumps as I had foolishly turned off overwrite any existing files a few days back It is now set to overwrite so I will catch any new dumps

I'll try tonight to navigate her through the BIOS or Boot menu to boot from a Memtest86 I built/tested/mailed to her.
I'd like to be 100% certain it's not a bad stick or RAM before doing too much more digging.

I do have one question for you. Which NVidia graphics driver do you recommend for stability? A manufacturer driver or an NVidia version? The laptops NVIDIA Quadro M1000M has a much newer Video and HDAudio driver in R510

1645716776395.png
 
I was able to walk the customer to booting MemTest86 this evening. There are no memory errors after 2 loops. I wanted more loops but it was getting late. I'm sure I'll have another BSOD and dump soon to share. I really appreciate your help so far.
 
stevepaulquinn said:
A manufacturer driver or an NVidia version? The laptops NVIDIA Quadro M1000M has a much newer Video and HDAudio driver in R510
Click to expand...
It's usually best to use the OEM drivers if it is a OEM machine (e.g. HP), however, since the user is already using the latest ones from them then I would try the Nvidia drivers for now.

stevepaulquinn said:
There are no memory errors after 2 loops. I wanted more loops but it was getting late. I'm sure I'll have another BSOD and dump soon to share. I really appreciate your help so far.
Click to expand...
No problem! It's best to let it run for about 8 passes (2 runs of 4 passes).
 
The HP OEM HDMI Audio Driver is 1.3.38.60.
This is the same version contained in the Official NVidia Standard Driver :-(
The NVidia DCH Driver however contains 1.3.39.3

1645812377263.png

Below is the relevant version from each these drivers INF's

HP OEM Driver
DriverVer=05/03/2021,1.3.38.60

NVidia Standard Driver
472.98-quadro-rtx-desktop-notebook-win10-win11-64bit-international-whql
DriverVer=05/03/2021,1.3.38.60

NVidia DCH Driver
511.79-quadro-rtx-desktop-notebook-win10-win11-64bit-international-dch-whql
DriverVer=01/02/2022,1.3.39.3

Would it be crazy to simply update the HDMI Audio Driver to 1.3.39.3 and leave the HP OEM Nvidia Video driver installed as is?

1645812332577.png
 
Hi There. Sorry for the delay. As it's heavy into tax season my customer has been understandably MIA.

Sunday's tend to be quiet with her so as of today Sunday March 13, I updated the HDMI Audio Driver to 1.3.39.3 and rebooted.

I hope to start a 4 loop Memtest86 this afternoon to be 110% sure it's not RAM

I appreciate your great support and have already sent a donation your way.

Keep you posted, crossing fingers either way
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top