[W koszu] - Blue Screen Win 7 64bit - co powoduje?

Zaloguj się Zarejestruj się

Całe forum

Przeszukaj

Całe forum

Użytkownicy

Wątek zamknięty

Tryb drzewa \| Tryb normalny [W koszu] Blue Screen Win 7 64bit - co powoduje?
Ethrond Nowy Liczba postów: 0	Post: #1 Blue Screen Win 7 64bit - co powoduje? Witam mam problem Od ostatniego czasu pojawiają sie blue screeny: Kod: Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C: \Windows\Minidump\080315-15974-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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff800`02e12000 PsLoadedModuleList = 0xfffff800`03059730 Debug session time: Mon Aug 3 19: 03: 13.431 2015 (GMT+2) System Uptime: 0 days 0: 00: 05.258 ******************************************************************* * 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 Mini Kernel Dump does not contain unloaded driver list ***************************************************************************** * * * Bugcheck Analysis * * * ***************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8007ae18f8, 0, 0} * 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!_WHEA_ERROR_RECORD_HEADER * * * ********************************************************************* ********************************************************************* * * * * * 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!_WHEA_ERROR_RECORD_HEADER * * * ********************************************************************* Unable to load image PSHED.dll, Win32 error 0n2 * WARNING: Unable to verify timestamp for PSHED.dll * ERROR: Module load completed but symbols could not be loaded for PSHED.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: pshed!_WHEA_ERROR_RECORD_HEADER * * * ********************************************************************* ********************************************************************* * * * * * 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR * * * ********************************************************************* ********************************************************************* * * * * * 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: pshed!_WHEA_ERROR_RECORD_HEADER * * * ********************************************************************* ********************************************************************* * * * * * 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: pshed!_WHEA_ERROR_RECORD_HEADER * * * ********************************************************************* ********************************************************************* * * * * * 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: pshed!_WHEA_ERROR_RECORD_HEADER * * * ********************************************************************* ********************************************************************* * * * * * 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 : hardware Followup: MachineOwner --------- Proszę kogos o pomoc Czeman na odpowiedz Pozdrawiam 03.08.2015 18:19
Podziękowania od:

thermalfake Ostatni Mohikanin Liczba postów: 13.580	Post: #2 RE: Blue Screen Win 7 64bit Proszę usunąć tę bezużyteczną próbę użycia debuggera - nie ma skonfigurowanych symboli. Wrzucić na forum spakowane pliki *.dmp z widocznej lokalizacji do prawidłowej i szczegółowej analizy - C:\Windows\Minidump\ Proszę podać pełną i dokładną specyfikację systemu - jeśli działa tryb awaryjny z obsługa sieci to ją włączyć i zrzucić informacje z programów do identyfikowania sprzętu albo print screen z msinfo32.exe z wiersza cmd. Nie zawsze ją jestem w stanie wyciągnąć z bsoda co jest pomocne. Ponadto na forum piszemy za pomocą polskiego układu klawiatury (znaki diakrytyczne) - jeśli nie ma to doinstalować. W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu. Jak mądrze zadawać pytania? - przejrzyj poradnik na forum. Nie udzielam porad via PW. 03.08.2015 18:57
Podziękowania od:

Ethrond Nowy Liczba postów: 0	Post: #3 RE: Blue Screen Win 7 64bit - co powoduje? Plik dmp: http://przeklej.org/file/Mygnp7/080315-15974-01.dmp Specyfikacja systemu: Jeżeli czegoś brakuje proszę napisać ponieważ jestem zielony w tych sprawach. 03.08.2015 19:17
Podziękowania od:

thermalfake Ostatni Mohikanin Liczba postów: 13.580	Post: #4 RE: Blue Screen Win 7 64bit - co powoduje? No to jeszcze pełny log z Microsoft Genuine Advantage Diagnostic Tool. W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu. Jak mądrze zadawać pytania? - przejrzyj poradnik na forum. Nie udzielam porad via PW. 04.08.2015 06:48
Podziękowania od:

Ethrond Nowy Liczba postów: 0	Post: #5 RE: Blue Screen Win 7 64bit - co powoduje? Diagnostic Report (1.9.0027.0): ----------------------------------------- Windows Validation Data--> Validation Code: 0 Cached Online Validation Code: 0x0 Windows Product Key: ***-*-GJY49-VJBQ7-HYRR2 Windows Product Key Hash: W5/6nm6F2UPXrCkY5xUhXb/+21g= Windows Product ID: 00426-OEM-8992662-00006 Windows Product ID Type: 2 Windows License Type: OEM SLP Windows OS version: 6.1.7601.2.00010100.1.0.001 ID: {FDE28774-3800-4E20-B22B-8FCE08BA2F9E}(3) Is Admin: Yes TestCab: 0x0 LegitcheckControl ActiveX: N/A, hr = 0x80070002 Signed By: N/A, hr = 0x80070002 Product Name: Windows 7 Ultimate Architecture: 0x00000009 Build lab: 7601.win7sp1_gdr.150525-0603 TTS Error: Validation Diagnostic: Resolution Status: N/A Vista WgaER Data--> ThreatID(s): N/A, hr = 0x80070002 Version: N/A, hr = 0x80070002 Windows XP Notifications Data--> Cached Result: N/A, hr = 0x80070002 File Exists: No Version: N/A, hr = 0x80070002 WgaTray.exe Signed By: N/A, hr = 0x80070002 WgaLogon.dll Signed By: N/A, hr = 0x80070002 OGA Notifications Data--> Cached Result: N/A, hr = 0x80070002 Version: N/A, hr = 0x80070002 OGAExec.exe Signed By: N/A, hr = 0x80070002 OGAAddin.dll Signed By: N/A, hr = 0x80070002 OGA Data--> Office Status: 109 N/A OGA Version: N/A, 0x80070002 Signed By: N/A, hr = 0x80070002 Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3 Browser Data--> Proxy settings: N/A User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32) Default Browser: C:\Program Files (x86)\Opera\launcher.exe Download signed ActiveX controls: Prompt Download unsigned ActiveX controls: Disabled Run ActiveX controls and plug-ins: Allowed Initialize and script ActiveX controls not marked as safe: Disabled Allow scripting of Internet Explorer Webbrowser control: Disabled Active scripting: Allowed Script ActiveX controls marked as safe for scripting: Allowed File Scan Data--> Other data--> Office Details: <GenuineResults><MachineData><UGUID>{FDE28774-3800-4E20-B22B-8FCE08BA2F9E}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*-*-*-*-HYRR2</PKey><PID>00426-OEM-8992662-00006</PID><PIDType>2</PIDType><SID>S-1-5-21-3868114190-1163008898-3392627017</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>H81M-H</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>FA</Version><SMBIOSVersion major="2" minor="7"/><Date>20140704000000.000000+000</Date></BIOS><HWID>4E8A3407018400F4</HWID><UserLCID>0415</UserLCID><SystemLCID>0415</SystemLCID><TimeZone>Środkowoeuropejski czas stand.(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>ACRSYS</OEMID><OEMTableID>ACRPRDCT</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> Spsys.log Content: 0x80070002 Licensing Data--> Wersja usługi licencjonowania oprogramowania: 6.1.7601.17514 Nazwa: Windows® 7, Ultimate edition Opis: Windows Operating System - Windows® 7, OEM_SLP channel Identyfikator aktywacji: 7cfd4696-69a9-4af7-af36-ff3d12b6b6c8 Identyfikator aplikacji: 55c92734-d682-4d71-983e-d6ec3f16059f Rozszerzony identyfikator PID: 00426-00178-926-600006-02-1045-7600.0000-2032015 Identyfikator instalacji: 019453080185070055164751747450079130880853845343382070 Adres URL certyfikatu procesora: http://go.microsoft.com/fwlink/?LinkID=88338 Adres URL certyfikatu komputera: http://go.microsoft.com/fwlink/?LinkID=88339 Adres URL licencji użytkowania: http://go.microsoft.com/fwlink/?LinkID=88341 Adres URL certyfikatu klucza produktu: http://go.microsoft.com/fwlink/?LinkID=88340 Częściowy klucz produktu: HYRR2 Stan licencji: licencjonowano Licznik pozostałych operacji przywrócenia pierwotnego stanu licencjonowania systemu Windows: 4 Godzina zaufana: 2015-08-04 12:52:26 Windows Activation Technologies--> HrOffline: 0x00000000 HrOnline: 0x00000000 HealthStatus: 0x0000000000000000 Event Time Stamp: 7:25:2015 16:24 ActiveX: Registered, Version: 7.1.7600.16395 Admin Service: Registered, Version: 7.1.7600.16395 HealthStatus Bitmask Output: HWID Data--> HWID Hash Current: NAAAAAEAAgABAAIAAAAEAAAAAQABAAEAln3Gw+po7GrCG1pSqvfE3oqb9AF6OTPQnh3I9g== OEM Activation 1.0 Data--> N/A OEM Activation 2.0 Data--> BIOS valid for OA 2.0: yes Windows marker version: 0x20001 OEMID and OEMTableID Consistent: yes BIOS Information: ACPI Table Name OEMID Value OEMTableID Value APIC ALASKA A M I FACP ALASKA A M I HPET ALASKA A M I MCFG ALASKA A M I FPDT ALASKA A M I SSDT PmRef Cpu0Ist SSDT PmRef Cpu0Ist SSDT PmRef Cpu0Ist SSDT PmRef Cpu0Ist DMAR INTEL HSW SLIC ACRSYS ACRPRDCT Notatka została dodana 04.08.2015 20:21. Ostatnia edycja dokonana 04.08.2015 20:21 przez irocket**: Na forum nie tolerujemy piractwa 04.08.2015 11:54
Podziękowania od:

Wątek zamknięty

Podobne wątki
Wątek:	Autor	Odpowiedzi:	Wyświetleń:	Ostatni post
W koszu Blue Screen	Jozefa	1	749	18.02.2016 23:20 Ostatni post: thermalfake
W koszu Bluescreen 0x00000124 Win7 64bit po formacie	Xylos	1	486	27.01.2016 02:06 Ostatni post: thermalfake
W koszu blue screen 0x0000050	Dexter1412	4	706	08.10.2015 23:17 Ostatni post: Dexter1412
W koszu Blue Screen 0x0000009f	xRazoor	0	412	20.02.2015 18:58 Ostatni post: xRazoor
W koszu Blue Screen przy filmach online	sirnative	5	993	11.02.2015 16:53 Ostatni post: thermalfake
W koszu blue screen 3b i d5	PLDaro	2	829	29.01.2015 21:53 Ostatni post: thermalfake

« Starszy wątek | Nowszy wątek »

Autor: Ethrond
Temat został oceniony na 0 w skali 1-5 gwiazdek.
Zebrano 1 głosów.

Regulamin for | Polityka Prywatności | Oznacz wszystkie działy jako przeczytane | Ekipa forum | Statystyki | Wersja mobilna | Użytkownicy | Wersja Lo-Fi | Mapa strony |

Copyright © Windows 7 Forum