New
#21
65C for a GPU isn't anything much to worry about, and 65C for a CPU is pushing it to where it'll age the CPU faster, but you're right, there's nothing here with the temperature that says it should cause these BSODs, nor is it a problem for the immediate health of the system (though 65C for CPU is pretty high). Rather, it really depends on if you are comfortable with those temperatures. If not, you'll want to step it up on the cooling a bit to make sure it doesn't reach that point. Temperature just shouldn't be something that you should be thinking about when using your system. A truly stable system is one that can be pressured for any length of time by the applications it's running without the user having to worry about it breaking down from the stress, and it appears yours just hasn't quite reached that level. I'm just saying this for your own sanity; you'll feel a lot better not having to worry about temp unless something bugs out like a fan, in which case that is when you'll have HWMonitor/Speedfan ready to alert you before it actually becomes an issue for the health of your system.
Anyways, Driver Verifier, once setup and the system restarted afterwards, will stay 'on' permanently unless you go in and manually turn it off, or you use System Restore to restore it to a point prior to DV being activated. Driver Verifier itself is really just a frontend for setting up extra driver checks built into Windows that are used for diagnostic purposes. It just makes Windows more paranoid with what drivers are doing, and if it find problems, it will do what it usually does when it finds one, and that is BSOD. The crashdumps generated from it will help us pinpoint the problem better.
What you'll want to do is just turn on Driver Verifier, restart the PC, verify it's on by going into Command Prompt and typing verifier /query or open DV again and select "Display existing settings", and once you find it's successfully on and going, just use the computer as normal. If it crashes again, provide us the crashdump. Obviously because of the extra checks, things may end up running a bit slower, so you'll have to deal with that.
The concern I have is that if DV has been on and hasn't 'found' anything yet, is that it may be hardware related, in which no amount of driver checks is going to discover. Of course, I'm crossing my fingers on it being the AVG/Spybot (wouldn't doubt it on AVG, it's done it to others before).