gracz722 354 Napisano 23 Kwietnia 2018 Udostępnij Napisano 23 Kwietnia 2018 (edytowane) Witam, mam dosyć nietypowy problem z bluescreenami na komputerze, gdy mam zainstalowany Windows 7, na komputerze nie ma resetów, ale gdy zainstaluję Win10 co jakiś czas(2-15h) wywali niebieski ekran. Na komputerze zainstalowane mam tylko sterowniki od płyty, karty, bitdefender, chrome, metin2, dxtory. Niestety na win7 dxtory nie działa najlepiej, na 10 spełnia moje oczekiwania, ale występują bluescreeny. Co ciekawe procek i płyta bardziej pod Win10 przystosowane i z Win7 trzeba kombinować. PC: ryzen 7 1800x, ax370 gaming 5, gt1030, rm550x, 16gb g.skilla(kilka razy testowane, w 100% sprawne), goodram iridium pro 2gen Pliki dmp: https://megawrzuta.pl/download/a33072bb5748be972f35e111812f2a7c.html https://megawrzuta.pl/download/520e858a0821ded38a3bb121b526b3f5.html Z góry dziękuje za porady Edytowane 23 Kwietnia 2018 przez gracz722 Cytuj Link to post Share on other sites
jarrino 3909 Napisano 23 Kwietnia 2018 Udostępnij Napisano 23 Kwietnia 2018 Pobierz program WinDbg i odczytaj te pliki. Cytuj Link to post Share on other sites
gracz722 354 Napisano 23 Kwietnia 2018 Autor Udostępnij Napisano 23 Kwietnia 2018 (edytowane) Niżej podaję odczyty Moim zdaniem problem tkwi w rejestrze i z usuwaniem bibliotek dll. Po resecie zawsze mam dużo nieprawidłowości w rejestrze(sprawdzam ccleanerem) Microsoft ® Windows Debugger Version 6.11.0001.402 X86Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Dominik\Desktop\042318-5250-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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeWindows 7 Kernel Version 16299 MP (16 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 16299.15.amd64fre.rs3_release.170928-1534Machine Name:Kernel base = 0xfffff801`fb088000 PsLoadedModuleList = 0xfffff801`fb3ee070Debug session time: Mon Apr 23 18:26:56.798 2018 (GMT+2)System Uptime: 0 days 0:29:36.486********************************************************************** 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*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeLoading Kernel Symbols...................................................................................................................................................................................Loading User SymbolsLoading unloaded module list.......******************************************************************************** ** Bugcheck Analysis ** ******************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff801fb0ed2a0, ffffd0028b192b78, ffffd0028b1923c0} ***** 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 ****** ************************************************************************************************************************************************** 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 : ntoskrnl.exe ( nt+652a0 ) Followup: MachineOwner--------- Microsoft ® Windows Debugger Version 6.11.0001.402 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Dominik\Desktop\042318-5343-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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 16299 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 16299.15.amd64fre.rs3_release.170928-1534 Machine Name: Kernel base = 0xfffff803`76c84000 PsLoadedModuleList = 0xfffff803`76fea070 Debug session time: Mon Apr 23 00:04:38.018 2018 (GMT+2) System Uptime: 0 days 1:19:03.704 ********************************************************************* * 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 *** 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 1000007E, {ffffffffc0000005, fffff80376ce92a0, ffff810b8bb92b78, ffff810b8bb923c0} *** WARNING: Unable to verify timestamp for mssmbios.sys *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys ***** 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 *** *** *** ************************************************************************* ********************************************************************* * 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 : ntoskrnl.exe ( nt+652a0 ) Followup: MachineOwner --------- Microsoft ® Windows Debugger Version 6.11.0001.402 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Dominik\Desktop\042318-5281-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 \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.exe Windows 7 Kernel Version 16299 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 16299.15.amd64fre.rs3_release.170928-1534 Machine Name: Kernel base = 0xfffff800`f7c1c000 PsLoadedModuleList = 0xfffff800`f7f82070 Debug session time: Mon Apr 23 22:48:58.412 2018 (GMT+2) System Uptime: 0 days 1:31:19.094 ********************************************************************* * 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.exe Loading Kernel Symbols ............................................................... ................................................................ ................................................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41201, ffff9b3ffc12e000, 1, ffffbb093205c010} ***** 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 *** *** *** ************************************************************************* ********************************************************************* * 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 : ntoskrnl.exe ( nt+175930 ) Followup: MachineOwner --------- Edytowane 23 Kwietnia 2018 przez gracz722 Cytuj Link to post Share on other sites
mabrothrax 5730 Napisano 24 Kwietnia 2018 Udostępnij Napisano 24 Kwietnia 2018 (edytowane) Wychodzi z nich tylko tyle, że w swoich systemie nie masz odpowiednich assetów do poprawnego debugowania programem WinDBg. By to naprawić, musisz ustawić systemową zmienną _NT_SYMBOL_PATH. Online'owe repo dla tych symboli to srv*[local cache]*[private symbol server]*https://msdl.microsoft.com/download/symbols. Więcej info na ten temat znajdziesz -> https://msdn.microsoft.com/en-us/library/windows/desktop/ee416588%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396 Aczkolwiek zamiast się z tym bawić to polecałbym po prostu przeczytać komunikat z bluescreena, zapisać błąd. Odpalić OS znowu, wejść do Event Viewera i w zakładce system oraz application szukać chwile przed godziną bluescreena Warningów lub Errorów, czytać co to i wysnuwać wnioski na tej podstawie. Ewentualnie jeśli to cykliczne, to poczekać mniej więcej do momentu kiedy się to dzieje, odpalić przed tym procmona i zacząć logować, po bluescreenie zacząć debugować log procmona. Aczkolwiek Event Viewer powinien wystarczyć, to stacja robocza a nie serwer NASA. Edytowane 24 Kwietnia 2018 przez mabrothrax 1 Cytuj Link to post Share on other sites
jarrino 3909 Napisano 24 Kwietnia 2018 Udostępnij Napisano 24 Kwietnia 2018 Możesz wypróbować FixWin 10. U mnie naprawił parę problemów i nic nie zepsuł. 1 Cytuj Link to post Share on other sites
gracz722 354 Napisano 24 Kwietnia 2018 Autor Udostępnij Napisano 24 Kwietnia 2018 (edytowane) W podglądzie zdarzeń krytycznych, mam 9 krytyków gdy wystąpił reset i każdy ma słowa kluczowe: (70368744177664),(2) BugcheckCode 26 BugcheckParameter1 0x41792 BugcheckParameter2 0xffffa93ffffa4000 BugcheckParameter3 0x2 BugcheckParameter4 0x0 SleepInProgress 0 PowerButtonTimestamp 0 BootAppStatus 0 Checkpoint 0 ConnectedStandbyInProgress false SystemSleepTransitionsToOn 0 CsEntryScenarioInstanceId 0 BugcheckInfoFromEFI true CheckpointStatus 0 BugcheckCode 59 BugcheckParameter1 0xc0000005 BugcheckParameter2 0xfffff802b9af62a0 BugcheckParameter3 0xffffed083ac3d0f0 BugcheckParameter4 0x0 SleepInProgress 0 PowerButtonTimestamp 0 BootAppStatus 0 Checkpoint 0 ConnectedStandbyInProgress false SystemSleepTransitionsToOn 0 CsEntryScenarioInstanceId 0 BugcheckInfoFromEFI true CheckpointStatus 0 BugcheckCode 126 BugcheckParameter1 0xffffffffc0000005 BugcheckParameter2 0xfffff801fb0ed2a0 BugcheckParameter3 0xffffd0028b192b78 BugcheckParameter4 0xffffd0028b1923c0 SleepInProgress 0 PowerButtonTimestamp 0 BootAppStatus 0 Checkpoint 0 ConnectedStandbyInProgress false SystemSleepTransitionsToOn 0 CsEntryScenarioInstanceId 0 BugcheckInfoFromEFI true CheckpointStatus 0 EventData BugcheckCode 0 BugcheckParameter1 0x0 BugcheckParameter2 0x0 BugcheckParameter3 0x0 BugcheckParameter4 0x0 SleepInProgress 0 PowerButtonTimestamp 0 BootAppStatus 0 Checkpoint 0 ConnectedStandbyInProgress false SystemSleepTransitionsToOn 2 CsEntryScenarioInstanceId 0 BugcheckInfoFromEFI true CheckpointStatus 0 Edytowane 24 Kwietnia 2018 przez gracz722 Cytuj Link to post Share on other sites
mabrothrax 5730 Napisano 24 Kwietnia 2018 Udostępnij Napisano 24 Kwietnia 2018 Screena daj z eventa a nie taki szajs przeklejasz. Cytuj Link to post Share on other sites
gracz722 354 Napisano 24 Kwietnia 2018 Autor Udostępnij Napisano 24 Kwietnia 2018 O coś takiego chodzi? Cytuj Link to post Share on other sites
lonialomax 806 Napisano 24 Kwietnia 2018 Udostępnij Napisano 24 Kwietnia 2018 (edytowane) Jest to samo co poprzednio problemy z adresowaniem pamięci. BUGCHECK_STR: 0x3BPROCESS_NAME: SearchFilterHoMODULE_NAME: memory_corruptionIMAGE_NAME: memory_corruptionFOLLOWUP_NAME: memory_corruptionJeżeli na Windows 7 nie ma problemów to wygląda, że jakieś oprogramowanie nie współgra z Windows 10. Przetestuj po kolei bez poszczególnych programów może wyłapiesz który bruździ. Edytowane 24 Kwietnia 2018 przez lonialomax 2 Cytuj Link to post Share on other sites
jarrino 3909 Napisano 24 Kwietnia 2018 Udostępnij Napisano 24 Kwietnia 2018 (edytowane) Jak @up i dodatkowo radzę jak najmniej wszelkiego rodzaju programów narzędziowych do systemu. Ja miałem kłopoty właśnie przez nie,oczywiście legalne. A tak myślę spróbuję,zobaczę,może się przyda. Niestety niektóre powodowały bardzo dziwne zachowanie komputera,tak jakby coś się miało zepsuć. Raz chłodzenie,innym razem grafika itp. Siedziałem nad tym czasami parę dni,a rozwiązanie przychodziło czasem przez przypadek (odinstalowanie jakiegoś programu do systemu).Im mniej,tym lepiej. Tym bardziej,że wiele z nich nie jest ,albo są słabo zoptymalizowane pod dziesiątkę. Edytowane 24 Kwietnia 2018 przez jarrino Cytuj Link to post Share on other sites
gracz722 354 Napisano 27 Kwietnia 2018 Autor Udostępnij Napisano 27 Kwietnia 2018 (edytowane) Zrobiłem aktualizacje wszystkich sterowników, może to pomoże Po przeinstalowaniu na starszą wersję systemu (Win10), problemy zniknęły, więc na 90% przyczyną problemów była instalka windowsa:-) Edytowane 27 Kwietnia 2018 przez gracz722 Cytuj Link to post Share on other sites
Recommended Posts
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ą.