The results from the DMP files do not give a definitive answer even though I suspect that this is hardware problem. While we investigate further here are a few things that you can do.
1-Run a system file check to verify and repair you system files. You do this by typing cmd in search, then right click and run as admin. SFC/ SCANNOW
2-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.
3-Event viewer
Go into event viewer (type eventvwr in search). Go to the windows log>application tab.
You want to look for critical errors (they have red in the left column ).
When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.
When you find them please note the event ID, and the source codes and tell us what they are.
4-Device manager
Please go to start>search>type device manager.
Are there any "unknown devices" with yellow triangles on them?
Is you driver there , listed, and working?
If y our driver is missing, or there is a yellow triangle on it, you will need to update it.
-Also, hard drive controller driver was blamed with stop code 50 (hardware come into play), I would suggest to run Disk Check and HD Diagnostic (download HDD test from manufacture site)
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: (Most recent one)
Code:
BugCheck 109, {a3a039d89570f5d3, b3b7465ee7edc7c9, fffff80002e4f0f0, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
BugCheck 1A, {41790, fffffa80006ba5d0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33a08 )
Followup: MachineOwner
---------
BugCheck 50, {fffff88002a58af8, 0, fffff80002e4f0f4, 0}
Could not read faulting driver name
Probably caused by : memory_corruption
Followup: memory_corruption
---------
BugCheck D1, {1, 2, 1, fffffa8004f4a947}
Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+11f )
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff80002e9f176, fffff88005398d00, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
BugCheck 50, {fffff30022d35bb9, 0, fffff88001261340, 7}
Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!memmove+b0 )
Followup: MachineOwner
---------
BugCheck 1000007E, {ffffffffc0000005, fffff800031e0251, fffff880009a96e8, fffff880009a8f50}
Probably caused by : ntkrnlmp.exe ( nt!RtlUnicodeStringToAnsiString+31 )
Followup: MachineOwner
---------
BugCheck 24, {1904fb, fffff88006edeea8, fffff88006ede710, fffff880012b803f}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
BugCheck 109, {a3a039d8969dc55d, b3b7465ee91a9753, fffff800032df0d0, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
Let us know if you need help
Tuan