Just giving you guys an update since you took the time to help out...
I just swapped the old 300W PSU and the XFX Card into my wife's computer, since they were originally in her computer and it played games well enough, despite the under-powered PSU. I fired up StarCraft 2 and the game performed the same as the other configurations. I started thinking the issue lies somewhere other than the PSU and Graphic Card. To test this, I swapped 500W PSU and the MSI card into my other desktop (the Dual Core with the 32-bit OS) to see how it performed. Starcraft 2 loaded fine and ran well with Ultra settings. Since both computers were back to their original configurations but the issue still persisted on her machine I believe the problem is more than a shitty PSU/Card.
Another clue to this problem is her computer BSODing itself at random times throughout the day. I asked my wife about this and she said the machine would reboot itself from time-to-time in the two years we've owned it. I checked the Event Logs and I have 52 Critical Events between Feb 2010 and Dec 2011, where 25 have been since I made the hardware swaps.
Cruising through the details of the event log, the source for all 52 errors is 'Kernel-Power', Event ID '41' and a Task Category of '63'. "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." is what most of the critical errors say.
Another interesting pattern I've found (which might not mean much) is that most of the Critical Kernel-Power events are followed with a BugCheck Error, within 30 seconds of the intial reboot. The BugCheck information says stuff like, "The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000022, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 120911-36909-01." Not exactly sure if that's significant, but I figured I'd drop it here for safe measure.
The last stuff I have to report on the issue is the results of looking at the .dmp files:
The last couple dumps... (without all the details)
Quote:
Loading Dump File [C:\Windows\Minidump\120911-29640-01.dmp]
BugCheck 50, {ffffffff90909090, 1, fffff80002a907c6, 5}
Could not read faulting driver name
Probably caused by : memory_corruption
Followup: memory_corruption
Loading Dump File [C:\Windows\Minidump\120911-28750-01.dmp]
BugCheck 109, {a3a039d8989fba11, b3b7465eeb1d895f, fffff80002f83000, 0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
Loading Dump File [C:\Windows\Minidump\120911-36301-01.dmp]
BugCheck FC, {fffff88001deb192, 800000020cc00121, fffff880055259f0, 2}
Unable to load image \SystemRoot\system32\DRIVERS\AVGIDSFilter.Sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys
Probably caused by : AVGIDSFilter.Sys ( AVGIDSFilter+34c4 )
Followup: MachineOwner
Loading Dump File [C:\Windows\Minidump\120911-36909-01.dmp]
BugCheck 19, {22, 0, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\avgmfx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgmfx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgmfx64.sys
Probably caused by : avgmfx64.sys ( avgmfx64+4a5d )
Followup: MachineOwner
Loading Dump File [C:\Windows\Minidump\120811-33197-01.dmp]
BugCheck 109, {a3a039d8989b9533, b3b7465eeb186489, fffff80002f17f40, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
Loading Dump File [C:\Windows\Minidump\120811-34523-01.dmp]
BugCheck A, {28, 2, 0, fffff80002b0fbd0}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
Followup: MachineOwner
Loading Dump File [C:\Windows\Minidump\120811-33041-01.dmp]
BugCheck A, {28, 2, 0, fffff80002b22bd0}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
Followup: MachineOwner
Two things jump out at me: AVG and Memory Corruption.
Although I've run Memory Diagnostics on that machine I decided I would do it again. I set it to Extended Testing, with Caching turned on, and I ran it for 50 passes. It took about 17 hours to run, but it didn't report any problems. I don't know of any other ways to test the RAM but I'm not sure the general 'memory corruption' cause is the result of faulty ram or perhaps some faulty software/driver. After running the test, I booted up SC2 and it was still playing like shit. A new problem I noticed is the audio puts itself on repeat...
The other thing I tried is uninstalling AVG. If it's causing critical errors then I figured it had to go. After uninstalling it, Torchlight and SC2 appear to be running better... hell, I was able to play a bit on Ultra settings (using the 300W PSU and the XFX card), but I stopped since I was just testing. I'll try to give it more game play tomorrow to make sure the game plays well. If it plays well tomorrow, I'll try to put my 500W PSU and MSI card back in her machine.
Now, my main concern here is the 'memory corruption' errors... does that mean my RAM is going to shit (even if Memory Diagnostic Tools is coming up clean) or could that have been caused by AVG?
Anyways, will update if the 500W PSU and MSI card work fine or if I have more problems.