I had trouble installing a network printer in my room due to temperature issues. The computer ran okay but would not install the printer. Is it hot in your room as well?

<edit> For fun, can you save the screen as a screen saver?

That's weird. I don't see a BSOD error code, least not a normal one

I just recently had my machine BSOD'ing quite often. I tracked the cause down to my wireless USB adapter and had to replace it. I also saw that BSOD a while ago last time my HDD crashed. The BSOD was almost identical to the one in your pic, so I'd say it's definitely a hardware issue.

Memtest is much more convenient than pulling random sticks and waiting for a crash. It's more definitive as well.

I've found your problem: You're using Windows.

But seriously, looks like a driver problem. Try reinstalling any applicable drivers. If that doesn't help, reinstall Windows.

This is Microsoft.

Now how dare you name my password out loud?! I trusted my password to your system, and you say it out loud?! I have problems with remembering these letters, so what?!

Erm, I must note that all Win7 BSODs look quite similar..
However, I see no reason for a hardware failure to occur the moment the system has the least load.. I've more of that feeling it's related with Win7 backward compatibility issues.

Are there any tests can be done without burning stuff and booting it?

Sounds good, I'll update my graphic card driver.

Any modern game with intense graphics challenges a well performing system's cooling system.. It's normal IMO.

P.S:

The reason I do not want to revert settings back to stock, is as follows:

1) I do not like the idea of having voltage of my CPU auto-adjusted, jumping high above any imaginable normal.
2) There's a huge number of settings in BIOS related with 2x clocks, 3x voltages and a countless number of other settings(especially memory stuff), and I found the "BIOS Profile" failing once, which forced me to restore all settings manually, which wasn't much of fun.. When I was busy with the adjustments, I ended up writing setting values down to a notebook.
3) The video card has its 2d clocks reduced using a BIOS flash, repeating this operation 2 more times isn't something one would be happy to do, especially without a UPS.
4) As mentioned above- the issue comes when the system isn't on "heavy duty", but.. In ancient games. However, it seems like the issue for Starcraft was solved using "compatibility adjustments"(in the executable's launch properties). However, I can't be sure as the error had never been anything regular, during all the countless hours I played it, I had the error maybe 4-8 times + once with "Overgod"(by Linley Henzell(so I didn't even play that game, only browsed it's settings))..

So reverting everything back, is a huge chunk of work which is likely not to come out useful.. I'd like to avoid it. I'll update drivers asap, but I may not know soon if it was any useful..

I'd like to really find out what the problem is, not just fix it.

P.P.S:

Could you link me somewhere I could get some well compiled information regarding the topic?

Thanks..

Thanks, crap though:

And if in three words- any low level application, e.g. that 256color emulation at 640 x 480, antivirus- easily(evil Kaspersky), driver also easily.. Jeez.

Append: driver updated.. Cute fact the software is 2 days old

They're all blue with white letters on'em

By default CPU voltage is automatically set by the motherboard which has very strange methods to identify the needed voltage so that I've had it outputting much higher values than I could imagine risking while I OC.

I almost agree, although I doubt my system would boot with everything on default settings.. But yes, it wouldn't be too much pain to reset it & fix voltage- I agree.

Erm. Guess you're right sir.

Append:
WOOOOOOW!
The update really rox!
I've had some nasty color bug in the menus of starcraft, now it's all original colors & it looks awesome!
Append1:
After an alt tab it got ruined though, and broke my mouse cursor..
Append2:
And after restart, it's still ugly again

Google for "save cmos to file". You could write it yourself except Windows NT won't let you read/write arbitrary hardware ports without some sort of device driver.

Huh?

Well, perhaps an option.

It's never is though.. At least so I heard a lot, and seen by third party tools measuring voltage- my mobo was overvloting the CPU, not like it has had any real effect on anything.

All default voltage & clock settings will boot and most likely work stable, but I'm quite sure it won't find the raid to boot from, unless pointed at it.. Also some devices are disabled I think(e.g. plugged in sound card + stock so one disabled) etc'

Look at your screenshot (didn't pay much attention to this meself actually), but note how big the *** STOP line is. Seems you're running 64-bit as well.

The way to know if it's a driver is something like that (afaik):

-Activate memory dump (google for it)
-Wait for a crash (i.e do your usual stuff)
-Boot the computer and get the dump. (I suggest you to take a look at that: http://www.google.fr/search?hl=fr&ei=3MMATK2GF8mG4QbM-O3LDg&sa=X&oi=spell&resnum=0&ct=result&cd=1&ved=0CBkQBSgA&q=analyzing+minidump&spell=1)

If it's a program/driver who's causing the bsod, you'll have the name of the faulting componant.

Else, it's an hardware failure and you're stuck to what I've already said: manual testing of each memory row.