Windows 10: BSOD - "Memory Management" error

Hello all,

I have been experiencing BSODs recently which state a generic memory management error.
I ran memtest for a day and no errors were detected. I have removed and re-seated all ram modules.

I noticed the BSOD was occurring when my external HDD woke up, however I unplugged it and the BSODs are continuing so I don't think it's that. I cannot link it to any other event and it has only just started. the PC is not a new build.

I have been running Driver Verifier and attached is the crash dump log extract (along with the zip file) *Now added a log which contains more info, however I have no idea what I'm looking at! Can anyone help please?

Thank you.

:)

 

about " memory full . close ... " problem ! n97 and equalizer !

i dont have any problems of those u listed i exit frrom all applications when i finish ! well this means there is no solution so thanks a lot nokia

and about the music i was talking about the phone loudspeaker .. !

 

about " memory full . close ... " problem ! n97 and equalizer !

1-hey ..! i did a format to my nokia n97 few days ago .. before i did the format i had the problem that sometimes when i go to photos its says " memory full close some applicartions ..." and now i have it again ! so i just wanna know how to
solve this problem its really annoying !



2- my best music kind is trance ,, but i dont enjoy listening trance on my n97 coz music does'nt sound good for this kind of music .. so i want to know if there is a way to make n97 music sounds like x6 or even 5800 ( i guess ) .. through some
application or through equalizer or whatever ! i dont wanna get another phone

hope u help me .. ! thanks

 

The zip file you uploaded is empty. Please try running dm_log_collector again.

If you still have problems running the collection tool, you can try our new beta tool instead:



log collector v2-beta06.zip

 

My apologies, please find attached an updated file. I used the beta tool as per your link.
Interestingly, just after pressing enter on the command prompt I got the BSOD again. I assume the record of this will be in the attached somewhere.
Many thanks for your time in helping.*Smile

 

There is only one dump in the zip file. Looks like all the others were large system dumps.

There were 10 of these:
Code: Event[557]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-12-14T16:15:06.268 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-2OGO4OA Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000061941, 0xffff9901bab84174, 0x0000000000000009, 0xffffbb8a5f5effb0). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 837d83cd-a123-434c-9fca-cbfb7e8de0a1.[/quote] Please zip this file and upload to a file sharing site like OneDrive then post a link to it here so I can download it
Code: Crash dump found at C:\WINDOWS\MEMORY.DMP Creation date: 12/28/2017 09:12:12 Size on disk: 960 MB[/quote] Bugcheck 1a is "MEMORY_MANAGEMENT" and shows a memory corruption has occurred. This can be caused by defective RAM or a buggy driver.

The first thing to do is test your RAM as follows:
===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.



Warning MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.



Note MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.
===================================================

If that runs okay, then I would enable Driver Verifier and test as described below:

Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to

PART TWO

and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun dm_log_collector and upload the resulting zip file.
===================================================

Please make sure your PC is configured for small dump files:

How to Configure Windows 10 to Create Dump Files on BSOD

 

Thanks for the in-depth response.

To answer point 1, I have uploaded the file as requested:
https://drive.google.com/open?id=1UD...aLBa1kcloDqWKR

I will run a full memtest overnight tonight (and into tomorrow if necessary) to see if this flags any issues.
I'll report back with findings.

Many thanks,
Steve

 

The full dump did show one more possibility:nvlddmkm.sys
Code: *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x21b730[/quote] You currently have : Driver Date: 14/11/2016 Driver Version: 21.21.13.4201 which is the latest available for that card.

If the memory test and Driver Verifier don't show us anything you may want to look into replacing your video card since the one you have now, the NVIDIA GeForce GTS 250 is pretty old and the driver is also old. Just something to keep in the back of your mind.

 

Thanks again; 3 passes completed overnight, no errors so still got a way to go. I'll check back in this evening. *Smile

 

Ok, so today's update: at 10am after 3 passes with no errors I had to reboot as my daughter needed to use the PC. When it booted back to Windows the graphics card fan went into overdrive for about 10 mins before slowing down to normal. At lunchtime I put it back onto memtest and it has done about 7-8 hours and at 6pm had done 2.5 passes.
I just switched the monitor on and within a seconds of the screen appearing the pc shut down without warning.
I switched it back on and I started to boot to Windows. The gfx fan was going mad again then everything froze. The gfx card is red hot - literally untouchable.
Could this be the cause or is this just a result of running memtest?

 

No, memtest puts no load on the graphics card. Sounds like it gone bad. Unfortunate but it happens.
I'd say it's time to replace it, and I suspect that will probably resolve the BSOD problem as well.

 

Hi again,
So repeated attempts to run memtest failed after around an hour each time.
I swapped out the GTS 250 gfx card for an old Geforce 8500GT card I had lying about. Using this I have successfully run a 22 hour memtest, completing 8 passes with no errors.
I put the GTS250 back in again, the PC shuts down with no warning about an hour in. So it seems pretty clear the card is kaput!
the 8500GT card is back in again and the PC is running OK at present. I'll keep an eye out for any further BSODs over the coming days.
Thank you for your help with this problem! *Smile

 

Bummer, but pretty definitive testing for sure.

Good luck and a Happy New Year.

 

Happy new year!

Sadly I'm back, and it looks like the problem wasn't fixed after all...
Although the PC did work OK for several hours yesterday, within 30 minutes of being on today it showed a BSOD again. This is the memory dump: https://drive.google.com/open?id=13BY_pXlkdwvUN4ewf9bSAqzFBtsvUvRN
This is the memtest screenshot: https://drive.google.com/open?id=11a...3Xx0UNZwO4d6h9
I hope this helps shed some more light?
I now have drive verifier running so I'll post any updates from this.



Many thanks,
Steve

 

Again names memory management.

What is the exact memory configuration of your system?

In your profile you have mentioned 11 gb ram?

Do you have different memory modules in your system?
Did you recently add some new (different) RAM to your system?

What happens if you run your system with only 8 GB of RAM?


Also in the stacktext of the dumpfile is named ACPI and HALacpi.
Code: STACK_TEXT: ffff858a`bd6fadc8 fffff802`a781dc54 : 00000000`0000001a 00000000`00061941 ffffe201`453ee174 00000000`00000009 : nt!KeBugCheckEx ffff858a`bd6fadd0 fffff802`a77f2c72 : 00000000`00000024 00000000`00000001 ffffba04`35cdc010 fffff802`a76ddf01 : nt!MmAccessFault+0x129fc4 ffff858a`bd6fafb0 fffff802`a760983b : 00000000`bf790430 00000000`00000000 00000000`00000024 ffffe201`453ed430 : nt!KiPageFault+0x132 ffff858a`bd6fb140 fffff802`a7609711 : 00006c00`00012170 00000000`00000000 fffff799`40002018 00000000`00000008 : hal!HalpAcpiCheckAndMapTable+0x6f ffff858a`bd6fb190 fffff802`a7609d00 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpAcpiGetTableFromBios+0xf1 ffff858a`bd6fb220 fffff802`a7609c21 : 00000000`00000000 00000000`4d44534d 00000000`00000000 00000000`00000000 : hal!HalpAcpiGetTableWork+0x9c ffff858a`bd6fb270 fffff802`a7609bd3 : 00000000`00000000 ffff858a`bd6fbc00 ffff958b`bb1817b0 00000000`00000001 : hal!HalpAcpiGetTable+0x41 ffff858a`bd6fb2a0 fffff808`a4b9dd50 : 00000000`00000000 fffff802`a79db600 00000000`00000000 fffff802`a76c13bb : hal!HalAcpiGetTableDispatch+0x13 ffff858a`bd6fb2d0 fffff808`a4b9dcea : ffff958b`bb1817b0 ffff858a`bd6fbcc0 ffff958b`bb1817b0 00000000`00000001 : ACPI!ACPIMapNamedTable+0x40 ffff858a`bd6fb340 fffff802`a7bd8b95 : ffff858a`bd6fb405 ffff958b`bb1817b0 ffff958b`54465241 00000000`00000000 : ACPI!ACPIEnumMapTableHandler+0x2a ffff858a`bd6fb380 fffff802`a7b7a5bf : 00000000`0000004c 00000133`77085f10 00000000`00000000 00000000`00000000 : nt!ExpGetSystemFirmwareTableInformation+0xe5 ffff858a`bd6fb3d0 fffff802`a7b797bb : 0000000d`058ff301 00000133`7706cc00 00007ff8`a7c7a040 00000133`77fecf90 : nt!ExpQuerySystemInformation+0xcef ffff858a`bd6fbc00 fffff802`a77f4553 : ffffba04`3f2ba040 00000000`00000000 ffffba04`3f2ba040 00000133`77099c20 : nt!NtQuerySystemInformation+0x2b ffff858a`bd6fbc40 00007ff8`d06c0504 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 0000000d`058fe2d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007[/quote] Is your BIOS, chipsetdrivers, SATA etc. up to date on your system.