New gaming rig. Strange different BSODs while\after playing a specific game

In the crash dump I did not see the xusb22.sys driver. BlueScreenView may mention it, but it is not a thorough program because it does not support symbols. If I had to turn on Driver Verifier for Windows drivers, I would have turned it on for the kernel driver (ntoskrnl.exe) to check if the drivers communicate properly with the kernel (from what I remember, the crash dumps are mainly about the kernel)
 
So, its been a long time. I decided to roll back audio driver back to Microsoft one instead of realtek to see if it helps. Was long time since last BSOD, but today it happened again with same game. This time DRIVER_IRQL_NOT_LESS_OR_EQUAL during playing. I can attach minidump if needed. Full dump is 1.3 gb.
Corrected WHEA-LOGGER errors (cache hierarchy errors) in event log seem to be irrelevant, since I had them from time to time without BSOD and today there were no WHEA-LOGGER event before BSOD (there were nothing of interest in event log before that BSOD at all).
 
You don't have any blue screens with Driver Verifier? In that case, enable Driver Verifier with the settings I recommended for you in the second post, but for verification, apart from third-party drivers, also select the drivers from the system kernel (ntoskrnl.exe and hal.dll)
 
MrPepka said:
You don't have any blue screens with Driver Verifier? In that case, enable Driver Verifier with the settings I recommended for you in the second post, but for verification, apart from third-party drivers, also select the drivers from the system kernel (ntoskrnl.exe and hal.dll)
Click to expand...
No, I had no BSODs with it enabled. I ran it for 3 days (since the lag is not noticeable at all with this PC, I thought to run it longer, but you recommended for around 2 days).
Will enable it again.
 
Ok. I enabled it again with same settings as in post 2 + checked hal.dll and ntoskrnl.exe. Windows startup is now very long + I noticed right after the boot, in event log it logs critical error DriverFramework-UserMode. First error says "There was a problem with one or multiple drivers in user mode and a main process was terminated. This could lead to some devices being unavailable" and second one right after first one says: "Device HID-compliant headset (source (unkonwn)) is disabled because of driver failure in user-mode. Windows will try to restart the device times: 5. Contact with device manufacturer for detailed information about this problem". (translated both as close as I could). Can this be relevant?
 
Do you use any headphones? It turns out that the driver crashed from them. Watch if BSODs are still playing
 
MrPepka said:
Do you use any headphones? It turns out that the driver crashed from them. Watch if BSODs are still playing
Click to expand...
I have both headset (connected via mini-jack in back panel) + usb microphone (it has jack output too, so I can use it instead back panel for headset, but I do not). I think this error is the main reason I always hear "device plugged-in sound" right after boot all the time (I think it crashes then restarts immediately). Device manager shows no errors and this event happens no more after boot.
On side note: there is also always (even before driver verifier and before we started troubleshooting) "CorsairGamingAudioConfig" service stopping error in event log (file could not be found) + at the same time "WinRing0_1_2_0" service stopping with same "file could not be found. With driver verifier they both come 4 seconds after errors described in my previous post.
Fun part: I don't have any Corsair peripherals, only Corsair case which comes with front RGB fans (I believe they are all connected to special corsair "head" "Lightning node" which then connects to SATA port I believe? Not sure.) which are controlled via Corsair iCUE program which runs it services at startup to load saved RGB profile.
I will continue playing to see if I can catch some BSODs and report.

Edit: Also in event manager right before all described above errors, there is always (even without driver verifier) Kernel-PnP error with driver failure "\Driver\WudfRd for device HID\VID_B58E&PID_9E84&MI_03&Col02\7&34221898&0&0001". I could try to check with device manager which device it is, but I don't know how to find it by it's path fast, even which category of devices to check.
 
Last edited:
Ok, this was a fast search. In device manager under HID devices, there is this "HID-compliant headset" with this exact path. I can try to unplug all my usb device (it says it runs via usb), but there is only mic and keyboard connected via usb.
 
Ok, I think maybe we are getting somewhere. I only use my mic (even its enabled and catches sounds all the time) while playing this problematic game to communicate via Discord with my squad mates. During usage in Discord it also shows in tray that mic is being used. Maybe sometimes it crashes second time (not only once after boot) and causes a BSOD? Strange that I only see this error in log only once after boot and never after. I also played R6 before while chatting in Discord with them, but I don't play it anymore for a long time (never there was a BSOD).
 
The last crash dump mentioned something about interrupt issues so it's quite possible that the microphone driver can't handle interrupts
 
MrPepka said:
The last crash dump mentioned something about interrupt issues so it's quite possible that the microphone driver can't handle interrupts
Click to expand...
The problem is, I don't think Yeti has any dedicated drivers that I can install instead of Microsoft one. On their support page it says that it should work out of the box. I can try to change USB port to see if that helps.
 
Check for now whether there are still BSODs while playing.
 
So yesterday when I enabled driver verifier with new settings, I haven't played problematic game, played different one with no problems, there was not even a lag. Today I woke up and tried to launch EFT, after hitting play in launcher and game starting to load up I immediately had driver-verifier BSOD (DRIVER_VERIFIER_DETECTED_VIOLATION), rebooted and double checked - same BSOD at game startup. I went ahead and tried a couple of different games from Steam - R6 - same BSOD on launch, tried PoE - everything good, KCD (kingdom come deliverance, which is pretty heavy on resources) - everything launches without BSOD + couple of older games like Dishonored - everything ok. So 2 games with the problematic one can't right now launch with new driver-verifier settings. I will attach 3 latest minidumps. 2 from launching EFT (first launch + double check) + launching R6.

Edit: I though it maybe something to do with some of them being full screen, some of them borderless windowed - not the case. KCD launches fine in full screen. PoE is borderless, EFT (which crashes) - I believe is borderless and R6 should be fullscreen.
Some of them are singleplayer some of them are multiplayer. Both that crashed are multiplayer only (tho, they crash on initial launch, I don't think they are trying to connect right away before intro cinematic plays), PoE is multiplayer only too - I switched it to full screen and successful logged in into server. KCD is singleplayer and resource heavy game launches perfectly fine in fullscreen. So overall I see no pattern here.
 

Attachments

Last edited:
The BEDaisy.sys driver has failed. It is a driver from BattlEye. On one hand, reinstallation of the driver might help, and on the other hand FAQ BattlEye says that their driver conflicts with Driver Verifier. Alternatively, in Driver Verifier you can disable the BEDaisy.sys driver from testing and keep trying, but you can also test the efficiency of the CPU, GPU and disk even
CPU STRESS testing: Mersenne.org Prime95 and Intel Processor Diagnostic Tool (IPDT)
How to Stress-Test CPUs and PCs (Like We Do)
FurMark Display Card Stress Test
Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test
 
MrPepka said:
The BEDaisy.sys driver has failed. It is a driver from BattlEye. On one hand, reinstallation of the driver might help, and on the other hand FAQ BattlEye says that their driver conflicts with Driver Verifier. Alternatively, in Driver Verifier you can disable the BEDaisy.sys driver from testing and keep trying, but you can also test the efficiency of the CPU, GPU and disk even
CPU STRESS testing: Mersenne.org Prime95 and Intel Processor Diagnostic Tool (IPDT)
How to Stress-Test CPUs and PCs (Like We Do)
FurMark Display Card Stress Test
Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test
Click to expand...
I think that might be it. Only those two games utilize BE as their anti-cheat. I am thinking right now, that I didn't experience BSOD cause of BE in R6 because of shorter play times (more of a session game), where EFT is more like an MMO and I can run it 8 hrs straight. The thing is, if it is really a BE problem, maybe it conflicts with something IDK. Sometimes I can play all day. Was almost like a month since first BSODs in my first post.
Will try to uncheck it in verifier and play.
I have already run IPDT, prime and FurMark earlier - everything was ok (when I suspected it has something to do with being under heavy load). Will double check.
 
Last edited:
Also did a quick google on BE BSODs, people been reporting since early 2019 that it can cause SYSTEM_SERVICE_EXCEPTION (it also runs some services along with driver) and IRQL_NOT_LESS_OR_EQUAL, especially with newer versions of Windows, like insider builds etc (dunno how new is my 1909 build in that case).
 
Version 1909 is the latest official version of Windows 10. This is not a build from Windows Insider. The BattlEye driver timestamp is from 2020 so the latest driver should be compatible with version 1909
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top