Solved Randomly getting BSOD

[muldy29]

Just randomly getting BSOD, have re installed Windows 7 and that hasn't fixed it, so over to you guys
Zip file attached
The time before last that I got a BSOD, the screen was blue, then it went to Vertical Black and white lines instead of blue

 

[muldy29]

Just gone again

 

[carwiz]

 ===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007d76148
Section       @ fffffa8007d762d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
 Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xb200004000000800

Your Bug Check is being caused by a hardware fault. More specifically, the L0 cache in the CPU. This may be caused by an overheated or damaged CPU. There's a couple of steps you could take if you feel comfortable doing maintenance on the inside of your PC. First would be to give it a complete cleaning and removal of dust. Next would be to remove the CPU cooler or heatsink, clean them and apply new heatsink compound. If this is not something you feel qualified to do, the best course of action would be to take it to a service center and have them perform the cleaning.

BIOS Version: American Megatrends Inc. V1.10, 04/09/2009
You might also check to see if there's a BIOS update for you system.

 

[muldy29]

Been fine, now gone again

Have replaced the heat sink and fan with an Arctic Cooler, running at around 50 degrees normal now.
No BSOD for almost a week, then tonight it just goes, is it still the same thing?

 

[carwiz]

Looks the same. Examine the area around the CPU socket carefully and make sure no heat sink compound is on the board. Also check for dark areas on the board.

From the dump:

 WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80071fc8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

 ===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80071fca08
Section       @ fffffa80071fcb90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
 Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xf200004000000800

And from the event log:

 Event[138]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2013-12-08T20:54:49.902
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Tony-PC
  Description: 
A fatal hardware error has occurred.
 Reported by component: Processor Core
Error Source: Machine Check Exception
[B][COLOR=blue]Error Type: Bus/Interconnect Error
Processor ID: 0[/COLOR][/B]
  
 Event[139]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2013-12-08T20:54:49.918
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Tony-PC
  Description: 
A fatal hardware error has occurred.
 Reported by component: Processor Core
Error Source: Machine Check Exception
[B][COLOR=blue]Error Type: Bus/Interconnect Error
Processor ID: 2
[/COLOR][/B]

 

[carwiz]

I forgot to mention: It looks like the cores on one side of the chip (cores 0,2) are having the problem. You might verify that your compound is evenly spread and not too thick. No compound is better than too much. The compound should be very thin and evenly spread. While you're in there, re-seat your CPU and check the board under it for dark areas.

 

[muldy29]

Ok, have replaced the heatsink with a better one and the system was fine until tonight, playing WoW and PVPing and boom BSOD, then on reboot another BSOD in an endless cycle, Tried System repair and it said it couldnt fix the problem automatically, then on reboot, i got into Windows, can you guys help again? Attached is the zip from just now, after i got back into Windows

 

[carwiz]

There's no dump(s) in your upload.

I looked at the system log and it's showing what could be power or disk fault shutdowns and at each restart it's showing some strange filter driver results. We'll need to approach the problem from several paths but it's critical that you perform the steps below, in order, to attempt to establish a stable system. As a side note, you have an application called Flux that is by some considered trojan malware. It has a backdoor link to your system and uses any camera attached. It also sends data to an IP address in China. Item #1 below should disable it and a few other questionable/suspect applications for the time being. (Apple Daemon, Fitbit and Garmin Express) These can cause instability.

1. Control Panel\All Control Panel Items\Administrative Tools > Right click System Configuration and select Run as Administrator > Click Startup Tab
Uncheck all items EXCEPT Microsoft Security Essentials (MSC). Click OK and reboot. Leave these settings until the completion of this thread.

2. Run a disk check (chkdsk) with repair on drive D: first. When it completes, run the check on drive C:. (This will require a restart to begin.)

3. Run SFC /scannow from an elevated command prompt taking special note that if it finds errors, you may need to reboot and run it again. If/When it completes with no errors, continue with the next step. If you still get errors after three runs, report back and STOP here.

4. Download and run AdwCleaner then reboot. Report back with the results of that scan. (Attach the list)

 

[muldy29]

1. Done
2. Done, no errors on both drives
3. No errors on first scan
4. # AdwCleaner v3.203 - Report created 26/04/2014 at 19:12:32
# Updated 26/04/2014 by Xplode
# Operating System : Windows 7 Home Premium Service Pack 1 (64 bits)
# Username : Tony - TONY-PC
# Running from : D:\Users\Tony_2\Downloads\AdwCleaner.exe
# Option : Scan

***** [ Services ] *****


***** [ Files / Folders ] *****

Folder Found C:\Users\Tony\.android

***** [ Shortcuts ] *****


***** [ Registry ] *****


***** [ Browsers ] *****

-\\ Internet Explorer v11.0.9600.17041


-\\ Google Chrome v34.0.1847.116

[ File : C:\Users\Tony\AppData\Local\Google\Chrome\User Data\Default\preferences ]

Found [Search Provider] : hxxp://uk.ask.com/web?q={searchTerms}

*************************

AdwCleaner[R0].txt - [725 octets] - [26/04/2014 19:12:32]

########## EOF - C:\AdwCleaner\AdwCleaner[R0].txt - [784 octets] ##########

 

[carwiz]

Ok, run a full scan with Malwarebytes Antimalware. Use the free version and make sure the install doesn't have any additional add-ons such as tool bars, etc. After starting don't click on the trial or the activate. Let it update then run the scan.

Is the system stable with the configuration from #1 above?

 

[muldy29]

yes, so far and with the Bing desktop and Battle.net app running and the 2 for Razer keyboard and mouse

 

[carwiz]

I would run it like that for a day or so. If it remains stable, you know the problem is with one of the startup applications. After a day, add back (uncheck) ONE and check stability for a another day or so. Continue doing this until the culprit if found but I'm betting on the Apple Daemon. Once you find the offender, check to see if there's an update for the software. Keep us posted on the results. Working without a dump makes diagnosis a trial and error procedure (and sometimes with it). And, I would seriously consider living without Flex. Depending on what display you have, the "feature" may be built in.

 

[muldy29]

Thanks for the help, Now have a new Motherboard/Processor and have a new Windows install, so hopefully that should be the end of it all