Question PC bluescreening randomly.

[eviltrash]

Since February I've been experiencing random BSOD while gaming. Today it happened while I was just watching some Twitch streams and am officially worried.

ntoskrnl.exe along with dxgkrnl.sys and nvlddmkm.sys is what BlueScreenView says caused it but I can't find any sort of fix for it at all.
I've tried sfc /scannow stuff and it seems to find corrupted files and fixes them.. but the BSOD will happen regardless and I gotta do it all over again.

System Specs
MOBO: Z390 AORUS ULTRA
CPU: Intel i7-9700k CPU
GPU: Nvidia GTX 1070
RAM: Corsair Vengeance Pro 32GB DD4 3600MHz
PSU: EVGA Supernova 650 GS
OS: Windows 10

here are all the minidumps I have:
https://drive.google.com/file/d/1kQiwchQ8OaWoC8UG2s5VkUqbNDlyPwOB/view?usp=sharing

 

[johnbl]

files not shared for public access

 

[eviltrash]

files not shared for public access

sorry about that!
It should be viewable now.

 

[johnbl]

I think you picked up some malware.
you might want to do a malwarebytes scan
(looking for malware that starts with NEP in the filename)


I would go into windows and turn off virtual memory to delete your pagefile.sys then boot windows, turn virtual memory back on, start cmd.exe as an admin then run
dism.exe /online /cleanup-image /restorehealth

then remove any software you don't use and update the rest.
then run a malware scan (you can do it first if you want)

it is not clear as to what is causing the problem. could be just a bug in a old driver. You might have to turn on verifier.exe testing to force the system to bugcheck faster.



-----------
last (oldest) bugcheck was a access violation in the nvidia gpu driver while running OVRServer_x64.exe (occulus server)
system was running 2 hours.

-----------
third bugcheck was a access violation in graphics subsystem.
system was running for 7 days.
3 suspect drivers:
NEPhwb4fso
NEP3kcn0ym
NEPb22cjca

looks like 3 different copies of the same driver with different names. (look for malware)
------
second bugcheck was a access violation (bad memory address used by driver) system was up 11 day 16 hours.
you have a suspect driver running:
NEPjwobo0p

it has s different name from the last bugcheck I looked at.
generally, it is a bad indication for drivers to be using different names on different bootups. Look for malware.

------------------
most current bugcheck was in the graphics subsystem, the
System Uptime: 6 days 0:52:12.568. I would suspect that some other driver used some kernel memory and released it, the windows graphic subsystem used it and then the old driver used it when it no longer owned the memory address.
here are some of the old suspect drivers that you have installed on your system.

SiLib.sys Thu Jul 15 15:08:26 2010
SiUSBXp.sys Thu Jul 15 15:27:13 2010
(software USBXpress, developed by Silicon Laboratories)
(generally usb driver before 2014 have problems, Also your BIOS is from 2018 and would not have various usb fixes)

(bunch of old oculus drivers installed)
OCULUS119B.sys Fri Mar 11 17:22:44 2016
Oculus_ViGEmBus.sys Wed Aug 2 16:42:02 2017
oculusvad.sys Wed Nov 29 19:43:18 2023
ocusbvid111.sys Fri Aug 26 21:00:04 2016

ssdevfactory.sys Tue Sep 15 15:02:05 2020
(steel series driver, check for firmware and driver update)
https://steelseries.com/gg/engine
some RBG drivers mess up the corsair AIO drivers

(old gigabyte driver)
gdrv2.sys Mon Apr 15 00:45:51 2019

not sure what this driver was:
NEPe51d0ur

I would start by removing any of these drivers you do not need.
then update any that you can update.
you might run microsoft autoruns64.exe to disable or remove drivers that you can not find a uninstaller for.
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

you might run driver explorer to remove old driver packages so windows plug and play will not reinstall them right after you remove them.
https://github.com/lostindark/DriverStoreExplorer/releases/tag/v0.12.88

I will look at the other bugchecks to see if any of them caught the actual bad driver. Most often you would have to turn verifier flags on to catch the driver that is causing a problem like this. (this bugcheck is most likely just the victim of the corruption)

machine info:
BiosVersion = F6
BiosReleaseDate = 12/04/2018
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z390 AORUS ULTRA

 

[eviltrash]

I think you picked up some malware.
you might want to do a malwarebytes scan
(looking for malware that starts with NEP in the filename)


I would go into windows and turn off virtual memory to delete your pagefile.sys then boot windows, turn virtual memory back on, start cmd.exe as an admin then run
dism.exe /online /cleanup-image /restorehealth

then remove any software you don't use and update the rest.
then run a malware scan (you can do it first if you want)

it is not clear as to what is causing the problem. could be just a bug in a old driver. You might have to turn on verifier.exe testing to force the system to bugcheck faster.



-----------
last (oldest) bugcheck was a access violation in the nvidia gpu driver while running OVRServer_x64.exe (occulus server)
system was running 2 hours.

-----------
third bugcheck was a access violation in graphics subsystem.
system was running for 7 days.
3 suspect drivers:
NEPhwb4fso
NEP3kcn0ym
NEPb22cjca

looks like 3 different copies of the same driver with different names. (look for malware)
------
second bugcheck was a access violation (bad memory address used by driver) system was up 11 day 16 hours.
you have a suspect driver running:
NEPjwobo0p

it has s different name from the last bugcheck I looked at.
generally, it is a bad indication for drivers to be using different names on different bootups. Look for malware.

------------------
most current bugcheck was in the graphics subsystem, the
System Uptime: 6 days 0:52:12.568. I would suspect that some other driver used some kernel memory and released it, the windows graphic subsystem used it and then the old driver used it when it no longer owned the memory address.
here are some of the old suspect drivers that you have installed on your system.

SiLib.sys Thu Jul 15 15:08:26 2010
SiUSBXp.sys Thu Jul 15 15:27:13 2010
(software USBXpress, developed by Silicon Laboratories)
(generally usb driver before 2014 have problems, Also your BIOS is from 2018 and would not have various usb fixes)

(bunch of old oculus drivers installed)
OCULUS119B.sys Fri Mar 11 17:22:44 2016
Oculus_ViGEmBus.sys Wed Aug 2 16:42:02 2017
oculusvad.sys Wed Nov 29 19:43:18 2023
ocusbvid111.sys Fri Aug 26 21:00:04 2016

ssdevfactory.sys Tue Sep 15 15:02:05 2020
(steel series driver, check for firmware and driver update)
https://steelseries.com/gg/engine
some RBG drivers mess up the corsair AIO drivers

(old gigabyte driver)
gdrv2.sys Mon Apr 15 00:45:51 2019

not sure what this driver was:
NEPe51d0ur

I would start by removing any of these drivers you do not need.
then update any that you can update.
you might run microsoft autoruns64.exe to disable or remove drivers that you can not find a uninstaller for.
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

you might run driver explorer to remove old driver packages so windows plug and play will not reinstall them right after you remove them.
https://github.com/lostindark/DriverStoreExplorer/releases/tag/v0.12.88

I will look at the other bugchecks to see if any of them caught the actual bad driver. Most often you would have to turn verifier flags on to catch the driver that is causing a problem like this. (this bugcheck is most likely just the victim of the corruption)

machine info:
BiosVersion = F6
BiosReleaseDate = 12/04/2018
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z390 AORUS ULTRA

Could I just reformat and then update my BIOS in order to fix this? I'm not very tech savvy to find all these drivers and get rid of them or update them individually. So i'm a bit confused where to start. Malwarebytes doesn't flag anything so no luck there.

 

[johnbl]

I think you picked up some malware.

I would go into windows and turn off virtual memory to delete your pagefile.sys then boot windows, start cmd.exe as an admin then run
dism.exe /online /cleanup-image /restorehealth

then remove any software you don't use and update the rest.
then run a malware scan (you can do it first if you want)

it is not clear as to what is causing the problem. could be just a bug in a old driver. You might have to turn on verifier.exe testing to force the system to bugcheck faster.



-----------
last (oldest) bugcheck was a access violation in the nvidia gpu driver while running OVRServer_x64.exe (occulus server)
system was running 2 hours.

-----------
third bugcheck was a access violation in graphics subsystem.
system was running for 7 days.
3 suspect drivers:
NEPhwb4fso
NEP3kcn0ym
NEPb22cjca

looks like 3 different copies of the same driver with different names. (look for malware)
------
second bugcheck was a access violation (bad memory address used by driver) system was up 11 day 16 hours.
you have a suspect driver running:
NEPjwobo0p

it has s different name from the last bugcheck I looked at.
generally, it is a bad indication for drivers to be using different names on different bootups. Look for malware.

------------------
most current bugcheck was in the graphics subsystem, the
System Uptime: 6 days 0:52:12.568. I would suspect that some other driver used some kernel memory and released it, the windows graphic subsystem used it and then the old driver used it when it no longer owned the memory address.
here are some of the old suspect drivers that you have installed on your system.

SiLib.sys Thu Jul 15 15:08:26 2010
SiUSBXp.sys Thu Jul 15 15:27:13 2010
(software USBXpress, developed by Silicon Laboratories)
(generally usb driver before 2014 have problems, Also your BIOS is from 2018 and would not have various usb fixes)

(bunch of old oculus drivers installed)
OCULUS119B.sys Fri Mar 11 17:22:44 2016
Oculus_ViGEmBus.sys Wed Aug 2 16:42:02 2017
oculusvad.sys Wed Nov 29 19:43:18 2023
ocusbvid111.sys Fri Aug 26 21:00:04 2016

ssdevfactory.sys Tue Sep 15 15:02:05 2020
(steel series driver, check for firmware and driver update)
https://steelseries.com/gg/engine
some RBG drivers mess up the corsair AIO drivers

(old gigabyte driver)
gdrv2.sys Mon Apr 15 00:45:51 2019

not sure what this driver was:
NEPe51d0ur

I would start by removing any of these drivers you do not need.
then update any that you can update.
you might run microsoft autoruns64.exe to disable or remove drivers that you can not find a uninstaller for.
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

you might run driver explorer to remove old driver packages so windows plug and play will not reinstall them right after you remove them.
https://github.com/lostindark/DriverStoreExplorer/releases/tag/v0.12.88

I will look at the other bugchecks to see if any of them caught the actual bad driver. Most often you would have to turn verifier flags on to catch the driver that is causing a problem like this. (this bugcheck is most likely just the victim of the corruption)

machine info:
BiosVersion = F6
BiosReleaseDate = 12/04/2018
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z390 AORUS ULTRA

Could I just reformat and then update my BIOS in order to fix this? I'm not very tech savvy to find all these drivers and get rid of them or update them individually. So i'm a bit confused where to start. Malwarebytes doesn't flag anything so no luck there.

I found a document that indicates that the NEPxxxx file
is a Chinese game developers anticheat driver. (NetEase Protect) the file name starts with NEP then some random characters in order to mess up cheating software. The file gets renamed so that it is hard to block from running.

wiping out windows that would work, just takes a bunch of time.
You would update the bios, then format and reinstall windows, then install the windows updates, then the motherboard drivers but not the motherboard utilities. Then install all of your software.

looks like your system takes a long time to crash, you might just schedule a reboot once a day (shutdown and restart)
If it were me, I would update the bios, the cpu chipset drivers and maybe some of the motherboard drivers. Then use autoruns64.exe to remove some of the really old drivers. Then see if the problem goes away.