Anzeige

Am Puls von Microsoft

Anzeige

System BlueScreen @ Vista x64

sHaRkS.p3

Herzlich willkommen
Hey Leute.....

Hatte gerad n BlueScreen....

Vll könnt ihr mir helfen

Mein System:
Intel E6850
ASUS P5N-E SLI
GeFroce 9600 GT @ 512MB
Vista x64 Ultimate

Please Help Me...;)

Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02bd3db0
Debug session time: Sun Jan 25 21:10:43.286 2009 (GMT+1)
System Uptime: 0 days 7:57:09.111
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002a762dd, 0, d0}

Unable to load image \SystemRoot\system32\DRIVERS\nvmfdx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmfdx64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmfdx64.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+682dd )

Followup: MachineOwner
---------
 
Zuletzt bearbeitet von einem Moderator:
Anzeige
Code:
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02bd3db0
Debug session time: Sun Jan 25 21:10:43.286 2009 (GMT+1)
System Uptime: 0 days 7:57:09.111
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002a762dd, 0, d0}

*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Probably caused by : kl1.sys ( kl1+4babe )

Followup: MachineOwner
---------
 
Symbol search path is: *** Invalid ***
Irgendetwas haut immer noch nicht hin, der Logfile ist auch nicht vollständig.
Hast du den Pfad so angelegt, wie im Tutorial beschrieben?
Wenn ja, lösche das Verzeichnis und Einstellungen des Debuggers und erstelle alles neu.

Falls obg. Schritte keinen vollständigen Debug-Log ergeben:
Im Logfile wird die Datei kl1.sys genannt, die gehört zu Kaspersky.
Deinstalliere das Programm/Suite und überprüfe, ob der Fehler immer noch auftaucht.
Wenn nein, vielleicht gibt es ein Update von Kaspersky.
Wenn ja, brauchen wir einen neuen Debug-Log.
 
Code:
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02bd3db0
Debug session time: Sun Jan 25 21:10:43.286 2009 (GMT+1)
System Uptime: 0 days 7:57:09.111
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002a762dd, 0, d0}

*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
Probably caused by : kl1.sys ( kl1+4babe )

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

1: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002a762dd, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 00000000000000d0, Parameter 1 of the exception

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

PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details

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

FAULTING_IP: 
nt!RtlVirtualUnwind+25d
fffff800`02a762dd 488b02          mov     rax,qword ptr [rdx]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000000000d0

READ_ADDRESS:  00000000000000d0 

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  hl2.exe

CURRENT_IRQL:  1

TRAP_FRAME:  fffffa600d58f9c0 -- (.trap 0xfffffa600d58f9c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000050 rbx=fffffa8008b8d650 rcx=0000000000000004
rdx=00000000000000d0 rsi=fffffa8008b8d650 rdi=fffff960000ca936
rip=fffff80002a762dd rsp=fffffa600d58fb50 rbp=0000000000000233
 r8=0000000000000006  r9=fffff80002a0e000 r10=ffffffffffffff80
r11=fffff80002c0d000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!RtlVirtualUnwind+0x25d:
fffff800`02a762dd 488b02          mov     rax,qword ptr [rdx] ds:0002:00000000`000000d0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a3ce47 to fffff80002a63350

STACK_TEXT:  
fffffa60`0d58f1d8 fffff800`02a3ce47 : 00000000`0000001e ffffffff`c0000005 fffff800`02a762dd 00000000`00000000 : nt!KeBugCheckEx
fffffa60`0d58f1e0 fffff800`02a631a9 : fffffa60`0d58f918 00000000`00000001 fffffa60`0d58f9c0 fffffa60`0d58fc10 : nt! ?? ::FNODOBFM::`string'+0x29317
fffffa60`0d58f7e0 fffff800`02a61fa5 : 00000000`00000000 fffffa80`dee40e55 fffffa80`05c53600 00000000`00000001 : nt!KiExceptionDispatch+0xa9
fffffa60`0d58f9c0 fffff800`02a762dd : 00000000`00000001 00000000`00000000 fffffa80`07483bb0 fffffa80`08b8d650 : nt!KiPageFault+0x1e5
fffffa60`0d58fb50 fffff800`02cfa9ea : fffff800`00000001 fffffa60`0b5b3500 00000000`00000000 ffffffff`ffffff80 : nt!RtlVirtualUnwind+0x25d
fffffa60`0d58fbc0 fffff800`02a7e2ed : ffffffff`ffffff80 fffffa80`07483bb0 fffffa60`0b5b3570 fffff800`02a0e000 : nt!PspGetSetContextInternal+0x36a
fffffa60`0d590110 fffff800`02a8d392 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspGetSetContextSpecialApc+0x9d
fffffa60`0d590220 fffff800`02a910c3 : fffffa60`0d590340 00000000`00000000 00000000`00000000 fffffa80`07483bb0 : nt!KiDeliverApc+0x1e2
fffffa60`0d5902c0 fffffa60`04654abe : fffffa80`06e12840 fffffa80`090647b0 fffffa80`0830dc94 00000000`00000000 : nt!KiApcInterrupt+0x103
fffffa60`0d590450 fffffa80`06e12840 : fffffa80`090647b0 fffffa80`0830dc94 00000000`00000000 fffa8006`74023002 : kl1+0x4babe
fffffa60`0d590458 fffffa80`090647b0 : fffffa80`0830dc94 00000000`00000000 fffa8006`74023002 fffffa60`046616ff : 0xfffffa80`06e12840
fffffa60`0d590460 fffffa80`0830dc94 : 00000000`00000000 fffa8006`74023002 fffffa60`046616ff fffff900`c0ea5410 : 0xfffffa80`090647b0
fffffa60`0d590468 00000000`00000000 : fffa8006`74023002 fffffa60`046616ff fffff900`c0ea5410 fffffa80`07a95908 : 0xfffffa80`0830dc94
fffffa60`0d590470 fffa8006`74023002 : fffffa60`046616ff fffff900`c0ea5410 fffffa80`07a95908 fffffa80`06fe6870 : 0x0
fffffa60`0d590478 fffffa60`046616ff : fffff900`c0ea5410 fffffa80`07a95908 fffffa80`06fe6870 fffffa80`07a958c0 : 0xfffa8006`74023002
fffffa60`0d590480 fffff900`c0ea5410 : fffffa80`07a95908 fffffa80`06fe6870 fffffa80`07a958c0 fffffa80`07a958c0 : kl1+0x586ff
fffffa60`0d590488 fffffa80`07a95908 : fffffa80`06fe6870 fffffa80`07a958c0 fffffa80`07a958c0 fffffa60`046523ce : 0xfffff900`c0ea5410
fffffa60`0d590490 fffffa80`06fe6870 : fffffa80`07a958c0 fffffa80`07a958c0 fffffa60`046523ce 00000000`01ffffff : 0xfffffa80`07a95908
fffffa60`0d590498 fffffa80`07a958c0 : fffffa80`07a958c0 fffffa60`046523ce 00000000`01ffffff 00000000`00000035 : 0xfffffa80`06fe6870
fffffa60`0d5904a0 fffffa80`07a958c0 : fffffa60`046523ce 00000000`01ffffff 00000000`00000035 fffffa80`07a95760 : 0xfffffa80`07a958c0
fffffa60`0d5904a8 fffffa60`046523ce : 00000000`01ffffff 00000000`00000035 fffffa80`07a95760 fffffa80`0830dc50 : 0xfffffa80`07a958c0
fffffa60`0d5904b0 00000000`01ffffff : 00000000`00000035 fffffa80`07a95760 fffffa80`0830dc50 fffa8006`ca323000 : kl1+0x493ce
fffffa60`0d5904b8 00000000`00000035 : fffffa80`07a95760 fffffa80`0830dc50 fffa8006`ca323000 fffffa60`0460afff : 0x1ffffff
fffffa60`0d5904c0 fffffa80`07a95760 : fffffa80`0830dc50 fffa8006`ca323000 fffffa60`0460afff 00000000`00200246 : 0x35
fffffa60`0d5904c8 fffffa80`0830dc50 : fffa8006`ca323000 fffffa60`0460afff 00000000`00200246 fffffa80`06fe6720 : 0xfffffa80`07a95760
fffffa60`0d5904d0 fffa8006`ca323000 : fffffa60`0460afff 00000000`00200246 fffffa80`06fe6720 00000000`07a95700 : 0xfffffa80`0830dc50
fffffa60`0d5904d8 fffffa60`0460afff : 00000000`00200246 fffffa80`06fe6720 00000000`07a95700 fffffa80`07a95760 : 0xfffa8006`ca323000
fffffa60`0d5904e0 00000000`00000035 : 00000000`00000000 00000000`00000000 fffffa80`07483bb0 fffffa80`08b8d650 : kl1+0x1fff
fffffa60`0d590520 00000000`00000000 : 00000000`00000000 fffffa80`07483bb0 fffffa80`08b8d650 00000000`00000002 : 0x35
fffffa60`0d590528 00000000`00000000 : fffffa80`07483bb0 fffffa80`08b8d650 00000000`00000002 fffffa60`04b82596 : 0x0
fffffa60`0d590530 fffffa80`07483bb0 : fffffa80`08b8d650 00000000`00000002 fffffa60`04b82596 00000000`00000035 : 0x0
fffffa60`0d590538 fffffa80`08b8d650 : 00000000`00000002 fffffa60`04b82596 00000000`00000035 fffffa60`04b4b000 : 0xfffffa80`07483bb0
fffffa60`0d590540 00000000`00000002 : fffffa60`04b82596 00000000`00000035 fffffa60`04b4b000 fffffa80`07a95720 : 0xfffffa80`08b8d650
fffffa60`0d590548 fffffa60`04b82596 : 00000000`00000035 fffffa60`04b4b000 fffffa80`07a95720 fffffa80`07a95700 : 0x2
fffffa60`0d590550 fffffa60`04b94ada : fffffa80`07a95700 fffffa60`0d590ca0 fffffa80`09043270 00000000`00000035 : afd!AfdGetBufferFast+0x56
fffffa60`0d590580 fffffa60`04b6ffd6 : fffffa80`09043270 fffffa60`0d590820 00000000`00000035 00000000`00000000 : afd! ?? ::GFJBLGFE::`string'+0x72d2
fffffa60`0d590670 fffff800`02ce709b : 00000000`00000035 fffffa80`04210720 00000000`00000001 fffffa80`0923e401 : afd!AfdFastIoDeviceControl+0xfc6
fffffa60`0d5909f0 fffff800`02cfffe6 : fffff880`0e3d2e01 00000000`00000230 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x35b
fffffa60`0d590b40 fffff800`02a62df3 : fffffa80`07483bb0 fffffa60`0d590ca0 00000000`0000078c fffff800`02cdfec4 : nt!NtDeviceIoControlFile+0x56
fffffa60`0d590bb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13


STACK_COMMAND:  kb

FOLLOWUP_IP: 
kl1+4babe
fffffa60`04654abe 4c8b7c2438      mov     r15,qword ptr [rsp+38h]

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  kl1+4babe

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: kl1

IMAGE_NAME:  kl1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48849e50

FAILURE_BUCKET_ID:  X64_0x1E_kl1+4babe

BUCKET_ID:  X64_0x1E_kl1+4babe

Followup: MachineOwner
---------
 
Jetzt passt's. :)

Es ist also tatsächlich eine Datei von Kaspersky,
dir für den Bluescreen verantwortlich ist.

Entweder du deaktivierst das Programm testweise,
oder nimmst an den Sicherheitseinstellungen entsprechende Änderungen vor.

Vielleicht gibt es auch einen Patch auf der Homepage des Herstellers.
 
ja hab Kaspersky mal Deinstalliert....bis jetzt hatte nich noch keinen BlueScreen

Hoffe das bleibt auch so ;)

THX noch mal :)
 
Anzeige
Oben