Windows 10: BSOD caused by mshidkmdf.sys

Discus and support BSOD caused by mshidkmdf.sys in Windows 10 BSOD Crashes and Debugging to solve the problem; So my PC started crashing randomly when I'm gaming or when I close a game, running driver verifier created a dump file that the fault is of mshidkmdf.... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by DumitruCoceban, Jan 11, 2021.

  1. DUMITRUCOCEBAN
    DumitruCoceban Win User

    BSOD caused by mshidkmdf.sys


    So my PC started crashing randomly when I'm gaming or when I close a game, running driver verifier created a dump file that the fault is of mshidkmdf.

    I've tried:

    • chkdsk /f
    • dism /online /cleanup-image /restorehealth
    • SFC /scannow

    Can anyone help me?

    The dump file is 16gb so I can't upload it, but running !analyze -v gives this:

    ******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DRIVER_VERIFIER_IOMANAGER_VIOLATION c9The IO manager has caught a misbehaving driver.Arguments:Arg1: 000000000000022e, The caller has completed a successful IRP_MJ_PNP instead of passing it down.Arg2: fffff80268e6a710, The address in the driver's code where the error was detected.Arg3: ffffe501ad3f0d80, IRP address.Arg4: 0000000000000000Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3749 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-28M5NOJ Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 4164 Key : Analysis.Memory.CommitPeak.Mb Value: 91 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: c9BUGCHECK_P1: 22eBUGCHECK_P2: fffff80268e6a710BUGCHECK_P3: ffffe501ad3f0d80BUGCHECK_P4: 0DRIVER_VERIFIER_IO_VIOLATION_TYPE: 22eIRP_ADDRESS: ffffe501ad3f0d80DEVICE_OBJECT: ffffe501a61984e0DRIVER_OBJECT: ffffe501a2d3fd70IMAGE_NAME: mshidkmdf.sysMODULE_NAME: mshidkmdfFAULTING_MODULE: fffff80d73be0000 mshidkmdfBLACKBOXNTFS: 1 !blackboxntfsPROCESS_NAME: SystemSTACK_TEXT: ffff878f`1c995e08 fffff802`683d7e34 : 00000000`000000c9 00000000`0000022e fffff802`68e6a710 ffffe501`ad3f0d80 : nt!KeBugCheckExffff878f`1c995e10 fffff802`683df323 : 00000000`00000000 00000000`00000000 00000000`0000022e fffff802`687489b0 : nt!VerifierBugCheckIfAppropriate+0xe0ffff878f`1c995e50 fffff802`67fa5e2b : 00000000`0000022e ffffe501`ad3f0d80 ffffe501`ad3f0d80 00000000`00000000 : nt!ViErrorFinishReport+0x117ffff878f`1c995eb0 fffff802`683e9e78 : 00000000`00000000 ffff878f`1c997000 00000000`00000011 00000000`00000000 : nt!ViErrorReport1+0x63ffff878f`1c995f50 fffff802`683dedec : ffffe501`a61bb1c8 00000000`00000001 00000000`00000000 00000000`00000000 : nt!VfPnpVerifyIrpStackUpward+0x158ffff878f`1c995fb0 fffff802`683d76d5 : ffffe501`ad3f0d80 ffff878f`1c9961f0 00000000`00000001 ffffe501`a6065380 : nt!VfMajorVerifyIrpStackUpward+0x74ffff878f`1c996000 fffff802`683cc756 : ffffe501`ad3f0d80 ffff878f`1c991000 ffff878f`00000000 ffff878f`1c991000 : nt!IovpCompleteRequest2+0xe5ffff878f`1c996070 fffff802`67c5285e : ffffe501`ad3f0d80 fffff802`67d36a04 00000000`00000006 ffff878f`1c996159 : nt!IovpLocalCompletionRoutine+0x96ffff878f`1c9960d0 fffff802`683cc16f : ffffe501`ad3f0d80 ffff878f`1c996200 00000000`000000c0 ffffe501`a61bb150 : nt!IopfCompleteRequest+0x11effff878f`1c9961c0 fffff802`67e3557b : 00000000`00000000 00000000`00000000 00000000`00000000 ffff878f`1c996328 : nt!IovCompleteRequest+0x1cfffff878f`1c9962b0 fffff802`68dc0f19 : 00000000`00000001 00000000`00000013 fffff80d`73c17008 ffffe501`ab686ff0 : nt!IofCompleteRequest+0x1e2e6bffff878f`1c9962e0 fffff802`683d0840 : 00000000`00000000 00000000`0000001b ffffe501`a8320fd0 ffffe501`ad3f0d80 : VerifierExt!IofCompleteRequest_wrapper+0x159ffff878f`1c996330 fffff80d`73bd12e8 : ffffe501`ad3f0ee0 ffffe501`ab688d00 00000000`0000001b ffffe501`ab688d00 : nt!VerifierIofCompleteRequest+0x10ffff878f`1c996360 fffff802`68e6a976 : ffffe501`ad3f0d80 ffffe501`ab688d00 ffffe501`a2d3cc50 ffffe501`a2d3cc50 : vmulti+0x12e8ffff878f`1c996390 fffff802`67d773d7 : fffff80d`73c10188 ffffe501`a2c88388 fffff80d`73c10188 ffffe501`ad3f0d80 : Wdf01000!FxDevice:BSOD caused by mshidkmdf.sys :DispatchWithLock+0x266 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447] ffff878f`1c9963f0 fffff802`683cbf1a : ffffe501`ad3f0d80 ffffe501`a2d3cc50 00000000`00000000 00000000`00000000 : nt!IopfCallDriver+0x53ffff878f`1c996430 fffff802`67e38973 : ffffe501`ad3f0d80 00000000`0000001b ffffe501`ad3f0d80 ffffe501`a2c882d0 : nt!IovCallDriver+0x266ffff878f`1c996470 fffff80d`73be61cf : ffffe501`9b733d80 fffff802`683dd932 08000000`00000001 fffff802`c00000bb : nt!IofCallDriver+0x1dba73ffff878f`1c9964b0 fffff80d`73bf3989 : ffffe501`ad3f0d80 ffffe501`a61984e0 00000000`00000001 fffff802`68091650 : mshidkmdf!HidKmdfPnp+0x8fffff878f`1c9964e0 fffff80d`73c1eddd : 00000000`00000013 ffffe501`ad3f0d80 ffffe501`a6198630 ffffe501`ad3f0f70 : HIDCLASS!HidpCallDriver+0xb9ffff878f`1c996550 fffff80d`73c1d831 : ffffe501`a6198630 fffff80d`73c10188 fffff80d`73c17008 ffffe501`ad3f0d80 : HIDCLASS!HidpFdoPnp+0x13dffff878f`1c9965c0 fffff80d`73bf2681 : ffffe501`a6198630 00000000`00000000 00000000`0000001b fffff802`68091650 : HIDCLASS!HidpIrpMajorPnp+0x71ffff878f`1c996600 fffff802`67d773d7 : 00000000`00000000 ffffe501`ad3f0d80 ffffe501`a61984e0 ffffe501`00000001 : HIDCLASS!HidpMajorHandler+0x1b1ffff878f`1c996690 fffff802`683cbf1a : ffffe501`ad3f0d80 ffffe501`a61984e0 ffffe501`ad3f0d80 fffff802`683d86c9 : nt!IopfCallDriver+0x53ffff878f`1c9966d0 fffff802`67e38973 : ffffe501`a61984e0 00000000`00000000 ffffe501`a61984e0 ffffe501`a3ac0650 : nt!IovCallDriver+0x266ffff878f`1c996710 fffff802`68091650 : 00000000`00000000 ffffe501`a61984e0 ffff878f`1c9967f0 ffff878f`1c996908 : nt!IofCallDriver+0x1dba73ffff878f`1c996750 fffff802`68136186 : 00000000`c00000bb ffffe501`9b785020 ffff878f`1c996928 ffffe501`9b733d80 : nt!IopSynchronousCall+0xf8ffff878f`1c9967c0 fffff802`68136064 : 00000000`00000000 ffff878f`1c996928 00000000`00000000 ffff878f`1c996929 : nt!PnpIrpQueryID+0x56ffff878f`1c996850 fffff802`68139e1b : 00000000`00000000 ffff878f`1c996929 00000000`00000001 00000000`00000001 : nt!PnpQueryID+0x34ffff878f`1c9968b0 fffff802`681303c1 : ffffe501`9b785020 ffff878f`00000001 00000000`00000000 00000000`00000000 : nt!PipProcessStartPhase3+0x16fffff878f`1c996990 fffff802`681c739c : ffffe501`a2df7e00 ffff878f`1c996b01 ffff878f`1c996ab0 fffff802`00000000 : nt!PipProcessDevNodeTree+0x2ddffff878f`1c996a60 fffff802`67d7625c : 00000001`00000003 ffffe501`a2df7ed0 00000000`00000000 ffffe501`a2df7ed0 : nt!PiProcessStartSystemDevices+0x60ffff878f`1c996ab0 fffff802`67c2f975 : ffffe501`9f5d0100 ffffe501`9b6d9cb0 fffff802`6864d3e0 ffffe501`00000000 : nt!PnpDeviceActionWorker+0x4ccffff878f`1c996b70 fffff802`67d21e25 : ffffe501`9f5d0100 00000000`00000080 ffffe501`9b6a7080 000f8067`b4bbbdff : nt!ExpWorkerThread+0x105ffff878f`1c996c10 fffff802`67e06dd8 : fffff802`66615180 ffffe501`9f5d0100 fffff802`67d21dd0 b9b9b9b9`b9b9b9b9 : nt!PspSystemThreadStartup+0x55ffff878f`1c996c60 00000000`00000000 : ffff878f`1c997000 ffff878f`1c991000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28STACK_COMMAND: .thread ; .cxr ; kbFAILURE_BUCKET_ID: 0xc9_22e_VRF_IMAGE_mshidkmdf.sysOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {66dafdea-7599-7c2b-4872-d1e6b938a67b}Followup: MachineOwner

    :)
     
    DumitruCoceban, Jan 11, 2021
    #1
  2. HORUS-3-ECHO
    Horus-3-Echo Win User

    QCAMAIN1.SYS CAUSING BSOD

    This was probably caused by the following module:
    qcamain1.sys (Qcamain10x64+0x108678)

    Bugcheck code: 0x1D3 (0x333, 0x0, 0x0, 0x0)

    Error: CUSTOM_ERROR

    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: qcamain1.sys .

    Google query: qcamain1.sys CUSTOM_ERROR

    Using WhoCrashed I found this thread: QCAMAIN1.SYS CAUSING BSOD (Code 37 Error) however without
    solution, locked.

    I did get BSOD almost everytime I moved the laptop.

    This worked for me:

    unscrew wifi module, push a little into the socket. Screw in. DONE
     
    Horus-3-Echo, Jan 11, 2021
    #2
  3. INTERESTINGKID005140
    interestingkid005140 Win User
    wdf01000.sys and ntoskrnl.exe BSOD

    I'm on Windows 10, 64bit

    Basically, whenever I try to update my LPC controller through Device Manager, BSOD with WDF_VIOLATION occurs (culprit being wdf01000.sys)

    So I try to use the driver verifier to see which driver is causing the BSOD, but then it causes BSOD (cultprit being ntoskrnl.exe)

    Have no idea which driver is causing them

    Please help!

    Here are my list of drivers and system info: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
     
    interestingkid005140, Jan 11, 2021
    #3
  4. JOY KEMPRAI
    Joy Kemprai Win User

    BSOD caused by mshidkmdf.sys

    BSOD - driver_irql_not_less_or_equal (l1c63x64.sys)

    Hi Seung,

    Sorry for the inconvenience caused by BSOD - driver_irql_not_less_or_equal (l1c63x64.sys).

    Please let us know the make/model of your computer.

    The L1C63x64.sys is the Atheros LAN driver and I would suggest to uninstall and reinstall the Atheros LAN driver but install the latest Atheros LAN driver by visiting the manufacture's website and avoid using any LAN driver available though Windows Update.

    However the problem could also be with any VPN software and other software so make sure you have the latest version of each of these software.

    If the errors continue uninstall the VPN software and check if the issue persist.

    Hope this helps. Get back to us for further queries for BSOD - driver_irql_not_less_or_equal (l1c63x64.sys). We are happy to help!
     
    Joy Kemprai, Jan 11, 2021
    #4
Thema:

BSOD caused by mshidkmdf.sys

Loading...

  1. BSOD caused by mshidkmdf.sys - Similar Threads - BSOD caused mshidkmdf

  2. BSOD caused by rtwlane601.sys?

    in Windows 10 Gaming
    BSOD caused by rtwlane601.sys?: Hi everyone,I seem to have been experiencing frequent Kernel Mode Heap Corruption BSODs and have already tried a few things but to no avail. Was hoping someone can help. System is relatively new, about 5 months old and wishing it isn't a hardware issue. Started experiencing...

  3. BSOD caused by rtwlane601.sys?

    in Windows 10 Software and Apps
    BSOD caused by rtwlane601.sys?: Hi everyone,I seem to have been experiencing frequent Kernel Mode Heap Corruption BSODs and have already tried a few things but to no avail. Was hoping someone can help. System is relatively new, about 5 months old and wishing it isn't a hardware issue. Started experiencing...

  4. BSOD caused by watchdog.sys and dxgmms2.sys

    in Windows 10 Software and Apps
    BSOD caused by watchdog.sys and dxgmms2.sys: Greetings, fellow Windows users!Yesterday, my computer had its BSOD while I'm using Adobe Premiere which was apparently caused by watchdog.sys and dxgmms2.sys.Here is a link to the dmp file: https://1drv.ms/u/s!AmT-xQXftxFWgiKU88vH7tRulzda?e=33kqdQThanks for any further help...

  5. BSOD caused by dxgmms2.sys and watchdog.sys

    in Windows 10 Software and Apps
    BSOD caused by dxgmms2.sys and watchdog.sys: I've tried reverting graphics drivers, windows updates, updating BIOS, resetting windows and other recommended methods such as chkdsk and DISM. I would like some confirmation on my issue being potentially video card related. Another pair of eyes/insight is the goal of this...

  6. BSOD caused by netwtw10.sys

    in Windows 10 Drivers and Hardware
    BSOD caused by netwtw10.sys: From a couple of days ago my machine has been frequently BSOD and showing the error to be caused by netwtw10.sys. I have attempted to reinstall network drivers, reset machine with content, reset to factory and the issue has persisted through all the changes I made. In...

  7. QCAMAIN1.SYS CAUSING BSOD

    in Windows 10 BSOD Crashes and Debugging
    QCAMAIN1.SYS CAUSING BSOD: This was probably caused by the following module: qcamain1.sys Qcamain10x64+0x108678 Bugcheck code: 0x1D3 0x333, 0x0, 0x0, 0x0 Error: CUSTOM_ERROR A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for...

  8. BSOD caused by Dot4.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD caused by Dot4.sys: I have a BSOD problem caused by Dot4.sys very often but I have no idea what is causing it. SYSTEM_SERVICE_EXCEPTION Dot4.sys+e23f IEEE-1284.4-1999 Driver Windows (R) Win 7 DDK driver Windows (R) Win 7 DDK provider 6.1.7600.16385 built by: WinDDK x64 ntoskrnl.exe+1aab90

  9. BSOD caused by QCamain10x64.sys and IntelHaxm.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD caused by QCamain10x64.sys and IntelHaxm.sys: My laptop crashed with STOP code DEVICE_IRQL_NOT_LESS_OR_EQUAL, stating that QCamain10x64.sys had failed, which according to Google, is the driver of my laptop's wireless adapter. Just to make sure before attempting to reinstall the driver via device manager, I saw this wiki...

  10. Random BSODs caused by cm11264.sys.

    in Windows 10 BSOD Crashes and Debugging
    Random BSODs caused by cm11264.sys.: Hi, i recently started having issues with my computer crashing. I will provide the dump files. I've looked up what cm11264.sys was connected to and it was my pair of Sennheiser 363d. I have since then tried multiple driver versions, and now have switched to a different port....