BSOD Memory Management, Bad Pool Header, Page Fault

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 7 Home Premium 64 bit
       #1

    BSOD Memory Management, Bad Pool Header, Page Fault


    I built a computer last week and everything seemed to be going fine until earlier this week, when I had a BSOD while surfing the internet and running Folding@Home on my CPU and GPU.

    I didn't think much of it until I got another BSOD the next day, maybe while playing DiRT 3. The first two BSOD's gave me the Memory Management error, so I downloaded Memtest86+ and ran 7 passes with no errors.

    I then got another BSOD while trying to play the Kerbal Space Program Demo and running F@H on both the CPU and GPU. This gave me the "Bad Pool Header" error. I tried several things after this BSOD, including flashing the motherboard BIOS to a newer version and uninstalling and reinstalling my video card drivers. I also ran a GPU memory stress test and a 15 minute Furmark stress test on the GPU, thinking it might be my problem. No issues.

    I booted up the computer today thinking that my problems might be solved, and left the computer running all day with F@H on full on the CPU and GPU. I started the KSP Demo again and got the Page Fault BSOD within about 30 seconds of opening the game.

    I'm at a loss as to what to do next. Thanks for taking the time to read through my issues and a big thanks for any help you can give.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi waharvey.

    Before doing anything else, uninstall AVG following http://www.avg.com/us-en/utilities. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

    Download, install and update those, and then run full system scans with both of them, one by one; as the installed antivirus is failing.

    Let us know the results. Will decide about the further steps after seeing it.
    Code:
    BugCheck 19, {3, fffffa8006662d80, 0, 0}
    
    *** WARNING: Unable to verify timestamp for avgmfx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgmfx64.sys
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
    
    Followup: Pool_corruption
    ---------
      My Computer


  3. Posts : 6
    Windows 7 Home Premium 64 bit
    Thread Starter
       #3

    Thanks for the help Arc.

    I haven't had any more blue screens since my post. Since every BSOD seemed to occur with F@H + a game running, I uninstalled the F@H client and have been able to play DiRT 3 without any issues a couple of different times. I have also followed your advice (I actually installed MBAM earlier in the week) and neither scan turned up anything significant.

    I will definitely update the post, especially if I get another BSOD.
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    Good news.

    Let us know about the situation accordingly.
      My Computer


  5. Posts : 6
    Windows 7 Home Premium 64 bit
    Thread Starter
       #5

    Another BSOD just now.

    I was running DiRT and it froze up on me; I then reopened DiRT and played for about 10 minutes before deciding it was time to quit. I tried to close DiRT and it froze again but eventually shut down. I locked my computer, walked away for a minute and came back to it restarting and getting the "Windows did not shut down correctly" screen.

    Blue screen viewer shows that I got a stop message with dxgkrnl.sys as the culprit. I'm uploading the forum diagnostic tool zip file so you have all the pertinent information.
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    It is a different issue.

    Uninstall your installed latest version of the display driver.


    Then clean up any possible leftover.


    Then install version 13.9 WHQL only.


    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

    Let us know the results.
    ______________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800b399010, fffff88003a94dc0, 0, 2}
    
    Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+bdc0 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800b399010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88003a94dc0, 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:
    ------------------
    
    
    FAULTING_IP: 
    atikmpag+bdc0
    fffff880`03a94dc0 4883ec28        sub     rsp,28h
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    fffff880`021b2718 fffff880`03d4f140 : 00000000`00000116 fffffa80`0b399010 fffff880`03a94dc0 00000000`00000000 : nt!KeBugCheckEx
    fffff880`021b2720 fffff880`03d4ee4a : fffff880`03a94dc0 fffffa80`0b399010 fffffa80`0d42b010 fffffa80`07f72410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`021b2760 fffff880`03c0ff13 : fffffa80`0b399010 00000000`00000000 fffffa80`0d42b010 fffffa80`07f72410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`021b2790 fffff880`03c3ded6 : fffffa80`ffffffff 00000000`002fee12 fffff880`021b28f0 fffffa80`07f72410 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`021b2870 fffff880`03c39a6c : 00000000`00000000 ffffffff`feced300 fffffa80`0c690b50 fffff880`03c3abee : dxgmms1!VidSchWaitForCompletionEvent+0x196
    fffff880`021b28b0 fffff880`03c38679 : fffffa80`07f72508 00000000`00000005 fffffa80`07f72410 fffff880`021b2bc0 : dxgmms1!VidSchiWaitForFence+0xf4
    fffff880`021b29a0 fffff880`03c38514 : fffff880`02fdbf40 fffff880`03c37f3c fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0xe1
    fffff880`021b2b90 fffff880`03c38012 : 00000000`00000000 fffffa80`12654a60 00000000`00000080 fffffa80`07f72410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`021b2bc0 fffff800`02f672ea : 00000000`fffffc32 fffffa80`07beea00 fffffa80`066d3040 fffffa80`07beea00 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`021b2c00 fffff800`02cbb8e6 : fffff880`02fd7180 fffffa80`07beea00 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`021b2c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+bdc0
    fffff880`03a94dc0 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  atikmpag+bdc0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  530aae0b
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys
    
    FAILURE_ID_HASH:  {83e844bc-fe68-2042-4230-7f5d3e90b48a}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm atikmpag
    start             end                 module name
    fffff880`03a89000 fffff880`03b2b000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Mon Feb 24 07:57:23 2014 (530AAE0B)
        CheckSum:         0009E33E
        ImageSize:        000A2000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  7. Posts : 6
    Windows 7 Home Premium 64 bit
    Thread Starter
       #7

    Arc, I had trouble installing the 13.9 drivers--the installer wouldn't recognize my GPU, so I am currently running the 13.12 drivers. I stress tested the graphics card with FurMark, no issues.

    Here's a snapshot I took of the system after having it on about an hour and a half with some gaming, internet surfing, and document writing. The temps seem fine on my end, the only thing I don't know much about is the mobo temp. http://speccy.piriform.com/results/Q...XMYpBkYJFXE6gD
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    Temps are not bad.

    What was the display driver version before you applied 13.12? Can you roll it back?
      My Computer


  9. Posts : 6
    Windows 7 Home Premium 64 bit
    Thread Starter
       #9

    Arc, I'm not quite sure what you are asking about the display driver. I've gotten two AMD drivers to work on the system, 13.12 (current) and a 14.something beta driver, which caused the latest BSOD. Windows had some generic display driver before I installed 13.12 most recently. With the generic driver I was getting a 1.0 for my graphics with the Windows Experience Index.
      My Computer


  10. Posts : 6,458
    x64 (6.3.9600) Win8.1 Pro & soon dual boot x64 (6.1.7601) Win7_SP1 HomePrem
       #10

    waharvey said:
    Arc, I had trouble installing the 13.9 drivers--the installer wouldn't recognize my GPU, so I am currently running the 13.12 drivers. I stress tested the graphics card with FurMark, no issues.
    If the 13.9 was unpacked you could try updating the driver in Device Manager (DevMgr).

    On the Driver tab
    Roll back to the base VGA driver

    Click the Update Driver... button
    Click Browse my computer for driver softare
    Enter, or [Browse...], the location of the unpacked 13.9 AMD package
    Select the 13.9 install information.

    OK out of DevMgr and restart your system.
    .
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 21:30.
Find Us