• "IRQL_NOT_LESS_OR_EQUAL" BSoD, with some other problems.
    12 replies, posted
I tried finding out answers on this problem after this getting this issue twice in one week, but all I could really find were explanations on why it's happening, which could be any number of things such as: -Faulty/corrupted drivers -Faulty/corrupted software -Messed up RAM memory connection Currently, I have a mouse, an external hard drive, and headphones plugged in. The RAM issue doesn't really make sense to me, since I bought this laptop almost exactly a year ago. For drivers, I constantly check whether or not I have the most up to date versions. The other problem I keep getting is that all programs suddenly stop responding at a random point in the day, and trying to open Task Manager or any other program doesn't work. When Task Manager did open, both CPU and Memory Usage were relatively low. Does anyone know how to fix these issues?
I've had this as well, windows 8 right? from what I recall it was a CPU related error? and reinstalling things did not seem to correct it. but anyways, what is the specs? [url]https://www.piriform.com/speccy[/url]
[QUOTE=huntingrifle;45634754]The other problem I keep getting is that all programs suddenly stop responding at a random point in the day, and trying to open Task Manager or any other program doesn't work. When Task Manager did open, both CPU and Memory Usage were relatively low.[/QUOTE] I've had this issue before once or twice, where everything would stop responding and eventually close without me being able to open anything again. I've also encountered the same BSOD once (within the past 3 months) with two different BSODs following. No idea what's causing it though, for me it is likely a corrupted part of windows 8 due to having encountered loss of power quite a few times (abnormal shutdowns)
-snip-
just post the summery
[code]Summary Operating System Windows 8.1 64-bit CPU Intel Core i5 3320M @ 2.60GHz 49 °C Ivy Bridge 22nm Technology RAM 8.00GB Dual-Channel DDR3 @ 798MHz (11-11-11-28) Motherboard ASUSTeK COMPUTER INC. G46VW (SOCKET 0) 51 °C Graphics NS-24L120A13 (1360x768@60Hz) Intel HD Graphics 4000 (ASUStek Computer Inc) 2047MB NVIDIA GeForce GTX 660M (ASUStek Computer Inc) 61 °C Storage 698GB Seagate ST750LM022 HN-M750MBB (SATA) 42 °C 931GB TOSHIBA External USB 3.0 USB Device (USB (SATA)) Optical Drives No optical disk drives detected Audio Realtek High Definition Audio[/code] Fixed
Have you been keeping your Intel HD 4000's driver up to date as well as the GTX 660M's? Also, have you been keeping the Realtek HD Audio driver up to date? I know you said you check for the latest versions, but you didn't specify which drivers. Also, how are you checking? Are you going to the individual driver support sites, or letting Windows Update handle your driver updates? (Note, this is not a setup for insults, it's a genuine question.) Can you grab [URL="http://www.nirsoft.net/utils/blue_screen_view.html"]BlueScreenView[/URL] and see if it specifies any drivers in the IRQL_blahblah errors in the dumps?
I typically use "Driver Booster" to update drivers that are really hard to find. I used that for the audio driver as well. The problem with the Intel GPU is that whenever I try to update it with an installer from Intel or the Update Utility tool they have, it tells me that I chekc Nvidia for updates on my GTX 660m, and apparently doesn't detect my desktop GPU. After running BlueScreenView, it tells me that the driver which caused the BSoD was "ntoskrnl.exe", which is apparently the computer's kernel. Here's the text document when I selected "Save Selected Items" [code]Dump File : 080814-64515-01.dmp Crash Time : 8/8/2014 6:38:11 PM Bug Check String : IRQL_NOT_LESS_OR_EQUAL Bug Check Code : 0x0000000a Parameter 1 : ffffffff`ffffffd0 Parameter 2 : 00000000`00000002 Parameter 3 : 00000000`00000001 Parameter 4 : fffff800`d8ebaf0c Caused By Driver : ntoskrnl.exe Caused By Address : ntoskrnl.exe+153fa0 File Description : NT Kernel & System Product Name : Microsoft® Windows® Operating System Company : Microsoft Corporation File Version : 6.3.9600.17085 (winblue_gdr.140330-1035) Processor : x64 Crash Address : ntoskrnl.exe+153fa0 Stack Address 1 : Stack Address 2 : Stack Address 3 : Computer Name : Full Path : C:\WINDOWS\Minidump\080814-64515-01.dmp Processors Count : 4 Major Version : 15 Minor Version : 9600 Dump File Size : 262,144 Dump File Time : 8/8/2014 6:45:17 PM[/code] [
Driver Booster sounds like some awful malware, you should probably stick to using the manufacturer's website for drivers. You should also try testing for bad ram sticks with [url=http://www.memtest86.com/]Memtest86[/url], and it wouldn't hurt to try reseating the ram sticks and your GPU after wiping their teeth clean. [editline]asdf[/editline] Oh and make sure you're not overclocking, and that your RAM is all the same brand (never mix and match ram, even ones that are the same model but from a different package), and that your RAM's recommended memory timings (Should be printed on them [something like 7-7-7-21], or it should at least have a model number to check for the recommended timings) match the actual settings in your bios.
[URL="http://www.tomshardware.com/answers/id-1775961/experience-driver-booster.html"]The Tom's Hardware forum seems to want to kill Driver Booster with fire,[/URL] and also includes a handy tip for finding the right driver for everything.
Uninstalled Driver Booster and looking up the correct drivers now, hopefully that'll fix it. I'll run memtest as well and report back with what I get.
SOme reason I had this a lot too - happened to be my PC overheating, so i shoved a fan on the side of my computer (as a temporary measure, as im buying a new PC)
A few days after switching my desktop over to a wireless adapter I started getting sudden BSOD errors along with my system slowing to a crawl then crashing. I was pretty thick headed about the situation and thought that the drivers for this tiny little wireless adapter couldnt be what was bringing my rig to its knees. After days of trouble shooting multiple different BSOD's I finally broke down and invested in a PCI wireless network card which promptly cured all errors. Turns out that the office max/staples brand adapter's drivers only ever made it into beta for my OS. Long story short I had BSOD errors and system freezing from shitty drivers, sounds like that may be the case here as well.
Sorry, you need to Log In to post a reply to this thread.