Oh here it is hope it helps
Hi and welcome
this crash was caused by hardware. You can use these https://www.sevenforums.com/crash-loc...-what-try.html to diagnose what.
Let us know if you need help
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\020210-30170-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a01000 PsLoadedModuleList = 0x82b49810
Debug session time: Tue Feb 2 08:54:20.516 2010 (GMT-5)
System Uptime: 0 days 0:00:10.530
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, 8585f4dc, 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: 00000000, Machine Check Exception
Arg2: 8585f4dc, 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_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
8ab17cc4 82acffc5 8585f4c0 82b68c28 82b68c20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8ab17ce4 82ad0def 82b68c20 8585f4c0 82b68c50 nt!WheapProcessWorkQueueItem+0x56
8ab17d00 82a6ef2b 82b68c20 00000000 848dba70 nt!WheapWorkQueueWorkerRoutine+0x1f
8ab17d50 82c0f66d 00000001 942b9412 00000000 nt!ExpWorkerThread+0x10d
8ab17d90 82ac10d9 82a6ee1e 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_GenuineIntel_PROCESSOR_BUS_PRV
BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------
Quote
