It can be Memory issue or drivers that cause memory issue. Memory corruption was blamed in the dump. Let's test the Ram first
Please 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.
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
BUGCHECK SUMMARY:
Code:
BugCheck A, {28, 2, 0, fffff8000331a410}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
Followup: MachineOwner
---------
BugCheck 1A, {5003, fffff780c0000000, 2fc0, 269300005f82}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a1ef )
Followup: MachineOwner
---------
BugCheck 19, {3, fffff8000345ca70, fffff8000345ca72, fffff8000345ca70}
Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )
Followup: Pool_corruption
---------
BugCheck A, {28, 2, 0, fffff80003310410}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
Followup: MachineOwner
---------
BugCheck 1E, {ffffffffc0000005, fffff880041864e2, 0, ffffffffffffffff}
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : usbohci.sys ( usbohci!OHCI_ProcessDoneAsyncTd+1d5 )
Followup: MachineOwner
---------
Run system files check please:
Let us know if you need help
Tuan