BSOD started after cleaning out computer dust & installing gfx driver

Hi guys,

I've attached the dump file as specified here: Blue Screen of Death (BSOD) Posting Instructions

Things I did leading up to when it first started.

1) Updated to NVIDIA drivers v 337.88.
2) BSOD started, rare and infrequent.
3) Happened again, so I took out my PC and cleaned it out with aircan.
4) BSOD started happening more frequently.
5) Also crashes and get CPU Temperature error at BIOS beginning which won't let me start. I used real temp and also ran prime95 and got the following result using Blend torture test:

[Sun Jun 08 16:34:10 2014]
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!
Self-test 448K passed!

Now the BSODs seem random, at least I haven't found a common pattern between them all. Any help would be appreciated

Code:

BugCheck 124, {0, fffffa8006fe3028, be000000, 800400}

You have had a 0x124 bugcheck which indicates a fatal hardware exception has occurred.
The first parameter is null which indicates a Machine Check Exception has occurred, this means the CPU found a fault with a piece of hardware which results in a system bugcheck.
The second parameter is the address of the WHEA error record.

Code:

0: kd> !errrec fffffa8006fe3028
===============================================================================
Common Platform Error Record @ fffffa8006fe3028
-------------------------------------------------------------------------------
Record Id     : 01cf836982ce69a3
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/8/2014 22:32:27 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8006fe30a8
Section       @ fffffa8006fe3180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000206a7
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8006fe30f0
Section       @ fffffa8006fe3240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : a7 06 02 00 00 08 10 00 - bf e3 9a 1f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8006fe3240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8006fe3138
Section       @ fffffa8006fe32c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 0 Bank 3)
  Status      : 0xbe00000000800400
  Address     : 0x00003800043b0a30
  Misc.       : 0x000000000003ffff

Internal Timer error, this may well be hardware but we can't say for certain.
My best bet is to test them all.
Make sure you STOP overclocking!

Stress test your CPU with Prime95

I recommend running Prime95 for around 2 hours

   Warning

As with most stress tests your component's temperature will rapidly increase.
It is advised that you download a temperature monitoring program like HWmonitor
Keep an eye on your temperatures and stop the tests if it starts to overheat

Stress test your graphics card with Furmark

I recommend running it for around 30 minutes

   Warning

Furmark will increase the temperature of your GPU rapidly so keep and eye on your temperatures

Memtest86 will test your RAM

   Information

Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing

Run a Disk Check to scan for errors

   Note

Afterwards go into an Elevated Command Prompt (Run as administrator) and type in sfc /scannow
If it finds errors reboot and run the scan two more times

Run SeaTools to see if your HDD or SSD is failing

Post back the results.

I noticed this in your dump file.

Code:

0: kd> !sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3399

Although it is only slight I am not convinced that this is normal so I recommend you remove this overclock if you have set it.

However, I have my doubts about hardware being the culprit seen as there are plenty of other bugchecks pointing to software.

Code:

Unable to load image \SystemRoot\system32\DRIVERS\eamonm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for eamonm.sys
*** ERROR: Module load completed but symbols could not be loaded for eamonm.sys
 eamonm+0x1f2fa

ESET Amon driver is causing issues.
ESET is an anti virus program I believe, remove it.

Replace it with MSE and Malwarebytes.

Microsoft Security Essentials - Microsoft Windows

Malwarebytes | Free Anti-Malware & Internet Security Software

   Tip

Make sure you don't enable the free trial of malwarebytes pro, deselect the option when prompted.

Code:

Unloaded modules:
fffff880`0c306000 fffff880`0c33c000   WUDFRd.sys
fffff880`01dd1000 fffff880`01ddf000   crashdmp.sys
fffff880`04246000 fffff880`045e0000   dump_iaStor.
fffff880`045e0000 fffff880`045f3000   dump_dumpfve

Intel Rapid Storage Technology is known for causing BSODs.

Uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "Disc Drives" by clicking on the triangle in front of it.
5. Select one item under it, right click, uninstall.
6. Continue the process for all items under "Disc Drives"
7. Now restart the computer. At restart, windows will auto configure the appropriate system driver, msahci.sys.

Code:

Unable to load image \SystemRoot\system32\DRIVERS\Soluto.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Soluto.sys
*** ERROR: Module load completed but symbols could not be loaded for Soluto.sys
 Soluto+0x46fa

Soluto is causing issues.
Remove this software completely.

Code:

DAEMON Tools Lite	"c:\program files (x86)\daemon tools lite\dtlite.exe" -autorun	Chris-PC\Chris	HKU\S-1-5-21-1570782980-2639801359-2538168383-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Daemon Tools/Alcohol is known cause of BSODs, you will have to find an alternative as there is no way around this.

Registry and SPTD problems | DAEMON Pro Help
How to remove sptd.sys from system

1. Uninstall Daemon Tools.
2. Download the SPTD standalone installer and follow these steps:
3. Double click the executable to open it
4. Click the button shown below



If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.

Code:

Unable to load image C:\Program Files\ESET\ESET NOD32 Antivirus\em006_64.dat, Win32 error 0n2
*** WARNING: Unable to verify timestamp for em006_64.dat
*** ERROR: Module load completed but symbols could not be loaded for em006_64.dat
 em006_64+0x18f4

This I believe is a data file for ESET anti virus, remove it as instructed previously.

Use Revo Uninstaller to software that can cling to your computer. Use Advanced Mode to remove leftover registry entries:

Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Run a disk check to check for system errors and bad sectors which can cause issues:

Disk Check

Use Kaspersky's TDSSKiller Anti Rootkit utility

Anti-rootkit utility TDSSKiller

Free your startup, remove all unnecessary programs from launching when you first login.

Startup Programs - Change

At idle temperature? That's very hot, it wouldn't surprise me.
Continue with the other steps.
The best thing about MSE is that it isn't a resource hog and it has never been known to cause issues.

It's been 5 days, no BSOD since I did all the removals. CPU temp runs around 50-60c when I'm using it (nothing intensive but I do have a few programs open) and 30-45c when idle.

That's good news, keep me posted :)