pojara utworzono 22 kwietnia 2009 utworzono 22 kwietnia 2009 witam wszystkich.mam problem z laptopem MSI Wind Netbook U100(orginalny system to SUSE Linux, obecnie winda xp sp2 i byla rowniez sp3). posiadma laptopa jakeies 2 miesiace i praktycznie od poczatku zakupu wyskakuje co jakis czas blue screen, bywa tak ze pare dni nic sie nie dziej ale bywa rowniez ,ze potrafi w ciagu 10 min wyskoczyc z 4 razy. raczej ten problem wyskakuje gdy probuje uruchomic przegladarke lub gdy ja uzywam (posiadam 2), czasami gdy wchodze do poczty incredimail. gdy wlacze jakas gre np XIII lub kurka wodna:D wszystko dziala bez zarzutów nic sie nie dzieje , testowalem jakimis programami i dysk twardy i pamiec ram lecz nic nie wskazywalo aby cos sie dzialo z nimi. czy moze byc to spowodowane tym ze msi to dno i sterowniki jakies slabe jak ta cala firma? z gory dziki za pomoc
rideluk komentarz 23 kwietnia 2009 komentarz 23 kwietnia 2009 jaka jest tresc tego BSODa? masz jakis plik w folderze windows/minidump?
Gość komentarz 23 kwietnia 2009 komentarz 23 kwietnia 2009 MSI to nie jest dno . To bardzo dobra firma . Ja też mam MSI Wind U100 i u mnie naprzykład nie wszystkie funkcje działały na Linuxie , komp sie zawieszał . Cały czas coś się działo . Przeżudziciłem sie na XP SP3 i wszystko OK . masz jakis plik w folderze windows/minidump? Sprawdź to .
pojara komentarz 23 kwietnia 2009 Autor komentarz 23 kwietnia 2009 jaka jest tresc tego BSODa? masz jakis plik w folderze windows/minidump? co do BSOD-a za szybko mija ale sprobuje jakos odczytac co go boli a co do windows/minidump- mam jakies 14 pliczkow czy podac jakie numerki ma lazdy? czy mozna je usunac?
rideluk komentarz 23 kwietnia 2009 komentarz 23 kwietnia 2009 no wlasnie. te pliczki to swieta rzecz. mozna sie dowiedziec co jest nie tak.. zainstaluj narzędzie WinDbg wchodzące w skład Debugging Tools for Windows. http://www.microsoft.com/whdc/devtools/deb...ng/default.mspx tutaj masz ladnie wytlumaczone. Zrob analize najnowszego pliku w mindump i wklej nam raport z WinDbg.. http://forum.pcformat.pl/showthread.php?tid=8255
pojara komentarz 23 kwietnia 2009 Autor komentarz 23 kwietnia 2009 dobra wklejam ta angielszczyzne i czarna magie Microsoft ® Windows Debugger Version 6.11.0001.404 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini042309-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 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 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700 Debug session time: Thu Apr 23 00:38:15.359 2009 (GMT+2) System Uptime: 0 days 0:54:39.060 ********************************************************************* * 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 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 ............... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000000A, {0, 1c, 0, 80501ffb} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** WARNING: Unable to verify timestamp for hal.dll *** ERROR: Module load completed but symbols could not be loaded for hal.dll ************************************************************************* *** *** *** *** *** 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 TfNetMon.sys *** ERROR: Module load completed but symbols could not be loaded for TfNetMon.sys *** WARNING: Unable to verify timestamp for tcpipBM.SYS *** ERROR: Module load completed but symbols could not be loaded for tcpipBM.SYS *** WARNING: Unable to verify timestamp for afd.sys *** ERROR: Module load completed but symbols could not be loaded for afd.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 *** *** *** ************************************************************************* ********************************************************************* * 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+ * ********************************************************************* ********************************************************************* * 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+ * ********************************************************************* Probably caused by : TfNetMon.sys ( TfNetMon+5386 ) Followup: MachineOwner ---------
Psycholandia komentarz 24 kwietnia 2009 komentarz 24 kwietnia 2009 tu masz pochodzenie pliku: TfNetMon.sys http://www.greatis.com/appdata/a/t/tffsmon.sys.htm odinstaluj program związany z nim
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.