I came back today around 10 P.M. to find out that my computer had a SYSTEM_SERVICE_EXCEPTION BSOD 2 weeks after I had the same BSOD, though I'm unsure if fltmgr.sys or something else caused it: SYSTEM_SERVICE_EXCEPTION bug caused by fltmgr.sys - Windows 10 Forums . I followed the instructions outlined in the post and had no BSODs until this point.
Warning
Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.
Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.
If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.
Note
Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
I tried the driver verifier, but I was away when my computer crashed, so I'm unsure what the BSOD was caused by.
I got another BSOD today, this time an IRQL_NOT_LESS_OR_EQUAL one.
I've done memory tests before with memtest86 and none of them have ever turned up with anything for either stick of RAM.
Sometimes using different memory modules can cause issues, irrelevant of any software tests performed. This doesn't mean that either of them is bad, just that there's a chance your system doesn't like it.
I can try swapping out memory modules but I've also noticed that in Device Manager, Realtek Audio Driver doesn't show up, but it seems to instead be replaced by a generic one from Microsoft called High Definition Audio Device. From what I've researched on the BSODs I've been having, a relatively common cause is the Realtek Audio Driver.
I didn't see the audio drivers in the dump as the cause, but you can try to install the drivers from Gigabyte.
Quote