Filo1 utworzono 31 sierpnia 2010 utworzono 31 sierpnia 2010 (edytowane) Witam Dzisiaj wyskoczył mi bluescreen zignorowałem to lecz po 40 min wyskoczył kolejny i tak cały dzień w każdym dowolnym momencie nie ma znaczenia co robię tutaj kod błędu [URL=http://img842.imageshack.us/i/zdjcie0113d.jpg/][IMG]http://img842.imageshack.us/img842/7207/zdjcie0113d.th.jpg[/IMG][/URL] Thankszauważyłem że zawsze to się dzieje gdy przewijam stronę scrolem ale cały czas przewijam nawet teraz i teraz nie dostałem bluescreena o co tu biegateraz co 10 min ;/
raazor90 komentarz 31 sierpnia 2010 komentarz 31 sierpnia 2010 Wykonaj: http://www.forumpc.pl/index.php?showtopic=16074
Filo1 komentarz 3 września 2010 Autor komentarz 3 września 2010 (edytowane) zaraz to wykonam lecz po odłączeniu podstawki DSS-25 problem ustąpił pytanie sterownik czy sama podstawka winna później odinstaluje sterowniki od podstawki [log]******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000000A, {ffdf, 2, 1, 806e6a8e} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** WARNING: Unable to verify timestamp for ftdibus.sys *** ERROR: Module load completed but symbols could not be loaded for ftdibus.sys *** WARNING: Unable to verify timestamp for ftser2k.sys *** ERROR: Module load completed but symbols could not be loaded for ftser2k.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 <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 : ftdibus.sys ( ftdibus+1b0e ) Followup: MachineOwner --------- [/log] inne stery wgrane co podstawka uszkodzona ? nadal BSODY ~bump poomocy ludzie nie moge softa do telefonu wgrać bo BSODY sypie co 15 min strach podłączać podstawkę co dopiero flashowaćrefresh
EnergyShot komentarz 3 września 2010 komentarz 3 września 2010 BSOD'y Ci sypię , ponieważ sterownik jakiego używasz do telefonu ma jakiś konflikt..
Filo1 komentarz 4 września 2010 Autor komentarz 4 września 2010 Heh tego się domyślam tylko nie mam pojęcia z czym może mieć konflikt na drugim kompie działa bez zarzutu na win7
raazor90 komentarz 5 września 2010 komentarz 5 września 2010 Odinstaluj sterowniki, przeczyść rejestr CCleanerem i zainstaluj najnowszą wersję
Filo1 komentarz 5 września 2010 Autor komentarz 5 września 2010 a i jeszcze jedno jak zmieniam port to może mieć wpływ? bo ja zmieniłem port 45 na port no. 2no i znowu BSOD znowu grrr
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.