ntoskrnl.exe - BSOD

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff900c266f084, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600024779c, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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

Could not read faulting driver name
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032bd0e0
GetUlongFromAddress: unable to read from fffff800032bd198
fffff900c266f084

FAULTING_IP:
win32k!GreSetRedirectionSurfaceSignaling+104
fffff960`0024779c f6465c01 test byte ptr [rsi+5Ch],1

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff880065f5980 -- (.trap 0xfffff880065f5980)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8005e74060 rbx=0000000000000000 rcx=fffff880065f5ae0
rdx=fffff900c021a898 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600024779c rsp=fffff880065f5b10 rbp=ffffffffa91211b1
r8=0000000000000001 r9=00000000000011b1 r10=000000000386f7a0
r11=fffff880065f5b08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
win32k!GreSetRedirectionSurfaceSignaling+0x104:
fffff960`0024779c f6465c01 test byte ptr [rsi+5Ch],1 ds:00000000`0000005c=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800031061e4 to fffff80003086f00

STACK_TEXT:
fffff880`065f5818 fffff800`031061e4 : 00000000`00000050 fffff900`c266f084 00000000`00000000 fffff880`065f5980 : nt!KeBugCheckEx
fffff880`065f5820 fffff800`03084fee : 00000000`00000000 fffff900`c06e3a60 fffffa80`05e74100 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42907
fffff880`065f5980 fffff960`0024779c : 00000000`00000000 ffffffff`a91211b1 00000000`0386f840 fffff8a0`01c69000 : nt!KiPageFault+0x16e
fffff880`065f5b10 fffff960`0026a969 : 00000000`00000001 fffff880`065f5c60 00000000`0386f840 00000000`000089f2 : win32k!GreSetRedirectionSurfaceSignaling+0x104
fffff880`065f5b60 fffff800`03086153 : fffffa80`05e74060 fffffa80`05e866e0 fffffa80`05eb91d0 fffffa80`05e866e0 : win32k!NtGdiHLSurfSetInformation+0x209
fffff880`065f5be0 000007fe`ff324efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0386f778 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff324efa

STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!GreSetRedirectionSurfaceSignaling+104
fffff960`0024779c f6465c01 test byte ptr [rsi+5Ch],1

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: win32k!GreSetRedirectionSurfaceSignaling+104

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e0

FAILURE_BUCKET_ID: X64_0x50_win32k!GreSetRedirectionSurfaceSignaling+ 104

BUCKET_ID: X64_0x50_win32k!GreSetRedirectionSurfaceSignaling+ 104

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (www.osr.com)
Online Crash Dump Analysis Service
See www.osronline.com for more information
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03015000 PsLoadedModuleList = 0xfffff800`03252e50
Debug session time: Sat Jan 17 18:13:45.209 2015 (UTC - 5:00)
System Uptime: 0 days 0:31:56.879

Arg3: fffff9600024779c, If non-zero, the instruction address which referenced the bad memory
address.

takže standardka- testuj ram.

Zkoušel jsem utilitku ve winu "Diagnostika paměti Windows" a neukázalo to žádné problémy. Mám spíše zkusit MemTest?

To vůbec nemusí vypovídat o chybě paměti.

nemusí. může.

nepoznám z toho, jestli máš servicepack 1.
z reportu taky hádám chybu paměti - zkus ještě jiný analyzátor (nirsoft bsod viewer) a nějaký jiný memtest.

Říkáš poslední dobou… jak dlouho se ti to děje? Nedělal jsi předtím nějaké změny v HW nebo SW konfiguraci počítače, kupříkladu nová grafická karta, nebo update jejích ovladačů?

Od té doby, co jsem začal hrát wowko :D od pátku. Nejdříve to dělali soubory cdd.dll a ntoskrnl.exe pak ntoskrnl.exe a win32k.sys a teď jen ntoskrnl.exe..
Musím si sehnat flashku a dát si tam ten memtest, protože když to dělám z CD, tak se mi tam neuloží log z testu

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (www.osr.com)
Online Crash Dump Analysis Service
See www.osronline.com for more information
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`0300f000 PsLoadedModuleList = 0xfffff800`0324ce50
Debug session time: Sun Jan 18 09:08:35.994 2015 (UTC - 5:00)
System Uptime: 0 days 1:28:10.579
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff96000166923, Address of the instruction which caused the bugcheck
Arg3: fffff880065c7030, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
win32k!HmgLockEx+a3
fffff960`00166923 0fb7430c movzx eax,word ptr [rbx+0Ch]

CONTEXT: fffff880065c7030 -- (.cxr 0xfffff880065c7030)
rax=fffff900c0210000 rbx=0000000000000000 rcx=fffffa8005740380
rdx=fffff900c0210000 rsi=0000000000010000 rdi=fffff900c0210000
rip=fffff96000166923 rsp=fffff880065c7a00 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000000 r10=0000000000000000
r11=fffff880065c7a68 r12=00000000036cc200 r13=0000000000000000
r14=0000000000000001 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
win32k!HmgLockEx+0xa3:
fffff960`00166923 0fb7430c movzx eax,word ptr [rbx+0Ch] ds:002b:00000000`0000000c=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff9600032c1e0 to fffff96000166923

STACK_TEXT:
fffff880`065c7a00 fffff960`0032c1e0 : fffff900`c2300420 00000000`00000001 ffffffff`c5120c68 fffff900`c2168cd0 : win32k!HmgLockEx+0xa3
fffff880`065c7a70 fffff960`0032b6de : fffff900`c2300420 00000000`00000000 00000c68`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40
fffff880`065c7aa0 fffff960`0032c5e3 : 00000000`00000000 ffffffff`c5120c68 fffff900`c2300420 00000000`036cc2e0 : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e
fffff880`065c7ae0 fffff960`00287c9f : 00000000`00000000 fffff900`c00c0010 fffff900`c2300420 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`065c7b20 fffff960`002a9278 : 00000800`00000001 00000000`00000001 fffff880`065c7c60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`065c7b60 fffff800`0307e953 : fffffa80`05740380 00000000`020cf7a0 000007fe`f950d610 00000000`00000000 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`065c7be0 000007fe`fdab4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`020cf1f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fdab4efa

FOLLOWUP_IP:
win32k!HmgLockEx+a3
fffff960`00166923 0fb7430c movzx eax,word ptr [rbx+0Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!HmgLockEx+a3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 54163648

STACK_COMMAND: .cxr 0xfffff880065c7030 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3

BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3

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

DAlší!

Co jsi dělal, než se to zhroutilo?

Zkus si aktualizovat ovladače, speciálně na grafickou kartu.

A nebo sem přilož ten dump.

Vždy se stane to samé. Hraju WoW, přijde mi zpráva na FB, tak ATL+Tab hru shodím a najednou se to sekne, nejdřív milion proužků barvy a pak BSOD.

Takže aktualizuj ovladače (grafika, chipset) a pak dej vědět.

Grafiku mam aktualizovanou, mám stáhnuto AMD Catalyst driver (14.12 Catalyst Omega software) a Chipset mám ze stránek Gigabyte.

pokud je to AMD čipset, tak potřebuješ čipset driver odpovídající Omega driveru (tedy 14.12), jinak to blbne přesně takto.

http://www2.ati.com/drivers/amd-catalyst-omega-14. 12-sb-sata-ahci-win8.1-win7.exe

log z memtestu nepotřebuješ - leda k případné reklamaci. jinak stačí, když rozeznáš červenou a zelenou barvu.

jiný debugger jsi taky nezkusil, mohlo být víc informací.

cdd.dll: nepoužíváš taky automatický update ovladačů?

Automatický update nepoužívám, vždy to jen vyskočí, že je nový driver, tak ho stáhnu, ale jinak nic.
Nainstaloval jsem ovladač pro grafiku, chipset, zvukovku

správné pořadí instalace ovladačů: chipset, pak grafika a zbytek.

jiný memtest a jiný bsod debugger by mohly pomoct, ale když nejdou spustit ...

Aspoň ten dump mohl hodit, když už nic jiného…

vždyť jsem sem ten výpis hodil

Myslel jsem ten *.dmp soubor…

minidump-rar
Tady máš všechny dumpy i ten, který se mi stal před minutou a to jsem smazal ovladače a nainstaloval sjem znovu - Chipset, Grafika, Realtek

MemTest vyšel dobrý, žádný Error ani příznak