BSOD in Win7 after witnessing firefox crashes

I got a BSOD not long after experiencing weird crashes in firefox.

Brief description of what happened: Firefox crashed without an apparent cause. Get a popup explaining something went wrong with the plugin container. The option to restart firefox resulted in an immediate crash with an identical popup. Closed all instances of Firefox and tried again. It still crashed, even before I choose which firefox session to restore.

I restart my PC, restart firefox and don't restore my old tabs. After a few minutes thinking it might be okay, it crashes again after 30-60 seconds of watching a youtube video. After half a second of seeing the crash, windows goes into BSOD.

When the computer restarts, windows gives me this message about my BSOD

Code:

 
Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    1033

Additional information about the problem:
  BCCode:    1a
  BCP1:    0000000000041790
  BCP2:    FFFFFA8005014A40
  BCP3:    000000000000FFFF
  BCP4:    0000000000000000
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\092114-15194-01.dmp
  C:\Users\user-name\AppData\Local\Temp\WER-38501-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

I ran the dm log collector, the resulting file is attached.

I think it might be bad memory or motherboard now after running memtest86+. Running memtest for 2 minutes already uncovered thousands of errors. I've only begun the process of testing different configurations of sticks and slots. So far stick 1 gives errors in the two slots I tried and stick 2 doesn't give any errors in the first slot I tried. I'm going to run my PC with this stick for a few days to see if that prevents any BSOD.

Regarding ESET:
In the last dump, I had disabled ESET anti-virus after booting up (it was still running, but in its inactive mode). I wonder if that is related to its appearance in the log files. (disabling ESET it didn't prevent the BSOD).

Something else to consider is that I encountered a BSOD when I restarted my PC and left it to sit idle at the "windows login screen" overnight. It took 7 hours at idle to encounter a BSOD. Since I hadn't logged in to windows, would that make it seem unlikely that ESET caused the BSOD?

By the way, what tool shows the ERROR/WARNING you quoted?