wdf_violation BSOD

Lara66

New Member
I use Win 10, recently updated to 1903, on an Asus notebook.

After updating to version 1903 and then using IObit Driver Booster to update some drivers (I don I get wdf_violation BSOD when restarting or on shutdown and sleep.

I don't remember the drivers which got updated in order to roll them back, and all the System Restore Points that I had created are gone.

I checked the dump files and I'm no expert. As far as I understood the cause is WUDFRd.sys but the app BlueScreenView identifies Wdf01000.sys as the problem. I checked both files with SFC but it responded with
Windows Resource Protection did not find any integrity violations.

By the way, is there any way to restore the missing System Restore Points? All in all they are created to be used in such cases.

Code:
*******************************************************************************
*                                                                             *
*                        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 bug check.
Arguments:
Arg1: 000000000000000d, A power irp was received for the device but the irp was not
    requested by the device (the power policy owner). Possibly there
    are multiple power policy owners. Only one driver in the stack can
    be the power policy owner. A KMDF driver can change power policy
    ownership by calling the DDI WdfDeviceInitSetPowerPolicyOwnership.
Arg2: ffff9b862fc6cc40, Device object pointer.
Arg3: ffff9b8638294050, Power Irp.
Arg4: ffff9b862f1f2dd0, Reserved.

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME:  K501UX

SYSTEM_SKU:  ASUS-NotebookSKU

SYSTEM_VERSION:  1.0      

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  K501UX.209

BIOS_DATE:  01/20/2016

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  K501UX

BASEBOARD_VERSION:  1.0      

DUMP_TYPE:  2

BUGCHECK_P1: d

BUGCHECK_P2: ffff9b862fc6cc40

BUGCHECK_P3: ffff9b8638294050

BUGCHECK_P4: ffff9b862f1f2dd0

BUGCHECK_STR:  0x10D_d

CPU_COUNT: 4

CPU_MHZ: 960

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 4e

CPU_STEPPING: 3

CPU_MICROCODE: 6,4e,3,0 (F,M,S,R)  SIG: C6'00000000 (cache) C6'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-2EALKN8

ANALYSIS_SESSION_TIME:  04-25-2019 22:58:39.0557

ANALYSIS_VERSION: 10.0.18317.1001 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8063bffb828 to fffff80637fbc810

STACK_TEXT:  
ffff8d85`687d5688 fffff806`3bffb828 : 00000000`0000010d 00000000`0000000d ffff9b86`2fc6cc40 ffff9b86`38294050 : nt!KeBugCheckEx
ffff8d85`687d5690 fffff806`3bfc0b4e : ffff8d85`687d5790 00000000`00000016 00000000`00000000 ffff9b86`2fd30060 : Wdf01000!FxVerifierBugCheckWorker+0x24 [minkernel\wdf\framework\shared\object\fxverifierbugcheck.cpp @ 68]
ffff8d85`687d56d0 fffff806`3bfa3c54 : ffff9b86`2fd30060 0000246f`b19bbfff ffff9b86`30df1080 ffff9b86`25166640 : Wdf01000!FxPkgFdo::_DispatchSetPower+0x10e6e [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 120]
ffff8d85`687d5720 fffff806`3bfaabd3 : ffff9b86`38294050 ffff9b86`2fcfc9b0 ffff9b86`38294050 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0xb4 [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 765]
ffff8d85`687d5790 fffff806`37f6fe1e : 00000000`00000016 ffff9b86`38294050 00000000`00000200 ffff9b86`38294240 : Wdf01000!FxDevice::DispatchWithLock+0x113 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430]
ffff8d85`687d57f0 fffff806`37e27dc0 : 00000000`00000000 fffff806`55b36ac6 00000000`80000000 ffff9b86`38294240 : nt!IopPoHandleIrp+0x36
ffff8d85`687d5820 fffff806`37f72279 : 00000000`00000000 00000000`00000016 fffff806`55b6ad88 ffff9b86`38294050 : nt!IofCallDriver+0x70
ffff8d85`687d5860 fffff806`55b32149 : 00000000`00000002 00000000`00000000 00000000`00000002 00000000`0000000e : nt!IoCallDriver+0x9
ffff8d85`687d5890 fffff806`55b31f64 : fffff806`34f11180 ffff9b86`2e844d00 00000000`00000000 00000000`80000000 : WUDFRd!RdPnpTracker::RdPnpProcessor+0x579 [minkernel\wdf\framework\umdf\redirector\driver\pnp.cpp @ 1265]
ffff8d85`687d5930 fffff806`55b31bb1 : 00000000`00000000 ffff9b86`2e844df0 00000000`00000000 fffff806`3838a240 : WUDFRd!RdPnpTracker::RdPnpProcessor+0x394 [minkernel\wdf\framework\umdf\redirector\driver\pnp.cpp @ 1130]
ffff8d85`687d59d0 fffff806`37ebdeff : 00000000`00000000 ffff9b86`2f4ad120 ffff9b86`2e844df0 fffff806`3c3f1fd0 : WUDFRd!RdPnpTracker::RdPnpCallbackAtPassiveInSystemProcess+0x11 [minkernel\wdf\framework\umdf\redirector\driver\pnp.cpp @ 2166]
ffff8d85`687d5a00 fffff806`37eae835 : ffff9b86`251299e0 ffff9b86`25166640 fffff806`37ebde00 00000000`00000002 : nt!IopProcessWorkItem+0xff
ffff8d85`687d5a70 fffff806`37f30925 : ffff9b86`25166640 00000000`00000080 ffff9b86`250e9240 00000000`00000001 : nt!ExpWorkerThread+0x105
ffff8d85`687d5b10 fffff806`37fc3d5a : ffffad81`f54cb180 ffff9b86`25166640 fffff806`37f308d0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffff8d85`687d5b60 00000000`00000000 : ffff8d85`687d6000 ffff8d85`687cf000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC:  aff857ac1f7c0e16f6bc5b3f292706b2a986b817

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  594b4feaa9284e0194212226a154709dbc9e9aa6

THREAD_SHA1_HASH_MOD:  0ba795ef9a0b77c35f26da9c76f76f84449945ea

FOLLOWUP_IP:
WUDFRd!RdPnpTracker::RdPnpProcessor+579 [minkernel\wdf\framework\umdf\redirector\driver\pnp.cpp @ 1265]
fffff806`55b32149 e932020000      jmp     WUDFRd!RdPnpTracker::RdPnpProcessor+0x7b0 (fffff806`55b32380)

FAULT_INSTR_CODE:  232e9

FAULTING_SOURCE_LINE:  minkernel\wdf\framework\umdf\redirector\driver\pnp.cpp

FAULTING_SOURCE_FILE:  minkernel\wdf\framework\umdf\redirector\driver\pnp.cpp

FAULTING_SOURCE_LINE_NUMBER:  1265

FAULTING_SOURCE_CODE:  
No source found for 'minkernel\wdf\framework\umdf\redirector\driver\pnp.cpp'


SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  WUDFRd!RdPnpTracker::RdPnpProcessor+579

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: WUDFRd

IMAGE_NAME:  WUDFRd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  2a40f545

IMAGE_VERSION:  10.0.18362.1016

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  579

FAILURE_BUCKET_ID:  0x10D_d_WUDFRd!RdPnpTracker::RdPnpProcessor

BUCKET_ID:  0x10D_d_WUDFRd!RdPnpTracker::RdPnpProcessor

PRIMARY_PROBLEM_CLASS:  0x10D_d_WUDFRd!RdPnpTracker::RdPnpProcessor

TARGET_TIME:  2019-04-25T18:15:27.000Z

OSBUILD:  18362

OSSERVICEPACK:  30

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  5902

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x10d_d_wudfrd!rdpnptracker::rdpnpprocessor

FAILURE_ID_HASH:  {3a1cc6a0-0a74-96e9-56fd-8d03045111ca}

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

Josephur

Windows Forum Admin
Staff member
Premium Supporter
Microsoft Certified Professional
"Driver Updaters" are generally bad practice to use, and most are a joke. Always get your drivers from your computer manufacturer, or the manufacturer of the hardware in question. Can you also attach the DMP file (zipped please)?
 

Lara66

New Member
"Driver Updaters" are generally bad practice to use, and most are a joke. Always get your drivers from your computer manufacturer, or the manufacturer of the hardware in question. Can you also attach the DMP file (zipped please)?
Thanks for such a quick reply.

I do agree on not using "Driver Updaters", but it's sometimes very difficult to find the drivers on manufacturers website.

I uploaded the DMP files.
 

Attachments

Neemobeer

Windows Forum Team
Staff member
Correct WUDFRd is the framework driver for other KMDF drivers. You see WDF01000higher in the stack

Code:
0: kd> kb
 # RetAddr           : Args to Child                                                           : Call Site
00 fffff800`34dfb828 : 00000000`0000010d 00000000`0000000d ffffd20d`8715d9b0 ffffd20d`88cb6b20 : nt!KeBugCheckEx
01 (Inline Function) : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!Mx::MxBugCheckEx+0x19 [minkernel\wdf\framework\shared\inc\primitives\km\mxgeneralkm.h @ 142]
02 fffff800`34dc0b4e : ffffce8f`6696f790 00000000`00000016 00000000`00000000 ffffd20d`880d8020 : Wdf01000!FxVerifierBugCheckWorker+0x24 [minkernel\wdf\framework\shared\object\fxverifierbugcheck.cpp @ 68]
03 (Inline Function) : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x10e3e [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 320]
04 fffff800`34da3c54 : ffffd20d`880d8020 00000000`00000004 00000000`00000003 00000000`00000000 : Wdf01000!FxPkgFdo::_DispatchSetPower+0x10e6e [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 120]
05 fffff800`34daabd3 : ffffd20d`88cb6b20 ffffd20d`883b99b0 ffffd20d`88cb6b20 00000000`00000004 : Wdf01000!FxPkgPnp::Dispatch+0xb4 [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 765]
06 (Inline Function) : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!DispatchWorker+0x9e [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1572]
07 (Inline Function) : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!FxDevice::Dispatch+0xbc [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1586]
08 fffff800`3176fe1e : 00000000`00000016 ffffd20d`88cb6b20 00000000`00000300 ffffd20d`88cb6d10 : Wdf01000!FxDevice::DispatchWithLock+0x113 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430]
09 fffff800`31627dc0 : 00000000`00000000 fffff800`4e156ac6 00000000`80000000 ffffd20d`88cb6d10 : nt!IopPoHandleIrp+0x36
0a fffff800`31772279 : 00000000`00000000 00000000`00000016 fffff800`4e18ad88 ffffd20d`88cb6b20 : nt!IofCallDriver+0x70
0b fffff800`4e152149 : 00000000`00000002 00000000`00000000 00000000`00000002 00000000`0000000e : nt!IoCallDriver+0x9
0c fffff800`4e151f64 : fffff800`2de77180 ffffd20d`87482d00 00000000`00000000 00000000`80000000 : WUDFRd!RdPnpTracker::RdPnpProcessor+0x579 [minkernel\wdf\framework\umdf\redirector\driver\pnp.cpp @ 1265]
0d fffff800`4e151bb1 : 00000000`00000000 ffffd20d`87482df0 00000000`00000000 fffff800`31b8a240 : WUDFRd!RdPnpTracker::RdPnpProcessor+0x394 [minkernel\wdf\framework\umdf\redirector\driver\pnp.cpp @ 1130]
0e fffff800`316bdeff : 00000000`00000001 ffffd20d`88162280 ffffd20d`87482df0 00000000`00000000 : WUDFRd!RdPnpTracker::RdPnpCallbackAtPassiveInSystemProcess+0x11 [minkernel\wdf\framework\umdf\redirector\driver\pnp.cpp @ 2166]
0f fffff800`316ae835 : ffffd20d`7df6d9e0 ffffd20d`88b13080 fffff800`316bde00 00000000`0000000c : nt!IopProcessWorkItem+0xff
10 fffff800`31730925 : ffffd20d`88b13080 00000000`00000080 ffffd20d`7dea4380 fffff800`00000001 : nt!ExpWorkerThread+0x105
11 fffff800`317c3d5a : fffff800`2de77180 ffffd20d`88b13080 fffff800`317308d0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
12 00000000`00000000 : ffffce8f`66970000 ffffce8f`66969000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a
 

Neemobeer

Windows Forum Team
Staff member
I would start by updating the Intel Rapid Storage driver and that also be causing the WDF issue.
 

Lara66

New Member
I would start by updating the Intel Rapid Storage driver and that also be causing the WDF issue.
Thanks for your reply.

Actually I just downloaded and installed Intel Rapid Storage Technology two days ago. I presume it contained the latest driver.

And I'm really curious to know how you found out that the Intel Rapid Storage driver is causing the WDF issue!?
 

Neemobeer

Windows Forum Team
Staff member
I'm not saying it is the issue, but the WDF error indicates something else in the driver stack is modifying the power policy. Intel RST can make changes to the power policy so it's quite possibly the culprit.
 

Lara66

New Member
I'm not saying it is the issue, but the WDF error indicates something else in the driver stack is modifying the power policy. Intel RST can make changes to the power policy so it's quite possibly the culprit.
I uninstalled the Intel Rapid Storage application, but I'm not sure if the driver has got uninstalled too (I don't see it in device manager under storage controllers though). And the problem is NOT solved.

37834
 

Neemobeer

Windows Forum Team
Staff member
It may not be removed. You can run the command pnputil /enum-drivers and look for it in the list. If it shows in the list, look for the associated oem##.inf file name and remove the driver with pnputil /delete-driver oem##.inf You will need to run the command prompt elevated (Right click cmd and select 'Run As Administrator')
 

Lara66

New Member
It may not be removed. You can run the command pnputil /enum-drivers and look for it in the list. If it shows in the list, look for the associated oem##.inf file name and remove the driver with pnputil /delete-driver oem##.inf You will need to run the command prompt elevated (Right click cmd and select 'Run As Administrator')
I used pnputil /enum-drivers and the list was very long. So used CTRL+F and searched for "Rapid" and found nothing.

But there is this:
37837
 

Lara66

New Member
Some of your dumps where pointing at the iaStorAC driver
Can you help me to get rid of them, please?

UPDATE: After installing three different versions of the driver, I highly doubt it to be the cause of the BSOD.
 
Last edited:

Lara66

New Member
Solved:
I paid too much attention to Dump files and had forgotten checking Event Logs. After taking a look at logs in Event Viewer I came across this:
The driver \Driver\WudfRd failed to load for the device PCI\VEN_8086&DEV_1903&SUBSYS_1D1D1043&REV_08
So the problem was Intel(R) Dynamic Platform & Thermal Framework and and NOT the Intel Rapid Storage.

The irony is that I think IObit Driver Booster caused the problem in the first place but as I couldn't find the driver for Intel(R) Dynamic Platform & Thermal Framework on any official website I used Driver Easy to update the driver and it worked. No Event error and no BSOD so far.
 
Last edited:
Top