Here's a new dump... I forgot to shut down my computer last night when I went to bed and it seemed to of BSOD'ed while I was sleeping. Nothing was running as far as I remember
https://www.dropbox.com/t/AnrWLKGUG5OGrqmw
I ran verifier.exe and clicked on create standard settings, then automatically select all drivers installed on computer to verify.
https://puu.sh/J9j5r/773818d509.png
I'm not sure what you mean with the / commands? Sorry I am a bit ignorant.. but yeah, when I tried to run it the other day it wouldnt let me boot up my computer all the way so I had to system restore
if you just run verifier.exe you get the graphics interface and can select options.
if you run verifier.exe and put command line options then the interface does not come up and the options just take effect.
for example run
verifier.exe /standard /all /driver.exclude vgk.sys
this would start verifier but exclude testing the riot games driver that verifier found bugs on the previous runs.
running
verifier.exe /standard /all /bootmode oneboot
would run verifier with the standard flags but will turn it back off after the next verifier error being detected.
(so you do not have to go into safe mode and run verifier.exe /reset )
if you bugcheck at boot, you would boot into safe mode and run
verifier.exe /reset
to turn off verifier so you can boot fully.
you should change the memory dump type to kernel and provide c:\windows\memory.dmp file which will have much more debugging data.
-----------
last bugcheck something wrote
33333333`33333333
on the process OVRServer_x64.
data.
this is part of the Oculus runtime.
I would estimate that about 80% of the time, I find that the program corrupts its own data. The rest of the time some other driver does the corruption.
I would be looking at the following drivers but would look at this one andappsvc64.sys first. Just because I have not seen it before.
you can remove software one by one, or you can run verifier on each driver one by one until you get a bugcheck.
if one driver is corrupting anothers drivers data then verifier testing will be required to prove the corruption. Verifier will cause a bugcheck at the time of corruption rather than the system bugchecking when the corrupted code it run.
when verifier finds the corruption it names the driver that did the corruption. You have to run this thru many cycles of bugchecks until you find the actual corruption cause. many 3rd party drivers will fail verifier testing in different ways so the process can be painful and take a long time.
your suspect drivers would be:
-bluestacks app and various drivers
- old webcam driver:
wdcsam64.sys Fri Oct 9 13:31:13 2015
- oculus drivers
Oculus_ViGEmBus.sys Wed Aug 2 16:42:02 2017
- vpn software:
Neo6_x64_VPN.sys Sun Feb 4 23:34:13 2018
- old logitech drivers:
LGBusEnum.sys Mon Jun 13 11:47:08 2016
(plus 4 other lg drivers)
and
andappsvc64.sys Wed Mar 3 23:05:25 2021
looks like you have already removed the vgk.sys driver.
-----------
edit:
you could also just use autoruns64 and disable this driver:
andappsvc64.sys
and see if your problem is resolved.