Bluescreen Critical Object Termination

BillyMorgan

Newbie
Registriert
Apr. 2014
Beiträge
3
Moin!

Ich bekomme diesen Bluescreen in unregelmäßigen Abständen auf meinem Laptop:
Lenovo t400s
Core2Duo P9400 2,4 GHZ
2x4GB RAM (ohne Fehler getestet)
WIN 7 Pro 64bit
Crucial m500 240GB mSATA SSD in 1,8 Zoll Adapter (im Verdacht)
Bin für jede Hilfe dankbar.






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


Loading Dump File [C:\Windows\Minidump\040114-10202-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*E:\Debugging*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c606d0
Debug session time: Tue Apr 1 20:02:44.474 2014 (GMT+2)
System Uptime: 0 days 0:02:14.113
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8008cff6f0, fffffa8008cff9d0, fffff80002d977b0}

Probably caused by : wininit.exe

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8008cff6f0, Terminating object
Arg3: fffffa8008cff9d0, Process image file name
Arg4: fffff80002d977b0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa8008cff6f0

IMAGE_NAME: wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: wininit.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

BUGCHECK_STR: 0xF4_C0000005

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`035f90a8 fffff800`02e20ab2 : 00000000`000000f4 00000000`00000003 fffffa80`08cff6f0 fffffa80`08cff9d0 : nt!KeBugCheckEx
fffff880`035f90b0 fffff800`02dcbabb : ffffffff`ffffffff fffffa80`08fa9060 fffffa80`08cff6f0 fffffa80`08cff6f0 : nt!PspCatchCriticalBreak+0x92
fffff880`035f90f0 fffff800`02d4b674 : ffffffff`ffffffff 00000000`00000001 fffffa80`08cff6f0 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`035f9140 fffff800`02a91e53 : fffffa80`08cff6f0 fffff800`c0000005 fffffa80`08fa9060 00000000`02610a00 : nt!NtTerminateProcess+0xf4
fffff880`035f91c0 fffff800`02a8e410 : fffff800`02add82f fffff880`035f9b38 fffff880`035f9890 fffff880`035f9be0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`035f9358 fffff800`02add82f : fffff880`035f9b38 fffff880`035f9890 fffff880`035f9be0 00000000`02612240 : nt!KiServiceLinkage
fffff880`035f9360 fffff800`02a92242 : fffff880`035f9b38 00000000`00050a34 fffff880`035f9be0 00000000`02611d18 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`035f9a00 fffff800`02a90dba : 00000000`00000001 00000000`02610fb8 00000000`0268f801 00000000`00050a34 : nt!KiExceptionDispatch+0xc2
fffff880`035f9be0 00000000`76f88e5d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`02610fc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f88e5d


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_C0000005_IMAGE_wininit.exe

BUCKET_ID: X64_0xF4_C0000005_IMAGE_wininit.exe

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

1: kd> !process fffffa8008cff6f0 3
GetPointerFromAddress: unable to read from fffff80002cca000
PROCESS fffffa8008cff6f0
SessionId: none Cid: 01e4 Peb: 7fffffd3000 ParentCid: 0188
DirBase: 1f02a7000 ObjectTable: fffff8a000c5ca40 HandleCount: <Data Not Accessible>
Image: wininit.exe
VadRoot fffffa8008cfc6f0 Vads 69 Clone 0 Private 807. Modified 1. Locked 2.
DeviceMap fffff8a000008bb0
Token fffff8a000c60060
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
ElapsedTime 00:00:00.000
UserTime 00:00:00.000
KernelTime 00:00:00.000
QuotaPoolUsage[PagedPool] 0
QuotaPoolUsage[NonPagedPool] 0
Working Set Sizes (now,min,max) (1624, 50, 345) (6496KB, 200KB, 1380KB)
PeakWorkingSetSize 1624
VirtualSize 47 Mb
PeakVirtualSize 49 Mb
PageFaultCount 1848
MemoryPriority BACKGROUND
BasePriority 13
CommitCharge 924

*** Error in reading nt!_ETHREAD @ fffffa8008d02060

1: kd> lmvm wininit
start end module name
 
Sieht eigentlich o.k aus.
 

Anhänge

  • crucial.PNG
    crucial.PNG
    79,3 KB · Aufrufe: 194
Zurück
Oben