New PC From Mesh BSOD Strikes Back

So I'm back, haven't had the chance to go on my pc for days was playing today and it blue screened again, guess it wasn't fixed =[.

Mesh aint really interested if i post here and find out if its easier to fix first that wud be better if not then ill go through hassle with mesh.

Today I got BCCODE :124

Here's the files needed any help would be great.

I'm running this set upits about a week old)
Windows 7 64bit
550W HEC Desktop Power Supply
ASUS M4A78LT-M Mainboard (uATX), with integrated HDMI/DVI/VGA Graphics - DDR3
Supports up to 12 USB 2.0 ports (6x mid-board, 6x back panel) - M4A78LT-M
AMD Athlon™ II X4 640 Quad Core Processor AM3 (3.0GHz)
4GB 1333MHz Dual Channel DDR3 SDRAM - (2x2GB)
1GB ATI Radeon HD5750 Graphics Accelerator
1TB Samsung F3 SATA 7200rpm 32MB Cache Hard Drive
22x SATA Dual Layer DVD-Rewritable Super Format ±R/±RW/RAM
7.1 High Definition onboard sound card - for 8 Channel Cinema sound
Network Ready PCIe Gigabit LAN

Thanks! Please Help!

Anyone help please?

BC Code 0x124 is caused by defective hardware
Stop 0x124 - what it means and what to try

Its either overheating or my gcard is broke i think, ima try and call mesh and see if they can fix it, i doubt they will they dont seem to care or respond, waste of money. well gutted.

Could it just be overheating im running my pc with no side on to see if its better, it wasnt ever hot though..

SnEAky said:

So I'm back, haven't had the chance to go on my pc for days was playing today and it blue screened again, guess it wasn't fixed =[.

Mesh aint really interested if i post here and find out if its easier to fix first that wud be better if not then ill go through hassle with mesh.

Today I got BCCODE :124

Here's the files needed any help would be great.

I'm running this set upits about a week old)
Windows 7 64bit
550W HEC Desktop Power Supply
ASUS M4A78LT-M Mainboard (uATX), with integrated HDMI/DVI/VGA Graphics - DDR3
Supports up to 12 USB 2.0 ports (6x mid-board, 6x back panel) - M4A78LT-M
AMD Athlon™ II X4 640 Quad Core Processor AM3 (3.0GHz)
4GB 1333MHz Dual Channel DDR3 SDRAM - (2x2GB)
1GB ATI Radeon HD5750 Graphics Accelerator
1TB Samsung F3 SATA 7200rpm 32MB Cache Hard Drive
22x SATA Dual Layer DVD-Rewritable Super Format ±R/±RW/RAM
7.1 High Definition onboard sound card - for 8 Channel Cinema sound
Network Ready PCIe Gigabit LAN

Thanks! Please Help!

These crashes were caused by hardware

Code:

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\122610-24429-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a1e000 PsLoadedModuleList = 0xfffff800`02c5be50
Debug session time: Sun Dec 26 14:25:54.028 2010 (GMT-5)
System Uptime: 0 days 0:00:12.870
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

...............................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8005fe18f8, 0, 0}

Probably caused by : hardware

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

2: 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: fffffa8005fe18f8, 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.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02fc46f0 fffff800`02cd8a89 : fffffa80`05fe18d0 fffffa80`039fb680 00000000`00000014 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fc4c10 fffff800`02bba667 : fffffa80`05fe18d0 fffff800`02c335f8 fffffa80`039fb680 00000000`00000286 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fc4c40 fffff800`02b22c45 : fffff800`02c95360 fffffa80`055bb828 fffffa80`055bb820 fffffa80`039fb680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fc4c80 fffff800`02a9b961 : fffff880`00e30e00 fffff800`02b22c20 fffffa80`039fb680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fc4cb0 fffff800`02d32c06 : 00000000`00000000 fffffa80`039fb680 00000000`00000080 fffffa80`03983890 : nt!ExpWorkerThread+0x111
fffff880`02fc4d40 fffff800`02a6cc26 : fffff880`02d64180 fffffa80`039fb680 fffff880`02d6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fc4d80 00000000`00000000 : fffff880`02fc5000 fffff880`02fbf000 fffff880`02fc4260 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

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 Stop 0x124 - what it means and what to try

Thanks


Ken

Just crashed again..

BCCODE 50?

Im so confused on what to do i no im calling mesh tomorrow but they wont offer anything i don't think. anyone else any ideas?

do i need yo upload bsod stuff again?

Should i reuplaod new data things for you guys to look at?

How and do i need to update bios?

SnEAky said:

Should i reuplaod new data things for you guys to look at?

How and do i need to update bios?

Yes reupload the new dump files