zoomman
(zoomman)
15 Październik 2007 21:30
#1
Komputer był włączony od kilku godzin, wyszedłem na 15min. do sklepu wracam a tu ekran do logowania. Po zalogowaniu pojawiła się informacja że komputer jest uruchomiony po krytycznym błędzie. Czy ktoś to umie rozszyfrować :-o
Microsoft ® Windows Debugger Version 6.6.0003.5 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20 Debug session time: Mon Oct 15 13:06:44.625 2007 (GMT+2) System Uptime: 0 days 22:54:24.194 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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 … *** WARNING: Unable to verify timestamp for USBPORT.SYS *** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS ERROR: FindPlugIns 8007007b ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 100000D1, {f85f6328, 2, 0, f85f6328} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** WARNING: Unable to verify timestamp for alcaudsl.sys *** ERROR: Module load completed but symbols could not be loaded for alcaudsl.sys *** WARNING: Unable to verify timestamp for alcan5wn.sys *** ERROR: Module load completed but symbols could not be loaded for alcan5wn.sys ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* Probably caused by : alcaudsl.sys ( alcaudsl+2f14 ) Followup: MachineOwner ---------
Jamaican
(Jamaican)
15 Październik 2007 22:52
#2
problem prawdopodobnie powoduje plik Alcaudsl.sys - Alcatel USB WDM xDSL Class Driver
strazak
(strazak)
15 Październik 2007 22:57
#3
To jest przyczyna
Masz internet z neo? Bo to jest chyba sterownik modemu.
zoomman
(zoomman)
16 Październik 2007 09:56
#4
Neta mam z Netii, do tego jest modem usb. Przeinstalować sterowniki do tego modemu? Do tego co jakiś czas zrywa mi połączenie.
strazak
(strazak)
16 Październik 2007 14:38
#5
Witam.
Na necie wyczytałem, że można zainstalować nowsze stery - jeżeli są, lub przeinstalować obecne, choć mówiąc szczerze to temat rzeka…
Pozdrawiam.