BSOD MEMORY_MANAGEMENT and others like it - a strange case, how to prove that the problem is hardware?

Question

Iron

I apologize in advance for the long description!
There is a laptop that has already drunk all my blood - Asus X507M https://www.citilink.ru/catalog/mobile/notebooks/1...
Almost immediately after it was purchased and delivered to our employee, problems began in the form of frequent blue screens.
I took a laptop from her for diagnostics and, oddly enough, memtest86 did not find anything. Although MEMORY_MANAGEMENT and a couple of dozen other codes that were in memory dumps usually clearly indicate problems with RAM, I still tested both hard and ran stress tests for heating, etc. - nothing! Demolished Windows, rolled it all over again (the organization already has 2 such laptops that work properly with an identical set of software). I drove it a little more - no problems.
I gave it back to the employee and by the evening the problem reappeared. This time, memtest86 sprinkled errors right off the bat, which means the software has nothing to do with it.
I packed it and took it to the guarantee, demonstrating the problem to the receiver on the spot, detailing all my checks.
2 weeks have passed - they say take away "no problems found." The report says that the BIOS has been updated. For the company, they also demolished my Pro Windows and put Home, morons, you can’t add it to the domain, well, to hell with them, I’ll rearrange it. I tested the memory right away - no problems.
Well, I started installing the software again and at a random moment I again catch MEMORY_MANAGEMENT .. I run the memory memory test - it writes errors again.
I'm downloading fresh memtest86 (from another computer) so that I can make a video with the test stages clearly so that the guaranteeers do not get out this time. Downloaded, recorded, launched - no errors, AGAIN! Windows test again - no errors! The laptop just lay on the table, no one touched it.
What the hell else could this be!? I hope that there is someone sensible in terms of hardware diagnostics, who can tell me something
. My guesses, but I don’t know how to prove it: oxides on the contacts of the memory module, a power problem, a problem with the memory controller

Answer 1

Carry out tests with Akum on the network, with Akum off the network, without Akum on the network. Memtest86 cut into 4 streams of 2GB to 100 percent each. Record all results. Windows memtest just once for each setup. I bet on a battery without a network.

Answer 2

Sometimes such problems are caused by the south bridge, well, or other coprocessors working with memory