BSOD normal or safe mode, multiple errors

[Overtow]

Greetings! A couple of years ago I made a post detailing my previous BSOD issues (original thread http://tinyurl.com/psp7ny5). I dont know if i found the cause but i did find a workaround.

Basically I started re-seating the memory modules in my ASUS m50vm and found that putting either of my two modules into one particular slot (the top slot in this case) would cause a BSOD error during the windows loading screen when booting normally OR into safe mode. Removing that module and placing it into the bottom slot, however, allows my computer to boot and work normally.

Upon discovering this, I assumed it was a hardware issue, a problem with my motherboard perhaps, and have been using my computer, with only one 2gb module seated in the lower slot on my motherboard, without issue since then.

Fast-forward to today, I decided to pop in the other 2gb module (into the top slot), boot up my machine, and as expected a BSOD error happened during the windows loading screen, and again after trying to boot into safe mode. Putting either module into that top slot, or one module into both slots, cause this to happen. I think I also re-installed windows sine my original thread.

My computer works fine otherwise, except that sometimes, if I leave Chrome alone for a while, my computer will BSOD, and it only seems to happen when I have Chrome open and am away from my computer or something (I do not have the specific .dmp files from these instances, though). I have the .dmp files from last night and earlier today, as well as some other goodies. I'm hoping someone can take a look at this and maybe help me to figure this out. Thanks!

 

[essenbe]

Overtow, all of the information from the file was not there please run http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html and upload the whole file.
I would like you to fill out your ststem specs.

Please fill out your System Specs​

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html​

As you suspected, ram is your problem. If what you think is correct, it can only be fixed by the manufacturer or by replacing the motherboard. Both dump files referenced memory as the problem.

Debugging Details:
------------------
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - [COLOR=red]The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.[/COLOR]
FAULTING_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`0226eac5 498b08          mov     rcx,qword ptr [r8]
EXCEPTION_RECORD:  fffff880026d1628 -- (.exr 0xfffff880026d1628)
ExceptionAddress: fffff8000226eac5 (nt!ExpInterlockedPopEntrySListFault16)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  nt!MiFindNodeOrParent+0
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035
IMAGE_VERSION:  6.1.7601.18247
IMAGE_NAME: [COLOR=red]memory_corruption[/COLOR]
FAILURE_BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0
BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0xa_nt!mifindnodeorparent+0
FAILURE_ID_HASH:  {d02b6ddb-b322-5b90-a0fb-b710165a1765}
Followup: MachineOwner

Either the memory is bad or the motherboard Dimm slot is bad. You seem to already know the answer to the question, but if you would like to be able to prove it, I believe we can do that with some tests. The tests are quite long and time consuming. If you would like to proceed with the tests, let me know and I can tell you exactly how to do it, and what tests to run