[Win XP sp3] BugCheck 100000D1, {719fdf5d, 2, 8, 719fdf5d}
Witam od początku pojawia mi się BSOD tyle wiem że chodzi o jakiś sterownik ale kompletnie nie wiem o jaki
[quote=BSOD]DRIVER_IRQL_NOT_LESS_OR_EQUAL
STOP: 0x000000D1 (0x719fdf5d, 0x00000002, 0x00000008, 0x719fdf5d)[/quote]
[b]BSOD pojawia się jedynie przy przeglądaniu stron internetowych - obojętnie jakich. Czasami wystarczy, że odpalę przeglądarkę i przy wczytywaniu strony głównej pojawia się BSOD.
[/b]
Szukałem w googlach i niema ani jednego tematu rozwiązującego ten problem.
[quote="log z dmp ze wczoraj"]
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini040210-03.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 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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Apr 2 22:46:00.625 2010 (GMT+2)
System Uptime: 0 days 6:36:17.355
*********************************************************************
* 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
................
Unable to load image tcpip.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, a5100448, a42a48e8, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
Probably caused by : tcpip.sys ( tcpip+3448 )
Followup: MachineOwner
---------[/quote]
[quote="log z dmp - dzisiaj"]
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini040310-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 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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Apr 3 10:36:56.296 2010 (GMT+2)
System Uptime: 0 days 2:09:39.001
*********************************************************************
* 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
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {719fdf5d, 2, 8, 719fdf5d}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** 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 ***
*** ***
*************************************************************************
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
[/quote]
Mam ze 20 takich logów z DMP i każdy wygląda jak ten drugi.
Odpowiedzi: 10
To co mam mieć włączone dwie zapory? Systemową i Outposta??
Prędzej dwie włączone zapory będą kolidować niż pomogą.
Jutro odinstaluje outposta i zaryzykuje będę na samej systemowej zaporze i zobaczymy.
Właśnie - co do wyłączenia systemowej mam wątpliwości .....
Obecnie jedyna zaporą jest Outpost bo systemowa jest wyłączona A nod jako tako nie jest zaporą tylko antivirem
Później odinstaluje Outposta i zobaczymy czy będą dalej bsody.
Tu nie chodzi o "stary" czy "nowy" sprzęt. To jest konflikt programu z jądrem systemu. Najprościej - odinstalować FW i sprawdzić. Względnie - upewnij się przed deinstalacją czy jest włączone tylko jedna zapora.
ESET NOD oraz Outpost Firewall
może outpost ma jakiś problem ;p ale kiedyś go na starym kompie używałem i było git
Tcpip.sys i afd.sys - to pachnie konfliktem programowym. Jakiego używasz oprogramowania ochronnego ?
Obojętnie czy to jest Firefox czy IE i tak są bsody
a co do karty sieciowej: Realtek RTL8168C(P) PCI-E Gigabit Ethernet NIC
Co stery niby nie te? Czy może wadliwa sieciówka?
Dostawca sterownika: Realtek Semiconductor Corp
Data: 2008-01-03
Wersja: 5.686.103.2008
Podpisany cyfrowo Microsoft Windows Hardware Compatibility Publisher
Najśmieszniejsze jest to że podczas grania w gry wymagające stałego połączenia do internetu nie pojawiają się BSOD'y.
Pewnie chodzi o sieciówkę. Jaki sprzęt? Jaka przeglądarka ? Sprawdzałeś czy na innej przeglądarce to samo ?
@Up
powiedziałem że mam SP3 a zobacz że ta poprawka jest dla SP2 i pliku HTTP.sys
chkdsk /f sprawdzanie nie wykazało żadnych błędów
jak pojawi się kolejny BSOD podam całość
Na początek uruchom chkdsk /f spod konsoli. Podaj też dalszą część komunikatu bluescreena spod numerów błędu.
Ponadto jak się chce, to się znajdzie, to tak przy okazji Świąt:
http://support.microsoft.com/kb/916595/pl
Strona 1 / 1
[quote=lukas_1993]To co mam mieć włączone dwie zapory? Systemową i Outposta?? Prędzej dwie włączone zapory będą kolidować niż pomogą. Jutro odinstaluje outposta i zaryzykuje będę na samej systemowej zaporze i zobaczymy.[/quote]Od trzech czy czterech lat opieram się na systemowej zaporze i jakoś żyję więc przez te parę chwil też pociągniesz i nie zginiesz. Nie tragizuj tak. Btw... Miałem też kiedyś i systemową i Kerio i jakoś nic nie kolidowało. To tylko kwestia dopilnowania swoich gratów.
[quote=lukas_1993]To co mam mieć włączone dwie zapory? Systemową i Outposta?? [/quote] Nie - ale z pewnych powodów śmiem twierdzić że systemowa może być nadal włączona.