Question BSOD Verifier IOManager Violation

Oct 2, 2019
4
0
10
0
I've been getting reoccurring, random BSOD lately. Most of the time the error message is IRQL no less than or equal. I followed some advice and tried to run verifier.exe but I keep getting BSOD on start up saying VERIFIEDR IOMANAGER VIOLATION. This happens regardless of which drivers have been selected for verification in the verifier menu. I suspect it's due to faulty memory since I'd upgraded my ram shortly before I started running into BSODs, but both memtest84 and mdschk.exe had found nothing wrong with my ram. So I'm really confused...
Here are some recent mini memory dump files.
Minidump files
 

gardenman

Admirable
Herald
Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/GkXE.html
File information:100219-7265-01.dmp (Oct 2 2019 - 08:18:52)
Bugcheck:DRIVER_VERIFIER_IOMANAGER_VIOLATION (C9)
Driver warnings:*** WARNING: Unable to verify timestamp for ctxusbm.sys
Probably caused by:ctxusbm.sys (Process: System)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 11 Sec(s)

File information:093019-8109-01.dmp (Sep 29 2019 - 18:20:14)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Driver warnings:*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by:Unknown_Image (Process: https://www.google.com/search?q=)
Uptime:0 Day(s), 0 Hour(s), 01 Min(s), and 25 Sec(s)

File information:093019-7140-01.dmp (Sep 29 2019 - 18:38:09)
Bugcheck:DRIVER_VERIFIER_IOMANAGER_VIOLATION (C9)
Driver warnings:*** WARNING: Unable to verify timestamp for ctxusbm.sys
Probably caused by:ntkrnlmp.exe (Process: System)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 11 Sec(s)

File information:093019-6937-01.dmp (Sep 29 2019 - 18:48:28)
Bugcheck:DRIVER_VERIFIER_IOMANAGER_VIOLATION (C9)
Driver warnings:*** WARNING: Unable to verify timestamp for ctxusbm.sys
Probably caused by:ctxusbm.sys (Process: System)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 10 Sec(s)

File information:093019-6859-01.dmp (Sep 29 2019 - 18:52:10)
Bugcheck:DRIVER_VERIFIER_IOMANAGER_VIOLATION (C9)
Driver warnings:*** WARNING: Unable to verify timestamp for ctxusbm.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 09 Sec(s)
Comment: The overclocking driver "IOCBios2.sys" was found on your system. (Intel Extreme Tuning Utility)

Possible Motherboard page: https://www.gigabyte.com/us/Motherboard/Z390-AORUS-PRO-rev-10#kf
There is a BIOS update available for your system (F10). You are using version F8. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Oct 2, 2019
4
0
10
0
Sep 21 2017ctxusbm.sysCitrix USB Filter Driver https://www.citrix.com
Not sure what this is part of? it is cause of all the errors (although the WHEA is unknown)

why are there AMD tools on a PC with an Nvidia GPU and Intel CPU?
Feb 15 2018AmdTools64.sys

link leads to radeon drivers? https://carrona.org/drivers/driver.php?id=AmdTools64.sys

Wifi card drivers are getting old too.
Citrix is a remote desktop client for university.
I don’t know why I have amdtools though.

Anyway, I’ve reset my PC and everything looks ok so far.
Will update if I run into the same issues again.
 
Thread starter Similar threads Forum Replies Date
L Windows 10 39

ASK THE COMMUNITY

TRENDING THREADS