![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
With all due respect, I stand by my previous post to ignore the bsod unless it begins to happen often. As I stated before, they do just sometimes happen. When that occurs you're pretty much looking for a needle in a hay stack. In fact, the BSOD screen specifically states "If this is the first time you've seen this stop error screen restart your computer. If this screen happens again, follow these steps." To go looking for the cause of an isolated incident is a waste of time and resources. Your statement that there is only one dump file confirms what I am saying. One dump file means it has only happened once.
10 passes with 0 errors :-)
Nothing wrong with checking the ram, but as I stated in my previous post, although the error message includes "Memory management" the issue is most often not related to faulty ram.
"Also, while the dump file states the error was a result of Memory Management, most often this error is not the ram. It is most often a fluke between the installed ram and pagefile".
Finally***,*** being old doesn't mean the computer should have issues. That is a human characteristic which computers do not share. A computer is made up of electronic and mechanical components. They either work or they don't. They don't work half way.