BSOD: Blue Screen chyba

[Maranov]

Protože kdyby se chyba nerozšířila z programu, tak ti jen spadne PunkBuster. Dělá to ten program v té verzi, kdy se to stalo, takže použití novější nebo starší verze možná pomůže.

Můžeš poslat ještě nějaké dumpy, jestli se z nich dozvíme víc.

[SVKOverclock]

082211-21949-01.rar

Protože kdyby se chyba nerozšířila z programu, tak ti jen spadne PunkBuster. Dělá to ten program v té verzi, kdy se to stalo, takže použití novější nebo starší verze možná pomůže.

Můžeš poslat ještě nějaké dumpy, jestli se z nich dozvíme víc.

Všetky dumpy sú tu

[SVKOverclock]

24082011501.rar

082211-21949-01.rar

Protože kdyby se chyba nerozšířila z programu, tak ti jen spadne PunkBuster. Dělá to ten program v té verzi, kdy se to stalo, takže použití novější nebo starší verze možná pomůže.

Můžeš poslat ještě nějaké dumpy, jestli se z nich dozvíme víc.

Všetky dumpy sú tu

Toto je moja blue screen

[Maranov]

To info z BlueScreen je i v tom dumpu, zkontroloval jsem jich pár a všechny ukazují to samé - chyba hardware (ovladače), pocházející z PunkBuster.

IMHO se rýpe kde nemá a porušuje nějakou segmentační ochranu... bez něj se hrát nedá?

[SVKOverclock]

To info z BlueScreen je i v tom dumpu, zkontroloval jsem jich pár a všechny ukazují to samé - chyba hardware (ovladače), pocházející z PunkBuster.

IMHO se rýpe kde nemá a porušuje nějakou segmentační ochranu... bez něj se hrát nedá?

Nedá je to taká na ...... anti cheat ochrana. Skúsim ešte napísať do EA support čo povedia.

[SVKOverclock]

to Maranov problém som vyriešil tým že som od inštaloval Easytune 6 a MSI Afterburner ktoré sa bili s punkbusterom. Ďakuje za pomoc pri riešení problému

[secretdagger]

Mám podobný problém s Blue Screen chybou u win7, můžete poradit, kde hledat problém?



Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\083111-22718-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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x8280e000 PsLoadedModuleList = 0x82958850
Debug session time: Wed Aug 31 14:00:53.275 2011 (UTC + 2:00)
System Uptime: 0 days 0:16:56.337
*********************************************************************
* 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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 92d24922, 8c413afc, 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!_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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : win32k.sys ( win32k+44922 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 92d24922, The address that the exception occurred at
Arg3: 8c413afc, Trap Frame
Arg4: 00000000

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

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

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: win32k

FAULTING_MODULE: 8280e000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7900f

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam

FAULTING_IP:
win32k+44922
92d24922 8b4004 mov eax,dword ptr [eax+4]

TRAP_FRAME: 8c413afc -- (.trap 0xffffffff8c413afc)
ErrCode = 00000000
eax=00000000 ebx=fe900000 ecx=00000000 edx=00000000 esi=00400000 edi=00000001
eip=92d24922 esp=8c413b70 ebp=8c413bfc iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k+0x44922:
92d24922 8b4004 mov eax,dword ptr [eax+4] ds00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 92daa87a to 92d24922

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8c413bfc 92daa87a 00000001 00000000 bf0509fd win32k+0x44922
8c413c10 92daee94 00000001 00000001 fe900000 win32k+0xca87a
8c413c24 92dae9c8 000008e4 00000001 000008e4 win32k+0xcee94
8c413c44 92dab19a fe577570 00000000 00000000 win32k+0xce9c8
8c413c64 92daaee1 fe577570 00000000 861586e0 win32k+0xcb19a
8c413c80 82a784fa 84d05690 00000000 b3f4d000 win32k+0xcaee1
8c413cfc 82a6abb9 00000000 ffffffff 0036f9f0 nt+0x26a4fa
8c413d24 8284c1ea ffffffff 00000000 0036f9fc nt+0x25cbb9
8c413d34 77c170b4 badb0d00 0036f9e8 00000000 nt+0x3e1ea
8c413d38 badb0d00 0036f9e8 00000000 00000000 0x77c170b4
8c413d3c 0036f9e8 00000000 00000000 00000000 0xbadb0d00
8c413d40 00000000 00000000 00000000 00000000 0x36f9e8


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k+44922
92d24922 8b4004 mov eax,dword ptr [eax+4]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k+44922

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: win32k.sys

BUCKET_ID: WRONG_SYMBOLS

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

kd> .trap 0xffffffff8c413afc
ErrCode = 00000000
eax=00000000 ebx=fe900000 ecx=00000000 edx=00000000 esi=00400000 edi=00000001
eip=92d24922 esp=8c413b70 ebp=8c413bfc iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k+0x44922:
92d24922 8b4004 mov eax,dword ptr [eax+4] ds00000004=????????
kd> lmvm win32k
start end module name
92ce0000 92f2c000 win32k T (no symbols)
Loaded symbol image file: win32k.sys
Image path: \SystemRoot\System32\win32k.sys
Image name: win32k.sys
Timestamp: Sat Nov 20 10:08:31 2010 (4CE7900F)
CheckSum: 002486D5
ImageSize: 0024C000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
kd> lmvm nt
start end module name
8280e000 82c20000 nt T (no symbols)
Loaded symbol image file: ntkrnlpa.exe
Image path: \SystemRoot\system32\ntkrnlpa.exe
Image name: ntkrnlpa.exe
Timestamp: Sat Nov 20 09:42:49 2010 (4CE78A09)
CheckSum: 003C88AC
ImageSize: 00412000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

[snaga]

Ahoj,

za posledni 3 dny jsem dostal 7x modrou smrt. Snazil jsem si otevrit minidump podle napovedy, nicmene se mi to nezadarilo. Proto prosim nekoho, kdo vi jak na to, at se mi na dump podiva a napise kde je mozna pricina padu.

Jen pro upresneni - 29.9 jsem nainstaloval betu battlefielda 3 s PnkBstrB a s novymi ovladaci grafarny (nvidia - beta verze). Myslel jsem si ze by to mohlo byt temi ovladaci, ale neni, po nainstalovani starsich ovladacu jsem zazil vcera dalsi dva pady. Pameti by to taky nemelo byt, pac jsem je projel memtestem (3 hodky). Jeden pad jsem zazil kdyz jsem paril empire total war a behem hrani jsem zapojil mobil do pc pres usb, ze by nestihal zdroj?

Dump je na http://totalwar.cz/dump/ (dal jsem tam vsech 7)

[quasimodo]

Ahojte, posledni 2 dny mi na novym notasu haze Bluescreen. Hledal jsem kod,ale nenasek te chybe nic podrobnejsiho, bud spatne hledam, nebo jsem lemra. Muzete se mi na to, prosim, podivat? Notas je cca mesic stary, vse jelo ok, pak prisla manzelka, ze se ji restartuje. dump je zde:

Kód: Vybrat vše

http://www.uloz.to/10532337/100611-22183-01-dmp

diky moc, jirka

[Maranov]

Spadl nějaký ovladač, původ v procesu fv.exe, což se mi nedaří identifikovat, co to je. Podívej se do běžících procesů, jestli o něm nenajdeš něco víc. Kdyžtak použij Process Explorer.

Hlavně informaci, kde je umístěný, to řekne asi nejlíp, k čemu patří.

[Golubowski]

Prosím poraďte co s tím?


Podpis problému:
Název události problému: BlueScreen
Verze operačního systému: 6.1.7600.2.0.0.256.1
ID národního prostředí: 1029

Další informace o problému:
BCCode: 24
BCP1: 00000000001904FB
BCP2: FFFFF8800317E6B8
BCP3: FFFFF8800317DF10
BCP4: FFFFF8800129FD10
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Soubory, které popisují problém:
C:\Windows\Minidump\102311-19609-01.dmp
C:\Users\Golubowski\AppData\Local\Temp\WER-48375-0.sysdata.xml

Přečtěte si prohlášení o zásadách ochrany osobních údajů online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0405

Pokud není k dispozici Prohlášení o zásadách ochrany osobních údajů online, přečtěte si toto prohlášení offline:
C:\Windows\system32\cs-CZ\erofflps.txt

Předem děkuji

[Maranov]

Kód: Vybrat vše

C:\Windows\Minidump\102311-19609-01.dmp

Šup ho sem.

[Golubowski]

Už asi vim odkud vítr vane.
Dal jsem ve win7 kontrolu paměti a diagnostikuje mi to chybu,takže zejtra vyndavám ramky a jdu reklamovat.

ten minidump sem nešoupnu,když to chci někam uploudnout tak mi to hlásí že nemám oprávnění.
nevíš jak na to? nejde mi ani zapakovat do raru (přístup odepřen)
a v čem ho otevřu ten DMP??

[Maranov]

Tak se kdyžtak ozvi, když to nepomůže.

Co ten soubor nejdřív někam zkopírovat a pak zazipovat?

[Golubowski]

Zkopírovat šel ale i tak nešel zipnout.

[newerko]

prosim vas poradte mi, dostavam bluescreen s tymto minidumpom, please co mam napravit
http://www.ulozto.sk/10843869/110111-16941-01-dmp

[Maranov]

Máš nějaký další? Vypadá to hardware, ukazuje to na CPU, ale může to být něco jiného.

Kód: Vybrat vše

X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

Zkontroloval bych paměti a CPU (memtest, Orthos). Máš nějaký overclock nebo vysoké teploty?

[newerko]

menil som cpu, ale robilo mi to aj pri starom. Skor mam pocit ze mi to robi odkedy som pamate vymenil. Pomohlo keby som ti vypisal zostavu, ci nie je problem v kompatibilite?
Inte Core2Duo E8400
asus P5P41TLE
corsair XMS 3 1333/4GB
ITec 530 Watt
Nvidia GeForce N430 GT

[newerko]

mam tieto pamate http://www.alza.sk/corsair-4gb-kit-ddr3 ... 159097.htm, tam pisu casovanie 9-9-9-24 a men CPUID ukazuje 8-8-8-20, moze to byt aj v tom?

[newerko]

no tak skusil som vymenit pamate a spravilo to znova, zeby to bolo ze cpu sa prehrieva? moze to byt v tom?