crashing and random restarts

where do i go to get them sorry not to good with pc's on my own

where do i go to get these sory im no good with pc's lol

Attachment 115205 think iv done it right let me no an thankyou for your help :)

richib said:

Attachment 115205 think iv done it right let me no an thankyou for your help :)

These all were identical and 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 blue-screens because it stems from a hardware complaint. Stop 0x124 mini-dumps 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

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\New folder\111710-29796-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02802000 PsLoadedModuleList = 0xfffff800`02a3fe50
Debug session time: Wed Nov 17 10:20:31.613 2010 (GMT-5)
System Uptime: 0 days 0:00:08.283
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, fffffa8002daa628, 0, 0}

Probably caused by : hardware

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

3: 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: fffffa8002daa628, 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`02f796f0 fffff800`02abca89 : fffffa80`02daa600 fffffa80`018d3680 00000000`00000010 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02f79c10 fffff800`0299e547 : fffffa80`02daa600 fffff800`02a175f8 fffffa80`018d3680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02f79c40 fffff800`02906b95 : fffff800`02a79360 fffffa80`02da9dd8 fffffa80`02da9dd0 fffffa80`018d3680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02f79c80 fffff800`02881161 : fffff880`00e6ee00 fffff800`02906b70 fffffa80`018d3680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02f79cb0 fffff800`02b17166 : 00000000`00000000 fffffa80`018d3680 00000000`00000080 fffffa80`01845b30 : nt!ExpWorkerThread+0x111
fffff880`02f79d40 fffff800`02852486 : fffff880`02d63180 fffffa80`018d3680 fffff880`02d6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f79d80 00000000`00000000 : fffff880`02f7a000 fffff880`02f74000 fffff880`03573540 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
---------

thankyou for your help just a thought when i bought the processer i took the label from my motherboard an asked the guy at the shop if this processer was right an he was sorta like errrrrrr for about 10 mins an then sed ye mate that works....when i built it all up the socket has diagonal holes on every corner where as the processer chip has 1 corner cut out iv drawn it on paint to try illustrate it .. could this be the problem.Attachment 115207 not good paint skills i no

Are you overclocking?

no mate not touched anything like that as i dont really no how my board supports turbo something or other where i can turn the clokin volts an speeds up etc from the desk top but i havent touched anything as i dont really understand how it all works

Tews said:

I would be very suspicious of any cpu that is not perfectly matched with the motherboard ... and yes, this could be the cause of your 0x124 hardware error...

hmm strange i asked in another pc shop the same question but he sed if its not the correct chip it wouldnt work at all so i just guessed must be something else but from talking to you guys its starting to make sence everything in my pc is basicly brand new week old