Temat
Ciągłe Restarty Systemu
84.205.223.* napisał:
Witam: )W windows debuggerze pokazuje mi się taki komunikat:
CYTAT
Microsoft ® Windows Debugger Version 6.5.0003.7
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini121805-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 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 = 0x8055a420
Debug session time: Sun Dec 18 07:48:16.140 2005 (GMT+1)
System Uptime: 1 days 10:47:15.720
*********************************************************************
* 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 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 unloaded module list
................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 44, {fb186008, d62, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_IRP ***
*** ***
*************************************************************************
Probably caused by : USBPORT.SYS ( USBPORT+9ee5 )
Followup: MachineOwner
---------
Czy ktoś może mi rozjaśńić w głowie czego dotyczą błedy tam pokazane ?
Bo ja niestety nie mam zielonego pojęcia
Z góry wielkie dzięki
83.29.244.* napisał:
A mozesz napisac co ci sie wogle dzieje?Plik USBPORT.SYS ktory powoduje problem to sterownik portu USB, a przyczyna wystepowania problemu moze byc tutaj wadliwy sterownik, uszkodzony np. kontroler lub urzadzenie/kabel USB
80.53.1.* napisał:
Zainstaluj jeszcze raz stery od mobo/usb.84.205.223.* napisał:
CYTAT
A mozesz napisac co ci sie wogle dzieje?
Plik USBPORT.SYS ktory powoduje problem to sterownik portu USB, a przyczyna wystepowania problemu moze byc tutaj wadliwy sterownik, uszkodzony np. kontroler lub urzadzenie/kabel USB
Plik USBPORT.SYS ktory powoduje problem to sterownik portu USB, a przyczyna wystepowania problemu moze byc tutaj wadliwy sterownik, uszkodzony np. kontroler lub urzadzenie/kabel USB
W skrócie:
Komputer sobie chodzi i nagle bez żadnego ostrzeżenia się wyłącza, to wygląda tak jakby ktoś na sekundę wyjął wtyczkę, po chwili uruchamia się ponownie, czasami skanuje jak po resecie a czasami nic nie robi po prostu uruchomi sie i mam spokój do ponownego wyłaczenia, które następuje czasami już po godzinie a czasami wytrzymuje nawet kilkanaście godzin i nic sie nie dzieje.
Ostatnio pojawił się niebieski ekranik z informacją o zrzucie pamięci fizycznej ale go zignorowałem i nie pamiętam dokladnie jego treści:(
CYTAT
Zainstaluj jeszcze raz stery od mobo/usb.
A dokładniej ? Mobo to płyta główna ?Może to głupie pytanie ale na komputerach znam sie tyci tyci: )
Nyny
próbowałem również wpisać w debuggerze ścieżke dostępu którą podałeś w FAQ na temat blue screenów i restartów ale po wpisaniu tego tekstu i po próbie debugowania minidump`a wiesza mi sie debugger, natomiasy jak wpisałem komendę !analize -v wywalilo mi naście linijek tekstu który też nie był dla mnie zrozumiały...po prostu komputeroiwiec ze mnie żaden....a z angielskim też kiepsko
(((((
83.29.244.* napisał:
Sproboj zainstalowac najnowsze steroniki do plyty glownej tak jak napisal Barthezzo oraz zaaktualizuj system o wszzystkie dostepne łatki.Sproboj tez wylaczyc automatyczne uruchamianie komputera, wtedy zamiast restartowac sie wywali blad i podeslij nam komunikat jaki sie tam pojawi.
Niekoniecznie musi to byc wina portu USB ale z reguly jak debugger pokazuje konkretny plik to cos jest nie tak. Masz podlaczone jakies urzadzenia na USB/huby czy przedluzki ?
84.205.223.* napisał:
CYTAT
Sproboj zainstalowac najnowsze steroniki do plyty glownej tak jak napisal Barthezzo oraz zaaktualizuj system o wszzystkie dostepne łatki.
Sproboj tez wylaczyc automatyczne uruchamianie komputera, wtedy zamiast restartowac sie wywali blad i podeslij nam komunikat jaki sie tam pojawi.
Niekoniecznie musi to byc wina portu USB ale z reguly jak debugger pokazuje konkretny plik to cos jest nie tak. Masz podlaczone jakies urzadzenia na USB/huby czy przedluzki ?
Sproboj tez wylaczyc automatyczne uruchamianie komputera, wtedy zamiast restartowac sie wywali blad i podeslij nam komunikat jaki sie tam pojawi.
Niekoniecznie musi to byc wina portu USB ale z reguly jak debugger pokazuje konkretny plik to cos jest nie tak. Masz podlaczone jakies urzadzenia na USB/huby czy przedluzki ?
jeżli chodzi o urządzenie to jedynie modem kablowy mam podłaczony pod usb no i drukarke
Jezeli chodzi o blue screena to komunikat wyglada tak:
"Pjawił się problem, system windows zostanie zamknięty aby zapobiec uszkodzeniu komputera
BUGCODE_USB_DRIVER
Jeżel iwidzisz ekran błedu pierwszy raz ponownie uruchom komputer. Jeżli błąd sie powtarza wyknaj nastepujace kroki:
Upewnij sie czy wszelki sprzet i oprogramowanie sa poprawnie zainstalowane
Jezeli jest to nowa instalacja popros producenta sprzetu lub oprogramowania o wszelkie aktualizacje dla systemu windows, ktore moga byc potrzebne
Jezeli problem bledu sie powtarza wylacz opcje pamieci systemu bios, takie jak buforowanie i przeslanianie. Jezeli musisz zrob to w trybie awarytjnym
Informacje techniczne:
*** STOP: 0x000000FE (0x00000004, 0x812A9878, 0x812EB238, 0x00000000)
Rozpoczyna się zrut pamięci fizycznej:
czyli wszystko wskazuje na blad USB Postaram sie zainstalowac wszystkie sterowniki i łatki i zobaczymy: ) Może rzeczywiście pomoże?
Mozę jeszcze kolejny log z debuggera plus komunikaty po komendzie !analize -v
CYTAT
Microsoft ® Windows Debugger Version 6.5.0003.7
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini121905-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 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 = 0x8055a420
Debug session time: Mon Dec 19 18:32:25.468 2005 (GMT+1)
System Uptime: 0 days 3:26:58.074
*********************************************************************
* 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 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 unloaded module list
.............
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {4, 812a9878, 812eb238, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Unable to load image USBPORT.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
*** WARNING: Unable to verify timestamp for NetMotCM.sys
*** ERROR: Module load completed but symbols could not be loaded for NetMotCM.sys
Probably caused by : NetMotCM.sys ( NetMotCM+b9c )
Followup: MachineOwner
---------
kd> analize -v
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*** WARNING: Unable to verify timestamp for dxg.sys
*** ERROR: Module load completed but symbols could not be loaded for dxg.sys
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*** WARNING: Unable to verify timestamp for aswRdr.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswRdr.SYS
*** WARNING: Unable to verify timestamp for srv.sys
*** ERROR: Module load completed but symbols could not be loaded for srv.sys
*** WARNING: Unable to verify timestamp for secdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for secdrv.sys
*** WARNING: Unable to verify timestamp for HTTP.sys
*** ERROR: Module load completed but symbols could not be loaded for HTTP.sys
*** WARNING: Unable to verify timestamp for wdmaud.sys
*** ERROR: Module load completed but symbols could not be loaded for wdmaud.sys
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
*** WARNING: Unable to verify timestamp for mrxdav.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxdav.sys
*** WARNING: Unable to verify timestamp for ndisuio.sys
*** ERROR: Module load completed but symbols could not be loaded for ndisuio.sys
*** WARNING: Unable to verify timestamp for sysaudio.sys
*** ERROR: Module load completed but symbols could not be loaded for sysaudio.sys
*** WARNING: Unable to verify timestamp for dump_atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_atapi.sys
*** WARNING: Unable to verify timestamp for mrxsmb.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxsmb.sys
*** WARNING: Unable to verify timestamp for rdbss.sys
*** ERROR: Module load completed but symbols could not be loaded for rdbss.sys
*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
*** WARNING: Unable to verify timestamp for netbt.sys
*** ERROR: Module load completed but symbols could not be loaded for netbt.sys
*** WARNING: Unable to verify timestamp for ipnat.sys
*** ERROR: Module load completed but symbols could not be loaded for ipnat.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for ipsec.sys
*** ERROR: Module load completed but symbols could not be loaded for ipsec.sys
*** WARNING: Unable to verify timestamp for axsaki.sys
*** ERROR: Module load completed but symbols could not be loaded for axsaki.sys
*** WARNING: Unable to verify timestamp for Dxapi.sys
*** ERROR: Module load completed but symbols could not be loaded for Dxapi.sys
*** WARNING: Unable to verify timestamp for update.sys
*** ERROR: Module load completed but symbols could not be loaded for update.sys
*** WARNING: Unable to verify timestamp for rdpdr.sys
*** ERROR: Module load completed but symbols could not be loaded for rdpdr.sys
*** WARNING: Unable to verify timestamp for psched.sys
*** ERROR: Module load completed but symbols could not be loaded for psched.sys
*** WARNING: Unable to verify timestamp for ndiswan.sys
*** ERROR: Module load completed but symbols could not be loaded for ndiswan.sys
*** WARNING: Unable to verify timestamp for portcls.sys
*** ERROR: Module load completed but symbols could not be loaded for portcls.sys
*** WARNING: Unable to verify timestamp for smwdm.sys
*** ERROR: Module load completed but symbols could not be loaded for smwdm.sys
*** WARNING: Unable to verify timestamp for ks.sys
*** ERROR: Module load completed but symbols could not be loaded for ks.sys
*** WARNING: Unable to verify timestamp for parport.sys
*** ERROR: Module load completed but symbols could not be loaded for parport.sys
*** WARNING: Unable to verify timestamp for serial.sys
*** ERROR: Module load completed but symbols could not be loaded for serial.sys
*** WARNING: Unable to verify timestamp for VIDEOPRT.SYS
*** ERROR: Module load completed but symbols could not be loaded for VIDEOPRT.SYS
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
*** WARNING: Unable to verify timestamp for rasacd.sys
*** ERROR: Module load completed but symbols could not be loaded for rasacd.sys
*** WARNING: Unable to verify timestamp for Mup.sys
*** ERROR: Module load completed but symbols could not be loaded for Mup.sys
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
*** WARNING: Unable to verify timestamp for KSecDD.sys
*** ERROR: Module load completed but symbols could not be loaded for KSecDD.sys
*** WARNING: Unable to verify timestamp for Fastfat.sys
*** ERROR: Module load completed but symbols could not be loaded for Fastfat.sys
*** WARNING: Unable to verify timestamp for fltMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for fltMgr.sys
*** WARNING: Unable to verify timestamp for SCSIPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SCSIPORT.SYS
*** WARNING: Unable to verify timestamp for atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for atapi.sys
*** WARNING: Unable to verify timestamp for dmio.sys
*** ERROR: Module load completed but symbols could not be loaded for dmio.sys
*** WARNING: Unable to verify timestamp for ftdisk.sys
*** ERROR: Module load completed but symbols could not be loaded for ftdisk.sys
*** WARNING: Unable to verify timestamp for pci.sys
*** ERROR: Module load completed but symbols could not be loaded for pci.sys
*** WARNING: Unable to verify timestamp for ACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
*** WARNING: Unable to verify timestamp for d347bus.sys
*** ERROR: Module load completed but symbols could not be loaded for d347bus.sys
*** WARNING: Unable to verify timestamp for isapnp.sys
*** ERROR: Module load completed but symbols could not be loaded for isapnp.sys
*** WARNING: Unable to verify timestamp for MountMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for MountMgr.sys
*** WARNING: Unable to verify timestamp for VolSnap.sys
*** ERROR: Module load completed but symbols could not be loaded for VolSnap.sys
*** WARNING: Unable to verify timestamp for disk.sys
*** ERROR: Module load completed but symbols could not be loaded for disk.sys
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.SYS
*** WARNING: Unable to verify timestamp for agp440.sys
*** ERROR: Module load completed but symbols could not be loaded for agp440.sys
*** WARNING: Unable to verify timestamp for processr.sys
*** ERROR: Module load completed but symbols could not be loaded for processr.sys
*** WARNING: Unable to verify timestamp for i8042prt.sys
*** ERROR: Module load completed but symbols could not be loaded for i8042prt.sys
*** WARNING: Unable to verify timestamp for imapi.sys
*** ERROR: Module load completed but symbols could not be loaded for imapi.sys
*** WARNING: Unable to verify timestamp for cdrom.sys
*** ERROR: Module load completed but symbols could not be loaded for cdrom.sys
*** WARNING: Unable to verify timestamp for redbook.sys
*** ERROR: Module load completed but symbols could not be loaded for redbook.sys
*** WARNING: Unable to verify timestamp for drmk.sys
*** ERROR: Module load completed but symbols could not be loaded for drmk.sys
*** WARNING: Unable to verify timestamp for rasl2tp.sys
*** ERROR: Module load completed but symbols could not be loaded for rasl2tp.sys
*** WARNING: Unable to verify timestamp for raspppoe.sys
*** ERROR: Module load completed but symbols could not be loaded for raspppoe.sys
*** WARNING: Unable to verify timestamp for raspptp.sys
*** ERROR: Module load completed but symbols could not be loaded for raspptp.sys
*** WARNING: Unable to verify timestamp for msgpc.sys
*** ERROR: Module load completed but symbols could not be loaded for msgpc.sys
*** WARNING: Unable to verify timestamp for termdd.sys
*** ERROR: Module load completed but symbols could not be loaded for termdd.sys
*** WARNING: Unable to verify timestamp for NDProxy.SYS
*** ERROR: Module load completed but symbols could not be loaded for NDProxy.SYS
*** WARNING: Unable to verify timestamp for aswTdi.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
*** WARNING: Unable to verify timestamp for wanarp.sys
*** ERROR: Module load completed but symbols could not be loaded for wanarp.sys
*** WARNING: Unable to verify timestamp for netbios.sys
*** ERROR: Module load completed but symbols could not be loaded for netbios.sys
*** WARNING: Unable to verify timestamp for Fips.SYS
*** ERROR: Module load completed but symbols could not be loaded for Fips.SYS
*** WARNING: Unable to verify timestamp for Cdfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for Cdfs.SYS
*** WARNING: Unable to verify timestamp for PCIIDEX.SYS
*** ERROR: Module load completed but symbols could not be loaded for PCIIDEX.SYS
*** WARNING: Unable to verify timestamp for PartMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for PartMgr.sys
*** WARNING: Unable to verify timestamp for PxHelp20.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHelp20.sys
*** WARNING: Unable to verify timestamp for mouclass.sys
*** ERROR: Module load completed but symbols could not be loaded for mouclass.sys
*** WARNING: Unable to verify timestamp for kbdclass.sys
*** ERROR: Module load completed but symbols could not be loaded for kbdclass.sys
*** WARNING: Unable to verify timestamp for fdc.sys
*** ERROR: Module load completed but symbols could not be loaded for fdc.sys
*** WARNING: Unable to verify timestamp for usbuhci.sys
*** ERROR: Module load completed but symbols could not be loaded for usbuhci.sys
*** WARNING: Unable to verify timestamp for TDI.SYS
*** ERROR: Module load completed but symbols could not be loaded for TDI.SYS
*** WARNING: Unable to verify timestamp for ptilink.sys
*** ERROR: Module load completed but symbols could not be loaded for ptilink.sys
*** WARNING: Unable to verify timestamp for raspti.sys
*** ERROR: Module load completed but symbols could not be loaded for raspti.sys
*** WARNING: Unable to verify timestamp for flpydisk.sys
*** ERROR: Module load completed but symbols could not be loaded for flpydisk.sys
*** WARNING: Unable to verify timestamp for vga.sys
*** ERROR: Module load completed but symbols could not be loaded for vga.sys
*** WARNING: Unable to verify timestamp for Msfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for Msfs.SYS
*** WARNING: Unable to verify timestamp for Npfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for Npfs.SYS
*** WARNING: Unable to verify timestamp for Aavmker4.SYS
*** ERROR: Module load completed but symbols could not be loaded for Aavmker4.SYS
*** WARNING: Unable to verify timestamp for usbprint.sys
*** ERROR: Module load completed but symbols could not be loaded for usbprint.sys
*** WARNING: Unable to verify timestamp for watchdog.sys
*** ERROR: Module load completed but symbols could not be loaded for watchdog.sys
*** WARNING: Unable to verify timestamp for iSMBIOS.SYS
*** ERROR: Module load completed but symbols could not be loaded for iSMBIOS.SYS
*** WARNING: Unable to verify timestamp for BOOTVID.dll
*** ERROR: Module load completed but symbols could not be loaded for BOOTVID.dll
*** WARNING: Unable to verify timestamp for serenum.sys
*** ERROR: Module load completed but symbols could not be loaded for serenum.sys
*** WARNING: Unable to verify timestamp for SMBus.sys
*** ERROR: Module load completed but symbols could not be loaded for SMBus.sys
*** WARNING: Unable to verify timestamp for ndistapi.sys
*** ERROR: Module load completed but symbols could not be loaded for ndistapi.sys
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for axskbus.sys
*** ERROR: Module load completed but symbols could not be loaded for axskbus.sys
*** WARNING: Unable to verify timestamp for kdcom.dll
*** ERROR: Module load completed but symbols could not be loaded for kdcom.dll
*** WARNING: Unable to verify timestamp for WMILIB.SYS
*** ERROR: Module load completed but symbols could not be loaded for WMILIB.SYS
*** WARNING: Unable to verify timestamp for intelide.sys
*** ERROR: Module load completed but symbols could not be loaded for intelide.sys
*** WARNING: Unable to verify timestamp for dmload.sys
*** ERROR: Module load completed but symbols could not be loaded for dmload.sys
*** WARNING: Unable to verify timestamp for d347prt.sys
*** ERROR: Module load completed but symbols could not be loaded for d347prt.sys
*** WARNING: Unable to verify timestamp for swenum.sys
*** ERROR: Module load completed but symbols could not be loaded for swenum.sys
*** WARNING: Unable to verify timestamp for USBD.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBD.SYS
*** WARNING: Unable to verify timestamp for Fs_Rec.SYS
*** ERROR: Module load completed but symbols could not be loaded for Fs_Rec.SYS
*** WARNING: Unable to verify timestamp for Beep.SYS
*** ERROR: Module load completed but symbols could not be loaded for Beep.SYS
*** WARNING: Unable to verify timestamp for mnmdd.SYS
*** ERROR: Module load completed but symbols could not be loaded for mnmdd.SYS
*** WARNING: Unable to verify timestamp for RDPCDD.sys
*** ERROR: Module load completed but symbols could not be loaded for RDPCDD.sys
*** WARNING: Unable to verify timestamp for SMBusP.sys
*** ERROR: Module load completed but symbols could not be loaded for SMBusP.sys
*** WARNING: Unable to verify timestamp for dump_WMILIB.SYS
*** ERROR: Module load completed but symbols could not be loaded for dump_WMILIB.SYS
*** WARNING: Unable to verify timestamp for ParVdm.SYS
*** ERROR: Module load completed but symbols could not be loaded for ParVdm.SYS
*** WARNING: Unable to verify timestamp for SIODRV.SYS
*** ERROR: Module load completed but symbols could not be loaded for SIODRV.SYS
*** WARNING: Unable to verify timestamp for dxgthk.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgthk.sys
*** WARNING: Unable to verify timestamp for Null.SYS
*** ERROR: Module load completed but symbols could not be loaded for Null.SYS
*** WARNING: Unable to verify timestamp for SENSUPGD.SYS
*** ERROR: Module load completed but symbols could not be loaded for SENSUPGD.SYS
*** WARNING: Unable to verify timestamp for audstub.sys
*** ERROR: Module load completed but symbols could not be loaded for audstub.sys
Couldn't resolve error at 'nalize -v'
Wydaje mi sie czy oprócz USB w logu jest informacje o kolejnym bledzie ?
CYTAT
Troszkę tWARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
*** WARNING: Unable to verify timestamp for NetMotCM.sys
*** ERROR: Module load completed but symbols could not be loaded for NetMotCM.sys
Probably caused by : NetMotCM.sys ( NetMotCM+b9c )
troche długie ale może to pomoże w ustaleniu przyczyny ?
Sterowniki zainstalowalem najnowsze jakie sa dostępne dla mojej plyty...a ze stara z niej babcia (Intel D850MV) to nie wiem czy te co były nie były czasem najnowsze ale nic ....teraz pozostaje mi czekac i miec nadzieje ze sterowniki to byla przyczyna : )
83.29.244.* napisał:
Wystarczy ze wkleisz blad:Probably caused by : NetMotCM.sys ( NetMotCM+b9c )
Nie musisz dawac reszty tych bazgrolow bo tam i tak nie ma nic do czytania.
Plik NetMotCM.sys jak udalo mi sie wyszukac na google to wlasnie steronik modemu kablowego prawdopodobnie motorili.
W polaczeniu z komunikatem BUGCODE_USB_DRIVER swiadczy to tylko i wylacznie o wadliwym sterniku tego urzadzenia.
Postaraj sie znalezc na stronie producenta najnowsze stery do tego modemu.
A druga sprawa to najswiezsze latki do systemu i lektura tego artykulu:
http://support.microsoft.com/default.aspx?scid=kb;pl;331988
Napisz czy te zabiegi pomogly a jesli nie to skontaktuj sie moze z adminem i powiedz mu co i jak. Niech albo przelaczy cie na interfejs ethernet albo niech wymieni co to urzadzenie
84.205.223.* napisał:
Wystarczy ze wkleisz blad:
Probably caused by : NetMotCM.sys ( NetMotCM+b9c )
Nie musisz dawac reszty tych bazgrolow bo tam i tak nie ma nic do czytania.
Plik NetMotCM.sys jak udalo mi sie wyszukac na google to wlasnie steronik modemu kablowego prawdopodobnie motorili.
W polaczeniu z komunikatem BUGCODE_USB_DRIVER swiadczy to tylko i wylacznie o wadliwym sterniku tego urzadzenia.
Postaraj sie znalezc na stronie producenta najnowsze stery do tego modemu.
A druga sprawa to najswiezsze latki do systemu i lektura tego artykulu:
http://support.microsoft.com/default.aspx?scid=kb;pl;331988
Napisz czy te zabiegi pomogly a jesli nie to skontaktuj sie moze z adminem i powiedz mu co i jak. Niech albo przelaczy cie na interfejs ethernet albo niech wymieni co to urzadzenie
Sorry na drugi raz zanim coś wkleje to sie zastanowie: )
Artykuł na stronie microsoftu przeczytałem (łatki microsoftu mam chyba zainstalowane wzelkie możliwe), przeinstalowałem sterowniki od modemu i napisałem do administartora mojej sieci.
Parwdopodobnie problem jest znany ponieważ bardzo szybko odpisał mi że jeżeli mam windows XP i procesor z obsługą HT to mam dwa rozwiązania:
1. Wyłaczenie HT
2. Podłaczenie modemu za pośrednictwem karty sieciowej
mam Intel Pentium IV 1,6GHz więc chyba moj procek nie obsluguje tej technologii ( w biosie nie moge nic namierzyc) oraz system windows xp....pozostanie pewnie zakup karty sieciowej
Dzięki za wszelkie porady Nyny...wiele mi pomogły
Pozdrawiam
83.29.211.* napisał:
No mam nadzieje ze podlaczeniu modemu poprzez Ethernet'a rozwiaze twoj problemPodobne tematy
Ciągłe zwisy
Zmiana procka i płyty i ciągłe zwiechy [b]Pomóżcie[/b]
ciągłe zwiechy - co jest??
Ciągłe Zwiechy
Zmiana procka i płyty i ciągłe zwiechy [b]Pomóżcie[/b]
ciągłe zwiechy - co jest??
Ciągłe Zwiechy
Działy
Copyright © 2002-2024 | Prywatność | Load: 1.38 | SQL: 1 | Uptime: 108 days, 14:09 h:m |
Wszelkie uwagi prosimy zgłaszać pod adresem eddy@heh.pl