Hier ist das Ergebniss!
------------------
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\1FB\temp\Minidump\Mini112104-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: F:\Debugsymbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 UP Free x86 compatible
Product: WinNt
Kernel base = 0x804d0000 PsLoadedModuleList = 0x8053e0a8
Debug session time: Sun Nov 21 19:15:51 2004
System Uptime: 0 days 2:08:22.425
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
......................................................................................................................
Loading unloaded module list
..............
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 1d6, f3a0acc8, 0}
Unable to load image vsdatant.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
Probably caused by : vsdatant.sys ( vsdatant+f1d6 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates
that an unaligned data reference was encountered. The trap frame will
supply additional information.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 000001d6, The address that the exception occurred at
Arg3: f3a0acc8, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.
FAULTING_IP:
+1d6
000001d6 ?? ???
TRAP_FRAME: f3a0acc8 -- (.trap fffffffff3a0acc8)
ErrCode = 00000000
eax=00000001 ebx=00000000 ecx=bf8741c7 edx=00000000 esi=000001d6 edi=0012fb88
eip=000001d6 esp=f3a0ad3c ebp=00000001 iopl=0 nv up ei ng nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
000001d6 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from f5eb61d6 to 000001d6
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f3a0ad38 f5eb61d6 0012fb88 f3a0ad64 0012fb88 0x1d6
00010292 00000000 00000000 00000000 00000000 vsdatant+0xf1d6
FOLLOWUP_IP:
vsdatant+f1d6
f5eb61d6 ?? ???
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: vsdatant+f1d6
MODULE_NAME: vsdatant
IMAGE_NAME: vsdatant.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4187b4dc
STACK_COMMAND: .trap fffffffff3a0acc8 ; kb
BUCKET_ID: 0x8E_vsdatant+f1d6
Followup: MachineOwner
---------
Sieht danach aus, das der Fehler von der Datei (Treiber) vsdatant.sys verursacht wird.
Sieht nach einem Crash mit Zonealarm aus.
Wenn du es installiert hast, teile es mit.
Hier ist eine Lösung auf English!
1. Configure ZoneAlarm preferences so that ZoneAlarm does not load at system
startup. This can be done by running the ZoneAlarm Control Center and clear
ing the Load at Startup check box. This step is optional, but doing this pre
vents ZoneAlarm from unnecessarily alerting you to a system change. Keep in
mind this setting will only be temporary.
2. Start the Computer Management applet by right-clicking My Computer then s
electing Manage.
3. Click Device Manager in the left-hand pane.
4. On the Computer Management menu bar, click View, and ensure that "Show hi
dden devices" is checked.
5. Click the '+' sign beside the Non-Plug and Play Drivers entry in the righ
t-hand pane of the Computer Management applet to expand these devices.
6. Scroll down to the entry for VSDATANT, right-click it, and select Disable
.
7. Reboot your computer. The CHKDSK will then run.
8. After the CHKDSK is complete and your computer reboots, return to the Com
puter Management applet and re-enable the VSDATANT device.
9. Return to the ZoneAlarm Control Center, re-enable the Load at Startup opt
ion, and reboot the computer.
Viele Grüße
Fiona
