Okay, Driver Verifier disabled now. Honestly I'd forgotten it was active again, so it was good you reminded me.
Yeah, I was aware that it was the AMD driver that crashed in game; since I read the BSOD and since I could, I actually used WhoCrashed this time, which is why I was thinking it was unrelated, and its probably just Wildstar stressing the Graphics Card out since its currently in Open Beta.
My Radeon still has its moments of derp, after all... since its not exactly great I may eventually consider getting a new nVidia. Though it seems to be behaving slightly better since they released a new 'stable' driver set (except the above BSOD, of course)
I've also uninstalled Spybot since it was causing some errors like this in Event Viewer:
Activation context generation failed for "c:\program files (x86)\spybot - search & destroy 2\Updates\Extracts\SDWSCSvc.exe". The setting http://schemas.microsoft.com/SMI/2005/WindowsSettings^antispywareProductDisplayName is not registered.
My Last Spyware scan came up blank anyway; but I'll reinstall it eventually when I do a new check in a couple of weeks, which might fix the above anyway.
I also used an elevated command prompt to delete the Netgear Device Checking Service since this was still showing up:
The NETGEAR WNDA3200 Device Checking Service service failed to start due to the following error:
The system cannot find the file specified.
And lo behold, its first startup for ages where it was superfast, and there has not been even a single error logged.
I still have an unknown device. Which I know is most likely the ASUS motherboard monitoring thing; but since it was causing errors and its driver is known to be glitchy in Win 7 64 and serves no purpose anyway without the ASUStools, I might as well leave it there~ hurts no-one whilst it sits there unknown...
