Zip and share files in C windows minidump. Do memtest and share the result.
Problem with BSOD probably a driver
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
Since about 3-4 weeks I have been getting BSOD's (almost) every time I start up my system. They vary in message but most of them are things like MEMORY_MANAGEMENT or ISQL or some others I can't remember. Using a blue screen viewer I have come to the conclusion that it is always 1 file that the error is coming from:
| Filename | Address In Stack | From Address | To Address | Size | Time Stamp | Time String |
|---|---|---|---|---|---|---|
| ntoskrnl.exe | ntoskrnl.exe+34ccaa | fffff8064ee00000 | fffff8064fe46000 |
0x01046000 | 0x64ebcc57 | 27/08/2023 23:21:11 |
I have ran a diskcheck on my main disk, reinstalled windows, ran memtest86+, updated all my drivers and ran driver verifier.
The last one gave me more of a clue to what was going on. It put me in a bluescreen loop which wasn't a huge deal as I could boot into safe mode and then see what the issue was. The first issue was a virtual bus driver that was apparently automatically installed once I had plugged in my controller, which caused driver verifier to crash. So now I tested the system more with trying to boot up again and I still had the blue screens. So I ran driver verifier again, now leading to the following file (which was also shown on the BSOD itself):
| Filename | Address In Stack | From Address | To Address | Size | Time Stamp | Time String | Product Name | File Description | File Version | Company | Full Path |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ntoskrnl.exe | ntoskrnl.exe+9cde34 | fffff8026ec10000 | fffff8026fc56000 |
0x01046000 | 0x64ebcc57 | 27/08/2023 23:21:11 | ||||||
| Wdf01000.sys | Wdf01000.sys+a710 | fffff802702b0000 | fffff80270381000 |
0x000d1000 | 0xa9a9d36e | 14/03/2060 09:40:14 |
Again ntoskrnl.exe and this time Wdf01000.sys. The problem now is that I cannot find any particular issue or fix related to this file. It is all the general: use a restore point or do this or that. Without actually knowing what the issue is. Is there any way to find out what is causing this (/which driver)?
As a note: I have all my chipset drivers installed from my motherboard manufacturer, and a legitimate copy of Windows 10 Educational.
Windows for home | Windows 10 | Devices and drivers
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
11 answers
Sort by: Most helpful
-
Anonymous
2020-12-10T09:42:22+00:00 -
Anonymous
2020-12-10T14:06:31+00:00 Hey there again Brokko!
First of all, I'll describe the minidump which mainly caught my attention, the one from Driver Verifier. I'll write the basic information here:
- DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
IMAGE_NAME: mshidkmdf.sys
FAILURE_BUCKET_ID: 0xc9_22e_VRF_IMAGE_mshidkmdf.sys
This driver (mshidkmdf.sys) seems to be this: "Pass-through HID to KMDF Filter Driver". It seems to be a Microsoft related driver, so we'll run over a system's files integrity check and some solutions that may help.
Hey there ____!
My name is Miguel Ángel and I'm an independent advisor, also a Microsoft user just like you! Let's try to solve your issue!
I've been checking on the BSODs you've attached, and I'll give you a brief description on each of them below.
SOLUTIONS AND DIAGNOSTICS:
- SYSTEM FILES INTEGRITY CHECK
First of all, make sure all Windows Updates are installed, all drivers are updated and BIOS is updated as well, everything with the latest installation possible.
Then, we will do some system files check, and also check the hard drive, just in case. Follow these steps:
- Press Windows + R. Type 'cmd' and press Enter.
- In the command prompt, run the following commands:
> dism /online /cleanup-image /restorehealth
> sfc /scannow
> chkdsk /f
Third command may ask you to type Y to reset the computer. Just type Y and then press Enter. I'd recommend you to post some feedback if these commands have fixed anything or not.
- CLEAN BOOT
Perform a clean boot following the steps given in https://support.microsoft.com/en-us/topic/how-t... and see if issues continue happening. Report back with some feedback!
I will meanwhile check on the other minidumps to see if I can get further information. Tell me how it goes!
Best of luck, we'll surely fix it so stay calm!
Miguel Ángel :)
-
Anonymous
2020-12-10T11:09:02+00:00 Default the BIOS and save it.
Uninstall Malwarebyte, Asus software.
Follow the DDU guide and install your updated GPU driver.
Except for keyboard and mouse, do not plug in USB.
-
Anonymous
2020-12-10T10:46:19+00:00 Thanks you (and Murat5038) for your response. Here is the link to my C:\Windows\Minidump folder. There are 5 .dmp files in there but the ones of importance are mainly 120920-6937-01.dmp from the driver verifier and the 121020-11546-01.dmp which is a BSOD that lead to me investigating the issue.
Hope this helps. Thanks again
Here is the link: https://1drv.ms/u/s!Avf8zan1UNdBdIMNOMgbo8hE4pg?e=ELL4Mp
-
Anonymous
2020-12-10T10:00:35+00:00 Hey there Brokko!
My name is Miguel Ángel and I'm an independent advisor, also a Microsoft user just like you! I'll try to help you today with this issue.
In order to be able to give a personal and custom solution, I'd need to check on the minidumps, which are files that Windows creates after blue-screening and which can give me more information. You can locate them in C:\Windows\Minidump. Please upload the files there to OneDrive or WeTransfer and share the link with me.
We will go step by step, but I'd like to read over the minidump just in case the culprit is around. If not, we'll run some checks.
I'll wait for your answer. Don't worry at all!
Miguel Ángel :)