******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************BAD_POOL_HEADER (19)The pool is already corrupt at the time of the current request.This may or may not be due to the caller.The internal pool links must be walked to figure out a possible cause ofthe problem, and then special pool applied to the suspect tags or the driververifier to a suspect driver.Arguments:Arg1: 0000000000000020, a pool block header size is corrupt.Arg2: fffffa801232e130, The pool entry we were looking for within the page.Arg3: fffffa801232e150, The next pool entry.Arg4: 0000000004020009, (reserved)Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR: 0x19_20POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec30e0GetUlongFromAddress: unable to read from fffff80002ec3198 fffffa801232e130 Nonpaged poolDEFAULT_BUCKET_ID: WIN7_DRIVER_FAULTPROCESS_NAME: mbamservice.exCURRENT_IRQL: 0LAST_CONTROL_TRANSFER: from fffff80002dbe6d3 to fffff80002c8b840STACK_TEXT: fffff880`0ce88358 fffff800`02dbe6d3 : 00000000`00000019 00000000`00000020 fffffa80`1232e130 fffffa80`1232e150 : nt!KeBugCheckExfffff880`0ce88360 fffff880`01b2842d : 00000000`00000008 fffff880`00000004 00000000`676e7049 fffffa80`11530094… : nt!ExFreePoolWithTag+0x18b4fffff880`0ce88410 fffff880`018da04a : 00000000`00000000 fffff880`018d60c3 00000000`00000000 fffffa80`12fae010 : tcpip!IppInspectBuildHeaders+0x65dfffff880`0ce886f0 fffff880`0c97512d : 00000000`00000000 00000000`00000014 00000000`00000000 fffffa80`112705f0 : fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+0x20afffff880`0ce88790 00000000`00000000 : 00000000`00000014 00000000`00000000 fffffa80`112705f0 fffffa80`11270604 : mwac+0x612dSTACK_COMMAND: kbFOLLOWUP_IP: fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20afffff880`018da04a 85c0 test eax,eaxSYMBOL_STACK_INDEX: 3SYMBOL_NAME: fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20aFOLLOWUP_NAME: MachineOwnerMODULE_NAME: fwpkclntIMAGE_NAME: fwpkclnt.sysDEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc164FAILURE_BUCKET_ID: X64_0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20aBUCKET_ID: X64_0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20aFollowup: MachineOwner---------******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************VIDEO_TDR_FAILURE (116)Attempt to reset the display driver and recover from timeout failed.Arguments:Arg1: fffffa80103534e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).Arg2: fffff880075c0e30, The pointer into responsible device driver module (e.g. owner tag).Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.Arg4: 0000000000000002, Optional internal context dependent data.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlapFAULTING_IP: nvlddmkm+13be30fffff880`075c0e30 4055 push rbpDEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULTBUGCHECK_STR: 0x116PROCESS_NAME: SystemCURRENT_IRQL: 0STACK_TEXT: fffff880`0d53d988 fffff880`06f3ccbc : 00000000`00000116 fffffa80`103534e0 fffff880`075c0e30 00000000`00000000 : nt!KeBugCheckExfffff880`0d53d990 fffff880`06f3c9c6 : fffff880`075c0e30 fffffa80`103534e0 fffffa80`11ec26c0 fffffa80`0fd46010 : dxgkrnl!TdrBugcheckOnTimeout+0xecfffff880`0d53d9d0 fffff880`07f87f07 : fffffa80`103534e0 00000000`00000000 fffffa80`11ec26c0 fffffa80`0fd46010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2fffff880`0d53da00 fffff880`07fb1b75 : 00000000`ffffffff 00000000`000118ed 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40bfffff880`0d53dae0 fffff880`07fb02bb : 00000000`00000102 00000000`00000000 00000000`000118ed 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71fffff880`0d53db10 fffff880`07f832c6 : ffffffff`ff676980 fffffa80`0fd46010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fbfffff880`0d53dbb0 fffff880`07fafe7a : 00000000`00000000 fffffa80`11ec26c0 00000000`00000080 fffffa80`0fd46010 : dxgmms1!VidSchiScheduleCommandToRun+0x1dafffff880`0d53dcc0 fffff800`02f1812a : 00000000`00000000 fffffa80`0d2a7040 fffffa80`0c74b450 fffff800`02c716c7 : dxgmms1!VidSchiWorkerThread+0xbafffff880`0d53dd00 fffff800`02c57d86 : fffff880`009b2180 fffffa80`0d2a7040 fffff880`009bd0c0 fffff880`01454534 : nt!PspSystemThreadStartup+0x5afffff880`0d53dd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16STACK_COMMAND: .bugcheck ; kbFOLLOWUP_IP: nvlddmkm+13be30fffff880`075c0e30 4055 push rbpSYMBOL_NAME: nvlddmkm+13be30FOLLOWUP_NAME: MachineOwnerMODULE_NAME: nvlddmkmIMAGE_NAME: nvlddmkm.sysDEBUG_FLR_IMAGE_TIMESTAMP: 51c41788FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sysBUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sysFollowup: MachineOwner---------Odinstaluj mbam.Ovladač GK nebo GK samotná - prověřit!! Ukázat celý příspěvek