IRQL_NOT_LESS_OR_EQUAL Error in Windows 10

Solution
evolve.sys = Echobit Evolve Virtual Miniport (Ethernet) driver - http://www.carrona.org/drivers/driver.php?id=evolve.sys Might be a VPN service?

not many details on it: https://www.reasoncoresecurity.com/evolve.sys-c6ca508d34ab1911c6e073252ac1d8be29b412ef.aspx
seems to relate to a game called Evolve - http://www.shouldiremoveit.com/Evolve-18001-program.aspx

winio.sys = Part of MSI Dragoon Gaming Center - http://www.carrona.org/drivers/driver.php?id=winio64.sys Should be on motherboard web site.

TripleThreat00

Reputable
Jun 25, 2014
4
0
4,510


On Sat 7/15/2017 4:56:08 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\071517-9484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F960)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF8036D7874DD)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

gardenman

Splendid
Moderator
Hi, I ran the dump file(s) through the debugger and got the following information: https://pastebin.com/C7dSZgWf

I'm not sure if it will provide enough information or not. Anyway, here's a brief description of the crash:

File: 071517-9484-01.dmp (Sat Jul 15 17:56:08.470 2017)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (a)] {28, 2, 0, fffff8036d7874dd}
Probably caused by: memory_corruption (Process: Battle.net.exe)

I can't help you with this. Wait for Colif or someone else to reply.
 
note: the bugcheck was cause when a driver over wrote another drivers data with the number 0x28.
which would not be a valid memory address. it is more likely a size value of a memory block.
you could run verifier.exe to force windows to name the driver in a bugcheck but I would just remove the 2 very old third party network drivers and retest to see if you still bugcheck.

Microsoft tunnel.sys driver is messed up.
most likely from the two 2010 network drivers that are installed.

I would remove:
winio64.sys Thu Jun 3 21:08:03 2010
and
evolve.sys Fri Aug 6 21:47:00 2010

then reboot and run cmd.exe and then run
dism.exe /online /cleanup-image /restorehealth
to fix the modified windows core files.
(if the command will work on the old windows 10 build)

after that you want to install the custom windows 10 drivers from your motherboard vendors website. just to prevent some other problems before you attempt to run the Microsoft windows update.
 

Colif

Win 11 Master
Moderator
evolve.sys = Echobit Evolve Virtual Miniport (Ethernet) driver - http://www.carrona.org/drivers/driver.php?id=evolve.sys Might be a VPN service?

not many details on it: https://www.reasoncoresecurity.com/evolve.sys-c6ca508d34ab1911c6e073252ac1d8be29b412ef.aspx
seems to relate to a game called Evolve - http://www.shouldiremoveit.com/Evolve-18001-program.aspx

winio.sys = Part of MSI Dragoon Gaming Center - http://www.carrona.org/drivers/driver.php?id=winio64.sys Should be on motherboard web site.
 
Solution