need help. bsod new mobo.

[nicejuno]

Hi all.
I blew mobo couple weeks ago.
I got biostar A780L.
After this, my comp crashs almost every hour.
gateway gt-5676 +WD 2G green, -mobo, +biostar A780L +windows 7 ultimate x64.

 

[zigzag3143]

Hi all.
I blew mobo couple weeks ago.
I got biostar A780L.
After this, my comp crashs almost every hour.
gateway gt-5676 +WD 2G green, -mobo, +biostar A780L +windows 7 ultimate x64.

these were all caused by hardware.

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... http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Thanks


Ken

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\022811-25677-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a53000 PsLoadedModuleList = 0xfffff800`02c98e90
Debug session time: Mon Feb 28 05:46:23.443 2011 (GMT-5)
System Uptime: 0 days 17:50:26.643
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004d5b028, b619a000, 175}

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: fffffa8004d5b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b619a000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000175, 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:  ConvertXtoDvd.

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02f6ba88 fffff800`02a1ca3b : 00000000`00000124 00000000`00000000 fffffa80`04d5b028 00000000`b619a000 : nt!KeBugCheckEx
fffff880`02f6ba90 fffff800`02be07d3 : 00000000`00000001 fffffa80`04d62ea0 00000000`00000000 fffffa80`04d62ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`02f6bad0 fffff800`02a1c700 : 00000000`00000728 fffffa80`04d62ea0 fffff880`02f6be30 00000000`00000000 : nt!WheaReportHwError+0x263
fffff880`02f6bb30 fffff800`02a1c052 : fffffa80`04d62ea0 fffff880`02f6be30 fffffa80`04d62ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02f6bc80 fffff800`02a0fe8f : 00000000`7d5c89d8 00000000`00000001 fffff880`02f6beb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02f6bcc0 fffff800`02ad1f2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02f6bcf0 fffff800`02ad1d93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02f6be30 00000000`66ac9ead : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0b85fcdc 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x66ac9ead


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
---------