Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Home NTDEV

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

UMDF verifier failure debugging

Michal_VodickaMichal_Vodicka Member - All Emails Posts: 109

I've received a dump with UMDF verifier failure. I've never seen it before and can't find a way how to find what was the problem. Also can't find what driver caused it, it probably wasn't mine but it occured during automatic tests so I need to check. I think so because the .txt file with the same timestamp in C:\ProgramData\Microsoft\WDF contains different device ID.

Well, I feel dumb but what am I supposed to do with it? I'd expect verifier tells me what was wrong. I've examined all threads in the dump and find nothing intresting. Posting full !analyze -v output:

   This is a verifier failure caused by a bug in a UMDF driver.
   A verifier failure is a runtime check performed by the framework that the driver failed.
   Please follow up with the owner of the driver. 
   Detected by :  WUDFx!WudfVerify
   Location    :  
   Message     :  
   Class       :  Unknown
   Kind        :  Unknown
   Error #     :  0x0
   Thread ID   :  0x1cd0 ~~[1cd0]k;~~[1cd0]s
   Visit http://go.microsoft.com/fwlink/?LinkId=525997 for debugging tips.


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on AAHID4PW5453

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 2

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : Timeline.Process.Start.DeltaSec
    Value: 11271


NTGLOBALFLAG:  2000100

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_LOADED: 1

CONTEXT:  (.ecxr)
rax=000000290e0fe580 rbx=00007fff59279ee0 rcx=000000290e0fe0b0
rdx=0000000000000000 rsi=000000000000003d rdi=000001b47d1b3f10
rip=00007fff592049cc rsp=000000290e0fe060 rbp=00007fff59279eb8
 r8=0000000000000008  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=000001b47d2c6e40 r13=000000290e0ff588
r14=000000290e0fee70 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
WUDFx!WudfVerify+0x7c:
00007fff`592049cc 0f1f440000      nop     dword ptr [rax+rax]
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 0000000000000000
   ExceptionCode: 00000000
  ExceptionFlags: 00000000
NumberParameters: 0

PROCESS_NAME:  WUDFHost.exe

FAULTING_THREAD:  00001cd0

STACK_TEXT:  
00000029`0e0fe060 00007fff`59218965 : 00000000`00000000 000001b4`039befc0 00007fff`59279e70 000001b4`7e0bafc0 : WUDFx!WudfVerify+0x7c
00000029`0e0fee10 00007fff`59215366 : 000001b4`7d4d3f00 000001b4`7e0b8f20 000001b4`039befc0 00000000`00000000 : WUDFx!CWudfDriverGlobals::~CWudfDriverGlobals+0xf5
00000029`0e0fef90 00007fff`59217f9f : 00000000`00000000 00007ff6`a53d0dcf 00000000`00000000 000001b4`7d4d3f00 : WUDFx!CWudfDriverGlobals::`scalar deleting destructor'+0xe
00000029`0e0fefc0 00007ff6`a53cde15 : 00000000`00000000 00000000`00000000 00007fff`830a8a08 00000000`00000001 : WUDFx!CWUDF::Uninitialize+0x6f
00000029`0e0ff030 00007ff6`a53cdcbe : 000001b4`02e40e10 00000029`0e0ff1d0 000001b4`7d4d3f58 00000000`00001f01 : WUDFHost!CWudfDeviceStack::~CWudfDeviceStack+0x13d
00000029`0e0ff0a0 00007ff6`a53bc473 : 00000000`00000000 00007fff`86d09084 000001b4`77800000 00000000`01000002 : WUDFHost!CWudfDeviceStack::`scalar deleting destructor'+0xe
00000029`0e0ff0d0 00007fff`830951f2 : 00000029`0e0ff588 000001b4`7d469f00 00000029`0e0ff5b0 00000000`00000000 : WUDFHost!CLpcNotification::Message+0x1cc3
00000029`0e0ff380 00007fff`8309440e : 000001b4`7d34cfd0 00000000`00000001 000001b4`7d34af90 00007fff`8309626c : WUDFPlatform!WdfLpcPort::ProcessMessage+0x122
00000029`0e0ff440 00007fff`8309612f : 000001b4`7d469f30 000001b4`7d340f00 00000029`0e0ff620 00007fff`82b05f61 : WUDFPlatform!WdfLpcCommPort::ProcessMessage+0x8e
00000029`0e0ff490 00007fff`83097e5e : 000001b4`7d469f30 00000000`00000001 00000000`00000001 00000000`00000001 : WUDFPlatform!WdfLpcConnPort::ProcessMessage+0xef
00000029`0e0ff540 00007ff6`a53c3f80 : 000001b4`7d35ef70 000001b4`7d35ef70 000001b4`7d475fa8 00007ff6`a53c3f30 : WUDFPlatform!WdfLpc::RetrieveMessage+0x15e
00000029`0e0ff6b0 00007fff`82b0db5b : 000001b4`79d73eb0 000001b4`7d475fa8 00007ff6`a53c3f30 00007ff6`a53c3f30 : WUDFHost!ThreadPoolWorkerThunk+0x50
00000029`0e0ff6e0 00007fff`86c20ebc : 000001b4`7d475e20 00000000`7ffe0386 00000029`0e0ff938 00000000`00000000 : vfbasics!AVrfpTpWaitCallback+0x6b
00000029`0e0ff770 00007fff`86c62f26 : 000001b4`7d475fa8 000001b4`06a66fb0 00000000`00000000 000001b4`7c2c0ff0 : ntdll!TppExecuteWaitCallback+0xa4
00000029`0e0ff7c0 00007fff`853d7034 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!TppWorkerThread+0x456
00000029`0e0ffac0 00007fff`86c62651 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000029`0e0ffaf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21


SYMBOL_NAME:  wudfx!WudfVerify+7c

MODULE_NAME: WUDFx

IMAGE_NAME:  WUDFx.dll

STACK_COMMAND:  ~4s ; .ecxr ; kb

FAILURE_BUCKET_ID:  APPLICATION_FAULT_AVRF_0_WUDFx.dll!WudfVerify

EXCEPTION_CODE_STR:  0

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {87cafaad-5e06-fc5a-4ee0-c53e629afa96}

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


Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Developing Minifilters 24 May 2021 Live, Online
Writing WDF Drivers 14 June 2021 Live, Online
Internals & Software Drivers 27 September 2021 Live, Online
Kernel Debugging 15 November 2021 Live, Online