bsod

[onestack]

Minidump.rar

included my minidumps as well as cbs report for scannow

have been having a hell of a time trying to track down an elusive blue screen.

this is a fresh install after having random blue screens for the last year+

thanks for any insight you all can give me.

o yeah i have run memtest86 on all my individual sticks of ram as well as run it collectively in 12 hour shifts untill all sticks were tested results were all zero erros.

from here im not sure where to go in the diagnosis process.

 

[ttran]

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:

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).

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:

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...
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Regard,

Tuan

 

[onestack]

thank you much for your quick reply have updated the drivers to newest versions available and am going to run the /scannow today while im at school will post results when return this evening