BSOD - IRQL - Not Less Or Equal (Various Crashes)

doucette_j

Prominent
Nov 11, 2018
7
0
510
Hey guys,

I've recently started having BSOD errors pop up. I ended up reformatting my laptop, fresh install of windows, reinstalling all drivers from the manufacturer's site, and doing my best to optimize but still they end up persisting.

I use bluescreenviewer, and have used eventvwr.msc to try to get to the bottom of it but it's beyond my understanding at this point and I need some help.

I've uploaded the latest dump file here :
Dump File 11 Nov 18 3:06pm

Thanks in advance.
 
it looks like a timing related problem, the filesystem deleted a file, but right after deletion something tried finally got access but ended up using a bad memory address (memory address zero)

three suspects:
old driver: (very old driver date)
Razer Lachesis Mouse driver
SystemRoot\system32\drivers\Lachesis.sys Fri Aug 17 00:48:44 2007
http://drivers.razersupport.com/index.php?_m=downloads&_a=view?_m=downloads&_a=view&_m=downloads&_a=view?_m=downloads&_a=view


Samsung NVMe drive
\SystemRoot\System32\drivers\secnvme.sys Wed Aug 3 22:39:04 2016
\SystemRoot\System32\drivers\secnvmeF.sys Wed Aug 3 22:38:58 2016
check samsung for updated driver:
https://www.samsung.com/us/support/


killer network driver:
\SystemRoot\System32\drivers\RivetNetworks\Killer\KfeCo10X64.sys Thu Jun 14 17:43:46 2018
(this is not your network card driver, it might be some kind of packet shaping driver to help gain an advantage in gaming by expediting some network packets and delaying others. these tend to cause timing problems, you might remove any killer network network packet shaping drivers)

Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver
\SystemRoot\System32\drivers\ScpVBus.sys Sun May 5 14:31:26 2013
this driver as a bug that can corrupt data in memory of any driver on the system.
I have never seen a fix for it, and the uninstaller often does not work.
you might remove it using https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
(generally it takes hours to detect problems by this driver, systems that sleep tend to save the problems to disk)



 
Ok, so I installed the Razer Lachesis driver, and removed the Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver using the method you mentioned as well as the Killer network driver.

However, this morning I had another BSOD while I was afk for a few minutes, here is the dump file :
https://drive.google.com/file/d/1LvvOcnpYCaN0LgeSjNlvfnFuDgl15SQ_/view?usp=sharing

I did notice a slight difference with the mouse being less jittery than before in a couple games, but there are obviously other underlying issues with my laptop. Hopefully you can shed some light for me, it's frustrating to say the least.

 
system seems to be underclocked by 100mhz (not sure why)
Processor Version Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Processor Voltage 88h - 0.8V
External Clock 100MHz
Max Speed 8300MHz
Current Speed 2700MHz

only other unexpected driver was:
\SystemRoot\System32\drivers\necbatt.sys Wed Jun 19 20:08:55 2013

the bugcheck looks like a timeout period expired with something running on one cpu core is waiting for a response from something running on another cpu core.

you might check to see if there is a bios update from the motherboard vendor(even though your system bios is pretty new) also update any drivers from the motherboard vendors website. you should also make sure none of the vents are blocked, overheating can trigger the system to underclock to reduce heat.

I have seen problems like this when a old driver attempts to install on one core and fails while another cpu core tries to use the driver and waits. So check control panel to see if some device is in need of a driver.

I seem to be seeing a lot of problems with system timers, there just might be some bug in windows.
if this is the case, make sure you check for new windows updates. Microsoft would be getting lots of complaints and would push out a fix via windows update.

you should change the memory dump to kernel then on the next bugcheck provide the memory dump. This will include the info on what is running on all of the cpu cores and the state of windows plug and play to see if something is broken trying to install its device driver.

Sometimes for laptops the vendor underclocks on purpose to reduce heat problems. but be sure to check to see if there are driver updates. the time out period was pretty long 7680 clock ticks. so the device that failed to respond must be some slower device (I don't recognize the number, just that faster devices like a GPU have timeouts of 30 clock ticks)






 
the graphics driver was writing to a memory mapped file (file stored in memory rather than on disk)
it freed up a memory allocation twice and it caused a bugcheck.

I would turn off all of the extra nvidia software and just leave the nvidia gpu driver and the nvidia sound driver
and see if you still get a problem.

several modified windows files.
will see if I can get a clue that would be more hepful

are you actually using the intel graphics driver?
start cmd.exe as an admin then run the command
findstr.exe /s /m /l SdSQ *.sys

----------------
just to check what is using all of the pagefile space.

NonPaged Paged
Tag Allocs Used Allocs Used

MmSt 0 0 11904 77745280 Mm section object prototype ptes , Binary: nt!mm
MmRe 0 0 2045 19188352 ASLR relocation blocks , Binary: nt!mm
CM25 0 0 3059 14336000 Internal Configuration manager allocations , Binary: nt!cm
Dprt 38 3232 206196 13215856 Video port for Vista display drivers , Binary: dxgkrnl.sys
Ntff 19 6688 7318 10069568 FCB_DATA , Binary: ntfs.sys
SdSQ 0 0 2749 9550496 UNKNOWN pooltag 'SdSQ', please update pooltag.txt
FMfn 6 1824 20874 9117616 NAME_CACHE_NODE structure , Binary: fltmgr.sys
Vi54 0 0 2103 8644096 Video memory manager PTE array , Binary: dxgmms2.sys
svtT 0 0 60688 6797056 UNKNOWN pooltag 'svtT', please update pooltag.txt
Toke 0 0 3831 6739424 Token objects , Binary: nt!se
SApn 0 0 83644 6691520 UNKNOWN pooltag 'SApn', please update pooltag.txt
Vi12 0 0 23686 4957632 Video memory manager process heap alloc , Binary: dxgmms2.sys
SaFA 0 0 27904 4943296 UNKNOWN pooltag 'SaFA', please update pooltag.txt
Vi01 0 0 9142 4826976 Video memory manager global alloc , Binary: dxgmms2.sys
NtfF 0 0 2927 4636368 FCB_INDEX , Binary: ntfs.sys
B2E3 0 0 17 4431376 UNKNOWN pooltag 'B2E3', please update pooltag.txt
RvaL 0 0 1617 3897520 UNKNOWN pooltag 'RvaL', please update pooltag.txt
SApt 0 0 75294 3675008 UNKNOWN pooltag 'SApt', please update pooltag.txt
D









 
So when I run that command this is what pops up.

drivers\NGCx64\1610010.004\SymEFASI64.sys


I have a GeForce GTX 1060, so should I be disabling or uninstalling the Intel driver ?
 
Symantec Extended File Attributes = SymEFASI64.sys

you should run the same command on some of the other unknown pooltags to find out what is using all of the pagefile.sys space

basically, the system is allocating virtual memory much faster than the clean up routines are able to clean up the free memory. like adding 3 gallons per minute of water to a tank while it drains at 2.5 gallons of water a minute, eventually if you do it long enough the tank will fill up and overflow. Only thing you can do is reduce the rate of fill or increase the rate of draining.

so the virus scanner checking the memory mapped file could be slowing down access to the file, the other nvidia utilites could be using a bunch of your pagefile.sys (virtual memory)

you need to slow down the rate at the pagefile.sys is being consumed. you can make the file bigger but that will just give you more time before it crashes again. (looks like it toke 1hr 47 minutes of running the game before the crash)

it could also be some bug with these drivers: (if the get a error and cause a delay in accessing virtual memory)
you should really look for updated drivers from Samsung or see if you actually need them.
https://www.samsung.com/us/support/

(guessing this drivers might be the likely cause, since I can not actually find nonpaged pool allocation failures)

Samsung NVMe driver
\SystemRoot\System32\drivers\secnvme.sys Wed Aug 3 22:39:04 2016
Samsung NVMe Filter driver
\SystemRoot\System32\drivers\secnvmeF.sys Wed Aug 3 22:38:58 2016


old razer mouse driver is back:
\SystemRoot\system32\drivers\Lachesis.sys Fri Aug 17 00:48:44 2007

the intel driver was also using a bunch of memory and pagefile.sys space. i did not know if you had a display attached to it. if not you might be able to disable it in bios and in windows to free up the memory/pagefile useage.

the unknown pooltags are of interest to help find out what was using the bulk of your virtual memory.
it is pretty reasonable that a virus scanner would use a lot.
the ones marked as unknown might be from a driver that is only on your system (rather than belonging to windows)
the findstr command searches thru the driver binaries on your machine trying to find the 4 letter tag and returns the name of the file.
when we have the name we can look up what the file is for. from here:
https://carrona.org/drivers/driver.php?id=secnvme.sys

guess I would also be looking at

SEMA Software Driver (just because it a CAD related)
C:\Windows\system32\drivers\semav6msr64.sys Mon Jan 22 09:35:46 2018


also running a killernetwork service but your using a intel wifi card and your wired killer network adapter is not connected. you might want to stop the service.

generally, a wired connection is faster than a wireless connection.
killer network drivers should be updated often because they tend ot cause issues.
(remove/stop the service if not used)

IntelCpHDCPSvc.exe is running stands for Intel Content Protection High-bandwidth Digital Content Protection Service not sure why it is running unless you use the intel gpu.

DSAService.exe is part of Intel Driver Update Utility. not sure why it would be running unless you were actively updating intel drivers. (I would not leave it running)

igfxCUIService running,stands for Intel Graphics Common User Interface Service



 
Hey johnbl,

So I'm happy to report that after doing another fresh install of windows 10, and opting not to install the Killer Network driver, as well as switching to a Cougar 550 mouse instead of my vastly outdated Razer Lachesis (which they don't even list on their website anymore) , I haven't had a single crash in the past couple days.

Hopefully, the problem has been resolved, I will keep my fingers crossed. I read other forums too and many people have had issues with the Killer Network and Killer Control Center crashing their systems.

Thank you for all your help, I will return again if I run into any more problems.