0x8000000000000002 bluescreen

nomo · 28 Dec 2009

hello, i got my very first bluescreen since i run win7
i got it while playing L4D2 on a 16 player server

i uploades the dmg file and a system report file , processed with everest
perhaps someone can help me out,

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 28.12.2009 11:10:00
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: Stalker
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2009-12-28T10:10:00.872488400Z" />
<EventRecordID>21770</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Stalker</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">292</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0xfffffa8004f31038</Data>
<Data Name="BugcheckParameter3">0xb2000040</Data>
<Data Name="BugcheckParameter4">0x800</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

nickle · 28 Dec 2009

You have what is called a machine check 0x124 exception code which means a fatal hardware error has occured. Refer to the folowing tutorial for some general guidelines to follow as a result of a 0x124 machine check exception: https://www.sevenforums.com/crash-loc...-what-try.html.

Code:

 
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\Nickle\AppData\Local\Temp\Rar$DI20.607\122809-58172-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02205000 PsLoadedModuleList = 0xfffff800`02442e50
Debug session time: Mon Dec 28 05:08:11.342 2009 (GMT-5)
System Uptime: 0 days 2:22:28.967
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8004f31038, b2000040, 800}
Probably caused by : hardware
Followup: MachineOwner
---------
0: 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: fffffa8004f31038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, 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:  left4dead2.exe
CURRENT_IRQL:  f
STACK_TEXT:  
fffff800`03870a98 fffff800`027f4903 : 00000000`00000124 00000000`00000000 fffffa80`04f31038 00000000`b2000040 : nt!KeBugCheckEx
fffff800`03870aa0 fffff800`0238b513 : 00000000`00000001 fffffa80`04f31ea0 00000000`00000000 fffffa80`04f31ef0 : hal!HalBugCheckSystem+0x1e3
fffff800`03870ae0 fffff800`027f45c8 : 00000000`00000728 fffffa80`04f31ea0 fffff800`03870e70 fffff800`03870e00 : nt!WheaReportHwError+0x263
fffff800`03870b40 fffff800`027f3f1a : fffffa80`04f31ea0 fffff800`03870e70 fffffa80`04f31ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`03870c90 fffff800`027f3dd5 : 00000000`00000002 00000000`00000001 fffff800`03870ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`03870cd0 fffff800`027e7e88 : 00000000`0000003c 00000000`0000009c 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`03870d00 fffff800`022757ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`03870d30 fffff800`02275613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`03870e70 00000000`0b0b0da0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0018dfb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xb0b0da0
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware
IMAGE_NAME:  hardware
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS
Followup: MachineOwner
---------

nomo · 02 Jan 2010

thx, i think i was a audio driver issue, but dont know why...