BSOD Minidumps attached. Please Help

Just a bunch of thoughts here:

Are you overclocking? If so, please return everything to the default values. Overclocked hardware doesn't lend itself well to troubleshooting - so you've got to ensure that the system is rock stable at default values before troubleshooting an overclock.

BSOD analysis is a driver oriented process. As I "specialize" in BSOD's, I frequently lose sight of the other things that can be causing these issues. Don't be quick to blame a driver - there's many other things that could go wrong.

Windows 7 is very sensitive to storage drivers (I have to buy a new RAID controller because of this).

Don't use registry cleaners - I have personal experience with them hosing several systems. Here's an interesting article about the registry that was written when XP came out - and it also applies to the Vista and Win7 registry's: XP Fixes Myth #1: Registry Cleaners

I don't like to mix IDE and SATA drives. Especially something as old as a 60 gB. I had problems with this back in the XP days - and haven't messed with it since.

Since the BSOD's occur with all OS's, I wonder if there's a compatibility issue with something connected to your system (or that something connected to the system is malfunctioning)?

I wonder if there's any issues due to the voltage of your RAM? I'm not real familiar with RAM stats, but I'd check it out and lower the voltage if necessary.

I'm not familiar with the Ultra power supplies, so I'd suggest checking the outputs with a voltmeter.

If, on the fresh install, you've installed all of your drivers and have updated Windows - then the problem is most likely hardware. As I mentioned above, this can be a compatibility problem, a hardware item failing, or even an overclock.

My gut tells me that this is important:

I know that on my Win7 installation, my NTFS file system was corrupted somehow. I either blame a registry cleaner or Kaspersky for that lol.

Registry cleaner's can't be blamed for this, and I haven't seen Kaspersky do this in the past (but it is possible). I think that this points to the issues in the previous paragraph.

So, to summarize (and add):
- If you're overclocking, reset to defaults and wait for BSOD's
- If you're using Asus utilities on the Windows 7 install - uninstall them (they cause problems!).
- If not overclocking, let me know and we'll try a shot at running Driver Verifier (with the settings that have been recommended to me).

You can get PSU testers for about $10 (US) if you shop around. I've got one that I use occasionally - but it's a PITA to carry around. I've taped a copy of the PSU pin-outs to the inside of my pocket multimeter and use that instead (multimeter cost $25 US).

There seems to be issues with Media Center and video games (we disregard the stress test since it's testing everything that it can). So, I'd suspect that it's something video or audio - with maybe memory being a factor. If these things are working with the internet - then we can add network stuff to the list. If we presume that this is a hardware problem (because it occurs in multiple OS's), then we've gotta add the mobo to the list (and the PSU until you test it).

How did you determine that the errors in Team Fortress 2 were due to paged pool memory or your memory timings? Also, does Everest have a log file that it generates during it's testing? Even a log that stopped when the system crashed can be useful.

FWIW - Have you checked the temps on the northbridge and the video and audio cards? At work the other day I accidentally burnt my finger on a video card. It's fan was working, so I thought that this was unusual. Since the system was shutting down on us I pointed a spare 80mm fan at the video card and, amazingly, the problem vanished! This could be the problem with any one of several devices on your system (the most common being video cards and northbridge chipsets - but I'd think that the audio card could suffer from this also).