Bluescreen ntkrnlmp.exe

Danyrail

Newbie
Registriert
Feb. 2010
Beiträge
6
Hallo,
seit 3 Tagen habe ich ca. alle 20 Minuten einen Bluescreen.
Der tritt auch auf wenn der PC einfach nur läuft und man nichts dran macht. Oder halt z.b. beim Surfen.

Habe mal WinDbg installiert und die neusten 3 dmp´s analysieren lassen.

Die sehen so aus:




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


Loading Dump File [C:\Windows\Minidump\022310-14242-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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Tue Feb 23 17:59:39.656 2010 (GMT+1)
System Uptime: 0 days 0:10:45.686
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
..........
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff80002c85798}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002c85798

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002cbc469 to fffff80002cbcf00

STACK_TEXT:
fffff880`02fd9ce8 fffff800`02cbc469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02fd9cf0 fffff800`02cba932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02fd9e30 fffff800`02c85798 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`02ff5db0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`02cba932 90 nop

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

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








Kann mir jemand helfen?
Aus der Meldung:

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

werde ich nicht schlau, googeln nach dieser exe hat mir nichts eingebracht, da die meisten Fälle da XP betreffen.

Ich habe aber Windows 7 Professional 64 bit.

Vielen Dank für jede Analyse meines Problems!
 
... Hardware (wahrscheinlich) oder Softwareproblem. Um die Hardware als Fehlerquelle aus zu schliessen könntest du Win 7 neu installieren. Interessant ist das hier: UNEXPECTED_KERNEL_MODE_TRAP 7f.
 
Zuletzt bearbeitet:
Was ist denn daran interessant?
Also ich habe davon keine Ahnung, vll magst du mich aufklären?
 
... weil das mehr über den Fehler aussagt als die "ntkrnlmp.exe".
 
Zurück
Oben