IRQL_NOT_LESS_OR_EQUAL Error in Windows 10

[Davobruhhh]

Computer name: SWAGLORD
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: Aspire E5-573, Acer, ZORO_BH
CPU: GenuineIntel Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4206178304 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 25/02/2017 22:13:12 your computer crashed
crash dump file: C:\WINDOWS\Minidump\022517-19406-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF806819A3BB4)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF806819A3BB4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network Driver Interface Specification (NDIS)
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.
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 Sat 25/02/2017 22:13:12 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ndis.sys (ndis!NdisMIndicateReceiveNetBufferLists+0x1604)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF806819A3BB4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network Driver Interface Specification (NDIS)
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.
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 Tue 29/11/2016 02:39:00 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112916-29140-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF8083D1B4670)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8083D1B4670)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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.
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 Sun 27/11/2016 13:15:47 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112716-32140-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF800D9BF4670)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF800D9BF4670)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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.
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 Sat 26/11/2016 13:47:15 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112616-22187-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF80D46203BB4)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF80D46203BB4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network Driver Interface Specification (NDIS)
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.
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.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

14 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

 

[Paul NZ]

Upload the dmp files to onedrive then post the link

 

[Colif]

go to this web site and look in the driver list for lan drivers - its possible you already have the latest version: Acer link

this is what Paul wants:

Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

 

[Davobruhhh]

https://1drv.ms/f/s!AhH-KYsFethChQbpN-lzGYbVZ5jq - heres a link to the dmp files

 

[Paul NZ]

Looks like this file wdiwifi.sys your wireless adapter drivers are crashing as well. Update this driver.

Dont use device manager. If it's part of the laptop, go to the Acer site

I would say this is crashing tcpip.sys, netio.sys, and ndis.sys

Update the BIOS. That may fix the 0x133 stop error

 

[Davobruhhh]

https://www.acer.com/ac/en/US/content/support-product/5977;-;Aspire%20E5-573G

thanks Paul, so I download the Wireless LAN Driver? Broadcom or Intel? How do I update the BIOS?

Cheers mate

 

[Paul NZ]

Intel wireless drivers, I think. I think you can only update the BIOS in windows

 

[Davobruhhh]

Hi Paul

In terms of the BIOS can it be updated using the acer website i pasted earlier?

 

[Paul NZ]

If thats the site for it yup. Thats the only place you should get it from

 

[Davobruhhh]

Hi Paul just had another crash and it said tcpip.sys failed, would that be to do with the BIOS? I still need to update this but do not know which one to install. Could you check the BIOS/ Firmware section and advise me which would be best?

Many thanks friend