BSOD After Driver Verifying - Thanks for the Help!

[matthew.k.sagen]

Hey All!

Would love to know what's causing this issue. Thanks in advance for all your hard work!

Link: https://drive.google.com/file/d/1ZMDu1zpSu3FVERaMe0oCOBHnglea513W/view?usp=sharing

 

[johnbl]

note: looks like the driver corrupted itself, no other drivers were on the stack
just a call to a debug print that most likely should not have been there.

basically the driver ysdrv.sys stack was modified, it could have corrupted itself, another driver may have corrupted it or it could also be a malware attack.
see info below: update the drivers you can update. normally when verifier is turned on, then it names the correct driver that did the corruption (ysdrv.sys in this case)

stack for this driver was corrupted:
BigNoxVM\RT\YSDrv.sys


0: kd> lmvm YSDrv
Browse full module list
start end module name
fffff803`36f30000 fffff803`36f73000 YSDrv T (no symbols)
Loaded symbol image file: YSDrv.sys
Image path: \??\C:\Program Files (x86)\Bignox\BigNoxVM\RT\YSDrv.sys
Image name: YSDrv.sys
Browse all global symbols functions data
Timestamp: Fri Jan 20 22:41:13 2017 (58830289)
CheckSum: 00042B72
ImageSize: 00043000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:

I would suspect this driver also as a potential source of corruption:
\SystemRoot\System32\drivers\secnvme.sys Thu Mar 16 23:03:34 2017
see info here and check for update:
https://carrona.org/drivers/driver.php?id=secnvme.sys

 

[matthew.k.sagen]

You're awesome! Thanks brother!