BSOD Out of the Blue

Random and just started. Went out of town for a week. Came home and boom. BSOD. Crash program says hardware, but how do I narrow it down to WHAT hardware?

Minidumps below

yea this can jst happen ,,then it could go away as quick as it cam, I had alot blue scree death on my vista ,windows 7 has bee na dream so far.
What i done was restore to a time before i done any major changes ,so if you changed something go back maybe a lil before then using system restore.
Or if that fails try a factory restore /Clean install from disk

I'm guessing either your memory or hard drive is causing the issue.

Download a copy of Memtest86 and burn the ISO to a CD using ImgBurn. Boot from the CD, and run at least 5 passes.

Also, see this page: Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.

Download the appropriate tools for your hard drive and run a test.

Yes, it does matter. Download the version that support 4 GB or more of RAM.

This is what I see:

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\Desktop\030210-39468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0845a000 PsLoadedModuleList = 0xfffff800`08697e50
Debug session time: Tue Mar  2 18:24:15.508 2010 (GMT-5)
System Uptime: 0 days 3:45:58.568
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004fbb038, b6000000, 181}

Probably caused by : hardware

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

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: fffffa8004fbb038, 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:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009efa08 fffff800`08423903 : 00000000`00000124 00000000`00000000 fffffa80`04fbb038 00000000`b6000000 : nt!KeBugCheckEx
fffff880`009efa10 fffff800`085e0513 : 00000000`00000001 fffffa80`04fbbea0 00000000`00000000 fffffa80`04fbbef0 : hal!HalBugCheckSystem+0x1e3
fffff880`009efa50 fffff800`084235c8 : 00000000`00000728 fffffa80`04fbbea0 fffff880`009efdb0 00000000`00000000 : nt!WheaReportHwError+0x263
fffff880`009efab0 fffff800`08422f1a : fffffa80`04fbbea0 fffff880`009efdb0 fffffa80`04fbbea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009efc00 fffff800`08416e8f : fffffa80`0745c478 00000000`00000001 fffff880`009efe30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009efc40 fffff800`084ca7ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`009efc70 fffff800`084ca613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009efdb0 fffff800`084d5b62 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`02f1b560 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiTimerWaitTest+0x222


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

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

Often RAM or hard drive are the issues, but not always.

Try testing your hard disk first.