iuve Opublikowano 10 Czerwca 2015 Zgłoś Opublikowano 10 Czerwca 2015 Witam, Piszę w imieniu koleżanki, który ma ewidentny problem ze stabilnością systemu Windows 8.1 na laptopie ASUS. Niedawno robiła format z powodu wirusów, niby wszystko działało, aż zaczęły ją męczyć blue screeny z oznaczeniem Critical_Process_Died. Blue screeny dzieją się losowo, kilka razy na dzień. Czasem po takim screenie laptop nie chce sie dłuższą chwilę włączyć. W managarze urządzeń nie ma błędów. Przywracanie systemu nie wchodzi w gre raczej, bo jej bolączki zaczęły się już na samym początku. Kilka razy był przywracany system i instalowane sterowniki z płyty głównej (INF widniał z wykrzyknikiem w managarze urządzeń - kontrola magistralii zarządzania systemem, potem po zainstalowaniu INF z płyty wykrzyknik zniknął). Wrzucam raport z debuggera. Jest ktoś w stanie coś poradzić co może byc przyczyną? Microsoft ® Windows Debugger Version 6.3.9600.17336 AMD64Copyright © Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\060815-45093-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol 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 \SystemRoot\system32\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.exeWindows 8 Kernel Version 9600 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.16384.amd64fre.winblue_rtm.130821-1623Machine Name:Kernel base = 0xfffff800`b9c14000 PsLoadedModuleList = 0xfffff800`b9edb9b0Debug session time: Mon Jun 8 20:26:39.422 2015 (UTC + 1:00)System Uptime: 0 days 11:25:49.067********************************************************************** 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 \SystemRoot\system32\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.exeLoading Kernel Symbols..................................................................................................................................................................Loading User SymbolsLoading unloaded module list................************* Symbol Loading Error Summary **************Module name Errorntoskrnl The system cannot find the file specifiedYou can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.You should also verify that your symbol search path (.sympath) is correct.******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck EF, {ffffe00002c82480, 0, 0, 0}***** Kernel symbols are WRONG. Please fix symbols to do analysis.----- ETW minidump data unavailable-----unable to get nt!KiCurrentEtwBufferOffsetunable to get nt!KiCurrentEtwBufferBase**************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands 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 ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands 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 ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands 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 ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands 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 ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands 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 ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands 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 ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands 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 ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands 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 : ntoskrnl.exeFollowup: MachineOwner--------- Cytuj
Gość znaffca Opublikowano 11 Czerwca 2015 Zgłoś Opublikowano 11 Czerwca 2015 nic za bardzo sie nie przegrzewa ? jak z sterownikami? Cytuj
iuve Opublikowano 11 Czerwca 2015 Autor Zgłoś Opublikowano 11 Czerwca 2015 nic za bardzo sie nie przegrzewa ? jak z sterownikami? Czasem mówiła, że laptop gorący, ale odkąd ma go tylko i wyłącznie na biurku (po kablu), to niby jest okej. Ale jak faktycznie jest, tego nie wiem. Laptop nieużywany w ogóle do gier - głównie internet/webtv, czasem photoshop. Jak sprawdzić temperatury i jakie powinny być prawidłowe? Natomiast sterowniki powinna mieć ok. W managarze urządzeń nie ma błędów na chwilę obecną - miała błąd magistralii zarządzania systemem, ale wyeliminowała go instalując z płyty dołączonej do laptopa sterownik INF (choć ten błąd widniał jej jakiś czas po formacie, po instalacji programów, innych sterowników itd, dopiero później go wyeliminowała). To samo z grafiką, też miała błąd, jednak (uprzednio wywalajac stare sterowniki) zainstalowala z nvidii troszkę starsze sterowniki i błąd zniknął. Czego błąd może dotyczyć? Gdzie szukać? Mogą mieć wpływ sterowniki z karty graficznej, które prawdopodobnie nie są najnowsze? Formatować nie chce za bardzo, dopiero co ~3 tyg temu to robiła i sobie wszystko na nowo ustawiła. Boję się, że bląd może powrócić. Laptop zakupiony ok ~1,5roku temu, wgrany docelowo był windows 8, ale bez partycji recovery - format robiony na płytce z windows 8.1. Myślę że mogła coś namieszać, bo kilka razy odzyskiwanie robiła po blu skrinach/totalnych zwiechach lapa (też miała blu skrin z grafiką związany, nie pamietam jaki). Czy to bardziej hardware czy soft? Czy dzienne występowanie tego błędu może FIZYCZNIE popsuć laptopa? Cytuj
Rekomendowane odpowiedzi
Dołącz do dyskusji
Możesz dodać zawartość już teraz a zarejestrować się później. Jeśli posiadasz już konto, zaloguj się aby dodać zawartość za jego pomocą.