Rare BSOD became far too common

Will someone PLEASE look at the latest W7F reports?

EDIT: Checking through the Event Viewer, I get these warnings for Diagnostics-Performance:

The Desktop Window Manager is experiencing heavy resource contention.
Reason : Graphics subsystem resources are over-utilized.
Diagnosis : A consistent degradation in frame rate for the Desktop Window Manager was observed over a period of time.

The Desktop Window Manager is experiencing heavy resource contention.
Scenario : The Desktop Window Manager responsiveness has degraded.

Windows has shutdown:
Shutdown Duration : 31307ms
IsDegradation : false
Incident Time (UTC) : ‎2013‎-‎02‎-‎27T23:24:49.470450300Z

And errors including:

Windows has started up:
Boot Duration : 69709ms
IsDegradation : false
Incident Time (UTC) : ‎2013‎-‎02‎-‎27T22:17:45.718400400Z

Another one, also:
This driver responded slower than expected to the resume request while servicing this device:
Driver File Name : \Driver\usbehci
Driver Friendly Name : EHCI eUSB Miniport Driver
Driver Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Driver Total Time : 1952ms
Driver Degradation Time : 1552ms
Incident Time (UTC) : ‎2013‎-‎02‎-‎14T21:57:46.601827500Z
Device Name : PCI\VEN_1002&DEV_4396&SUBSYS_83891043&REV_00\3&267a616a&0&92
Device Friendly Name : Standard Enhanced PCI to USB Host Controller
Device Total Time : 1998ms
Device Degradation Time : 1598ms

This driver responded slower than expected to the resume request while servicing this device:
Driver File Name : \Driver\usbohci
Driver Friendly Name : OHCI USB Miniport Driver
Driver Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Driver Total Time : 1942ms
Driver Degradation Time : 1542ms
Incident Time (UTC) : ‎2013‎-‎02‎-‎14T21:57:46.601827500Z
Device Name : PCI\VEN_1002&DEV_4399&SUBSYS_83891043&REV_00\3&267a616a&0&A5
Device Friendly Name : Standard OpenHCD USB Host Controller
Device Total Time : 1998ms
Device Degradation Time : 1598ms

The start-up/shutdown ones and the graphics ones seem to come from the new install date, 13/2/13, while the unresponsive drivers are an isolated event. This doesn't look good at all...

I've looked at both the attachments, and have a few questions:

1. Can you explain the entries in your HOSTS file?

2. Your first attachment contains this information:

Code:

Host Name:                 PARENTS-PC
OS Name:                   Microsoft Windows 7 Professional 
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Parents
Registered Organization:   
Product ID:                00371-177-0000061-85980
Original Install Date:     18/04/2011, 18:24:01
System Boot Time:          09/02/2013, 10:00:19
System Manufacturer:       System manufacturer
System Model:              System Product Name

Your second attachment contains this information:

Code:

Host Name:                 PARENTS-PC
OS Name:                   Microsoft Windows 7 Ultimate 
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Parents
Registered Organization:   
Product ID:                00426-OEM-8992662-00173
Original Install Date:     11/02/2013, 22:07:24
System Boot Time:          23/02/2013, 10:04:12
System Manufacturer:       System manufacturer
System Model:              System Product Name

Lets check to ensure the current installation is correctly activated:

1. Download and save this tool to your desktop:
http://go.microsoft.com/fwlink/?linkid=52012

2. Run the tool, and then click 'Copy' - ignore any errors if they appear

3. Use CTRL+V to paste the unedited results of the validation tool here in your next reply

I'll repost the reports, the first ones were from the previous install, which was from May/June 2011 (plus the computer threw a tantrum last night with a heap of BSOD events, so those need to be looked at). That install was completely wiped out because we replaced the harddrive, now using Windows 7 Ultimate. If you want to, look at the reports generated in the first attachment, but since it was using a different install, it might not be too helpful. Only those 23/2/13 onwards will be using the new install, since the 13/2/13 is when my brother returned the computer (it was taken on the 11/2/13 for reinstall/new harddrive). If you check my attachment on the 23/2/13, it may list different drivers since a change was made on the 25/2/13 to drivers, and Windows was updated (wondering if we shouldn't have removed some of those drivers after all...but my brother states the Atheros NIC driver we uninstalled was network-related, not graphics or desktop related).

Basically...yeah, it may be wise to disregard any attachment before 23/2/13 because it was using the previous install, hence the different OS. I do consider that the error reports may still be valid and it wasn't a harddrive issue afterall (there are similarities, especially the randomness to the error generated and the fact it continued after getting back into Windows and not being in a game). The harddrive may have simply been a very lucky catch, an accident waiting to happen that we fixed before it really did anything.

Last night, after running Skyrim for ~10 minutes, it went. No reboot, had to turn off then back on. Not even the reboot button would work. Then, in Windows, I barely got a look at bluescreenviewer, and bam! Then tried to boot in safe mode, had no idea what to do, so continued using defaults, had to turn off because it did nothing. Got it back into Windows normally, and after 5-10 minutes checking over the errors, bam! The BSOD errors seem to be all over the place, as they were before.

Unfortunately, my brother is going away for 3 weeks on Sunday, so I can't muck about too much at the moment. I'm suspecting those errors about the graphics subsystem point to a problem with the graphics card or drivers (it happens with other games too).

You've forgotten to attach the MGADIAG report - please provide as requested.

Also, lets look at the hardware you are using:
System Info - See Your System Specs

Golden said:

You've forgotten to attach the MGADIAG report - please provide as requested.

^^^