Skocz do zawartości

r   e   k   l   a   m   a

Zdjęcie

Blue screen podczas gry na nk


  • Zaloguj się, aby dodać odpowiedź
6 odpowiedzi w tym temacie

#1 karkosik87

karkosik87
  • Użytkownicy
  • 44 postów

Napisano 28.12.2012 - 00:09

witam
wczoraj po dluzszej grze na nk w gre (Miskrity) zrobil sie blue screen i przed chwila znowu (0:03)

to wyskoczylo po ponownym uruchomieniu :

Podpis problemu:
Nazwa zdarzenia problemu: BlueScreen
Wersja systemu operacyjnego: 6.1.7601.2.1.0.256.48
Identyfikator ustawień regionalnych: 1045

Dodatkowe informacje o problemie:
BCCode: d1
BCP1: 0000000000000008
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF880014425BB
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Pliki pomagające opisać problem:
C:\Windows\Minidump\122812-22401-01.dmp
C:\Users\Kamil\AppData\Local\Temp\WER-63835-0.sysdata.xml

Przeczytaj w trybie online nasze zasady zachowania poufności informacji:
http://go.microsoft.... ... cid=0x0415

Jeśli zasady zachowania poufności informacji w trybie online nie są dostępne, przeczytaj nasze zasady zachowania poufności informacji w trybie offline:
C:\Windows\system32\pl-PL\erofflps.txt

Co to znaczy? czy ram do wymiany?

#2 adam9870

adam9870
  • Użytkownicy
  • 14562 postów

Napisano 28.12.2012 - 00:22

Poproszę o zrzuty pamięci z C:\windows\minidump
Dwie metody do wyboru w celu odczytu
Pierwsza metoda: WinDbg (zapoznaj się z wiadomością napisaną przez przez Robinhio » 04 grudnia 2006 20:56:00)
Druga metoda: BlueScreenView (zapoznaj się z wiadomością napisaną przez przez deFco247 » 21 stycznia 2010 16:55:07)
Jeżeli w c:\windows\minidump będzie pusto to zobacz komputer-sie-wylacza-t498828.html#p3137602

#3 karkosik87

karkosik87
  • Użytkownicy
  • 44 postów

Napisano 28.12.2012 - 12:25

Microsoft ® Windows Debugger Version 6.2.9200.20512 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C]
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 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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02c07000 PsLoadedModuleList = 0xfffff800`02e4b670
Debug session time: Fri Dec 28 00:02:26.947 2012 (UTC + 1:00)
System Uptime: 0 days 0:22:55.679
*********************************************************************
* 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 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 D1, {8, 2, 0, fffff880014425bb}

*** 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.

*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
*************************************************************************
*** ***
*** ***
*** 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 : ndis.sys ( ndis+95bb )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880014425bb, address which referenced memory

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

MODULE_NAME: ndis

FAULTING_MODULE: fffff80002c07000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79392

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000008

CURRENT_IRQL: 0

FAULTING_IP:
ndis+95bb
fffff880`014425bb 498b5e08 mov rbx,qword ptr [r14+8]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from fffff80002c85769 to fffff80002c861c0

STACK_TEXT:
fffff800`00ba29d8 fffff800`02c85769 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt+0x7f1c0
fffff800`00ba29e0 00000000`0000000a : 00000000`00000008 00000000`00000002 00000000`00000000 fffff880`014425bb : nt+0x7e769
fffff800`00ba29e8 00000000`00000008 : 00000000`00000002 00000000`00000000 fffff880`014425bb fffffa80`01d15db0 : 0xa
fffff800`00ba29f0 00000000`00000002 : 00000000`00000000 fffff880`014425bb fffffa80`01d15db0 00000000`00000000 : 0x8
fffff800`00ba29f8 00000000`00000000 : fffff880`014425bb fffffa80`01d15db0 00000000`00000000 00000000`00000000 : 0x2


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
ndis+95bb
fffff880`014425bb 498b5e08 mov rbx,qword ptr [r14+8]

SYMBOL_NAME: ndis+95bb

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ndis.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

Nie wiem czy dobrze to zrobilem, nie dalo sie spolszczenia wrzucic, a wiec zrobilem analize i wklejam co wyszlo.


#4 adam9870

adam9870
  • Użytkownicy
  • 14562 postów

Napisano 28.12.2012 - 17:17

Zapoznaj się z moją wiadomością w tym temacie: bluescreen-windows-t489660.html

#5 karkosik87

karkosik87
  • Użytkownicy
  • 44 postów

Napisano 28.12.2012 - 18:52

zapoznalem sie, ale mam aktualne sterowniki sieciowki,
nadal nie wiem co moze byc powodem

#6 adam9870

adam9870
  • Użytkownicy
  • 14562 postów

Napisano 28.12.2012 - 22:14

No to sprawdź inną wersję sterowników, wyłącz programy zabezpieczające, wykonaj czysty rozruch http://support.micro...om/kb/929135/pl i sprawdź czy będą problemy, napisałem o tylu możliwościach.

#7 karkosik87

karkosik87
  • Użytkownicy
  • 44 postów

Napisano 28.12.2012 - 22:43

Ja tez napisalem na poczatku ze po dluzszej grze na nk w gre (Miskrity to nowa aplikacja) zrobil sie blue screen. dzis np popoludniu to sie zdazylo, ale tylko podczas gry w ta aplikacje, tak to nie sie nie dzieje. Slucham muzyki, ogladam filmy siedze na portalach ogloszeniowych i system dziala stabilnie, tylko jak pogram dluzej 10-... min w tamta aplikacje (gre) to blue... i restart.
Sprawdzilem ram memtestem ponad 270% i 0 erroru, grafike takze sprawdzilem jakims programem temp urosla do 79oC i nic nawet sie nie zachwiala. dysku nie bede sprawdzal bo ma 3-4 miesiecy (kupilem nowke w sklepie na gwarancji), wiec juz nie wiem co jest powodem.

-- Dodane 28.12.2012 (Pt) 22:51 --

Ja tez napisalem na poczatku ze po dluzszej grze na nk w gre (Miskrity to nowa aplikacja) zrobil sie blue screen. dzis np popoludniu to sie zdazylo, ale tylko podczas gry w ta aplikacje, tak to nie sie nie dzieje. Slucham muzyki, ogladam filmy siedze na portalach ogloszeniowych i system dziala stabilnie, tylko jak pogram dluzej 10-... min w tamta aplikacje (gre) to blue... i restart.
Sprawdzilem ram memtestem ponad 270% i 0 erroru, grafike takze sprawdzilem jakims programem temp urosla do 79oC i nic nawet sie nie zachwiala. dysku nie bede sprawdzal bo ma 3-4 miesiecy (kupilem nowke w sklepie na gwarancji), wiec juz nie wiem co jest powodem.


oto foto blue screen'a ktory nastapil za 1 razem http://www.fotosik.p...463f31135d.html

-- Dodane 29.12.2012 (So) 12:18 --

ale ze mnie debil.
myslalem ze winna jest kostk ram, wiec wystawilem ja na aukcje na handel. a wczoraj glebiej przeczytalem twoj post, i znalazlem wykrzyknik w Menedżerze urzadzen i probowalem zainstalowac brakujacy sterownik, i nic. blokada ze strony Outpost Firewall Pro po wylaczeniu zapory zainstalowal sie brakujacy sterownik i gralem w ta gre na nk prawie 1h i zero blue screena czy czegos innego!!
I jestem 2gb ramu w plecy bo wczoraj rano sie sprzedala a wieczorem rozwiazalem problem.

Dziekuje za pomoc

Życze szczesliwego nowego roku