BSOD: IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe+14d220, Win7 & Win10

[MyCookedGooseEgg]

I've been getting a BSOD for a while and have been trying off-and-on to fix it (They come and go in waves, ie: week 1 has 10 crashes, week 2 has 1). It's not an OS problem as I updated to Win10 from Win7 on the 29th. I've run multiple disk checks, looked for software updates, used bluescreen view, mem-test, the whole shamwow and still, I keep getting the error.

Here's the report bluescreenview generated (full .dmp file below):
==================================================
Dump File : 073115-55156-01.dmp
Crash Time : 7/31/2015 8:59:48 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffff6f0`00dce000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`4c74b312
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14d220
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.10240.16393 (th1_st1.150717-1719)
Processor : x64
Crash Address : ntoskrnl.exe+14d220
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\073115-55156-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 10240
Dump File Size : 323,304
Dump File Time : 7/31/2015 9:04:18 AM
==================================================
.DMP FILE: https://goo.gl/T03QHm

.DMP File as .txt: https://goo.gl/nPyPVH

I've tried taking a look at these myself but I've just hit dead ends each time, thanks for any help!

Note: They occur most often right after / during start-up but, they happen at random times as well.

 

[viveknayyar007]

Hello MyCookedGooseEgg

We have a complete text and video tutorial to resolve this issue on Windows 8 and I am sure this would work on Windows 10 as well. The link to the tutorial is here.

Hope this helps.

 

[MyCookedGooseEgg]

Hello MyCookedGooseEgg

We have a complete text and video tutorial to resolve this issue on Windows 8 and I am sure this would work on Windows 10 as well. The link to the tutorial is here.

Hope this helps.

If I boot in safe-mode will it tell me a specific driver instead of just the windows kernel (ntoskrnl.exe)?

 

[viveknayyar007]

Hello MyCookedGooseEgg

We have a complete text and video tutorial to resolve this issue on Windows 8 and I am sure this would work on Windows 10 as well. The link to the tutorial is here.

Hope this helps.

If I boot in safe-mode will it tell me a specific driver instead of just the windows kernel (ntoskrnl.exe)?

Hello again MyCookedGooseEgg

I am afraid that is not how it works. To get the exact cause of issue, you can go to Computer Management (by pressing the Windows + R keys, typing the COMPMGMT.MSC command in the Run command box, pressing Enter), and from the left pane of the Computer Management snap-in, you can check the logs in Event Viewer.

By going to Safe Mode, all non-essential Windows' system files are not loaded in the memory and therefore you get full access on them. This enables you to perform most troubleshooting steps that is not possible otherwise.

Cheers!!

 

[MyCookedGooseEgg]

Hello again MyCookedGooseEgg

I am afraid that is not how it works. To get the exact cause of issue, you can go to Computer Management (by pressing the Windows + R keys, typing the COMPMGMT.MSC command in the Run command box, pressing Enter), and from the left pane of the Computer Management snap-in, you can check the logs in Event Viewer.

By going to Safe Mode, all non-essential Windows' system files are not loaded in the memory and therefore you get full access on them. This enables you to perform most troubleshooting steps that is not possible otherwise.

Cheers!!

I don't crash at startup so I don't really need to be in safe-mode right? Just need help identifying the driver, or device that causes the crasg, because it's not the windows kernel

 

[viveknayyar007]

Hello again MyCookedGooseEgg

I am afraid that is not how it works. To get the exact cause of issue, you can go to Computer Management (by pressing the Windows + R keys, typing the COMPMGMT.MSC command in the Run command box, pressing Enter), and from the left pane of the Computer Management snap-in, you can check the logs in Event Viewer.

By going to Safe Mode, all non-essential Windows' system files are not loaded in the memory and therefore you get full access on them. This enables you to perform most troubleshooting steps that is not possible otherwise.

Cheers!!

I don't crash at startup so I don't really need to be in safe-mode right? Just need help identifying the driver, or device that causes the crasg, because it's not the windows kernel

Hello again MyCookedGooseEgg

You can still use the method given above to go to Computer Management and then check the logs in Event Viewer to get the exact cause of error.

Hope this helps.

 

[johnbl]

also note: it was AvastSvc.exe that maded calls to your network driver that resulted in the bugcheck. You can disable it until you update the BIOS or USB drivers.


your BIOS is from 2009, I expect you have Bugs in the USB support in your BIOS and this is causing a bugcheck in your USB wireless ethernet device
check to see if you can find a BIOS update.

your bugcheck was in
RTL8192SU Wireless LAN 802.11n USB 2.0 Network Adapter Driver
Image path: \SystemRoot\System32\drivers\RTL8192su.sys
Timestamp: Thu Mar 28 00:41:32 2013

here is the website:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true

but the driver they have is older than the one you have installed.

machine info:
BIOS Version P01-A0
BIOS Release Date 04/03/2009
Manufacturer Acer
Product WG43M
Processor Version Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz
Processor Voltage 8dh - 1.3V
External Clock 333MHz
Max Speed 2333MHz
Current Speed 2333MHz

 

[MyCookedGooseEgg]

It seems users were having problems with avast 5 so I'll downgrade to 4.8 version. Should I switch to the driver they have on the website for the wlan card & where would I get an updated bios?

PS thanks so much, I hope to rid of this forever : )