BSOD Everytime: MEMORY_MANAGEMENT 0x0000001a 00000000`00004477

Page 2 of 2 FirstFirst 12

  1. Posts : 9
    Windows 10, Update
    Thread Starter

    axe0 said:
    Most likely the main causes are the outdated drivers, some are 9 years old.
    Some you can update by updating programs or reinstalling programs like Malwarebytes, but others are drivers your manufacturer provides.

    You can't really fix the problem for Windows 10 due to outdated drivers, I can show you what drivers are outdated but I can't do much more.

    Ok, that would be helpful. I will update all the ones I can. I have uninstalled all the NI software for now, and a bunch of other stuff. No luck yet. Next I will update what I can then start picking away at the list of MS services that get disabled in the SafeBoot Minimal. If I can figure that out, it will be a good hint towards the issue....
      My Computer

  2. Posts : 14,893
    Windows 10 Pro

    Like I said, the problem with your system is the drivers, you never will be able to update them to Windows 10.
      My Computers

  3. Posts : 9
    Windows 10, Update
    Thread Starter

    axe0 said:
    Like I said, the problem with your system is the drivers, you never will be able to update them to Windows 10.
    Hello ,
    So I figured it out. It is the softmodem driver. Once I figured out using WinDbg, it was actually fairly straightforward. Here are some details for others with similar consistent BSOD that produce minidumps.

    1. Go to Microsoft and download the standalone WinDbg. It is easy to find, and there is plenty of help, for example:
    Debugging Using WinDbg - Windows 10 hardware dev

    I think this is easier than full Visual Studio, YMMV.

    2. Load the minidump into WinDbg. I loaded symbols from Microsoft public server, you may not need to do this, but it is very helpful. In my case it didn't have the symbols for the driver, so it complains about it, and means I found mine without those symbols. You will get a whole bunch of output about symbols you can ignore, looks like this:
    Attachment 56500
    3. When you get a command prompt, type in: !analyze -v, and you'll get output (hopefully) like this:
    Attachment 56501
    4. Pretty easy to see the culprit here: CAX_CNXT.sys which is a driver for the softmodem
    5. You can find is on your computer in the drivers folder, or use the LMVM command to locate it:
    Attachment 56502

    So I unloaded this driver, and I can go in and out of sleep fine. Hurray!

    I hope that might help other people. Now I am looking on the best way to permanently delete/disable the driver. Things that don't work so far:
    1. Using device manager to uninstall and delete does not work
    2. Deleting the driver files directly, even if I do both .inf and .pnf, even if I do step 1 first
    3. gpedit - I have Win10 Home, so sadly no gpedit for me
    4. pnpuntil - holds promise, Win10 home does have that. Going to play with that to either do it once (I guess this will fail as 2. above fails and I think Win10 will auto update it) -OR- create a batch file or something to run pnputil either before sleep or after waking up. I think this will work in some fashion.

    So now that I invested the time to figure out how to use WinDbg a little, I think analyzing BSOD in the future will be easier and faster, with less trial and error. I hope the tips above might help others do the same. And there are tons of other things you can debug with these tools. It seems pretty easy, but I do have a background in developing (long time ago on Windows though), but there are tons of help files and it is all free.

    I am going to mark as solved because I found the BSOD root cause, even though I am still automating the fix, which seems a different project to me.

    Good luck to you all, and regards,
    Last edited by rfrance67; 01 Jan 2016 at 13:24.
      My Computer

  4. Posts : 9
    Windows 10, Update
    Thread Starter

    One last update. I finally was able to uninstall and delete all the CNXT drivers and force a Microsoft softmodem driver to replace it before doing the sleep which caused the original driver to get reinstalled. So although I could never force jsut leaving the HW without a driver, doing the substitution to a different driver the behaves works great. So finally done with this one and glad it worked out. Probably the last stop on the line though, won't be upgrading this one again!

    Thanks to axe0 for all the replies!
      My Computer

  5. Posts : 14,893
    Windows 10 Pro

    I was already aware of the cause, but I just thing it isn't smart to stay with Windows 10.
      My Computers


  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 21:00.
Find Us

Windows 10 Forums