Hi and Welcome to Sevenforum
It looks like that all of your crash dumps are memory related, from stop codes to what were being blamed.
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
STOP 0x0000004E: PFN_LIST_CORRUPT
Usual causes: Device driver, ?memory
In looking through your drivers, I can see that you are using Kapersky. Third party antivirus software are notorious for causing BSOD and Kapersky is not an exception. I would recommend you to remove it completely for testing. Then, use MSE to make sure your system is protected
MSE: http://www.microsoft.com/security_essentials
To remove Kapersky: Removal tool for Kaspersky Lab products
Please download third party called memtestx86, burn it to CD using iso recorder: ISO Recorder v3 (link), and let it run for at least 6,7 passes.
Code:
BugCheck 1A, {3452, e57000, fffff70001082248, b590000008617c66}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33a23 )
Followup: MachineOwner
---------
BugCheck 4E, {99, 18ffd7, 2, 18ff97}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff9600006bbe6, fffff88008595200, 0}
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
Probably caused by : win32k.sys ( win32k+5bbe6 )
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff80002b5856d, fffff8800736e750, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
Followup: MachineOwner
---------
BugCheck 1000007E, {ffffffffc0000005, fffff80002bd2a04, fffff880031d2888, fffff880031d20f0}
Probably caused by : ntkrnlmp.exe ( nt!ObDereferenceSecurityDescriptor+a8 )
Followup: MachineOwner
BugCheck 1A, {41284, 3e2001, 0, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
Followup: MachineOwner
------------------
Run system file check:
SFC /SCANNOW Command - System File Checker
Let us know if you need help
Tuan