IRQL_NOT_LESS_OR_EQUAL and other BSOD on Windows 8.1

m7

Reputable
Dec 17, 2014
12
0
4,510
My notebook has been crashing with the error "IRQL_NOT_LESS_OR_EQUAL" last night. I have no idea what that means.
and other different BSOD for the last 3 months. 1 at least in 24hours

i'v tried lot and lot of different way to solve these bsod problem, like updating and rolling back drivers. installing new windows, installing/blocking updates.

here i upload last 3 dmp files https://drive.google.com/file/d/0ByuA9e9YRlVZeU12REpSSDBOMGs/view?usp=sharing

and this is my laptop specs

Processor Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
Ram 16gb DDR3
Graphics 2gb Intel HD Graphics 4000
1TB Hard Drive

Please help. Any answer is welcome.
 
Solution
here is a better link for the realtek network drivers:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=4&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true

third bugcheck was also in the sleep functions of the realtek driver. It is most likely going to be a BIOS bug in your notebook. Check for a BIOS update or you may want to go to windows control panel, device manager, find the realtek network driver and disable its low power management functions (tell it not to sleep) if you can not get a BIOS update or a driver update that helps
-----------
Second bugcheck was in the sleep circuit for the realtek network device
So update the driver and update the BIOS. I would check with the device maker for the...
here is a better link for the realtek network drivers:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=4&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true

third bugcheck was also in the sleep functions of the realtek driver. It is most likely going to be a BIOS bug in your notebook. Check for a BIOS update or you may want to go to windows control panel, device manager, find the realtek network driver and disable its low power management functions (tell it not to sleep) if you can not get a BIOS update or a driver update that helps
-----------
Second bugcheck was in the sleep circuit for the realtek network device
So update the driver and update the BIOS. I would check with the device maker for the updates first or look on realteks website:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=4&Level=5&Conn=4&DownTypeID=3&GetDown=false
(sorry, not sure which device you actually have)


machine info:
BIOS Version 4.6.5
BIOS Release Date 10/03/2013
Manufacturer CLEVO CO.
Product Name W55xEU
Product W55xEU
Version D02
Chassis Type Notebook
Processor Version Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
Processor Voltage ffh - 12.7V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 2200MHz





-----------
looking at the first bugcheck. system memory corruption, can not debug bug can look at the driver list for clues:
suspect driver:
WinDivert.sys network packet injector, used by malware, game cheats, can cause virus scanners to mess up.

Intel® Wireless WiFi Link Driver - Intel® Wireless WiFi Link Adapter from 2013 (generally ok)
Realtek PCI/PCIe Adapters from 2013 (genearlly ok)

I would remove the network packet injector and see if it has a effect.

I would also run cmd.exe as an admin then run
dism.exe /online /cleanup-image /restorehealth
particularly if you did not intentionally install the packet injector.

 
Solution

m7

Reputable
Dec 17, 2014
12
0
4,510



ok thanks
i'll try update the realtek network drivers and report back
 
looks like chrome made directx graphics calls and used a bad memory address
the suberror code was 0x5003 The working set free list is corrupt. This is probably a hardware error(according to microsoft website, it could just be a power problem to the GPU)

But I would disable any chrome extensions.

I would reset the BIOS back to defaults, run memtest86 and confirm your memory is ok, if no error is detected, I would look for a driver corrupting system memory. boot windows, start cmd.exe as an admin, then run
verifier.exe /standard /all
this will turn on extra device driver checking and will bugcheck the system if it finds a bad driver.
 

m7

Reputable
Dec 17, 2014
12
0
4,510


memory locks fine (scaned with memtest86)
the verifier doesn't help

i'v got new bsod : DRIVER_IRQL_NOT_LESS_OR_EQUAL

this is last 3 new crashs

On Wed 22/04/2015 19:44:53 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF80001CB0419)
Bugcheck code: 0xD1 (0x118, 0xA, 0x0, 0xFFFFF80001CB0419)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 21/04/2015 16:14:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042115-89343-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x2B25D)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8000083825D, 0xFFFFD00035884B30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 20/04/2015 12:17:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042015-19906-01.dmp
This was probably caused by the following module: igdkmd64.sys (igdkmd64+0xB2B26)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80001DAAB26, 0xFFFFD00024BA7F30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\igdkmd64.sys
product: Intel Graphics Accelerator Drivers for Windows 8(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).

waiting for ur reply
thanks
 
in your new list:
bugcheck 0xd1 attemting at access memory address 0x118 (most likely a bad memory address)
bugcheck 0x3b error code 0xC000001D = An attempt was made to execute an illegal instruction
bugcheck 0x3b attempting to access memory address 0xC0000005
this does not make sense, it looks like a error code 0xC0000005 which would be a bad memory access error code but it is not the correct parameter.

if you are still using a packet injector I would guess it is not working correctly. Malware and rootkit scans come up ok?
 

m7

Reputable
Dec 17, 2014
12
0
4,510


no malware detected.

packet injector??
 
I think the first bugcheck I looked at had windivert.sys installed, people use it to cheat at games, and pirates use it to steal passwords and userids from people who play games.



 
if memtest86 is working without errors, and verifier does not show name a driver that is poorly written that is corrupting memory. Then I would suspect that a driver that is written to modify system memory covertly may be the cause. I would remove the windivert.sys driver and see if you still get bugchecks.

any driver can cause the memory corruption problem you are seeing. Normally, you would remove any suspect drivers update all the other drivers. if you still get a bugcheck, you turn on verifier.exe for all the drivers and change the memory dump type to FULL or kernel (not minidump) then when you bugcheck, the system will not strip out the extra debugging info and someone might be able to see the cause of the memory corruption.

With out the debugging info all a person can do is make educated guesses as to the cause. Without most corruptions that are caused by software are not detected at the time of corruption but later when the victim of the corruption has an error that causes a bugcheck. (This may be 4 hours after the corruption occurred or even days later) Windows tries to randomize the loading of drivers and only some will check for data corruption, if you have verifier turnned on and one of the core windows files data is corrupted verifier will force a bugcheck and name the bad driver. it might name one bad driver in 10 crashes of the system, it just takes time to get the right conditions where it can catch a bad driver. Takes a really long time if the bad driver is trying to be hide.
 

m7

Reputable
Dec 17, 2014
12
0
4,510


ok i will try my best

thanks man!
 
this is the file that bugchecked. I guess it is a Intel Wireless WiFi Link Adapter
but a version from a OEM.

Image path: \SystemRoot\system32\DRIVERS\NETwew01.sys
Image name: NETwew01.sys
Timestamp: Tue Jan 06 08:19:19 2015

I would think that the you are hitting a bug in the software that is making calls to this driver.

if you change the memory dump type from minidump to kernel or full I can get a better idea.


machine info:
Manufacturer CLEVO CO.
Product W55xEU
Version D02
BIOS Release Date 10/03/2013

 

m7

Reputable
Dec 17, 2014
12
0
4,510
@johnbl

Strange. BSOD Problems did not happen with me for three days
I started to doubt that the problem related to the battery or charger.

Because I used the computer without the battery and not even single bsod happens with me for 3 days. Is it possible that this has to do with bsod???
 
not sure, but wireless adapters often will go into a lower power mode when they are running on battery power.
they reduce the power to the antenna to save power. These are settings in the windows control panel device manager for the device. older machines that were migrated from windows 7 to windows 8.x tend to have bugs in the wireless drivers because windows 7 had the low power state features turned off by default while windows 8 turns them on by default.
Then end result is windows 8 gets blamed for a bunch of bugs in old drivers. Most often you just have to update the wireless driver (or maybe the BIOS) or turn off the feature in control panel, device management for the wireless card.





 

m7

Reputable
Dec 17, 2014
12
0
4,510


"feature in control panel" where i can find this exacly
 
it will be in windows control panel, device management, then right click on the device and see if there is a power management setting.

there are other ways to get to it also from the power management UI.

I am running windows 10 so it would be best to google for instructions on how to get to them with windows 8.x