BSOD - Generic memory 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.

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.:)

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.

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:P

Code:

Crash dump found at C:\WINDOWS\MEMORY.DMP
Creation date: 12/28/2017 09:12:12
Size on disk: 960 MB

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

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

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.

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.