[SOLVED] IRQL_NOT_LESS_OR_EQUAL ntoskrnl BSOD

[johnderekmurphy]

Hey guys, im at a loss for what to do to resolve my pc issues. I tried to tackle the issue myself tonight but i fear i might just cause more issues if i were to continue without proper guidance.

I have WhoCrashes installed but im not sure how to share my results with you guys. so ill just paste it here. My apologies if this isnt proper etiquette.



System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-4OAJGG7
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\WINDOWS
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., X99-A II
CPU: GenuineIntel Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 34266243072 bytes (31.9GB)




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

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Tue 2019-01-08 10:38:41 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010819-9156-01.dmp
This was probably caused by the following module: scpvbus.sys (0xFFFFF80F6596B174)
Bugcheck code: 0xC9 (0x21F, 0xFFFFF80F6596B174, 0xFFFFD900868A4DC0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\WINDOWS\system32\drivers\scpvbus.sys
product: Scp Virtual Bus Driver
company: Scarlet.Crush Productions
description: Scp Virtual Bus Driver
Bug check description: This is the bug check code for all Driver Verifier crashes.
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: scpvbus.sys (Scp Virtual Bus Driver, Scarlet.Crush Productions).
Google query: scpvbus.sys Scarlet.Crush Productions DRIVER_VERIFIER_IOMANAGER_VIOLATION



On Tue 2019-01-08 10:38:41 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: scpvbus.sys (0xFFFFF80F6596B174)
Bugcheck code: 0xC9 (0x21F, 0xFFFFF80F6596B174, 0xFFFFD900868A4DC0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\WINDOWS\system32\drivers\scpvbus.sys
product: Scp Virtual Bus Driver
company: Scarlet.Crush Productions
description: Scp Virtual Bus Driver
Bug check description: This is the bug check code for all Driver Verifier crashes.
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: scpvbus.sys (Scp Virtual Bus Driver, Scarlet.Crush Productions).
Google query: scpvbus.sys Scarlet.Crush Productions DRIVER_VERIFIER_IOMANAGER_VIOLATION



On Tue 2019-01-08 10:00:44 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010819-11484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0xA (0xFFFFC5011495B0C0, 0x2, 0x1, 0xFFFFF803A8E73CB5)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





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

3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

scpvbus.sys (Scp Virtual Bus Driver, Scarlet.Crush Productions)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.



If you need any other info, please let me know!

Any help is greatly appreciated!

 

[Colif]

scpvbus.sys as the who crashed shows is likely cause, they used for PS3 controller drivers. Scarlet Crush. So its your choice, find new drivers or live with errors or stop using PS3 controller.

They are known to cause BSOD.

if you go to C:\WINDOWS\Minidump
copy the contents to a new folder
upload the copies from new folder to a file sharing web site and we have a look to see if anything else might be cause

 

[johnderekmurphy]

Hi Colif, thank you very much for taking the time to answer and help me with my problem. I really appreciate it!

Interesting, i do not own nor ever have had a ps3 controller while owning this PC. But regardless, id like to have the issue resolved, so how would i go about removing this scpvbus.sys?

edit: here is a link to the minidump folder https://drive.google.com/open?id=1GV7FGFWhi9rxYuI9KFxWsOsW4qab_qCF
edit 2: updated gdrive link

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/mRZw.html

File: 010819-9156-01.dmp (Jan 8 2019 - 21:38:41)
BugCheck: [DRIVER_VERIFIER_IOMANAGER_VIOLATION (C9)]
*** WARNING: Unable to verify timestamp for ScpVBus.sys
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 11 Sec(s)

File: 010819-11484-01.dmp (Jan 8 2019 - 21:00:44)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
*** WARNING: Unable to verify timestamp for IntelNit.sys
Probably caused by: memory_corruption (Process: System)
Uptime: 5 Day(s), 0 Hour(s), 25 Min(s), and 31 Sec(s)

Motherboard: https://www.asus.com/us/Motherboards/X99-A-II/HelpDesk_Download/
There are BIOS updates available for your system.
Your version: 1003
Current version: 1902
Wait for additional information before deciding to update or not. Also verify the information before attempting to update. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.

 

[Colif]

IntelNit.sys = Intel® Turbo Boost Max Technology 3.0 so update it if you use it: https://downloadcenter.intel.com/download/26103/Intel-Turbo-Boost-Max-Technology-3-0 (BIOS update might also help this error)

Scarlet Crush. I think this removes it: https://github.com/nefarius/ScpToolkit/wiki/Manual-driver-removal

Updating BIOS might help as well. Instructions are in your motherboard manual or here: https://dlcdnets.asus.com/pub/ASUS/mb/LGA2011/X99-A_II/E11090_X99-A_II_UM_WEB.pdf on page 3-37
If you update bios, also update Intel Management Engine Interface to version Version 11.0.5.1189 as it likely matches new bios. It is 1st link under Chipset here: https://www.asus.com/us/Motherboards/X99-A-II/HelpDesk_Download/

 

[johnderekmurphy]

Hey Colif, Thank you again for the response and help.

I managed to install/update my intel Turbo Boost Max as you suggested. I also Updated my mobos BIOS via the internet with the EZ updater on the BIOS interface.

The only thing i couldn't do was, as per your Scarlet Crush GitHub link, find SCP DSx Service in my Services.msc. Nothing shared that name that was listed in my service console. Here is a screenshot of my services window.

https://imgur.com/LLxp6sf

At this point should i do another run of WhoCrashed and upload it here? I again sincerely appreciate your time and help.

 

[Colif]

If you get any more BSOD, try running this on PC and remove scarlet crush file (scpvbus.sys) from running at startup - https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns