Question BSOD (again) usually IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe

Page 3 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

jj360live

Commendable
Jun 20, 2017
51
0
1,530
Hey

I know this is probably going to find itself lost in a wave of people posting similar threads. Trust me- i have not been lazy, i have read all of these threads and still found no solution. I've also posted threads on here regarding the same issue but still the problem has persisted on and off for the best part of a year.

I will get a BSOD on average 1 x a day, however sometimes i wont see it for 3 days, a week, who knows at this point, and sometimes i will get 2 or 3 in a day. As someone who uses his PC for gaming and work, both of my uses are extremely impacted by this.

I will attached below a minidump of my most recent one, along with some screenshots that might help (?). For reference heres a list of the things i have tried to fix the problem:
Checked RAM with memtest
Done windows Diagnostic
Downloaded "BlueScreenView" to look further into it
Updated all my drivers- the ones windows said needed updating and i downloaded a third party software to find any outdated drivers
Updated my BIOS to most recent (still maybe 4 years old but was the closest)
Performed a full system reset to factory

I took my PC to a repair shop once and they didnt find an issue, which has made me speculate that it might be to do with one of my peripherals or maybe a faulty USB driver. I use a:
Razer Blackwidow Keyboard
Logitech G502 Mouse (had issues before i had this mouse)
Blue Yeti Blackout Microphone
DT 990 Pro Headphones

I really hope someone can help me because i honestly dont know what else to do. I am looking to upgrade my PC as most parts of it are old now. If there was a part that was likely to be the issue i would consider just swapping it out for an upgrade in the summer.

The Below DB link has a minidump and a few screengrabs, hope someone out there has the solution.
https://www.dropbox.com/sh/l306hkai4lkd9dm/AAC0kJ6bJLHlYBKjow6w4BHOa?dl=0

Thanks in advance
Jack


https://www.dropbox.com/sh/l306hkai4lkd9dm/AAC0kJ6bJLHlYBKjow6w4BHOa?dl=0
 
Another quick note before you all look at that- i used this program BlueScreenView and it is saying the driver that gave that code is LGBusEnum.sys which looking online seems to relate to Logitech drivers, specifically i saw posts to do with a G502 mouse, this is the mouse i have. Im not sure if this is a false positive, but i was getting the BSODs before i got this new mouse, and i was using a Razer one before. Could it be something to do with the USB port i have this mouse plugged into or is that a push?

Sorry for the overload of messages i just thought its best to give you every detail possible at this point, i crashed again last night this time it blamed USBXHCI.sys

I keep seeing people with problems tied to the USB eXtensible Host Controller. but not all the same makes, some are intel, some aren't. I have also seen that Logitech driver mentioned. The drivers for usbxhci are built into windows itself.

I would follow CIn's instructions, I don't want to get in his way :)
 
Thanks for the replies.

I am trying to work with the idea of stripping down to the minimum hardware, however a lot of the time i actually need to be using a few things at once for work (mic keyboard mouse) so thats presenting a bit of an issue. On top of that the infrequency of the BSOD is very frustrating when trying to work out which is the bad hardware because for instance i didnt get a crash today which might leave me thinking the problem is fixed but i could get 3 tomorrow for all i know.

I might look to get a temp keyboard because if that doesnt fix it then i can almost guarantee its the Mic.

On the point of me not getting a BSOD today, i actually looked into the Logitech driver and found it was something to do with a Logitech Game Panel Emulator (or something similar) although i wasnt sure this was the exact issue i found a fix to update it as a lot of people clearly have an issue with it. On top of this i noticed a Logitech keyboard driver which i just removed as im using Razer.

So im...hoping...touch wood... maybe i didnt get a BSOD today because this driver was the issue all along (??) its a stab in the dark but if im wrong then hey its just another option ive narrowed down :)

Thanks for all the continued help, Colif in terms of what youre saying about the USB Controller problems is this something that has a solution if my problem turns out not to be hardware related?
 
I would follow CIn's instructions, I don't want to get in his way :)
Don't worry about it, we all try to help. If someone has any good idea, just go ahead.

@op try to use the minimum hardware first, and recommend to clean up your PC with CCleaner too. https://www.ccleaner.com/

Also try use only one or two sticks RAM, because you did test the RAM with MemTest86, but only few runs, so maybe one of them does have problem. If you still get the same memory error, try other RAM.

And do you update the intel chipset driver? because it will come with the memory controller driver too. https://www.msi.com/Motherboard/support/Z97-G43#down-driver&Win10 64
 
Logitech gamepanel - older Logitech keyboards had a LCD screen on them that could be used to show various details about game or PC. Newer ones don't have this but may have an app that does the same thing. My G910 has a Dock I could put my phone on, if I chose to.

So its possible the Logitech GamePanel Virtual Bus Enumerator Driver collected info from system for the screen. I would remove it if you can.
 
Hey guys, hadnt had a problem for a couple of days so was feeling hopeful but it crashed this morning. The crashes now all seem to be pointing to Driver_irql_not_less_or_equal and USBXHCI.SYS , whereas before i would get different codes.

Ive tried stripping my pc down to the minimum that i can deal with and made sure everything i did have was in a USB 2.0. But still no luck. Today ive unplugged my mic too so will see if i get any crashes with that out, although i will have to plug it in later to teach with.

I believe i got rid of everything to do with that Logitech Driver, although i was only deleting things from driver files not from like registry editor. I've also been using CCCleaner for a while now- what would you suggest i do on it in particular?

Im going to attach some photos as well as the DMP file, see if anything in the photos springs up to you as maybe being something to look into.

https://www.dropbox.com/s/7g81i12afq86siv/052319-6078-01.dmp?dl=0 (<--- DMP)

https://www.dropbox.com/s/hpo494nci5m52ty/Drivers.jpg?dl=0 (<--- Photo 1)
https://www.dropbox.com/s/a9rhcavy46e4zor/Logs.jpg?dl=0 (<--- Photo 2)
 
I ran the new dump file through the debugger and got the following information: https://pste.eu/p/tJxs.html

File information:052319-6078-01.dmp (May 23 2019 - 03:31:55)
Bugcheck:DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 20 Hour(s), 04 Min(s), and 08 Sec(s)

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.
 
Somehow you managed to gain Intel Extreme Overclocking utility that wasn't there a few days ago

use autoruns and stop both of these
Feb 26 2015 XtuAcpiDriver.sys !!! Intel Extreme Tuning BIOS Interface driver https://downloadcenter.intel.com/
Jun 09 2015 lgcoretemp.sys CPU Core Temperature Monitor http://support.logitech.com/

if that doesn't help, try stopping razer as well
Oct 26 2016 rzendpt.sys Razer RzEndPt driver https://www.razer.com/
Oct 26 2016 rzudd.sys Razer Rzudd Engine Driver https://www.razer.com/

if its the USB being set off, it might be the keyboard or mouse itself causing it

it didn't help that driver verifier didn't do anything other than crash windows as usual

it could always be the nvidia drivers as well since they include
Aug 16 2018 nvvhci.sys Nvidia Virtual USB Host Controller driver

I wonder what thats used for? virtual reality headsets maybe??
 
Hey Colif- Sorry i must have missed your post! Interesting that those drivers have somehow come back on... i will make sure to get rid of them!! I thought for sure it was my microphone, so i got in touch and they gave me a replacement. I then didnt get a crash for all of 4 days. So i thought i mustve solved it. Until tonight, the dreaded BSOD KMode came back, and this time weirdly the audio kept looping whilst the crash was writing the DMP.

I'll attach the DMP file, but it sounds like you might have found what the problem is. Question: When i use Autoruns to disable those drivers, will they stay disabled forever or do i have to do it everytime i turn my PC on? Is there any definitive way to just get rid of these pesky drivers?

https://www.dropbox.com/s/2rph6nfv1lrxrq2/052719-8156-01.dmp?dl=0
 
Auto runs just stops them loading at every startup, if an application uses the files it can restart them. You don't need to do it again once its set..

looping sound is common if its a driver error. It may be first time you heard it but its not unusual.

we should be able to figure out how to remove them IF it is proved they are the cause. Best way to see IF is to stop them and then if you stop getting BSOD, we could assume.

Gardenman may read those, he was ill last week but I have seen him about.
 
Ok thank you very much, sorry for taking up so much of your time with this i really appreciate the help. I stopped all 5 of the mentioned on Autoruns. Looking at some of the others theres one called "USBHUB3" description is "SuperSpeedHub USB3 HUB Driver" I know its probably nothing but just it saying SuperSpeed makes me think its something overclocking related.

i might try getting rid of any programs i can find that could be launching these drivers. thanks again.
 
I don't think you can overclock USB anyway. Short search finds other Superspeed USB hubs. Its likely just a sales term. I wouldn't stop USB drivers unless you don't want the ports to work.

Don't worry about the time, its your problem. I wish we could fix it faster for you :)
 
I ran the dump file through the debugger and got the following information: https://pste.eu/p/nBn1.html

File information:052719-8156-01.dmp (May 27 2019 - 17:10:26)
Bugcheck:KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:memory_corruption (Process: chrome.exe)
Uptime:1 Day(s), 9 Hour(s), 04 Min(s), and 38 Sec(s)

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.
 
Hey Colif, because of the issue i had with the drivers, when i went to get a new Blue mic they sent me a Pro one, its the only one where its not plug and play and you have to DL the drivers through the site. I dont think these are likely to be the issue as obviously i was having problems before i got the mic, however i went through the link you sent and am downloading them again just to make sure.

I figure it probably is this XTU driver that keeps coming back, as i had removed it and didnt get a crash for a few days, then suddenly when i get a crash it is back. I had an NVIDIA update today and it brought back the Nvvhci driver so i got rid of it again.

Is there any way i can work out what program is bringing back the XTU driver? I obviously have it stopped on Autorun which then allowed me to delete the driver but im worried it will just come back when i open something random
 
fair call about microphones.

If you have deleted the driver, it can't come back?

The XTU driver is part of Intel Extreme Tuning Utility which is on your motherboards website - https://www.msi.com/Motherboard/support/Z97-G43#down-driver&Win10 64 - So that would be 1st thing I would look for. What Intel programs show up on settings/apps/apps & Features?

Here are a few suggestions: https://www.tenforums.com/drivers-h...tely-remove-intel-extreme-tuning-utility.html

There is also this: https://www.tenforums.com/tutorials/4499-start-stop-disable-services-windows-10-a.html#post954645 but if you go anywhere near the registry, back it up first - https://www.thewindowsclub.com/backup-and-restore-registry-windows
 
Ok now im just really confused...i crashed again- KMODE again, this time is specifically blamed the new Blue Yeti Drivers, when i used this BlueScreenView programme it looks to be blaming BlueYetiPro_64.sys, NETIO.sys and ntoskrnl.exe but i will link the DMP for someone more experienced than me to have a look at..

https://www.dropbox.com/s/53nub7gezsafagz/052819-6187-01.dmp?dl=0

Nothing comes up in my Apps to do with intel, i just had a check. Its weird because i didnt have my Mic plugged in for a few days, and wasnt seeing any crashes, so then i got this new mic, with new drivers and it starts to crash again. I thought it was just a coincidence but now im starting to think my PC has a problem with Blue Yeti products... is this actually a possibility or do you think it would be the same with any microphone?

Again this time when it crashed i had that looping audio- i know you said this is common but seems interesting to me that the only 2 times i heard it was the times with my new mic/new drivers.

Thanks again
 
netio.sys is the network i/o drivers for windows 10, so odd to see it mentioned

You can run this to try to fix netio/sys Kmode exception error
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

Another test is run chkdsk on the hdd - see here under step 2 - https://www.thewindowsclub.com/fix-netio-sys-bsod-error
normally only drivers that cause those are Network adapters, your Intel drivers are fairly new (December)

I almost suggested you run memtest again as you keep getting errors in random things, and that can point to ram problems.

Need to wait for gardenman to read dumps now
 
Ok i took those steps you suggested, didnt seem to pick up on any errors but maybe it repaired something and i missed it.

I've attached an image of the event viewer that shows a couple of Blue Yeti driver errors before and after the BSOD.

https://www.dropbox.com/s/a7vh3cy3r6fjz3a/BY.jpg?dl=0

It's just so annoying to me that i need a high quality microphone for work and I feel like its looking more and more likely that my PC is having issues with the microphones. Do you think a different brand with different drivers could solve this or is it likely i have like generic drivers clashing with the Blue Yeti ones?
 
That is USB related

The USB_ENDPOINT_DESCRIPTOR structure is used by USB client drivers to retrieve a USB-defined endpoint descriptor. The members of this structure are described in the Universal Serial Bus 3.1 Specification available at USB Document Library. See section 9.6.6.

The bInterval value contains the polling interval for interrupt and isochronous endpoints. For other types of endpoint, this value should be ignored. This value reflects the device's configuration in firmware. Drivers cannot change it.

The polling interval, together with the speed of the device and the type of host controller, determine the frequency with which the driver should initiate an interrupt or an isochronous transfer. The value in bInterval does not represent a fixed amount of time. It is a relative value, and the actual polling frequency will also depend on whether the device and the USB host controller operate at low, full or high speed.

To be honest, I have very little experience with this sort of thing. Bold text seems to suggest its a hardware setting. what i suggest is asking on here as well - read their instruction sticky as it shows what they need in a post. They might find an answer I can't see. You should link to this thread so as to avoid doubling up on things.

Sure feels like USB is out to get you

I will get gardenman to do latest dumps as well.
 
Hey!

Thanks for the advice- I set up an account and made a thread on that site- someone immediately said to get the new intel Rapid storage drivers as that has been a common problem lately, so i will do that now.

Whilst going through all this i got another crash, this time saying Kernel Security Check Failure and saying it was from ntoskrnl.exe

Sorry to be giving you and gardenman so much work but ive linked it if it helps

https://www.dropbox.com/s/2rmmnlypgnwcjmh/052819-6000-01.dmp?dl=0
 
It's no problem for me, I enjoy helping (when I can). I ran the dump files through the debugger and got the following information: https://pste.eu/p/z5WS.html

File information:052819-6187-01.dmp (May 28 2019 - 09:20:18)
Bugcheck:KMODE_EXCEPTION_NOT_HANDLED (1E)
Driver warnings:*** WARNING: Unable to verify timestamp for blueyetipro_x64.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 12 Hour(s), 05 Min(s), and 12 Sec(s)

File information:052819-6000-01.dmp (May 28 2019 - 12:32:06)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:memory_corruption (Process: chrome.exe)
Uptime:0 Day(s), 2 Hour(s), 27 Min(s), and 53 Sec(s)

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.
 
Also why did you still use 4 sticks RAM? Because other member run your dump file every time that showed the memory error. Even you did run the memory test already, which shows the test is fine, but the test is only few passes, it maybe not detect the error until more passes, so you should try different stick.
 
Hey all,

Feels like a while since i've had any problems so i was actually preparing to come back to let you guys know, however unfortunately tonight i crashed. I'll be posting a similar message over on the other forum too but just wanted to keep you guys posted. After cin19 pointed out about the RAM sticks, i took 2 out and have only been running 2x 4GB RAM (8GB) for the past week or so. No problems at all until tonight and i was starting to think maybe one of the two sticks i took out was in fact the faulty one, howeevr today i got a crash saying SYSTEM SERVICE EXCEPTION. I've attached a link to the DMP, is it interesting to you that when only running 8GB of RAM it took far longer to crash or is this just a stroke of luck?

https://www.dropbox.com/s/mgcmhasw3rqcir6/060619-8671-01.dmp?dl=0

Thanks again
Jack