Help! Can anyone fix this?

[darkkiller782]

Hi, I just started here but I have a problem I have currently have a custom pc I built so here are the specs:

Biostar MCP63
AMD Athlon II X4 630
Radeon HD 6670
LG GH22NS50B DVD Writer
2x Patriot PC10600 2GB DDR3
WD Caviar 500GB Serial ATA HD 7200/16MB

Anyways I was playing Terraria and while playing the computer first stuttered and then froze. I managed to look through the dump file and I got this:

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: 00000000, Machine Check Exception
Arg2: 86bfd2d4, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, 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: 0

STACK_TEXT:
8d793cc4 82eeebad 86bfd2b8 82f86c68 82f86c60 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8d793ce4 82eef9d7 82f86c60 86bfd2b8 82f86c90 nt!WheapProcessWorkQueueItem+0x56
8d793d00 82e9aaab 82f86c60 00000000 855e1020 nt!WheapWorkQueueWorkerRoutine+0x1f
8d793d50 83026f5e 00000001 a43d58cf 00000000 nt!ExpWorkerThread+0x10d
8d793d90 82ece219 82e9a99e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

Followup: MachineOwner

I also uploaded the dump file if you want.

Please help!

 

[zigzag3143]

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html