Hi and Welcome to SF!!!
It's good that you have checked your RAM with memtestx86 and come with no error. Let's get to driver issue because I can see some common issue here:
First of all, these drivers are old and needed to be updated:
Code:
ASACPI ASACPI.sys Sun Mar 27 21:30:36 2005 (42476C4C)
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
Code:
ctgame ctgame.sys Tue Apr 06 19:42:49 2004 (40734E89)
Creative Game Port Enumerator
Please update it as soon as possible Creative Worldwide Support
BUGCHECK SUMMARY:
Code:
BugCheck 4E, {99, a5a82, 0, a6682}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner
---------
BugCheck A, {fffffa8024873270, 2, 0, fffff80002a94fd1}
Probably caused by : tcpip.sys ( tcpip!WfpAlepFindRemoteEndpoint+33 )
Followup: MachineOwner
---------
BugCheck A, {fffff68000120600, 0, 0, fffff80002acf305}
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+266 )
Followup: MachineOwner
---------
BugCheck 1A, {403, fffff6800002b720, fad000012eae6867, fffff6fd40027730}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29922 )
Followup: MachineOwner
---------
Can you please run sfc /scannow one more time and let me know the report at the end of the scan, whether it said it didn't find any violation or it say it repair etc...
SFC /SCANNOW Command - System File Checker
Regard,
Tuan
Quote