Hi and Welcome to SF!!!
There are few things that you can try:
First of all, please remove Eset Nod32 as I can see some stop codes related to that:
How to uninstall or remove ESET Nod32 antivirus totally?
Then install MSE for testing purpose:
http://www.microsoft.com/security_essentials
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
This driver is old:
Code:
PxHlpa64 PxHlpa64.sys Tue Dec 11 06:49:01 2007 (475DD06D)
Sonic CD/DVD driver (used by many different CD/DVD programs)
If you don't know what program you use, then
Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK
This will break your CD/DVD program, but can easily be renamed after we've finished.
Then test your RAM, Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
BUGCHECK SUMMARY:
Code:
BugCheck 50, {fffff8801896c338, 0, fffff960000c5b4d, 2}
Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k+c5b4d )
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff80002c42340, fffff8800979e920, 0}
Probably caused by : ntkrnlmp.exe ( nt!soutput_s+f0 )
Followup: MachineOwner
---------
BugCheck FC, {fffff8a00c102e00, e67000006a255963, fffff8800a26b7c0, 2}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42497 )
Followup: MachineOwner
---------
BugCheck 1A, {31, fffffa80061ac810, fffff88000b71000, fffff8a0099038bd}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+6378 )
Followup: MachineOwner
---------
Regard,
Tuan
Quote