Windows 10: BSOD Playing Counter-Strike: Global Offensive, related to ntoskrnl.exe

I was playing CS:GO as usual, and for the first time (that I noticed) I got this BSOD IRQL_NOT_LESS_OR_EQUAL while playing the game, it hadn't happened before so I thought it was just a one time thing and as soon as the computer restarted I jumped into the game, just to get the same BSOD a few seconds later, and, it kept happening afterwards.

Checking it with BlueScreenView I've noticed that before the few that the BSOD was related to ntoskrnl.exe and it HAS happened before, two times, once 2 months ago and the other time 3 months ago, even though

I don't remember it happening while playing CS:GO and only today I got it to occur 4 times in a short spam of time, always in the game.

Others BSOD occurred when using driver verifier and rebooting

:)

 

csgob0t.online

Its related to the game Counter Strike: Global Offense ...

If you have that game installed, uninstall then reinstall it.

 

Computer Randomly Black Screening

Its not one particular game. I’ve had t happen with Counter Strike: Global Offensive, Oblivion, and 7 Days To Die.

 

All the dumps are the same:
Code: BugCheck A, {ffffe001145d8778, 2, 0, fffff801e2a5e61f} Probably caused by : ntkrnlmp.exe ( nt!KiRetireDpcList+48f )[/quote] The dumps themselves don't have any useful data in them.

BugCkeck A is often caused by defective RAM. Can also be a driver problem. So lets check your RAM then if that shows nothing enable Driver Verifier. Instructions follow:

===================================================
RAM:

Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums



Information




MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.



Warning
MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.



Note
MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to


PART TWO


and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.

 

Just finished running MemTest86+ for 8 passes with no errors returned. It's pretty late here, so I'll do the Driver Verifier tomorrow and return with results as soon as possible.

Anyway, Thanks for the help so far.

 

Just enabled Driver Verifier and my computer wouldn't even boot, after some BSODs I could desable driver verifier throught boot options.


dump files anexed

 

The newest dump indicates a problem with Scpvbus.sys.

Code: Unable to load image \SystemRoot\System32\drivers\ScpVBus.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ScpVBus.sys *** ERROR: Module load completed but symbols could not be loaded for ScpVBus.sys[/quote] This belongs to Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver. The one you have is old:

Code: 5: kd> lmvm ScpVBus start end module name fffff801`aafa0000 fffff801`aafae000 ScpVBus T (no symbols) Loaded symbol image file: ScpVBus.sys Image path: \SystemRoot\System32\drivers\ScpVBus.sys Image name: ScpVBus.sys Timestamp: Sun May 05 17:31:26 2013 (5186CFAE) CheckSum: 00010BD7 ImageSize: 0000E000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] I think this has something to do with a Playstation. Needs to be removed or updated.

Edit: Just for information purposes, I see you have a lot of old drivers on this system:

Code: 2007/03/07 19:13:19 C:\WINDOWS\system32\DRIVERS\pnetmdm64.sys 2008/09/24 20:28:20 C:\WINDOWS\system32\drivers\SiSRaid2.sys 2008/10/01 23:56:04 C:\WINDOWS\system32\drivers\sisraid4.sys 2009/04/08 16:28:44 C:\WINDOWS\system32\drivers\xusb21.sys 2009/07/31 05:40:32 C:\WINDOWS\system32\drivers\MBfilt64.sys 2010/06/04 06:08:03 \??\C:\Program Files (x86)\MSI\Dragon Gaming Cen 2010/08/12 12:26:14 C:\WINDOWS\system32\drivers\CM10864.sys 2011/04/11 20:48:16 C:\WINDOWS\system32\drivers\iaStorV.sys 2011/05/12 15:06:54 C:\WINDOWS\system32\drivers\ssadbus.sys 2011/05/12 15:08:26 C:\WINDOWS\system32\DRIVERS\ssadmdfl.sys 2011/05/12 15:08:36 C:\WINDOWS\system32\DRIVERS\ssadmdm.sys 2011/05/12 15:09:54 C:\WINDOWS\system32\DRIVERS\ssadserd.sys 2012/05/03 21:56:17 C:\WINDOWS\system32\DRIVERS\GEARAspiWDM.sys 2012/05/12 06:27:12 C:\WINDOWS\system32\drivers\MijXfilt.sys 2012/06/05 03:04:12 C:\WINDOWS\system32\drivers\N360x64\1607000.04C\ 2012/10/25 12:27:58 \??\C:\Program Files (x86)\MSI\SUPER CHARGER\NTI 2012/11/27 01:02:51 C:\WINDOWS\system32\drivers\stexstor.sys 2012/12/11 22:21:44 C:\WINDOWS\system32\drivers\amdsbs.sys 2013/01/21 20:00:28 C:\WINDOWS\system32\drivers\vstxraid.sys 2013/02/04 20:47:18 C:\WINDOWS\system32\drivers\bxvbda.sys 2013/02/13 18:25:48 C:\WINDOWS\system32\DRIVERS\bwcW8x64.sys 2013/03/16 00:39:38 C:\WINDOWS\system32\drivers\lsi_sss.sys 2013/03/20 22:24:01 C:\WINDOWS\system32\drivers\e22w8x64.sys 2013/03/26 22:36:54 C:\WINDOWS\system32\drivers\HpSAMD.sys 2013/05/05 23:31:26 C:\WINDOWS\system32\drivers\ScpVBus.sys 2013/06/04 00:02:39 C:\WINDOWS\system32\drivers\megasr.sys 2013/07/02 20:38:08 C:\WINDOWS\system32\DRIVERS\TeeDriverx64.sys 2013/07/16 00:39:01 C:\WINDOWS\system32\DRIVERS\netaapl64.sys 2013/07/29 21:50:14 C:\WINDOWS\system32\drivers\NARAx64\0405000.009\ 2013/07/29 21:50:14 C:\WINDOWS\system32\drivers\NATx64\010A000.009\c 2013/08/29 00:13:22 C:\WINDOWS\system32\drivers\iaStorA.sys 2013/09/24 05:58:04 C:\WINDOWS\system32\drivers\NSTx64\7DE070B0.02A\ 2013/09/27 08:41:43 C:\WINDOWS\system32\DRIVERS\RtsPer.sys 2013/12/17 23:47:38 C:\WINDOWS\system32\drivers\intelaud.sys 2013/12/17 23:47:38 C:\WINDOWS\system32\drivers\iwdbus.sys 2014/01/02 10:51:22 C:\WINDOWS\system32\DRIVERS\ssudbus.sys 2014/01/02 10:51:26 C:\WINDOWS\system32\DRIVERS\ssudmdm.sys 2014/03/16 11:07:36 C:\WINDOWS\system32\drivers\bcmfn2.sys 2014/04/21 20:28:42 C:\WINDOWS\system32\drivers\nvraid.sys 2014/04/21 20:34:03 C:\WINDOWS\system32\drivers\nvstor.sys 2014/04/22 21:21:41 C:\WINDOWS\system32\drivers\vsmraid.sys 2014/05/23 22:39:04 C:\WINDOWS\system32\drivers\mvumis.sys 2014/05/27 18:42:05 C:\WINDOWS\system32\drivers\SteelBus64.sys 2014/05/27 18:46:34 C:\WINDOWS\system32\drivers\SAlpham64.sys 2014/06/27 16:18:38 \??\C:\Program Files (x86)\GbPlugin\wsftprp64.sy 2014/07/15 19:30:23 C:\WINDOWS\system32\Drivers\usbaapl64.sys 2014/10/01 22:17:32 C:\WINDOWS\system32\DRIVERS\Smb_driver_Intel.sys 2014/12/08 11:13:10 C:\WINDOWS\system32\drivers\dtlitescsibus.sys[/quote] I'm not saying they are a problem, but it looks like you upgraded from an older version of Windows, like Windows 7 or 8 and the old drivers came along with that upgrade.

If you continue to have problems is would be a good idea to save your data (anything you don't want to lose) then do a Clean Install of Windows 10. See here: How to Clean Install Windows 10


Just something to keep in the back of your mind for a later time.

 

Sorry for the long time without feedback, I was travelling and unable to use my laptop. I'll check that driver, I did use it so my computer would recognize a PS4 controller a couple of months ago.

Thanks, I'll keep you posted if the problem persists or doesn't happen anymore.