• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Any failures related to Hotkey UWP service? Click here for tips.
Check out our WINDOWS 11 Support Center info about: OPTIMIZATION, KNOWN ISSUES, FAQs, VIDEOS AND MORE.
HP Recommended

We got a lot of blue screen of death errors (WDF_Violation), on different HP laptops, with the use of a HP dockingstation, see below de .dmp files, i analysed. If we dont use the dockingstation ethernet connection and plug the ethernetcable in to the laptop, nothing will happen, that is for now the quick fix.

 

I have tried everything, other Operating system , other laptop, other cables, nothing works. In the files below I found something intressting about rtump64x64.sys, In my opinion it is causing a conflict with the dockingstation. I noticed that rtump64x64.sys stand for  rtump64x64.sys (Realtek USB FE/1GbE/2.5GbE/5GbE NIC Family Miniport 6.4 64-bit Driver). 

 

See below the operating system for the different laptops.

 

Operating system

Windows

Operating system version

10.0.22000.978

Operating system language

nl-NL

Operating system edition

Enterprise

Operating system SKU

Windows 10/11 Enterprise (4)​

 

Dumpfile (same outcome with other users):

 

Microsoft (R) Windows Debugger Version 10.0.22621.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Users\shuisman\Downloads\093022-10781-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff804`55a00000 PsLoadedModuleList = 0xfffff804`566297b0
Debug session time: Fri Sep 30 08:17:10.830 2022 (UTC + 2:00)
System Uptime: 0 days 0:01:41.782
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
..................
For analysis of this file, run !analyze -v
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this BugCheck.
Arguments:
Arg1: 0000000000000006, A fatal error was made in handling a WDF request. In this case,
      Parameter 2 further specifies the type of fatal error that has
      been made, as defined by the enumeration WDF_REQUEST_FATAL_ERROR.
Arg2: 0000000000000003, The driver attempted to send a framework request that has
      already been sent to an I/O target.
Arg3: 000028fe4f1d2d58, The WDF request handle value.
Arg4: ffffd701b5589010, Reserved.
 
Debugging Details:
------------------
 
*** WARNING: Unable to verify timestamp for rtump64x64.sys
*** WARNING: Unable to verify timestamp for win32k.sys
 
KEY_VALUES_STRING: 1
 
    Key  : Analysis.CPU.mSec
    Value: 3796
 
    Key  : Analysis.DebugAnalysisManager
    Value: Create
 
    Key  : Analysis.Elapsed.mSec
    Value: 23300
 
    Key  : Analysis.Init.CPU.mSec
    Value: 3249
 
    Key  : Analysis.Init.Elapsed.mSec
    Value: 97847
 
    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 105
 
    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:  093022-10781-01.dmp
BUGCHECK_CODE:  10d
BUGCHECK_P1: 6
BUGCHECK_P2: 3
BUGCHECK_P3: 28fe4f1d2d58
BUGCHECK_P4: ffffd701b5589010
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
 
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT:  1
PROCESS_NAME:  System
 
STACK_TEXT:  
ffff9c08`b1077568 fffff804`5a41ca8c     : 00000000`0000010d 00000000`00000006 00000000`00000003 000028fe`4f1d2d58 : nt!KeBugCheckEx
ffff9c08`b1077570 fffff804`5a3fa234     : 000028fe`4f1d2d58 00000000`00000000 000028fe`4f1d2d58 fffff804`5a3b5df6 : Wdf01000!FxVerifierBugCheckWorker+0x24 [minkernel\wdf\framework\shared\object\fxverifierbugcheck.cpp @ 68]
ffff9c08`b10775b0 fffff804`5a3bb090     : 00000000`00000000 ffffd701`b5589010 00000000`00000000 00000000`00000000 : Wdf01000!FxIoTarget::SubmitLocked+0x3f064 [minkernel\wdf\framework\shared\targets\general\fxiotarget.cpp @ 1318]
ffff9c08`b1077640 fffff804`76e96edf     : ffffd701`b5589100 ffffd701`b0e2d2a0 ffffd701`b04f4da0 ffffd701`b056f290 : Wdf01000!imp_WdfRequestSend+0x100 [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 2055]
ffff9c08`b10776c0 ffffd701`b5589100     : ffffd701`b0e2d2a0 ffffd701`b04f4da0 ffffd701`b056f290 00000000`00000000 : rtump64x64+0x46edf
ffff9c08`b10776c8 ffffd701`b0e2d2a0     : ffffd701`b04f4da0 ffffd701`b056f290 00000000`00000000 00000000`00000000 : 0xffffd701`b5589100
ffff9c08`b10776d0 ffffd701`b04f4da0     : ffffd701`b056f290 00000000`00000000 00000000`00000000 00000000`00000018 : 0xffffd701`b0e2d2a0
ffff9c08`b10776d8 ffffd701`b056f290     : 00000000`00000000 00000000`00000000 00000000`00000018 00000000`00000000 : 0xffffd701`b04f4da0
ffff9c08`b10776e0 00000000`00000000     : 00000000`00000000 00000000`00000018 00000000`00000000 00000000`00000000 : 0xffffd701`b056f290
 
 
SYMBOL_NAME:  rtump64x64+46edf
 
MODULE_NAME: rtump64x64
 
IMAGE_NAME:  rtump64x64.sys
 
STACK_COMMAND:  .cxr; .ecxr ; kb
 
BUCKET_ID_FUNC_OFFSET:  46edf
 
FAILURE_BUCKET_ID:  0x10D_6_rtump64x64!unknown_function
 
OS_VERSION:  10.0.22000.1
 
BUILDLAB_STR:  co_release
 
OSPLATFORM_TYPE:  x64
 
OSNAME:  Windows 10
 
FAILURE_ID_HASH:  {132c4212-eca3-af60-788b-e397e6403655}
 
Followup:     MachineOwner

 

Last but not least, we use:

 

HP ProBook 450 G8 Notebook PC

HP ProBook 450 G7

 

and this type of dockingstation:

 

HP EliteDisplay E273d 27inch Docking monitor and HP USB-C Dock G4

 

In the Dumpfile I saw four arguments, what specified the cause of my problem (I think), unfortanley, I am not able to fix it my self, Hopefully someone can help me out?

 

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.