I'm just downloading your, I assume, dump files now. At 147mb there must be a few of them lol.. Looking at your memtest results I noticed the different timing readings which is a little odd. The only reason I can think of is that usually AMD boards have RAM slots which are dual channel. This can sometimes mean that certain slots must be used for the Dual channel system to work. My Gigabyte board for example has dual channel but only if the sticks are placed in slot 1 and then slot 3. Perhaps your board is similar (I'll know better once I read the dump file).
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff96000105a50, fffff8800a1eb0a0, 0}
Probably caused by : win32k.sys ( win32k!MapDesktopObject+20 )
Followup: MachineOwner
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click and apply to exit the dialogs, then reboot for the changes to take effect.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002e6fac5, fffff8800d904e80, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
Followup: MachineOwner
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904fb, fffff88002971338, fffff88002970b90, fffff880012b2d4f}
Probably caused by : Ntfs.sys ( Ntfs!TxfAccessCheck+9f )
Followup: MachineOwner