A little update, I runned Drier Verifier and it caused BSOD on startup. So the problem has to be a bad driver, but which one...
PS. Then I manage to jam my BIOS and had to clear CMOS. Then I spend an hour struggling with re-installating NIC drivers and I was confused why it was no longer working, did I break something while clearing CMOS. Then I noticed that the date was 2089 and that's why the driver installation didn't work.
... And after several reboots and Driver Verifier variations I have narrowed the boot BSOD 0xC9 (or something like that) to be one of these drivers:
aswfsblk.sys
aswmonflt.sys
aswrdr.sys
aswsp.sys
aswtdi.sys
All of them are from ALWIL Software (Avast), so I'm a bit doubtful is that Driver Verifier really working? Without putting those drivers to the list, the computer will boot up nicely without BSOD all the way to windows, but if I have those drivers in the list, it won't even manage to start windows properly.
Driver check also gave me crash with rivatuner, so I removed it. Thinking about it, RivaTuner could have been the cause of crashes. But I still don't like the BSOD with Driver Verifier though...
Uninstall Avast completely, then run its removal tool: http://files.avast.com/files/eng/aswclear5.exe
Then download and install Microsoft Security Essentials.
I'll do that tomorrow, it's early morning here already. :)
So, I can fully trust on Driver Verifier? If it's say it's bad, it has to be bad?
Driver Verifier is reliable, yes. That doesn't always mean the dmp will point to the cause, so the best you can do is try it.
RivaTuner removal seem to be done the trick. No BSOD since yesterday and I've been encoding two videos, previously it crashed everytime after 1h, and I've playing games, no problems. :)
I left Avast there, even though there is that Driver Verifier issue, as long as there is no BSODs coming.
Thanks for guys for the help. :)
Quote