multiple BSODs started recently

[maky13]

In the past few hours I`ve had 4 BSODs. Using Windows 7 x64.
Minidumps here: https://www.dropbox.com/s/opj0q3l4dvkh07c/bsod.zip?dl=0
Last dump: https://www.dropbox.com/s/44w0vq3hbu9qqgx/102517-31247-01.dmp?dl=0
No hardware changes in the past months; no (significant) software changes recently that I can think of.
Ran Memtest, said no memory errors.
What can I do?

 

[johnbl]

something corrupted memory being used by device drivers.
if I were to guess I would suspect this driver:
Intel® Hardware Accelerated Execution Manager (involved in Android app emulation)
IntelHaxm.sys Mon Sep 28 21:31:25 2015
check here for update (if you need it, or just remove if not used anymore)
https://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager-intel-haxm

your Intel(R) 82579V Gigabit Network Connection driver
is also old, you might also update it from the motherboard vendors website or from intel:
https://downloadcenter.intel.com/

you also have a old firewall
ESET Antivirus/Firewall - check for a free upgrade to the latest version
http://www.carrona.org/drivers/driver.php?id=epfwwfpr.sys

I can not tell what corrupted the kernel memory. you would have to run verifier.exe functions to force the system to bugcheck at the time of corruption to catch the driver in the act of corrupting shared kernel memory. Best to update all of the old 3rd party drivers first (motherboard drivers+ bios and any add on drivers like your firewall) then see if you still bugcheck. if you do then change the memory dump type to kernel and run the verifier functions to try to catch the driver corrupting memory.

to use verifier you would start cmd as an admin then run
verifier.exe /standard /all
then reboot.

Note: be sure you know how to get into safe mode in case the system bugchecks during the next boot up.
this is so you can turn verifier off via
verifier.exe /reset

you have to turn it off after you are done testing or your machine will run slowly until you do.

generally, if verifier catches a driver doing something wrong it will name the driver in the memory dump file.

 

[maky13]

Update:
System is kinda dead.
I realized that the memtest I ran was the windows one, not Memtest86 or 86+
Main ssd (with windows) started to act badly too, stuff like "C:\Program files not found or corrupted"; although that might be caused by the 20 bsods from last night.
I want to find out if its the ssd, the ram or somrthing else. What is a good way to run diagnostics?
I cant get memtest86+ to boot via usb.

 

[johnbl]

I would start checking motherboard connections, maybe put the hard drive on a different sata port or the slower primary sata controller.
Then attempt to boot into bios and reset it to defaults and check the voltages and see if the machine seems stable while in bios.
when the bios is stable, let the current ssd sit with power on but don't try to boot windows for a hour or 2. this would give the ssd firmware time to run its repair routines (in case the drive was full or there was some bad blocks that the ssd had to move, generally 5 minutes after it is idle it will start repairs)


then attempt to boot windows, if it boots up great, you can start looking for other problems. if not then you should make a bootable usb drive with a current windows 10 install image on it then boot up and attempt a repair of your ssd.

if you have access to another machine I would build a usb thumb drive with a current windows 10 image on it