Minidump, Reset i Net


(Kaadeel1990) #1

mam problem i licze na wasza pomoc

mianowicie komp dzialal świetnie bez zarzutu, do momentu coś przed świętami... wiadomo komp sie zaśmiecil i zrobilem mu format, świeżak i działa dobrze, lecz ma resety (znaczy sie bluescreeny i minidump sie pojawiaja)... za ktorymś razem tak sie resetnał, że net (od netii) zdechł - czyli polaczony zostal do neta, ale żadnej poza tym reakcji, FF 3.0b nie uruchamial sie, dla alternatywy IE 7.0 tez nie dzialalo, GG (pod AQQ) sie nie laczylo... czyli net is dead!

innego wyboru nie bylo niż zrobić raz jeszcze format! zrobilem i po tygodniu ta sama sytuacja... za ktoryms razem sie resetnal ze dostal te same skutki co ostatnio i znow format!

po formacie nie było już bluescreenow, ale za to net (czyli p2p - uTorrent i eMule) nie pobierają z max predkością, co wczesniej nie sprawialo problemow, za to FF czy FlashGet pobierają z maximum łącza! - mialem NOD32 3.0 i firewall SP2

i myslalem ze to sprawka firewalla od SP2 bo mial problem z portami najpierw, ale potem się ustosunkowal jakoś od siebie ;/ - dziwne

wiec zainstalowalem Outpost Firewall Pro 2008 - i wykrylem sprawce! bo od momentu jego dzialania zaczely sie dziać te boazerie...

potem doszedlem do wniosku, że to się dzialo za sprawą Outpost Firewall Pro (wersja bez znaczenia - bo 4.0 i 2008 to samo powodowalo) - wiec po instalacji i doswiadczeniu calej sprawy, postanowilem go odinstalować... problem z glowy (teoretycznie)

dziś siostra oznajmia ze znowu dostal reseta i pliki minidump sie zjawily w folderze...

czy możecie sprawdzić na podstawie plikow w minidump co może być przyczyną tego problemu i jak mu zaradzic...

oraz sprawa nr 2 - czy możecie coś poradzić na tego neta... mam mam XP'ka SP2 (przez caly czas) ; neta od netii przez USB SAGEM F@st 800... i zainstalowany cFosSpeed... dodam, że wczesniej czyli od kiedy mam neta w 2006r do tego kwietnia dzialało bez zarzutu i nie bylo sie czego przyczepic... a teraz jak mam 128KB max łacza to teraz maxymalnie sciaga przez p2p z predkoscia do ok 60KB i nie wiecej!

licze na wasza pomoc


(pakeroso) #2

Mogłeś złapać jakiegoś wirusa który siedzi na innej partycji (chociaż to mało prawdopodobne), może to być wina programu który masz zainstalowany, a on po czasie psuje ci system (u mnie tak było z VTP), może to być wina sprzętowa np. przegrzewające się kości lub proc.

Aby sprawdzić zawartość minidump'ów pobierz i zainstaluj Debugging Tools for Windows (v6.8 chyba najnowsza). Odpalasz go przez WinDbg, następnie File -> Open Crash Dump... Na samym dole loga będziesz mieć nazwę pliku który może powodować awarię - wpisz je tutaj bądż poszukaj w :google:

Niestety jeśli to będzie wina sprzętu to minidump'y mogą wskazywać błędne diagnozy.


(sdar) #3

Proszę o zmianę tytułu na bardziej konkretny.

Użyj opcji zmien.gif

Pomocne może być zapoznanie się z TYMI informacjami.


(Kaadeel1990) #4

dobra zarzucam ostatni z nich...

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86

Copyright (c) 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 0n2

*** 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) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0

Debug session time: Wed Apr 2 15:14:24.656 2008 (GMT+2)

System Uptime: 0 days 7:51:17.435

*********************************************************************

* 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 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

.............

Unable to load image psched.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for psched.sys

*** ERROR: Module load completed but symbols could not be loaded for psched.sys

Unable to load image NDIS.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for NDIS.sys

*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 100000D1, {6e6f6974, 2, 0, ba4e2258}


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


*** WARNING: Unable to verify timestamp for cfosspeed.sys

*** ERROR: Module load completed but symbols could not be loaded for cfosspeed.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!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 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Probably caused by : cfosspeed.sys ( cfosspeed+29d6b )


Followup: MachineOwner

---------

czy będziecie w stanie jakoś mi pomóc ?