• driver irql_less_or_not_equal crash
    20 replies, posted
Happened 2 times so far, while playing Dark Souls 3. I have no idea how to read the .dmp to find the issue, can someone please help me diagnose what's going on?
95% of the time, this BSOD error code is caused by a bad device driver that's doing something wrong and triggering a full crash. Grab [URL="http://www.nirsoft.net/utils/blue_screen_view.html"]BlueScreenView[/URL] and use it to get the filename (e.g. ntfs.sys, ntoskrnl.exe, whatever) that triggered the crash. It might help us identify what driver is the problem. Having the full crash info (the stop code parameters) might yield some useful info. Usually it's video drivers when a game causes it, but that's not always the case.
Sounds like a driver causing a BSOD. Can you post pictures of the memory dumps? Good program for this would be BlueScreenView ([url]http://www.bleepingcomputer.com/download/bluescreenview/[/url]) The dumps can tell us exactly what driver is causing this. [editline]18th May 2016[/editline] [QUOTE=elixwhitetail;50344699]95% of the time, this BSOD error code is caused by a bad device driver that's doing something wrong and triggering a full crash. Grab [URL="http://www.nirsoft.net/utils/blue_screen_view.html"]BlueScreenView[/URL] and use it to get the filename (e.g. ntfs.sys, ntoskrnl.exe, whatever) that triggered the crash. It might help us identify what driver is the problem. Usually it's video drivers when a game causes it, but that's not always the case.[/QUOTE] Beat me to the punch.
[img]https://i.gyazo.com/ece5086fe8b7b2c22203ddf3e49e8e38.png[/img] [img]https://i.gyazo.com/b7aec50533e11dc789d6a25ef5b1d545.png[/img] These are the recent 2, within 10 minutes of each other.
[QUOTE=Daemon White;50344733][img]https://i.gyazo.com/ece5086fe8b7b2c22203ddf3e49e8e38.png[/img] [img]https://i.gyazo.com/b7aec50533e11dc789d6a25ef5b1d545.png[/img] These are the recent 2, within 10 minutes of each other.[/QUOTE] Sort them by datestamp, because those crashes are from April 23rd. Unless you've had the problem since then and haven't asked about it until now, those probably aren't relevant. ...make sure your system clock isn't wildly fucked, too. That might have something to do with it.
[QUOTE=Daemon White;50344733][img]https://i.gyazo.com/ece5086fe8b7b2c22203ddf3e49e8e38.png[/img] [img]https://i.gyazo.com/b7aec50533e11dc789d6a25ef5b1d545.png[/img] These are the recent 2, within 10 minutes of each other.[/QUOTE] None of those are recent. It must have made a memory.dmp (the big blue screen log) This program should let you view that one: [url]http://www.thewindowsclub.com/analyze-windows-memory-dump-files[/url] [editline]18th May 2016[/editline] [QUOTE=elixwhitetail;50344754]Sort them by datestamp, because those crashes are from April 23rd. Unless you've had the problem since then and haven't asked about it until now, those probably aren't relevant. ...make sure your system clock isn't wildly fucked, too. That might have something to do with it.[/QUOTE] This is just going to be a thing now isn't it? lol
[QUOTE=elixwhitetail;50344754]Sort them by datestamp, because those crashes are from April 23rd. Unless you've had the problem since then and haven't asked about it until now, those probably aren't relevant. ...make sure your system clock isn't wildly fucked, too. That might have something to do with it.[/QUOTE] [img]https://i.gyazo.com/c0d01699c7c4195335e768e7e325f388.png[/img] I probably grabbed the wrong data. Is this more correct? edit: updated with column names
[QUOTE=ghostofme;50344755]This is just going to be a thing now isn't it? lol[/QUOTE] Maybe, but I'm usually the one getting ninja'd so this is all fine by me :v: [editline]18th May 2016[/editline] [QUOTE=Daemon White;50344768][img]https://i.gyazo.com/c0d01699c7c4195335e768e7e325f388.png[/img] I probably grabbed the wrong data. Is this more correct?[/QUOTE] ayyy, better. Okay, so the first thing I'd look at is if there's a newer version of your sound driver, because that's what cmudaxp.sys seems to be related to. USBPORT.SYS is something with your USB hubs. Unplug any unnecessary USB devices like controllers. It's unlikely that the USB hub devices themselves need driver updates, but there might be a device on USB that misbehaves in just the wrong way at the wrong time.
[QUOTE=elixwhitetail;50344770]Maybe, but I'm usually the one getting ninja'd so this is all fine by me :v: [editline]18th May 2016[/editline] ayyy, better. Okay, so the first thing I'd look at is if there's a newer version of your sound driver, because that's what cmudaxp.sys seems to be related to. USBPORT.SYS is something with your USB hubs. Unplug any unnecessary USB devices like controllers. It's unlikely that the USB hub devices themselves need driver updates, but there might be a device on USB that misbehaves in just the wrong way at the wrong time.[/QUOTE] If it's USB, I get a feeling it's my controller dying (Dualshock 3)... which isn't so bad because I'll have a new xbox controller soon. If it's the sound card, then shit... It's old as well, but was doing solid for [I]over 7 years[/I] [editline]thanks[/editline] Thanks for the help, I'll test some shit then let you know which it is.
The sound card itself isn't necessarily damaged or failing. But there might be an updated sound driver. Or, there might not be because [IMG]https://facepunch.com/fp/browser/windows10.png[/IMG] but I'd go look at least. Also go into Device Manager (is it still there in Win10?) and look for any yellow or red triangles over devices in the list. If everything is just a normal list and everything's collapsed and fine with no yellow or red triangle icons, we can probably skip that avenue for now.
Unless it really is a super nice sound card you can probably do without it. Assuming you have a stand-alone sound card. [editline]18th May 2016[/editline] [QUOTE=elixwhitetail;50344829]The sound card itself isn't necessarily damaged or failing. But there might be an updated sound driver. Or, there might not be because [IMG]https://facepunch.com/fp/browser/windows10.png[/IMG] but I'd go look at least. Also go into Device Manager (is it still there in Win10?) and look for any yellow or red triangles over devices in the list. If everything is just a normal list and everything's collapsed and fine with no yellow or red triangle icons, we can probably skip that avenue for now.[/QUOTE] Yeah, Device Manager still exists in Windows 10. It's more comparable to Windows 7 then 8 IMO, so if you're familiar with 7 you probably know your way around 10.
It's fixed. Been playing for the past few hours. I reinstalled / updated the sound card driver, and also cleaned the shit out of the computer. There might have been a driver issue or the card itself might have been loose on the connections, but it's fine now guys. Thanks a bunch! [editline]18th May 2016[/editline] Update, it took a while, but crashed again. :/ Took the card out completely now, using the motherboard sound now.
I had a wireless network card driver throw BSOD's before. I would suggest unplugging yours or reinstall the driver if you are using a wireless card.
It's the card, 100% sure now. Been playing since a day ago without issues after taking the card out. RIP Asus Xonar DG, you were a good sound card. (200?-2016)
Don't throw the card away yet, I had the same crash message and managed to get rid of it for a while until it returned.
[QUOTE=zenthekiller;50358777]Don't throw the card away yet, I had the same crash message and managed to get rid of it for a while until it returned.[/QUOTE] Same, this wasn't the first time it happened, and I dont really want to deal with it again. The card was only ~$20 when my parents originally bought it (I took it after that old computer died, and the new one didn't have the proper slot for it).
Which drivers are you using for your card?
[QUOTE=waxrock;50360838]Which drivers are you using for your card?[/QUOTE] Tried UNi drivers and official ones. UNi ones worked great for the most part, and the official ones were the redownload I tried for a fix and it worked for a while, but eventually crashed again.
Sorry, you need to Log In to post a reply to this thread.