BSOD (Critical_Structure_Corruption) once every few days or so

How long should I keep the driver verifier running? Can I play games/do stuff while driver verifier is on?

You can. It should not hurt your ability to play any games. In fact playing games may cause a BSOD and then hopefully we can determine the problem from that alone.

Got it, will activate driver verifier again and see what happens.

EDIT: Ok, so these are the drivers I've enabled Driver Verifier for (everything that's not from Microsoft). Interestingly enough, if I sort by provider, there are still 2 drivers at the bottom that are non-Microsoft (the Nvidia driver and something else), which I enabled. Anyway, here's the list of drivers that I've enabled:

atmfd.dll - Windows NT OpenType/Type 1 Font Driver
bcmsmbsp.sys - Broadcom SMBus Controller Driver (is this normal? is it supposed to say Broadcom? might be another wrong driver, no idea)
cthda.sys - Creative High Definition Audio Device Driver
dump_diskdump.sys
dump_dumpfve.sys
dump_iastora.sys
e2xw10x64.sys - Killer e2400 PCI-E Gigabit Ethernet Controller (this sounds wrong because I thought my motherboard has Killer e2200?)
iastora.sys - Intel Rapid Storage Technology driver x64
iccwdt.sys - Intel Watchdog Timer Driver (Intel WDT)
ndis.sys - Network Driver Interface Specification (NDIS)
nvlddmkm.sys - Nvidia Windows Kernel Mode Driver, Version 372.54
rtcore64.sys (what is this?)
teedriverw8x64 - Intel Management Engine Interface (why is it w8 and not w10?)
xqhdrv.sys - VirtualBox Support Driver (why is this still here? I uninstalled VirtualBox)

And, of course, I ticked: I/O Verification, Force pending I/O requests and IRP logging.

So, already I have noticed some issues with these drivers I think, as I noted in parentheses. Let me know how I can fix those, if indeed I'm right?

Sounds good! If a new BSOD does happen, make sure you post the new files.

Yeah, will do. In the meantime, I edited my last post so can you take a look at it? It has all the non-Microsoft drivers listed with some questions.

ahh i didn't see this when i replied!

Let me take a look.....

rtcore64.sys (what is this?)

RivaTuner. It is a known BSOD causer in Win7. Lets uninstall Rivatuner for now, and if it appears not to be the problem then you can always reinstall it.

teedriverw8x64 - Intel Management Engine Interface (why is it w8 and not w10?)

You can always check for an update at Drivers & Software

xqhdrv.sys - VirtualBox Support Driver (why is this still here? I uninstalled VirtualBox)

As for this, I had to google a solution for it. I found it, but only do it if you feel comfortable manually deleting files from your system folder. Here is the link https://dottech.org/101997/how-to-un...rs-on-windows/ I suggest ONLY removing the files and do not touch your systems registry.

I have W10, so I'd say it shouldn't be the issue especially as it's been fine for a long time with no BSODs (only recently they started appearing). However, I'll uninstall it.

For the Intel Driver Update Utility, it gives me: "Windows can't open this type of file (.bat)". I suppose the associations are messed up? How do I set Windows to open .bat files normally?

As for xqhdrv.sys, I followed that advice before and indeed those files (the ones the website mentioned) were there and I deleted them, but the website doesn't say anything about xqhdrv.sys.

EDIT: Nevermind about Intel Driver Update Utility, found the fix. Regedit folder in HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.bat and set Default to batfile.

EDIT2: Uninstalled Rivatuner, however its driver file still persists and it can be seen in Driver Verifier even after turning off Driver Verifier and turning it on again (deleting settings, and rebooting).

EDIT3: I was able to get rid of the RivaTuner driver file, it seems uninstalling RivaTuner was not enough. I also had to uninstall MSI Afterburner.

It might not be the issue. I am not forcing you to uninstall it, I am just trying to narrow down an issue.

.bat is normally ran with cmd as batch is a type of coding language for command line. Did you try this install? Download Intel® Management Engine Consumer Driver for Intel® NUC

I will take a look more at this driver, and reply with what I find.

The Intel Driver Update Utility kept failing once I tried updating, instead I downloaded and installed this: Download Intel® Chipset Device Software (INF Update Utility)

Not sure about the Intel driver you linked, the one I linked might be more appropriate?

Looks solid to me. For now we can standby until there is a new BSOD.