Frequent BSOD memory_management

Page 5 of 6 FirstFirst ... 3456 LastLast

  1. Posts : 28
    Windows 10
    Thread Starter

    Hi zbook

    Maybe 'hang' is the wrong word...the system just wasn't getting past the Windows logo at all with verifier enabled. I had to reset twice to get the startup/recovery options and then disable verifier.

    Anyway, by enabling drivers one by one in Verifier I eliminated the driver that was causing the above issue (pxhlpa64.sys) and with that removed now the system doesn't 'halt'(?) at the windows logo with verifier enabled.

    In fact, I instantly got a driver verification BSOD - the log and crash dump for these are attached.

    If there isn't anything in this dump that helps I will try the 'Repair Install'.

    Attachment 150249
      My Computer

  2. Posts : 39,955
    windows 10 professional version 1607 build 14393.969 64 bit

    The driver that you uninstalled was:

    PxHlpa64.sys Sonic CD/DVD driver (used by many different CD/DVD programs)

    The driver that caused the latest bsod was: atikmpag.sys
    Please update the AMD drivers.
    The best way to do this is to uninstall everything of AMD using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the AMD website. When you do this be sure the "clean install" box is checked and only install the Graphics driver.[2]=Hardware%20and%20Drivers

    Event[14229]:  Log Name: System  Source: Service Control Manager  Date: 2017-08-10T19:03:23.143  Event ID: 7045  Task: N/A  Level: Information  Opcode: N/A  Keyword: Classic  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-L224S2J  Description: A service was installed in the system.Service Name:  amdkmdapService File Name:  \SystemRoot\system32\DRIVERS\atikmpag.sys
    atikmpag.sys ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)
    Get from OEM for laptops

    amdkmdap     amdkmdap               amdkmdap               Kernel        Manual     Running    OK         TRUE        FALSE        8,192             368,640     0          30 Jan 16:04:58        C:\WINDOWS\system32\DRIVERS\atikmpag.sys         4,096
    Name	ATI FirePro V4800 (FireGL V)PNP Device ID	PCI\VEN_1002&DEV_68C8&SUBSYS_240A1002&REV_00\4&31024D2F&0&0018
    Adapter Type	AMD Radeon Graphics Processor (0x68C8), Advanced Micro Devices, Inc. compatible
    Adapter Description	ATI FirePro V4800 (FireGL V)
    Adapter RAM	1.00 GB (1,073,741,824 bytes)
    Installed Drivers	aticfx64.dll,aticfx64.dll,aticfx64.dll,amdxc64.dll,aticfx32,aticfx32,aticfx32,amdxc32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
    Driver Version	15.201.2401.1010
    INF File	oem6.inf (ati2mtag_EvergreenGL section)
    Colour Planes	Not Available
    Colour Table Entries	4294967296
    Resolution	1680 x 1050 x 60 hertz
    Bits/Pixel	32
    Memory Address	0xD0000000-0xFBFFBFFF
    Memory Address	0xFBE20000-0xFBE3FFFF
    I/O Port	0x0000E000-0x0000EFFF
    IRQ Channel	IRQ 4294967292
    I/O Port	0x000003B0-0x000003BB
    I/O Port	0x000003C0-0x000003DF
    Memory Address	0xA0000-0xBFFFF
    Driver	c:\windows\system32\drivers\atikmpag.sys (, 498.52 KB (510,488 bytes), 16 Dec 19:07)
      My Computer

  3. Posts : 28
    Windows 10
    Thread Starter

    Hi zbook

    The AMD GPU drivers are already the latest version - should I still do another clean install of the current driver?

    Also, any thoughts on why it always seems to be the graphics driver, despite installing a different brand of card (have always had an Nvidia GPU in there, up until a couple of weeks ago)?
      My Computer

  4. Posts : 28
    Windows 10
    Thread Starter


    I did a clean driver re-install for the AMD card but still had the same issue.

    I have moved back to the NVIDIA graphics card and am currently running driver verifier with every non-MS driver being tested.

    No more windows logo halts....promising!

    Will see how it goes....

      My Computer

  5. Posts : 39,955
    windows 10 professional version 1607 build 14393.969 64 bit

    Drivers get corrupted like windows and software so they need to be reinstalled and updated. Sometimes they need to be rolled back. By default Windows automatically updates non-Microsoft drivers and sometimes new drivers produce bsod and must be rolled. This roll back has been fixing many laptop computers Realtek/Asus drivers lately.
    For the computer you can perform the following steps:
    1) uninstall and reinstall clean drivers
    2) switch video cards
    3) completely remove the video card
    Testing can be done with windows driver verifier and with Furmark with the aim to find a working driver/card and a stable computer environment.
    For each card please enter the driver version and date into the thread so that if needed you can look back in time and see what did and did not work.
    Whenever you have a crash post a new zip:
    BSOD - Posting Instructions - Windows 10 Forums
      My Computer

  6. Posts : 28
    Windows 10
    Thread Starter

    Another Memory management BSOD (unfortunately didn't have verifier enabled as I had disabled to get some graphic intensive work done). This was with latest nvidia driver. Version dated 21/8/2017.

    Reverting to latest manufacturer (Zotac) approved version (385.41).

    Edit: Just realised that these are both the same version. Will leave on this driver and try and catch another with verifier enabled.

    Also, just remembered I ran furmark (with verifier enabled) for a couple of hours without issue.
      My Computer

  7. Posts : 39,955
    windows 10 professional version 1607 build 14393.969 64 bit
      My Computer

  8. Posts : 28
    Windows 10
    Thread Starter

    Here are the BSDODs from today,

    I also had another IRQ BSOD (second of the day) about an hour ago that blue screend with verifier enabled. However the minidump never generated/updated because the progress of the BSOD was stuck on 0%. I left it on the BSOD for an hour but it didn't change.

    Notes: the IRQ error seems to happen most commonly when I shutdown whilst still get connected to a vpn (not 100% consistent with that though).

    The memory management errors are accompanied by a sound loop.

    Attachment 151241
      My Computer

  9. Posts : 39,955
    windows 10 professional version 1607 build 14393.969 64 bit

    There were 2 new bsod that were debugged and there was no definitive misbehaving identified yet.

    Windows driver verifier is a tool which is useful in finding misbehaving drivers.
    It will repetitively make misbehaving drivers produce bsod.
    Each bsod can then be debugged to identify the misbehaving driver.
    Windows driver verifier will repetitively produce bsod until the misbehaving drivers are fixed or until the tool is turned off.

    Download and install:
    Bluescreenview: Blue screen of death (STOP error) information in dump files.

    Modify system control panel > advanced system settings > startup and recovery settings > un-check automatically restart
    This will allow you to view the bsod window. When windows driver verifier is used the typical bsod dump code is driver verifier detected violation. Sometimes the misbehaving driver is displayed in the form *,sys. If you see the misbehaving driver displayed please record it and post it into the thread.

    To turn off Windows driver verifier you will use the windows advanced troubleshooting menu.
    There are 3 methods to turn off windows driver verifier and they should be used in the order listed.
    If the first method works there is no reason to go to the 2nd method. The additional methods are listed in case one of the methods fails to turn off windows driver verifier.
    1) startup options (not startup repair) > type: verifier /reset
    2) command prompt > Administrator X:\Windows\system32\cmd.exe > type: verifier /bootmode resetonbootfail
    3) restore
    When a restore is done the mini dump often disappears and little progress is made in the troubleshooting.
    To practice using the windows advanced troubleshooting menu open administrative command prompt and type or copy and paste: shutdown /r /o /f /t 00

    After each bsod you will turn off windows driver verifier > return to the desktop > run each bluescreenview and whocrashed > identify any misbehaving driver > uninstall the driver

    After uninstalling the driver you can either use windows driver verifier again to identify the next misbehaving driver and uninstall it or you can reinstall a driver after it has been uninstalled. The end result should be the same.

    As the bsod appear please post a new zip so that we can guide you through the process:

    BSOD - Posting Instructions - Windows 10 Forums

    Before using windows driver verifier:
    1) backup all files
    2) create a backup image using Macrium:
    Macrium Software | Your Image is Everything
    3) place the backup image on another drive
    4) create a brand new restore point.

    This link has the customized settngs for using windows driver verifer:

    This link has the methods to turn off windows driver verifier:

    Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials

    When you feel comfortable using the windows advanced troubleshooting menu and have time to troubleshoot the bsod please turn on windows driver.

    When there are no longer any bsod you will run windows driver verfier for an additional 36 hours with the computer under typical use. If there are no more bsod you can turn off windows driver verifier and that will complete the troubleshooting.
      My Computer

  10. Posts : 28
    Windows 10
    Thread Starter

    Hi zbook,

    I hope you're well.

    I've been running driver verifier for a week now and finally got a memory management BSOD this afternoon.

    I'm hoping there's something of use in there because I don't think I can stand running verifier for much longer (system is very choppy with it running).

    Attachment 152565
      My Computer


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

Designer Media Ltd
All times are GMT -5. The time now is 04:39.
Find Us

Windows 10 Forums