BSOD Random

[xsolidgoldx]

Hey guys, I'm at my witts end here!
I have been trying to fix the random BSOD for a year now, I have replaced nearly every part of my computer.
It now had new ram, new harddrive, new cpu, new motherboard, new PSU (ive unplugged the dvdrive), the only things that remain the same is:
a usb port card which im gunna take out soon and see if that could be part of the problem.
Other than that I have my external devices (which I was on the impression that external devices can not cause BSOD, but perhaps im wrong?)
I have a logitech G15 Keyboard, A logitech G9 Gaming Mouse, A Logitech Fusion Webcam, Speakers, BT Homehub connected via ethernet, My screen which is a prolite E2207WS LCD, my HP Photosmart B210a Printer.

I really need some genius to tell me what the problem is!
I have a fresh, brand new operating system installed on my brand new harddrive, and i am running windows 7 (I have had this problem trying XP, Vista and Windows 7) so it is not a driver fault, it is a hardware fault, but who knows which?

I have attached the minidump files and a computer specs list generated through HWinfo32.

Please help guys! I will love you forever!!!

 

[Vir Gnarus]

You said you replaced the CPU and motherboard and it's still causing problems? Both the crashdumps report an error in your internal L1 CPU cache during a cache snoop. It is slightly possible this could come from the motherboard, but most likely it's a CPU problem. There is the offchance you may have replaced the CPU with another defective CPU. Motherboard incompatibilities may also cause the problem.

When you replaced the parts, did you replace them with the exact same model/brands as the previous ones? Are you overclocking your system in any way? In addition to answering those questions, what PSU have you been using? PSU price judges quality, and quality for PSUs isn't so much performance as it is reliability. Cheaper version PSUs (even from reputable brands) have cheaper parts in them and get increasingly more prone to failure, even from out of the box.

If you wish, you may run a battery of hardware tests, as followed:

RAM: Memtest86+ - 7+ passes
CPU: Prime95 - Torture Test; Blend; overnight (9+ hours)
GPU: MemtestCL - Run twice (if any of the tests work on your GPU; ATI cards will need to install the ATI APP SDK as it requires OpenCL)
Drives: Seatools - All basic tests aside from the Fix all or the advanced ones.

All of these (excluding MemtestCL) are included in the UBCD if you prefer a Live CD environment (which is the best environment to test hardware on). Note that Prime95 currently does not work on the UBCD. Also, please provide us temps/voltages using HWInfo with Sensors only option checked. Log two 30-minute instances: one for idle, and one for high load.

Other then that, my recommendations would be to update motherboard drivers (all of them) as well as the BIOS. In addition, uninstall all motherboard utilities and software. They have a tendency to create WHEA errors like this due to bugs.

Analysts:

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: [COLOR=DarkGreen]fffffa8004add1d8[/COLOR], Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000181, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009f1a08 fffff800`02e0aa3b : 00000000`00000124 00000000`00000000 fffffa80`04add1d8 00000000`b6000000 : nt!KeBugCheckEx
fffff880`009f1a10 fffff800`0299cc43 : 00000000`00000001 fffffa80`04ac2900 00000000`00000000 fffffa80`04ac2950 : hal!HalBugCheckSystem+0x1e3
fffff880`009f1a50 fffff800`02e0a700 : 00000000`00000728 fffffa80`04ac2900 fffff880`009f1db0 fffff880`009e9100 : nt!WheaReportHwError+0x263
fffff880`009f1ab0 fffff800`02e0a052 : fffffa80`04ac2900 fffff880`009f1db0 fffffa80`04ac2900 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f1c00 fffff800`02dfde8f : 00000000`00000000 00000000`00000001 fffff880`009f1e30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f1c40 fffff800`0288b62c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`009f1c70 fffff800`0288b493 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f1db0 fffff880`043051f2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`02f1bc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : amdk8!C1Halt+0x2


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

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

1: kd> !errrec [COLOR=DarkGreen]fffffa8004add1d8[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa8004add1d8
-------------------------------------------------------------------------------
Record Id     : 01cd05f82b1486eb
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/19/2012 17:54:15 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000040f33
Processor ID  : 0x0000000000000001

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

Local APIC Id : 0x0000000000000001
CPU Id        : 33 0f 04 00 00 08 02 01 - 01 20 00 00 ff fb 8b 17
                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  @ fffffa8004add3f0

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

Error         : [COLOR=Red]ICACHEL1_SNOOP_ERR[/COLOR] (Proc 1 Bank 1)
  Status      : 0xb600000000000181
  Address     : 0x00000000cf371900
  Misc.       : 0x0000000000000000

 

[xsolidgoldx]

Vir Gnarus, Thankyou for your excellent response! I think you may be right, it could very well be the CPU afterall, the guy i brought my cpu off suggested i installed the software that came with the motherboard as the AMD processor may have needed a patch from the motherboard software CD, I tried this not long ago, and still go a blue screen when I was downloading Adobe Master Collection CS5.5.

Every part that I changed in the computer was new, except the CPU, he had a 2nd hand one that he said should be fine but perhaps this is not the case. I think I may have even damaged the changed CPU too as in one of my fits of swapping things about, I didnt connect the cpu properlly and some of the pins got bent, but I carefully straitened them up again and reinserted. I do now believe that the CPU is to fault so Im going to go and purchase another second hand one now and I will keep you updated it this doesnt work either.

Thanks for your help

 

[Vir Gnarus]

Ack, bent pins can do it. Even if you do end up straightening them, there's the chance of permanent damage to the pins and they can no longer properly connect to the ZIF socket. They may fit inside, but they won't be flush.