[SOLVED] Windows crashes with CRITICAL_STRUCTURE_CORRUPTION (0x109) and DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xD1). FIX: I removed and reinstalled the network driver

[jk1993]

• A brief description of your problem (but you can also include the steps you tried)
  • I've been experiencing random BSODs/crashes for a while now. I believe it started when I updated my Windows 10 version to 20H2 (on the ‎11/‎12/‎2020) from 1904, but I could be wrong. In my head, the system was stable prior to this.
  • I've seen 2 different error codes in the BSODs: CRITICAL_STRUCTURE_CORRUPTION, and DRIVER_IRQL_NOT_LESS_OR_EQUAL
  • The PC will also crash with no blue screen - just restarts on it's own
  • I've tried updating graphics drivers, chipset drivers, SSD firmware, and network drivers, uninstalling unnecessary programs
  • Ran Prime95, system crashes but with no BSOD after approx. 1 hour
  • Ran driver verifier - originally crashed, but after updating some drivers and uninstalling some programs, I can boot the computer with driver verifier enabled
  • Latest crash had this entry in event viewer:
    • The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109 (0xa3a025dd2dd8d565, 0xb3b73263805b7651, 0xffffe684a40deae0, 0x000000000000001c). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 7602cd80-ef83-49cb-8aca-06b3a8ad3c5a.
    • Saw that 0x1C in param 4 for 0x109 indicates "Driver object corruption" according to Bug Check 0x109 CRITICAL_STRUCTURE_CORRUPTION - Windows drivers
• System Manufacturer? Custom
• Laptop or Desktop? Desktop
• Exact model number (if laptop, check label on bottom) N/A
• OS ? (Windows 10, 8.1, 8, 7, Vista) Windows 10
• x86 (32bit) or x64 (64bit)? x64
• (Only for xp, vista, 7) Service pack? N/A
• What was original installed OS on system? Windows 10
• Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Full Retail Version
• Age of system? (hardware) Built 09/2019
• Age of OS installation? Installed 09/2019
• Have you re-installed the OS? No
• CPU AMD Ryzen 9 3900X
• RAM (brand, EXACT model, what slots are you using?) G.Skill Trident Z Neo F4-3200C16D-32GTZN 32GB (2x16GB) DDR4 in slots 2 and 4
• Video Card Sapphire Radeon RX 5700 XT
• MotherBoard - (if NOT a laptop) Gigabyte X570 Aorus Pro WiFi Motherboard
• Power Supply - brand & wattage (if laptop, skip this one) Seasonic Prime Ultra Titanium 850W Power Supply
• Is driver verifier enabled or disabled? disabled
• What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth) Default Windows Defender
• Are you using proxy, vpn, ipfilters or similar software? No, had NordVPN installed but have uninstalled it
• Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software) No
• Are you currently under/overclocking? Are there overclocking software installed on your system? Not overclocking, overclocking software was installed but haven't run it

At this point, I believe that it's a driver that's causing the problem, but I'm not sure how to identify the culprit. I've already tried updating the drivers that I can think of, and I'm still getting the same error. Any help would be very appreciated :)

Speccy snapshot: http://speccy.piriform.com/results/hyArq8LTDVuigsL3XpURoQQ

Following the instructions for the SysnativeFileCollectionApp, the output zip is still over 8mb, so I've uploaded it to my Google drive instead here: SysnativeFileCollectionApp.zip Please let me know if there's something else I should do.

 

[philc43]

Hello jk1993 and welcome to Sysnative!

I have had a look through all 27 crash dumps and spotted that at one point you had run Driver Verifier which identified the SteamStreamingMicrophone.sys driver as at fault and it looks as if this was removed.

For the remaining crashes many look as if they might be associated with a driver for the wireless network part of the system since the Microsoft tcpip.sys was often working at the time of the crash.

I can see that you have already tried updating the Intel wireless driver and you actually have two drivers installed. I would remove both and then reinstall just the one which is provided on the motherboard website.

There is also a Motherboard BIOS update which you would be as well to update to.

Summary of crashes - most recent first:

BugCheck 109, {a3a025dd2dd8d565, b3b73263805b7651, ffffe684a40deae0, 1c}
Probably caused by: Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a3a01e6737a06845, b3b72aed8a21e315, fffff8072c600000, 2c}
Probably caused by: Ntfs.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck D1, {ffffdb0e8dabdff8, 2, 1, ffffb80a0541da64}
Probably caused by: ntkrnlmp.exe ( nt!KiPageFault+469 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a3a00d678518d4f0, b3b719edd79b95c8, fffff80261fffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39fd3dd633f4516, b3b6e063b5c11126, fffff80086bffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C4, {2000, fffff80be15c8506, 0, 72436350}
Probably caused by: SteamStreamingMicrophone.sys ( SteamStreamingMicrophone+8506 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39fd9dc9d00678e, b3b6e662ef832866, fffff8022cdffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39fe7da8e5f4853, b3b6f460e0e11463, fffff80019fffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39ff0dad7df45fb, b3b6fd612a60c1eb, fffff8024e80fa94, 1}
Probably caused by: Ntfs.sys ( Ntfs!NtfsVerifyAndFixFileRecord+0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39fc4627178d5cd, b3b6d0e8c3fb96a5, fffff80463fffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a3a018dc48ff457a, b3b725629b81118a, fffff802509ffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39fd9daab7f456c, b3b6e660fe01117c, fffff80387fffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39fe3d9bd5f4961, b3b6f0600fe11571, fffff80614fffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39ff85be8c06574, b3b704e23b43264c, fffff802251ffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39fd958c7b8c8b0, b3b6e5df1a3a94c0, fffff8002b9ffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39ff1e3aaaf161b, b3b6fe69fd30e22b, fffff8072e3ffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39fdae23fcf16d1, b3b6e7689250e2e1, fffff8070d3ffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39fdad9f5d8c663, b3b6e760485a9273, fffff80467fffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39ff35b81d02690, b3b6ffe1d452e768, fffff801503ffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!TcpIoControlEndpoint+6b869 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39fd86662d8d932, b3b6e4ecb55b9a0a, fffff80745fffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39fe7ddd848d58b, b3b6f4642acaa19b, fffff805605ffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck D1, {fffff18b10831ff8, 2, 1, ffff978268f1d688}
Probably caused by: ntkrnlmp.exe ( nt!KiPageFault+469 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a3a01bdc8e78d7d2, b3b72862e0faa3e2, fffff803405ffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39fc0e35a3f4b03, b3b6cd69acc11713, fffff8055bfffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39fd4e3e498da2e, b3b6e16a371aa63e, fffff80134dffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 109, {a39fca5fcb2f16ea, b3b6d6e61db0e2fa, fffff807571ffc9a, 1}
Probably caused by: tcpip.sys ( tcpip!AleInspectBindRequest+6b45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck D1, {1ec00, 2, 1, fffff80219510016}
Probably caused by: memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

[jk1993]

Hi philc43, thanks so much for going through those and getting back to me! I really appreciate it.

You mentioned that I should remove both Intel wireless drivers, and only install one. Is there a specific way to go about removing both? I tried going to Device Manager and uninstalling the "Intel(R) Wi-Fi 6 AX200 160MHz" and "Intel(R) l211 Gigabit Network Connection" devices, and then installing the wifi and LAN drivers from the motherboard website, but I'm not sure if that would have uninstalled both. Is there a way for me to verify that I only have one installed now? I also noticed that upon restarting my computer, Windows Update auto-installed a driver update called "Intel - Net - 12.18.11.1". Should I be disabling driver updates from Windows Update?

I just updated the motherboard BIOS to the latest version as well, so I'll see how it's going for a little bit.

Again, thanks for your help with this :)

 

[philc43]

You are doing the driver updates correctly but well spotted that Windows is automatically updating the drivers again. It would be as well to turn the WU driver updates off while you are trying to get the system stable.

 

[jk1993]

Hello, posting a quick update. Since uninstalling and reinstalling the network drivers, as well as updating the BIOS, I haven't experienced any crashes I'm cautiously optimistic that my issue has been resolved. Thank you so much for your help! I'd been spending over a month dealing with the issue and trying to fix it on my own with no success. I really appreciate you taking the time to help me out :)