What is causing this Windows 10 blue screen (MEMORY_MANAGEMENT ntoskrnl.exe)?

I'm getting the following blue screen in Windows 10:

================================================== Dump File : 010216-40531-01.dmp Crash Time : 1/2/2016 8:13:36 PM Bug Check String : MEMORY_MANAGEMENT Bug Check Code : 0x0000001a Parameter 1 : 00000000`00041201 Parameter 2 : fffff6bf`fcdc6488 Parameter 3 : 20700001`1349e025 Parameter 4 : ffffe001`5a2bf8a0 Caused By Driver : ntoskrnl.exe Caused By Address : ntoskrnl.exe+14f4d0 File Description : NT Kernel & System Product Name : Microsoft® Windows® Operating System Company : Microsoft Corporation File Version : 10.0.10240.16590 (th1_st1.151104-1714) Processor : x64 Crash Address : ntoskrnl.exe+14f4d0 Stack Address 1 : Stack Address 2 : Stack Address 3 : Computer Name : Full Path : C:\WINDOWS\Minidump\010216-40531-01.dmp Processors Count : 4 Major Version : 15 Minor Version : 10240 Dump File Size : 266,288 Dump File Time : 1/2/2016 8:24:35 PM ================================================== 

I'm also getting similar errors with ntoskrnl.exe with the error "IRQL_NOT_LESS_OR_EQUAL".

Everything I've searched on this is very vague. I'm not very good at decoding these dumps. I ran MemTest86 and memory checked out. Any insight on what might be causing this?

I'm running Windows 10 on a Dell Latitude E6410.

EDIT: Dump file can be downloaded here:

10

3 Answers

When doing Bugcheck Analysis it is important to obtain and read all output; not only that, you also need multiple dumps to cross check this output along other bug checks to avoid false positives.

Your dump reveals quite a bit, but not enough for a conclusion:

  • Unknown memory management error (1a, parameter 1: 41201) occured.

    MEMORY_MANAGEMENT (1a)

    Arg1: 0000000000041201, The subtype of the bugcheck. 
  • Classified to be a driver fault that occurred during execution of audiodg.exe.

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: audiodg.exe 
  • Produced while querying virtual memory at the end of copying system service memory.

    STACK_TEXT: nt!KeBugCheckEx nt! ?? ::FNODOBFM::'string'+0x122c8 nt!MiQueryAddressState+0x307 nt!MiQueryAddressSpan+0x139 nt!MmQueryVirtualMemory+0x648 nt!NtQueryVirtualMemory+0x25 nt!KiSystemServiceCopyEnd+0x13 0x00007ff9'bbdf37aa 

    0x00007ff9'bbdf37aa is of particular interest here, because that is what is where the chain of calls originates from. However, there is no information about that because your system is not configured to take complete memory dumps:

    Mini Kernel Dump File: Only registers and stack trace are available

It's also not yet guaranteed that every dump you get results in the same, that needs to be verified.

Until you have more information, you have way too much possible solutions to try. More dumps that contain more complete information will spare you the hassle to go through all that.

But if you have some time, here is an incomplete list with no guarantees:

  • Remove and reinstall your audio drivers.
  • Update all your drivers
  • Run RAM tests.
  • Replace the RAM out of precaution.
  • Remove your antivirus and consider another one.
  • Make sure you are clean of viruses, malware, ...
  • Run sfc /scannow and Microsoft's SUR or DISM utility to check system health.
  • Reinstall your operating system.
  • Keep replacing hardware till the broken piece is gone.
  • ...
5

I'm almost positive that it could be a driver conflict with your wireless card. Mostly from experience with this laptop and wireless NIC's I've seen in the field.

Try re-installing and updating the driver(s) from the device manager, I would not advise updating the bios through Windows because of the off chance of a BSOD occuring while the update is running. Driver Identifier is a great service for finding/updating drivers.

If you must, either check if you can install the BIOS update through a FreeDOS live USB. I provided a link to the driver details page on Dell's website for that laptop for further details. Just navigate to the "Install Instructions" drop-down and check that out.

Also, here is a link to a good guide on creating a FreeDOS live USB and installing the BIOS update.

Good luck!

You get the Bug Check 0x1A: MEMORY_MANAGEMENT

The MEMORY_MANAGEMENT bug check has a value of 0x0000001A. This indicates that a severe memory management error occurred.

From the callstack I can see that virtual memory operation where done:

00 nt!KeBugCheckEx 01 nt! ?? ::FNODOBFM::`string' 02 nt!MiQueryAddressState 03 nt!MiQueryAddressSpan 04 nt!MmQueryVirtualMemory 05 nt!NtQueryVirtualMemory 06 nt!KiSystemServiceCopyEnd 07 0x0 

So, this looks like some RAM issues. If memtest86+ shows no errors, check the RAM timings. Run CPU-Z, look into the tabs Memory and SPD and verify that the values match and that Command Rate is set to 2. If Command Rate (CR) is set to 1, go to the BIOS and change it to 2.

7

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

You Might Also Like