NoMoreBugCheck
NoMoreBugCheck copied to clipboard
NoMoreBugCheck - Tampering Whith Audio Drivers?
Hello Im A User who has a steam deck and windows is installed on it ( 11 ) does when a audio drivers crash causes a bsod im curious i havent tested it yet my drivers ( amd audio drivers ) high def
Audio drivers usually run in userspace now a days in Windows so an audio driver crash shouldn't really cause a BSOD. I wouldn't recommend you running this driver as well since if an actual crash occurs in a device driver it might damage the hardware. So please refrain from running this on real hardware. Also Windows 11 on a steam deck? (you're weird (jk))
also a problem here?
I moved the file here i tested whith space and whitout the " but still keep on the bug here
You have to use sc.exe
. sc
in powershell is entire different.
If you're in powershell use sc.exe
or in cmd simply sc
or sc.exe
I wouldn't recommend you running this driver as well since if an actual crash occurs in a device driver it might damage the hardware. So please refrain from running this on real hardware.
I may have been responsible for a few people running this on real hardware, since a couple months ago I posted this video which unexpectedly got 2.6K views and probably drove a few dozen people here.
I did at least add a warning to not run this anywhere since it will almost certainly cause data loss if Windows "crashes" but didn't add that it could cause hardware damage since I didn't think anyone would be running this outside a VM. Maybe a much more visible warning should be added to the README so nobody tries to seriously use this
I wouldn't recommend you running this driver as well since if an actual crash occurs in a device driver it might damage the hardware. So please refrain from running this on real hardware.
I may have been responsible for a few people running this on real hardware, since a couple months ago I posted this video which unexpectedly got 2.6K views and probably drove a few dozen people here.
I did at least add a warning to not run this anywhere since it will almost certainly cause data loss if Windows "crashes" but didn't add that it could cause hardware damage since I didn't think anyone would be running this outside a VM. Maybe a much more visible warning should be added to the README so nobody tries to seriously use this
True, I should add such a warning. Thank you got checking my projects out as well! It means alot to me!!!