We're dealing with a mixture of a few problems.
First, there is this 0x24 error which is the first seen in the thread now:
Code:
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904fb, fffff88006d5fb58, fffff88006d5f3c0, fffff880012460fd}
Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireFcbWithPaging+12d )
Followup: MachineOwner
---------
That tells us that there is either a physical error with the hard drive itself (most likely), connection to it or damage to a storage driver. It actually in rare instances can be caused by antivirus, which leads me to your other errors, one of which has been a 0x3B stop. That is caused when video drivers pass bad data to the kernel code, and antivirus is usually responsible for this as well...
Code:
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff960000a409e, fffff88009957a70, 0}
Probably caused by : win32k.sys ( win32k+3409e )
Followup: MachineOwner
For now, here is the prescription to attempt alleviation of all errors.
1) Uninstall ESET NOD32 in the normal method and then use the special utility found here to ensure its complete removal from the system:
AV Uninstallers - Windows 7 Forums
2) Install MSE. It is lightweight with a very small footprint, free and great because it is actually in Microsoft's best interest to rid the net the best they can of Malware. Other companies do not have this incentive. For this and many other reasons, MSE is a great antivirus solution and also, it simply never ever causes bsod. Very reliable unlike all other a/v.
3) Open an elevated command prompt. Copy and paste the following comand then hit enter to detect and resolve any file system structural damage.
If you have more than one hard drive or partition, run the command for them too like this, changing the drive letter to match...
chkdsk /r D:
chkdsk /r E:
4) Have you copied the Zyxel driver over the existing one at C:\Windows\System32\drivers yet? It seems to be the 2008 version still, in the crash dumps.
Good luck with this. It should all prove helpful. Let us know how it went and as always, please post a new crash dump if needed after.