ntoskrnl.exe+80640 BSODs 2 a Day on 2 PCs Exactly the Same BSOD Every Time

[AtlBo]

Happening for a month W7 Pro x64. PCs are connected via ethernet. One is a wi-fi connected desktop and the other (desktop) gets its connection via ethernet connection sharing from the other. About 2 BSODs per day on both PCs. Sometimes they go at roughly the same time, but it could be coincidence idk.

Does anyone have specific knowledge on this specific bluescreen?

Dump File: 032418-15756-01.dmp
Crash Time: 3/24/2018 9:49:55 AM
Bug Check String: DRIVER_IROLNOT_LESS_OR_EQUAL
Bug Check Code: Ox000000dl
Parameter 1: 00000000’00000000
Parameter 2: 00000000’00000002
Parameter 3: 00000000’00000008
Parameter 4: 00000000’00000000
Caused By Driver ntoskrnl.exe
Caused By Address: ntoskrnl.exe+80640
File Description: NT Kernel & System
Product Name: Microsoft® Windows® Operating System
Company. Microsoft Corporation
File Version: 6.17601.17514 (winlspl_rtm.101 119-1850)
Processor x64
Crash Address: ntoskrnl.exe+00640
StackAddressl: - _________
Stack Address 2:
Stack Address 3:
Computer Name:
Full Path: C:WindowsMinidump032418-15756-01.dmp
Processors Count 4
Major Version: 15
Minor Version: 7601
Dump File Size: 288,052
Dump File Time: 312412018 9:51:11 AM

I have dozens of dumps from both PCs, and they are exactly the same. Installed FortKnox Firewall around the time the BSODs started to occur, but at this time I don't want to uninstall software. Details on this bug code would get me started for now and then I can see if the FK dev can help.

Other software I had on the PCs but have removed is NVT OSArmor which is a kernel level security policy setting program. I don't think it caused this problem, but it is beta and I first installed it on both PCs around the same time.

Please, not looking for a solution at this point. Just general information on this specific bluescreen. It looks generic enough that it should be easy to read, but I haven't been able to find anything on Google.

Thx

 

[hang-the-9]

You installed software and issue started happening on both computers, why don't you want to uninstall it to see if it will fix it? That is the number one troubleshooting step. If you did something and issue started happening, undo what you did and see if that fixes it.

 

[johnbl]

you would have to provide the actual memory dumps so they could be looked using the windows debugger.
the files are located in c:\window\minidump directory

you would have to put them on a cloud server like Microsoft onedrive or google docs, share the files for public access and post a link.

in general, the error means that a driver told the window memory manager that it had everything in memory and was going to run before the memory manager. Then the driver tried to access something that was not in memory but the windows memory manager could not run since it had to wait for the device driver to finish first. Also, the memory address used was bogus. it would not have worked anyway.

You would look for old device drivers or overclocked hardware (or malware)