Tryb drzewa | Tryb normalny
|
Ocena wątku:
- 0 Głosów - 0 Średnio
- 1
- 2
- 3
- 4
- 5
Częste Blue Screeny podczas użytkowania Windows 7
|
fakeman
Nowy
Liczba postów: 2
Dołączył: Jan 2012
Reputacja: 0
Podziękował: 0
Pomógł: 0
|
 Częste Blue Screeny podczas użytkowania Windows 7
Witam otóż ciągle wywala mi bluescreena .Troche chodzenia po internecie i bluescreen(20minut) przy włączeniu np GTA IV chwila i blue screen pozniej przez jakis czas(po bluescreenie podczas gry pff tzn przewaznie próbie jej uruchomienia) nawet od razu po załadowaniu systemu
log z WDB
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\012012-19952-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 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c1a000 PsLoadedModuleList = 0xfffff800`02e5f670
Debug session time: Fri Jan 20 19:49:30.671 2012 (UTC + 1:00)
System Uptime: 0 days 0:00:30.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 \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
....
Unable to load image \SystemRoot\System32\Drivers\Ntfs.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904fb, fffff88008f2c998, fffff88008f2c1f0, fffff880012b8366}
***** 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 ***
*** ***
*************************************************************************
Probably caused by : Ntfs.sys ( Ntfs+aa366 )
Followup: MachineOwn
Notatka została dodana nie znane . Ostatnia edycja dokonana 21.01.2012 02:26 przez peciaq:
Używaj treściwych, precyzyjnych tematów w nagłówkach, zapoznaj się z: Jak poprawnie tytułować wątki? i popraw tytuł.
(Ten post był ostatnio modyfikowany: 21.01.2012 12:02 przez fakeman.)
20.01.2012 21:49
|
 Podziękowania od: |
|
|
|
thermalfake
Starszy specjalista
Liczba postów: 4.541
Dołączył: Nov 2010
Reputacja: 61
Podziękował: 4
Pomógł: 800
|
RE: Win 7 64x bluescreen
Masz zrypany ten zrzut bo WinDbg nie wie gdzie jest biblioteka symboli.
Szybciej będzie jak podrzucisz tego minidumpa lub wkleisz zawartość po analizie -> http://www.osronline.com/page.cfm?name=analyze
![[Obrazek: tmpff.png]](http://img714.imageshack.us/img714/70/tmpff.png)
|
| Podziękowania od: |
|
|
|
fakeman
Nowy
Liczba postów: 2
Dołączył: Jan 2012
Reputacja: 0
Podziękował: 0
Pomógł: 0
|
RE: Win 7 64x bluescreen
Witam otoz dzisiaj czytalem inny plik bylo juz zupelnie co innego hmmm daje z dzisiejszaego dnia ostatni (z godziny 11:52 zaraz pewnie bedize następny  ] po analizie z tej stronki
Kod:
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c5b000 PsLoadedModuleList = 0xfffff800`02ea0670
Debug session time: Sat Jan 21 05:51:24.446 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:32.835
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002cda890
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002cd71e9 to fffff80002cd7c40
STACK_TEXT:
fffff880`02f6aca8 fffff800`02cd71e9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02f6acb0 fffff800`02cd56b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f6adf0 fffff800`02cda890 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00fff880`03c147c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXSave+0x8f
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`02cd56b2 90 nop
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiDoubleFaultAbort+b2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Followup: MachineOwner
---------
,a tutaj z WDB
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\012112-19344-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 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c55000 PsLoadedModuleList = 0xfffff800`02e9a670
Debug session time: Sat Jan 21 00:18:24.546 2012 (UTC + 1:00)
System Uptime: 0 days 0:00:39.686
*********************************************************************
* 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 E3, {fffffa8008763308, fffffa800c059b60, 0, 2}
***** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+7cc40 )
Followup: MachineOwner
---------
(Ten post był ostatnio modyfikowany: 21.01.2012 12:03 przez fakeman.)
21.01.2012 12:01
|
| Podziękowania od: |
|
|
|
thermalfake
Starszy specjalista
Liczba postów: 4.541
Dołączył: Nov 2010
Reputacja: 61
Podziękował: 4
Pomógł: 800
|
RE: Win 7 64x ciągły Bluescreen po chwili użytkowania ...
Na początek memtest86, jakieś testy obciążeniowe typu Orthos, diagnostyka dysku hdd np HD Tune, diagnostyka grafiki Furmark'iem. Zrobić porządek ze sterownikami (aktualizacje). Powyłączać testowo programy zabezpieczające (internet odłącz) i pograj w coś pooglądaj filmy itp - ogólnie zajmij go czymś.
Cytat:UNEXPECTED_KERNEL_MODE_TRAP - Błędy sprzętowe lub programowe jądra systemu (awaria sprzętu, problemy z oprogramowaniem lub problemy z uzyskaniem przerwania) Najczęstszą przyczyną tego błędu jest awaria sprzętu. Jest wielce prawdopodobne, że ujrzysz ten komunikat o błędzie Stop, jeżeli masz wadliwe kości pamięci, niedopasowane moduły pamięci, wadliwie działający procesor albo awarię wentylatora lub zasilania, która powoduje przegrzanie. Pojawienie się tego błędu jest szczególnie prawdopodobne w wypadku systemów, w których procesor został przestawiony na pracę z szybkością przekraczającą szybkość nominalną - czyli po overclockingu.
Rozwiązanie:
-Przywróć ustawienia Biosu.
-Wykonaj gruntowne testy całego sprzętu.
-Uaktualnij wszystkie sterowniki.
-Przywróć rejestr.
(Ten post był ostatnio modyfikowany: 21.01.2012 21:17 przez thermalfake.)
21.01.2012 21:16
|
| Podziękowania od: |
|
|
|
