the verify problem listed below will lead to corruption of data stored in memory as the network driver is being used. It could have caused the corruption in the running file system driver that we saw in the previous memory dumps. I would update the driver and the netcard firmware and reboot and see if verifier still flags the buffer allocation.
Also it did not name this driver, it named a network componet that was reading settings from the registry. So this can be a bogus registry setting. In this case you would want to download the update network driver, turn off the plug and play service, uninstall the current network driver, remove the software from your machine, install the updated driver, and turn the plug and play service back on.
(or use the pnputil.exe to remove the old install pacakge so plug and play will not reinstall the driver a few seconds after you remove it, often with network drivers you have to actually activate(explicitly select it) the new driver as it will not automatically be selected as the default right after the install) and the windows control panel interface before widows 10 does not show the date/time stamp or the build number for the network driver during the install.
anyway, install the driver/firmware updates reboot and see if verifier finds a problem on the next boot.
----------
the most current bugcheck was in networking code.
it looks like you have a Intel(R) 82579V Gigabit Network Connection driver
\SystemRoot\system32\DRIVERS\e1c62x64.sys Wed Aug 12 15:27:36 2015
your driver is pretty current but here is the most current version from intel:
https://downloadcenter.intel.com/download/18713/Network-Adapter-Driver-for-Windows-7-
also look for a firmware update for your network card. google "82579V nvm firmware update"
here is the one listed at the last one (10/26/2012)
https://downloadcenter.intel.com/download/22026/NVM-Update-Utility-for-Intel-82579V-Gigabit-Ethernet-PHY-Network-Connection
(sometimes a vendor will get custom fixes that will only be on the vendor web site, look for NVM (non volitile memory)/firmware update)
Looks like the system was trying to start the network, read some values from the registry and then attempted to allocate some memory but verifier did a "sanity" check on the allocation, found something it did not like and called a bugcheck. verifier indicates that the driver attempted to allocate a buffer that was zero bytes. This would often just be a programming mistake that would lead to corruption of the system if the driver actually attempted to use the buffer. I would install the updated driver and see if there is a firmware update for the actual network card on the machine.
get rid of this file: (old piece of a remote networking driver written way too long ago)
C:\Windows\system32\drivers\LMIRfsDriver.sys Mon Jul 14 09:26:56 2008
it is listed as a logmein driver but is still installed on your system
use this method to remove the driver:
https://technet.microsoft.com/en-us/library/cc730875.aspx