Help needed with BSOD bad_pool_header

Berto_Lux

Reputable
Jan 13, 2016
1
0
4,510
Hi, i need help with that BSOD bad pool header :(

There is all i could take from the analysis:



Firma problema:
Nome evento problema: BlueScreen
Versione SO: 6.1.7601.2.1.0.256.1
ID impostazioni locali: 1040

Ulteriori informazioni sul problema:
BCCode: 19
BCP1: 0000000000000020
BCP2: FFFFFA800A96D250
BCP3: FFFFFA800A96D4D0
BCP4: 000000000C2812F0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\011316-5491-01.dmp
C:\Users\Roberto\AppData\Local\Temp\WER-9344-0.sysdata.xml

Leggere l'informativa sulla privacy online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0410

Se l'informativa sulla privacy online non è disponibile, leggere quella offline:
C:\Windows\system32\it-IT\erofflps.txt





Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.19110.amd64fre.win7sp1_gdr.151230-0600
Machine Name:
Kernel base = 0xfffff800`02e02000 PsLoadedModuleList = 0xfffff800`03049730
Debug session time: Wed Jan 13 13:33:52.836 2016 (UTC - 5:00)
System Uptime: 0 days 3:13:53.929
*******************************************************************************
* *
* 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 of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa800a96d250, The pool entry we were looking for within the page.
Arg3: fffffa800a96d4d0, The next pool entry.
Arg4: 000000000c2812f0, (reserved)

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

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

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b3100
GetUlongFromAddress: unable to read from fffff800030b31c0
fffffa800a96d250 Nonpaged pool

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: Photoshop.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002faccbe to fffff80002e75c00

STACK_TEXT:
fffff880`0a0b2018 fffff800`02faccbe : 00000000`00000019 00000000`00000020 fffffa80`0a96d250 fffffa80`0a96d4d0 : nt!KeBugCheckEx
fffff880`0a0b2020 fffff800`02ec1fce : 00000000`00008706 00000000`00000002 fffffa80`7ffffa80 00008704`00961c16 : nt!ExFreePool+0xd8a
fffff880`0a0b20d0 fffff800`02efe64e : fffffa80`0a96d260 fffffa80`0ac81d50 fffff880`0a0b22b0 00000000`34bf0000 : nt!MiPhysicalViewRemover+0x11e
fffff880`0a0b2130 fffff800`02e74e93 : ffffffff`ffffffff fffff8a0`03cb8d98 fffff8a0`03cb8dc0 00000000`00008000 : nt! ?? ::FNODOBFM::`string'+0x5288d
fffff880`0a0b2230 fffff800`02e71450 : fffff880`0f43562e fffff8a0`03535980 fffffa80`0a8c3b10 fffffa80`09227750 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0a0b23c8 fffff880`0f43562e : fffff8a0`03535980 fffffa80`0a8c3b10 fffffa80`09227750 fffff8a0`03cb8d90 : nt!KiServiceLinkage
fffff880`0a0b23d0 fffff880`0f420c93 : 00000000`00000000 fffff8a0`09a23a70 00000000`00000001 fffff800`00000174 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2
fffff880`0a0b2400 fffff880`0f41b637 : fffffa80`0ac80300 00000000`00000001 fffff8a0`03535980 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x11b
fffff880`0a0b24b0 fffff880`0f401ecc : fffffa80`00000000 fffff880`00000000 fffffa80`08957738 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0a0b2580 fffff880`10119ccc : fffff8a0`03cb8e00 fffff8a0`036e7000 fffff8a0`036e7000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0a0b25b0 fffff880`1011a3ac : fffff8a0`04043eb0 fffff8a0`04043eb0 00000000`00000001 fffff8a0`036e7000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0a0b26a0 fffff880`10119651 : fffff8a0`036e7000 fffff8a0`036e7000 fffff8a0`09db6f10 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyResource+0x84
fffff880`0a0b26d0 fffff880`101198e1 : fffff8a0`036e7000 fffff8a0`036e7000 00000000`00000001 fffff8a0`03195160 : dxgkrnl!DXGDEVICE::processTerminationList+0x95
fffff880`0a0b2720 fffff880`1011d739 : 00000000`00000000 fffff880`0a0b2b60 fffff8a0`02d8a690 fffff880`100e43af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`0a0b2770 fffff880`10120285 : fffff8a0`036e7000 fffff880`0a0b2850 00000000`4b677800 00000000`000007ff : dxgkrnl!DXGDEVICE::DestroyAllocation+0x99
fffff880`0a0b2800 fffff960`0019c002 : 00000000`13996b90 fffffa80`0a8bfb50 00000000`00000020 00000000`0f9f4680 : dxgkrnl!DxgkDestroyAllocation+0xa9d
fffff880`0a0b2ab0 fffff800`02e74e93 : 00000000`15ff7900 fffff880`0a0b2b60 00000000`000000b9 00000000`00406ad0 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`0a0b2ae0 000007fe`fedf4a5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001df058 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fedf4a5a


STACK_COMMAND: kb

FOLLOWUP_IP:
dxgmms1!VIDMM_PROCESS_HEAP::Free+a2
fffff880`0f43562e 488b0e mov rcx,qword ptr [rsi]

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5164dc13

FAILURE_BUCKET_ID: X64_0x19_20_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

BUCKET_ID: X64_0x19_20_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

Followup: MachineOwner



Please, any help would be great :(