BSODs for the BSOD throne

In June, I built myself this computer. It bluescreens occasionally, but there isn't a pattern and my usual debugging methods didn't work, so I just sorta lived with it.

Average time is around two hours, but I've seen it crash seconds after restarting, and I've seen it go all day with no issues.

Recently, I decided I was fed up with it, so I completely reinstalled windows and then only installed the absolute basics; graphics drivers, a couple video games, and firefox. The crashes became much less frequent but they're still happening. There still isn't a pattern to them.

So, to sum up:

64 bit
Original system
Full Retail copy
Age of hardware: 6 months
Age of most current win7 installation: 3 days

Maguscreed said:

Yeah, they're ntoskrnl errors, which is basically what windows throws up when it's stumped.
I would like to see if driver verifier can make this a little more specific for us.
Driver Verifier - Enable and Disable

Hoping that will turn up a few more specific dumps.

Your nvidia drivers are up to date, but just about everything else seems to have been neglected. I'm guessing you know how to find drivers since the nvidia is up to date at least.

I had been following the train of thought:

1. Computer hasn't crashed in safe mode
2. Therefore, it must be a non-windows software issue
3. It crashed shortly after I installed windows
4. Therefore, something I installed shortly after windows
5. The first thing I did was to update all my drivers!
6. ONE OF THEM WAS PROBABLY EVIL, LETS NOT UPDATE THEM AND SEE IF THAT HELPS

Will run the program you suggested as soon as I get back from class

Maguscreed said:

Yeah, they're ntoskrnl errors, which is basically what windows throws up when it's stumped.
I would like to see if driver verifier can make this a little more specific for us.
Driver Verifier - Enable and Disable

Hoping that will turn up a few more specific dumps.

Your nvidia drivers are up to date, but just about everything else seems to have been neglected. I'm guessing you know how to find drivers since the nvidia is up to date at least.

Okay, I followed the steps, but the verifier hasn't popped up or anything. From the verifier topic, it looks like I won't see any sign that the verifier is running until there's a problem, so I should just proceed as normal? Can do.

Just crashed, but it didn't BSOD.

After two hours of normal use (That is, I let it sit there for an hour, and then started playing company of heroes) the screen froze and the sound was replaced by buzzing. Normally a freeze and a buzz is immediately followed by a BSOD, but in this case, it progressed at a rate of one frame every few seconds, with the buzzing changing in pitch to match.

I pressed CTRL-ALT-DELETE and the screen turned black, the speakers played a series of beeps, and then the CTRL-ALT-DELETE screen appeared as normal. I pressed "Start task manager" and the computer froze and was unresponsive for ten minutes, at which point I rebooted.

There doesn't seem to be a new minidump, presumably because it didn't BSOD.

Maguscreed said:

That almost sounds viral. Have you scanned with a up to date antivirus lately?
If not just grab the free version of this and give it a spin.
Malwarebytes

I installed Avast earlier today, and after I read your post I told it to run a full scan. After a couple minutes, I got a BSOD mentioning an attempt to write to read only memory.

The usual "preparing dump" meter usually flies up to 100 in about a second, but this time it stopped at 25 and stayed there. I punched RESET and told windows to boot up normally.

It got most of the way through the reboot process before BSODing again to "IQRL_NOT_LESS_THAN_OR_EQUAL"

A second RESET had the computer start to boot up normally, but then just sit at the loading screen with the softly pulsating windows logo.

A third RESET started the computer normally.

I'll edit the message and attach the new dumps as soon as the weird dump-finding .exe finishes doing its thing.

It might be worth downloading TDSSKiller and running it in Safe Mode. You've nothing to lose!

While the BSOD-thing was running it crashed again, so I restarted in safe mode to run it. New files attached here.

Going to let Avast do a full scan, as long as I'm sitting in safe mode.