BSOD BAD_POOL_HEADER and other errors

[thefatshizms]

Okay all uninstalled, DV off.. what now? Do you want me to wait for the next crash and send the dmp?

 

[Arc]

I want you to observe the situation and report us accordingly

 

[thefatshizms]

As soon as I did the above (uninstalled etc) I noticed that BSOD were less frequent.. doesn't mean that they don't still come back though. Around 20 minutes ago I bluescreened, I then logged back in and around 5 mins later bluescreened again. Below I have attached a zip of the crash info, I hope this can be fixed as it's so danm annoying!

 

[Arc]

OK, let us come to our next step

Update your ATI/AMD display driver. It is backdated.

fffff880`04200000 fffff880`04261000   atikmpag   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
[COLOR=Red]    Image name: atikmpag.sys
    Timestamp:        Sat Jul 28 06:44:47 2012[/COLOR] (50133D07)
    CheckSum:         00064351
    ImageSize:        00061000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You can get it from the link in our forum, http://www.sevenforums.com/graphic-...alyst-video-driver-windows-7-a.html#post17671, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.

During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

Also try to update the DirectX.

• Download DirectX End-User Runtime Web Installer from Official Microsoft Download Center
• How to download and install DirectX

Let us know the results.

_________________________________________________________________________
BSOD ANALYSIS:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80017371e0, ffff, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80017371e0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  TeamViewer_Des

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002d2fd40 to fffff80002cbec00

STACK_TEXT:  
fffff880`07b86ae8 fffff800`02d2fd40 : 00000000`0000001a 00000000`00041790 fffffa80`017371e0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`07b86af0 fffff800`02cab3ff : fffffa80`00000000 00000000`0e67ffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35084
fffff880`07b86cb0 fffff800`02cbde93 : ffffffff`ffffffff fffff8a0`02f06988 fffff8a0`02f069b0 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`07b86db0 fffff800`02cba450 : fffff880`0539662e fffff8a0`02a67850 fffffa80`071257e0 fffffa80`08868e30 : nt!KiSystemServiceCopyEnd+0x13
fffff880`07b86f48 fffff880`0539662e : fffff8a0`02a67850 fffffa80`071257e0 fffffa80`08868e30 fffff8a0`02f06980 : nt!KiServiceLinkage
fffff880`07b86f50 fffff880`05381bfc : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000001 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2
fffff880`07b86f80 fffff880`0537c2b4 : 00000000`00000000 fffff8a0`02a67850 fffff8a0`6d4d6956 fffffa80`00000174 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x84
fffff880`07b87030 fffff880`05362aa7 : fffff8a0`03619470 fffff8a0`03e65970 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::OpenOneAllocation+0x514
fffff880`07b87120 fffff880`052ae4bd : fffff8a0`02a1b548 fffff880`07b87630 00000000`00000000 fffff8a0`04753770 : dxgmms1!VidMmOpenAllocation+0xeb
fffff880`07b87170 fffff880`052a7a5a : fffff880`07b87418 fffff880`07b87890 fffff880`07b875f0 fffff880`07b875f0 : dxgkrnl!DXGDEVICE::CreateVidMmAllocations<_DXGK_ALLOCATIONINFO>+0x291
fffff880`07b87200 fffff880`052a9e58 : fffff8a0`003c0000 fffff880`07b87890 fffff880`07b87b00 00000000`00000701 : dxgkrnl!DXGDEVICE::CreateAllocation+0x10ae
fffff880`07b87840 fffff880`052ac7b5 : 00000000`00000124 00000000`00000001 fffff8a0`0b962ab0 00000000`00000124 : dxgkrnl!DXGDEVICE::OpenResource+0x5a0
fffff880`07b87920 fffff960`00211116 : 00000000`0088e110 00000000`7ef9b000 00000000`000007d4 00000000`000007d5 : dxgkrnl!DxgkOpenResource+0x72d
fffff880`07b87ab0 fffff800`02cbde93 : fffffa80`0721b9b0 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!NtGdiDdDDIOpenResource+0x12
fffff880`07b87ae0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  5

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_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

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

 

[thefatshizms]

Did both of them and I'm now getting frequent crashes. Crash info below.

 

[Arc]

It appears that you haven't updated the display driver.

fffff880`0484c000 fffff880`0526d000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
[COLOR=Red]    Image name: atikmdag.sys
    Timestamp:        Sat Jul 28 07:18:09 2012 [/COLOR](501344D9)
    CheckSum:         009DA146
    ImageSize:        00A21000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Follow this method:

• First uninstall all elements of display driver in Control Panel > Programs and Features, including CCC.
• Then follow follow Drivers - Clean Left over Files after Uninstalling
• Go to http://www.sevenforums.com/graphic-...alyst-video-driver-windows-7-a.html#post17671, download and install WHQL Version: 13.4, dated April 24th 2013

Let us know the results.

 

[thefatshizms]

Aparently, I don't have the whole catalist control center driver thing.. I've tried using that sweaper but the source is corrupt or something so it won't start.

 

[thefatshizms]

I can't uninstall.. All I have is AMD catalist install manager which needs repairing and AMD quick stream which I don't know if thats the driver

 

[koolkat77]

Can you post a screenshot of your control panel > add/remove programs?

 

[Dude]

Try using ATI's uninstall utility

:ar: Removal ATI

 

[thefatshizms]

Okay, I've uninstalled my drivers and reinstalled them with the newest ones... I still crash. Crash info below.

 

[Arc]

Try Driver Verifier once more? None of the crash dumps are showing anything as failing.

 

[thefatshizms]

Just put on driver verifier and this happened: http://imtransfer.im4mobile.com/vr/uploads/6136137018362319787/IMG-20130602-00142.jpg

 

[essenbe]

If you haven't already, try Option 2 of this http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html Also, what brand and size PSU do you have and what brand of GPU do you have? Also, do you have an extra hard drive that you could use?

This may help you to update your system specs, it is easy and will automatically do it for you. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

 

[thefatshizms]

My psu is a corsair, I'm not really sure what size but I'll try find a link to it in a second. GPU I'm not really sure ethier, all I know is it's built in "AMD A8-5600K APU with Radeon(tm) HD Graphics" so AMD I guess. No I don't have an extra hardrive :/

I'm now running the sfc /scannow I'll do it a couple of times, as the page said it can take serveral times for it to fix.

 

[essenbe]

If it gets errors, reboot and run it at least 3 times or until it says no integrity errors.

 

[thefatshizms]

At the moment, its failing the scan everytime. it's saying "Windows resource protection could not perform the requested operation". It failed at 15% then I scanned again then it failed at 50% its going up..

 

[essenbe]

Go down to option three and post the details text here. Let Arc take a look at them.

 

[thefatshizms]

Here you go:

 

[Arc]

A lot of files like Japanese language pack, Canon printer driver etc are corrupt beyond repair. Better than repairing them individually, start as fresh. Follow http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html to get a perfect working windows installation.