Random BSODs

Restart manually and then execute the SF diag tool again. Let us see if the dump got recorded or not.

There are six new BSODs, and all them are 0x7F (not DV enabled, obviously. If DV is enabled, the Default bucket ID shows it.)

According to Carrona.org, STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Usual causes: Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

Here, for your case, the service pack is not missing. And your virus scanners are MSE and MBAM, which are not the issues. No third party firewall is not visible apparently. No SCSI in use. Network (Atheros and realtek) are up to date.

So check for the rest.

1. If possible, disable the Virtual WiFi adapter.
2. If the 4 GB is more than one module, make it sure the FSBs are matching.
3. Test your RAM modules for possible errors.
   How to Test and Diagnose RAM Issues with Memtest86+
   Run memtest for at least 8 passes, preferably overnight.
4. As you are getting BSODs, you should stop overclocking (if it is present there) and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
   How To Clear CMOS (Reset BIOS)
5. Do some Disc checks.
   
   • Run chkdsk /f/r, following the option two of the tutorial Disk Check
   • Seatool for dos: SeaTools | Seagate download
   • Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
   
   
6. If you have any BsckUp tool, Uninstall it.
7. If all of them works good, you should contract the vendor, as your's an OEM license which is tagged with the motherboard.

There are three verifier enabled dumps, and only one caught a problem, Intel(R) HD Graphics.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88007530004, 1, fffff88004c8a74b, 0}

*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys

Could not read faulting driver name
Probably caused by : igdkmd64.sys ( igdkmd64+6774b )

Followup: MachineOwner
---------

And the driver is kinda old.

Code:

fffff880`04c23000 fffff880`057e1140   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Tue Jul 31 23:20:01 2012 (50181AC9)
    CheckSum:         00BC426F
    ImageSize:        00BBE140
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update the Intel HD Graphics Driver, either from our forum link, Latest Intel HD Graphics Driver for Windows 7, or You may get it from Intel Download Center.
Moreover, you may run the Intel (R) Driver Update Utility to auto detect the appropriate driver for your computer.

Probably I have suggested it to you earlier. Drivers are not updated still.
Only crash dump analysis other than action will not lead to a solution at all.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Just a suggestion, you could at least shake off that laziness and buy a CD in order to eliminate
the HDD as an issue, after Arc's hard work in analysing your issues :)

Perhaps re-reading through the thread and checking you have indeed followed the fixes and
installed the drivers suggested may help in fixing your issue.

cheers

Dave

Yeah, this stuff does smell of corrupted installation media to me too. The only thing you need is the sticker, follow tutorial posted by gregrocker.

Yes well laziness aside seems like you are impatient one minute slack the next so I would go with Greg but try a run with this.


http://www.bleepingcomputer.com/download/adwcleaner/

download from bleeping computer

if I missed it a sfc would be handy SFC /SCANNOW Command - System File Checker