BSOD 0x8000000000000002

[warmaku]

just recently started getting and happen every so often
this one happened in a league of legends game, went back and was fine, didnt happen again

windows 7 64-bit Retail
mostly all hardware is year old but are new old..
just reinstalled yesterday


Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 3/10/2011 1:15:39 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: Tim-PC
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="Error">
<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="2011-03-10T18:15:39.288826000Z" />
<EventRecordID>1766</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Tim-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">30</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

 

[mgorman87]

You'll need to follow the instructions posted here before anyone can help you
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[yowanvista]

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[warmaku]

corrected

 

[warmaku]

bump

 

[mgorman87]

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Mike\Downloads\1\Windows_NT6_BSOD_jcgriff2\030911-23899-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*C:\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.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c1d000 PsLoadedModuleList = 0xfffff800`02e5ae50
Debug session time: Wed Mar  9 22:51:50.402 2011 (UTC - 5:00)
System Uptime: 0 days 5:28:13.493
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80073f8a20, fffff80000b9c518, fffffa8007d75e10}

Probably caused by : pci.sys

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80073f8a20, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8007d75e10, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc117

MODULE_NAME: pci

FAULTING_MODULE: fffff88000f57000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02cfc273 : 00000000`0000009f 00000000`00000003 fffffa80`073f8a20 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02c9929e : fffff800`00b9c600 fffff800`00b9c600 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`00b9c570 fffff800`02c98dd6 : fffffa80`077974d0 00000000`0013433b 00000000`00000000 fffffa80`09bcf000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02c994be : 0000002d`da3cb419 fffff800`00b9cc58 00000000`0013433b fffff800`02e0a9e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02c98cb7 : 0000000a`727f0cc2 0000000a`0013433b 0000000a`727f0cfe 00000000`0000003b : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02c95eea : fffff800`02e07e80 fffff800`02e15c40 00000000`00000000 fffff880`0feed650 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_L1E62x64_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_L1E62x64_IMAGE_pci.sys

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

It is pointing to the driver L1E62x64.sys which is your Ethernet driver. Try updating that.

Loading Dump File [C:\Users\Mike\Downloads\1\Windows_NT6_BSOD_jcgriff2\031011-29203-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c5b000 PsLoadedModuleList = 0xfffff800`02e98e50
Debug session time: Thu Mar 10 13:14:12.835 2011 (UTC - 5:00)
System Uptime: 0 days 14:01:01.926
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\drivers\Lachesis.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Lachesis.sys
*** ERROR: Module load completed but symbols could not be loaded for Lachesis.sys
Probably caused by : Lachesis.sys ( Lachesis+f44 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3466346136373435
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002cc346e to fffff80002ccb710

STACK_TEXT:  
fffff880`02ffcc18 fffff800`02cc346e : 00000000`00001000 fffffa80`0783d6d0 fffff880`02ffd420 fffff800`02cf8668 : nt!KeBugCheck
fffff880`02ffcc20 fffff800`02cf140d : fffff800`02ed9b7c fffff800`02e13ea4 fffff800`02c5b000 fffff880`02ffd380 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffcc50 fffff800`02cf8a90 : fffff800`02e1ab34 fffff880`02ffccc8 fffff880`02ffd380 fffff800`02c5b000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffcc80 fffff800`02cfa06a : fffff880`02ffd380 fffff880`02ffd420 00000000`00000001 00000000`00000000 : nt!RtlDispatchException+0x410
fffff880`02ffd360 fffff800`02d26112 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0c0add00 : nt!RtlRaiseStatus+0x4e
fffff880`02ffd900 fffff880`0fed1f44 : fffff880`0fed5640 00000000`00000000 00000000`00000002 fffff800`02d08700 : nt! ?? ::FNODOBFM::`string'+0xf5fc
fffff880`02ffd980 fffff880`0fed5640 : 00000000`00000000 00000000`00000002 fffff800`02d08700 fffffa80`00000000 : Lachesis+0xf44
fffff880`02ffd988 00000000`00000000 : 00000000`00000002 fffff800`02d08700 fffffa80`00000000 00000000`00000000 : Lachesis+0x4640


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Lachesis+f44
fffff880`0fed1f44 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  Lachesis+f44

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Lachesis

IMAGE_NAME:  Lachesis.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  46c552dc

FAILURE_BUCKET_ID:  X64_0x1E_0_Lachesis+f44

BUCKET_ID:  X64_0x1E_0_Lachesis+f44

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

3: kd> lmvm Lachesis
start             end                 module name
fffff880`0fed1000 fffff880`0fed8680   Lachesis T (no symbols)           
    Loaded symbol image file: Lachesis.sys
    Image path: \SystemRoot\system32\drivers\Lachesis.sys
    Image name: Lachesis.sys
    Timestamp:        Fri Aug 17 03:48:44 2007 (46C552DC)
    CheckSum:         00016FC6
    ImageSize:        00007680
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

fffff880`04430000 fffff880`04438000   ASACPI   ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)
fffff880`0fed1000 fffff880`0fed8680   Lachesis Lachesis.sys Fri Aug 17 03:48:44 2007 (46C552DC)
fffff880`0441e000 fffff880`04430000   L1E62x64 L1E62x64.sys Thu Jun 11 02:45:22 2009 (4A30A802)

I would update these 3 drivers

The second dump points to Lachesis.sys which is your Razer mouse drivers.

 

[warmaku]

tyvm for your time