Yeah my bad,I said from the beginning three programs do this. Of course not using them stops it. Doesn't fix the problem.
Okay, I just uninstalled Avast, the Intel Management Software and the NVidia graphics drivers. I restarted, installed (in this order) the INF driver, the Intel Management, both for Windows 7, and then the NVidia.
Curiously, restarting with no NVidia didn't look any different, but I confirmed it was gone before going on. Now I'm going to turn MR Shifty on. Before, it would consistently Bluescreen me within a minute, so will edit to let you know.
Edit: Bluescreened. Curiously, when the PC restarted, my icons weren't rearranged as they normally would have been. Not sure if that means anything to you. Here's the crash report.
I like Avast, so happy to rule it out as the problem. I guess testing the ram and psu is redundant, as I'm replacing both to fit in a newer motherboard.Hey there -- just wanted to check up on this and see if you've made any progress. It doesn't sound like Avast is involved in these errors you're seeing but if you ever do need any help, please reach out to us.
I've seen any kind of issue with games crashing you can think of (BSoD, PC won't even post, garbled screen effects, etc) and it's usually due to the program itself, or something in the hardware. From skimming the thread it looks like you've tried updating your BIOS, have you checked other areas of the hardware, e.g. doing a RAM test and checking your PSU? Just some other ideas to try. Again, we're here to help if you need support with Avast.
I like Avast, so happy to rule it out as the problem. I guess testing the ram and psu is redundant, as I'm replacing both to fit in a newer motherboard.
If that doesn't fix it, I'll be pretty upset.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff800038d426f, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiDivideErrorFault+af )
Followup: MachineOwner