[SOLVED] Windows 10 frequent BSODs “KERNEL_SECURITY_CHECK_FAILURE”

[Devilmoon]

For context, I have originally asked this question on Superuser but wasn't able to fix the issue. I have currently set up a bounty over there, so if you have an account and would like to earn the bounty you can repost the solution as an answer there and I'll mark it.

So for the past few weeks I've been experiencing quite frequent BSODs on my Windows 10 machine, this ranges from once every 24-48 hours to multiple times a day, and I can't find any kind of solution to the problem.
The usual error message is "KERNEL_SECURITY_CHECK_FAILURE" as reported in the title, and by examining the dumps with windbg it always seems to be some kind of buffer overflow, however the process is not always the same (the last two I checked were Firefox and the GOG Galaxy client).
I also had a few BSODS with the error message related to bad drivers (can't remember it exactly), but I think that was tied to either an old Logitech application or DS4Windows, both of which I've removed from my machine (without fixing the actual problem, it seems).
I have tried checking all my disks (chkdsk), my RAM (mdsched), full AV scans with both Windows Defender and Malwarebytes and yet I have found no issues and none of these steps have so far resolved my problem.

Has anyone experienced anything similar to this? I have searched for this problem online but there doesn't seem to be a clear solution to it, and Microsoft's help and documentation isn't very useful in this regard either.

If it can help pinpoint the problem I can provide a few of the minidumps I still have to dig through, but I don't think there's much more valuable information in there.
I should also mention that I upgraded my motherboard, CPU and RAM a few months back, but the issue is much more recent and hence I can't say if they are in any way related.
I believe the only thing I haven't tried yet (other than just wiping all my disks and doing a clean install) is updating the BIOS of my motheboard, but again the problem seems to be something recent and I've been using the same bios since I put the motherboard in.

My issue, as indicated by the original error code "KERNEL_SECURITY_CHECK_FAILURE", came from a misbehaving driver even though by analysing the dumps it seemed like random processes on my machine were responsible.

To pinpoint the culpript I used the Verifier tool built into Windows and selected most of the drivers not signed by Microsoft themselves (I also excluded drivers built by other well known companies or that I had for a long time and didn't give me issues, like Nvidia, AMD, Logitech and Valve). When restarting my machine to let Verifier run I booted directly into a BSOD, this time with a different error code ("DRIVER _VERIFIER_IOMANAGER_VIOLATION") indicating that the issue came from Verifier and one of the drivers this time. By going through the new minidump the misbehaving driver seemed to be ScpVBus.sys, part of ScpToolkit (which was an older version of DS4Windows apparently).

Just to make sure I also run Verifier with only this driver selected and booted again into a BSOD, so I decided to remove the driver assuming this was the cause of my problems. Unfortunately a standard removal procedure didn't seem to work, but I found a guide here to remove it completely.

A couple of days after removing this driver, I started getting BSODs again. Once again I ran Verifier, this time checking some logitech drivers since I had an issue in the past with a Logitech app, and because by analizyng the stack trace of the dump by following this guide I could find quite a few references to some HID related components. This did in fact trigger a new wave of BSODs, indicating that one of the drivers was causing some issue, so I removed all of them, uninstalled all Logitech apps from my PC and reinstalled the one I use to control my m+kb from scratch.

This again seemed to solve the problem but after a couple of days I got another BSOD. This time from the stack trace I cannot find mention of any likely culpript, and the process indicated by the dump is firefox.exe.
I noticed a couple of insteresting things in the trace though, and that is:

ffffcb82`0220ab18 fffff803`7c87580bUnable to load image \SystemRoot\System32\DriverStore\FileRepository\nvddi.inf_amd64_afaf8d9a55376d3c\nvlddmkm.sys, Win32 error 0n2

nvlddmkm+0x7f580b

[...]

ffffcb82`0220c0a8 fffff803`6ff10801Unable to load image \SystemRoot\system32\drivers\wd\WdFilter.sys, Win32 error 0n2

WdFilter+0x40801

At this point I believe my only course of action is to somehow completely uninstall the nvidia drivers and reinstall them from scratch, and to somehow fix the missing windows defender driver.
So now my question becomes: How do I do it?

I am providing all past minidumps I have saved, plus the latest one and the full DUMP here for an in-depth analysis.

· OS - Windows 10, Version 1909, build 18363.959
· x86 (32-bit) or x64 (64-bit)? 64
· What was the originally installed OS on the system? Windows 10
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Retail
· Age of system (hardware) RAM, Mobo, CPU, boot disk ~5-6 months, GPU, PSU and other disks a few years (If I had to guess 5+)
· Age of OS installation - have you re-installed the OS? ~5-6 months when swapping components installed on clean boot disk, removed from original SSD (now one of the other disks)

· CPU Ryzen 5 3600
· Video Card Nvidia GTX 970
· MotherBoard - (if NOT a laptop) MSI B450 GAMING PLUS MAX
· Power Supply - brand & wattage (if laptop, skip this one) Cooler Master 650

· System Manufacturer N/A
· Exact model number (if laptop, check label on the bottom) N/A

· Laptop or Desktop? Desktop

 

[MrPepka]

Update BIOS - Support For B450 GAMING PLUS MAX | Motherboard - The world leader in motherboard design | MSI Global
Update AMD chipset driver - https://www.amd.com/en/support/chipsets/amd-socket-am4/b450

 

[Devilmoon]

Doing that now. Regarding the BIOS, should I pick the latest one available which is marked as Beta or go with the previous one?

 

[MrPepka]

Best take this H.60

 

[Devilmoon]

I went with H72 since online I found people saying that it works better than H60, if it causes problems I will downgrade down to H60.
Regarding the chipset drivers I can see from RAPR that there are multiple versions of the same driver installed on the machine still. Should I manually remove the older ones?

 

[MrPepka]

They do not need to be removed. Older drivers are kept in the system in case the newer versions are troublesome, so keep the older versions

 

[Devilmoon]

Perfect, thanks a lot.
Someone over on Superuser suggested I Do a Repair Install of Windows 10 with an In-place Upgrade, should I go for it?

 

[Devilmoon]

So, even after BIOS and chipset driver update I got another BSOD, again a KERNEL_SECURITY_CHECK_FAILURE from process firefox.exe; This time I couldn't actually find anything out of place in the stack trace, so I don't even know what to think.
Altough I am starting to notice that BSODs seem to happen when I am watching videos on Youtube, another time I am sure it happened while watching a movie with mpv, and a few times I got BSODs while playing video games. Could it be something tied to the GPU?

Anyway, I am attaching the latest minidump and the full DUMP is here.

 

[MrPepka]

Test CPU with Prime95 and OCCT - CPU STRESS testing: Mersenne.org Prime95 and Intel Processor Diagnostic Tool (IPDT) How to Stress-Test CPUs and PCs (Like We Do)
Test disks with SeaTools - Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test and check their S.M.A.R.T with CrystalDiskInfo - HDD S.M.A.R.T Test with CrystalDiskInfo
Test GPU with FurMark - FurMark Display Card Stress Test
Connect the RAM to other slots, boot the computer with only one RAM stick, and change the RAM to another

 

[Cknoettg]

Thank you for submitting the files!

I wanted to make a suggestion:
Can you temporarily uninstall the MSI Gaming App, and see if the system stabilizes.

After you are done uninstalling, can you verify that this file no longer exists:
C:\Program Files (x86)\MSI\Gaming APP\Lib\NTIOLib_X64.sys

Let us know how that works out.

 

[Devilmoon]

Test CPU with Prime95 and OCCT - CPU STRESS testing: Mersenne.org Prime95 and Intel Processor Diagnostic Tool (IPDT) How to Stress-Test CPUs and PCs (Like We Do)

I tested with Prime95, 1.5h~ each for Small, large and Blend, temps between 75 and 85 °C, no errors or bsods

Test disks with SeaTools - Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test and check their S.M.A.R.T with CrystalDiskInfo - HDD S.M.A.R.T Test with CrystalDiskInfo

Seatools finished without errors on all drives (Long test). Smart is Good for every drive except one which is unknown, but I believe that one doesn't support Smart:

Test GPU with FurMark - FurMark Display Card Stress Test
Connect the RAM to other slots, boot the computer with only one RAM stick, and change the RAM to another

FurMark ran for 20 minutes, no issues and temps were stable at 85-86 °C. I don't quite understand what you want me to do with RAM, do you want me to move the two sticks in the other two slots, then test with only one stick, and then swap out my RAM for another stick?

Thank you for submitting the files!

I wanted to make a suggestion:
Can you temporarily uninstall the MSI Gaming App, and see if the system stabilizes.

After you are done uninstalling, can you verify that this file no longer exists:
C:\Program Files (x86)\MSI\Gaming APP\Lib\NTIOLib_X64.sys

Let us know how that works out.

I removed the app and that file is gone (in fact the whole Gaming App folder). May I ask why you think the MSI program is causing instability? I have a few of their programs on my PC that I don't really use, if they are known to be problematic I could remove all of them.


Also, do you guys think I should go for the in-place reinstall+upgrade as suggested on Superuser?

 

[Cknoettg]

Either an install or an update to the MSI Afterburner driver in the MSI Gaming App immediately preceded one of the BSOD's. It was the one case where a driver that has caused problems in the past was linked to the problem you are having.

I would wait it out for a few days, unless a new BSOD occurs before then. Then we can see if doing the repair install makes sense. I also noticed that you are on 1909. Sometimes updating to the next major Feature Update of Windows 10 has the side effect of clearing out some junk, but we'll have to see if the benefits outweigh the costs.

Event[451]:
  Log Name: System
  Source: Service Control Manager
  Date: 2020-08-07T16:24:23.251
  Event ID: 7045
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: S-1-5-21-954013909-2997750862-1615757465-1001
  User Name: DESKTOP-AB7G8DO\lucag
  Computer: DESKTOP-AB7G8DO
  Description:
A service was installed in the system.

Service Name:  NTIOLib_MBAPI
Service File Name:  C:\Program Files (x86)\MSI\Gaming APP\Lib\NTIOLib_X64.sys
Service Type:  kernel mode driver
Service Start Type:  demand start
Service Account:

Event[452]:
  Log Name: System
  Source: Microsoft-Windows-Winlogon
  Date: 2020-08-07T16:24:19.703
  Event ID: 7001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-AB7G8DO
  Description:
User Logon Notification for Customer Experience Improvement Program

Event[453]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2020-08-07T16:24:16.329
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-AB7G8DO
  Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80003c21cc5, 0xffffac8ccbbf7198, 0xffffac8ccbbf69e0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 6ff61e1a-4d1f-4d6b-a259-b1d50f356404.
[\code]

 

[Devilmoon]

Either an install or an update to the MSI Afterburner driver in the MSI Gaming App immediately preceded one of the BSOD's. It was the one case where a driver that has caused problems in the past was linked to the problem you are having.

I see, that makes sense.

I also noticed that you are on 1909. Sometimes updating to the next major Feature Update of Windows 10 has the side effect of clearing out some junk, but we'll have to see if the benefits outweigh the costs.

I was already trying to update to v. 2004 but unfortunately I am not able to. I have a message saying that the update is on its way, but even if I manually check for updates it doesn't pop up (even though Microsoft docs say it should). See:


Anyways, thanks a lot for your help. I will keep using my PC normally until I get another BSOD and I'll be sure to keep you all updated. Fingers crossed!

 

[Devilmoon]

Another day, another BSOD.
After around 30 hours of the machine being on I got a SYSTEM_SERVICE_EXCEPTION bsod, indicated process in windbg is again firefox.exe and I couldn't find anything else in the dump (dps doesn't seem to work). As usual, attaching minidump and full dump is here.

 

[Devilmoon]

bump
Any suggestions? I might go for the repair install suggested over on Superuser if there's nothing left to try. One commenter over there also said:

I used SCPDriver a few years ago and this happened to me. The only way i got rid of it was to download the media creation tool for windows 10 onto a USB, boot into the USB, delete my entire system and reinstall windows.

 

[Cknoettg]

I would go for it. This link is a good guide to doing the repair install:
How To Reinstall Windows 10.

Let us know how it works out.

 

[Devilmoon]

For now I'm still holding off on the reinstall since I'm working against a deadline, and also because the pc has been on for ~55 hours without a BSOD. I want to see how long it will take for another one to strike!

 

[Cknoettg]

Hold off on the repair install for now.

Just to confirm, did you remove the MSI Gaming App, and check that C:\Program Files (x86)\MSI\Gaming APP\Lib\NTIOLib_X64.sys no longer exists?

If you did that, and still received the BSOD, create a new System Restore point and run verifier again.
Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista

Let us know how that works out.

 

[Devilmoon]

Just to confirm, did you remove the MSI Gaming App, and check that C:\Program Files (x86)\MSI\Gaming APP\Lib\NTIOLib_X64.sys no longer exists?

I did and that file is gone.

I'll try running verifier on all non-microsoft drivers and see what happens, thanks.

 

[Devilmoon]

Verifier has been running for a few hours now and still no issues. This is the output of \query:

Time Stamp: 08/15/2020 16:09:56.216

Verifier Flags: 0x0012892b

Standard Flags:

[X] 0x00000001 Special pool.
[X] 0x00000002 Force IRQL checking.
[X] 0x00000008 Pool tracking.
[ ] 0x00000010 I/O verification.
[X] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[X] 0x00000100 Security checks.
[X] 0x00000800 Miscellaneous checks.
[X] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.
[X] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[ ] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

Internal Flags:

[X] 0x00100000 Extended Verifier flags (internal).

[X] Indicates flag is enabled.

Verifier Statistics Summary

Raise IRQLs: 121625035
Acquire Spin Locks: 6884427
Synchronize Executions: 0
Trims: 509267

Pool Allocations Attempted: 7892177
Pool Allocations Succeeded: 7892177
Pool Allocations Succeeded SpecialPool: 7892177
Pool Allocations With No Tag: 36
Pool Allocations Not Tracked: 0
Pool Allocations Failed: 0
Pool Allocations Failed Deliberately: 0

Driver Verification List

MODULE: amdpsp.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 3 / 0 )
Current Pool Bytes: ( 1280 / 0 )
Peak Pool Allocations: ( 3 / 0 )
Peak Pool Bytes: ( 1280 / 0 )
Contiguous Memory Bytes: 32768
Peak Contiguous Memory Bytes: 36864

MODULE: ysdrv.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 25 / 0 )
Current Pool Bytes: ( 52816 / 0 )
Peak Pool Allocations: ( 26 / 0 )
Peak Pool Bytes: ( 55880 / 0 )
Contiguous Memory Bytes: 4096
Peak Contiguous Memory Bytes: 4096

MODULE: ene.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: rt640x64.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 13 / 0 )
Current Pool Bytes: ( 248916 / 0 )
Peak Pool Allocations: ( 13 / 1 )
Peak Pool Bytes: ( 248916 / 204 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: nvlddmkm.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 64645 / 1017 )
Current Pool Bytes: ( 26417034 / 2562332 )
Peak Pool Allocations: ( 68602 / 1180 )
Peak Pool Bytes: ( 27668488 / 3069286 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: amdpcidev.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: amdgpio2.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: amdgpio3.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: steamstreamingmicrophone.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 5 / 0 )
Current Pool Bytes: ( 209416 / 0 )
Peak Pool Allocations: ( 8 / 0 )
Peak Pool Bytes: ( 209672 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: steamstreamingspeakers.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 5 / 0 )
Current Pool Bytes: ( 209416 / 0 )
Peak Pool Allocations: ( 8 / 0 )
Peak Pool Bytes: ( 209672 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: nvvad64v.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 3 / 0 )
Current Pool Bytes: ( 960 / 0 )
Peak Pool Allocations: ( 5 / 4 )
Peak Pool Bytes: ( 2328 / 2768 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: nvvhci.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 0 / 1 )
Current Pool Bytes: ( 0 / 110 )
Peak Pool Allocations: ( 0 / 2 )
Peak Pool Bytes: ( 0 / 125 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: nvmoduletracker.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: logi_joy_bus_enum.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 2 / 0 )
Current Pool Bytes: ( 258 / 0 )
Peak Pool Allocations: ( 3 / 5 )
Peak Pool Bytes: ( 289 / 282 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: logi_joy_xlcore.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 1 )
Peak Pool Bytes: ( 0 / 64 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: nvhda64v.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 44 / 16 )
Current Pool Bytes: ( 41344 / 10048 )
Peak Pool Allocations: ( 46 / 21 )
Peak Pool Bytes: ( 43352 / 13088 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: rtkvhd64.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 806 / 0 )
Current Pool Bytes: ( 296474 / 0 )
Peak Pool Allocations: ( 810 / 4 )
Peak Pool Bytes: ( 358570 / 39224514 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: nahimic_mirroring.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 9 / 0 )
Current Pool Bytes: ( 1996 / 0 )
Peak Pool Allocations: ( 9 / 0 )
Peak Pool Bytes: ( 1996 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: dump_dumpstorport.sys (load: 0 / unload: 0)

MODULE: dump_stornvme.sys (load: 2 / unload: 1)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: dump_dumpfve.sys (load: 2 / unload: 1)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 1 / 0 )
Current Pool Bytes: ( 16400 / 0 )
Peak Pool Allocations: ( 1 / 0 )
Peak Pool Bytes: ( 16400 / 0 )
Contiguous Memory Bytes: 65536
Peak Contiguous Memory Bytes: 65536

MODULE: amdryzenmasterdriver.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 37 / 0 )
Current Pool Bytes: ( 37403 / 0 )
Peak Pool Allocations: ( 38 / 2 )
Peak Pool Bytes: ( 73403 / 316 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: logi_core_temp.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: rtcore64.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

MODULE: logi_joy_vir_hid.sys (load: 1 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 2 / 0 )
Current Pool Bytes: ( 134 / 0 )
Peak Pool Allocations: ( 2 / 0 )
Peak Pool Bytes: ( 134 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

Should I let it run for 24 hours?