BSOD >>> EXCEPTION_CODE: (NTSTATUS) 0xc0000005 :(

[filipp]

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

FAULTING_IP: 
win32k!BLTRECORD::bBitBlt+4a6
9b19edab f7422000000200  test    dword ptr [edx+20h],20000h

TRAP_FRAME:  bcd869e0 -- (.trap 0xffffffffbcd869e0)
ErrCode = 00000000
eax=fd225008 ebx=bcd86c3c ecx=00004249 edx=6905002e esi=bcd86c30 edi=fd1ff7d8
eip=9b19edab esp=bcd86a54 ebp=bcd86b84 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
win32k!BLTRECORD::bBitBlt+0x4a6:
9b19edab f7422000000200  test    dword ptr [edx+20h],20000h ds:0023:6905004e=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  Acrobat.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 9b188600 to 9b19edab

STACK_TEXT:  
bcd86b84 9b188600 bcd86c30 bcd86c24 bcd86cbc win32k!BLTRECORD::bBitBlt+0x4a6
bcd86cf0 9b1887c2 90011557 00000000 00000000 win32k!GreStretchBltInternal+0x659
bcd86d2c 81e97a1a 90011557 00000000 00000000 win32k!GreStretchBlt+0x30
bcd86d2c 774a9a94 90011557 00000000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f9d4 00000000 00000000 00000000 00000000 0x774a9a94


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!BLTRECORD::bBitBlt+4a6
9b19edab f7422000000200  test    dword ptr [edx+20h],20000h

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!BLTRECORD::bBitBlt+4a6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a856c3f

FAILURE_BUCKET_ID:  0x8E_win32k!BLTRECORD::bBitBlt+4a6

BUCKET_ID:  0x8E_win32k!BLTRECORD::bBitBlt+4a6

Followup: MachineOwner

Ovo gore je dakle iz WinDbg.

Ima li ko neki tip, posto sam netu ne nadjoh nesto konkretno, osim da je mozda memorija u pitanju.
Svaki predlog dobrodosao :wave:

 

[filipp]

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 846ac510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 8bc0f190, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000d, Optional internal context dependent data.

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


FAULTING_IP: 
igdkmd32+6190
8bc0f190 55              push    ebp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
9b3e8bc0 8c332d76 00000116 846ac510 8bc0f190 nt!KeBugCheckEx+0x1e
9b3e8be4 8c333a68 8bc0f190 00000000 0000000d dxgkrnl!TdrBugcheckOnTimeout+0x8d
9b3e8c04 8c2d0ed1 00000000 00000102 9136c8b8 dxgkrnl!TdrIsRecoveryRequired+0xa1
9b3e8c6c 8c2e1f22 9136c8b8 0000b3cd 00000000 dxgkrnl!VidSchiReportHwHang+0x2f5
9b3e8c98 8c2e1c54 9136c8b8 00000000 00000000 dxgkrnl!VidSchiCheckHwProgress+0x97
9b3e8cc4 8c2bea4c 00000002 9136e568 879d0e18 dxgkrnl!VidSchiWaitForSchedulerEvents+0x13f
9b3e8d54 8c2e1f9b 9136c8b8 81e65645 9136c8b8 dxgkrnl!VidSchiScheduleCommandToRun+0xac
9b3e8d68 8c31f053 9136c8b8 00000000 913686a8 dxgkrnl!VidSchiRun_PriorityTable+0xf
9b3e8d7c 81fe9b22 9136c8b8 dca7800e 00000000 dxgkrnl!VidSchiWorkerThread+0x62
9b3e8dc0 81e42a2e 8c31eff1 9136c8b8 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
igdkmd32+6190
8bc0f190 55              push    ebp

SYMBOL_NAME:  igdkmd32+6190

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd32

IMAGE_NAME:  igdkmd32.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  457ef9d2

FAILURE_BUCKET_ID:  0x116_IMAGE_igdkmd32.sys

BUCKET_ID:  0x116_IMAGE_igdkmd32.sys

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

Drugi BSOD na istoj masini

 

[alfaunits]

Stivo: http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx
Malo konkretnije:
http://codinghut.com/2008/02/analyzing-windows-crash-dump-files/
(uradi search za VIDEO_TDR_FAILURE u ovom textu, tj. preskoci ostalo)
Moje misljenje: memorija 😉 retko kad to kazem za dumpove ali ovde verovatno jeste.