after new format

format and then kernal 41 twize freezing

started to freeze while installing avast , twice i tryed

deanolfc said:

format and then kernal 41 twize freezing

started to freeze while installing avast , twice i tryed

We really need more than one dmp and this one is corrupt. I can tell you this was 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... Stop 0x124 - what it means and what to try -https://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

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\032711-21496-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 (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0284d000 PsLoadedModuleList = 0xfffff800`02a92e90
Debug session time: Sun Mar 27 11:11:58.970 2011 (GMT-4)
System Uptime: 0 days 0:00:10.250
Loading Kernel 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, fffffa800813f8f8, 0, 0}

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: fffffa800813f8f8, 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`031856f0 fffff800`02b10d29 : fffffa80`0813f8d0 fffffa80`06d33040 fffff8a0`00000010 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03185c10 fffff800`029f0217 : fffffa80`0813f8d0 fffff800`02a6a658 fffffa80`06d33040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03185c40 fffff800`02957865 : fffff800`02acc3a0 00000000`00000001 fffffa80`08143170 fffffa80`06d33040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03185c80 fffff800`028d7a21 : fffff880`010aae00 fffff800`02957840 fffffa80`06d33000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03185cb0 fffff800`02b6acce : 8c53ea9e`003284b0 fffffa80`06d33040 00000000`00000080 fffffa80`06d21040 : nt!ExpWorkerThread+0x111
fffff880`03185d40 fffff800`028befe6 : fffff880`02f64180 fffffa80`06d33040 fffff880`02f6ef80 00000201`80000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03185d80 00000000`00000000 : fffff880`03186000 fffff880`03180000 fffff880`009fd540 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
---------

i was thinkin hardware my self i formatted because i couldnt turn windows security centre on trying everythink goin into services.msc enabling it then it would disable after like 2 minutes , and now i have the same message back cannot start windwos security centre.