bsod multiple times daily

SET MINIDUMPS:
Windows 7:
Go to Start and type in "sysdm.cpl" (without the quotes) 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 (64 kB)" in the dropdown box
Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

Is that what you asked for?

socrgy, post back tomorrow and update us. If you are still running without crashes, we will ask the mods to mark this thread as solved.

And by the way, thank you for your service!

It blamed your graphic card with little mentioning to your memory with exception code fffffc0000005, which is memory access violation.

I haven't turned back to previous pages to see if any one ever told you to re-install the graphic card driver yet, but it looks like the graphic card is having problem. The best way to check it is to try if you can borrow another graphic card adapter and try on yours system.

If you want to try re-install graphic card driver again. When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

Check you RAM again if you wants.
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.

BUGCHECK SUMMARY:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.700\081410-12776-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c59000 PsLoadedModuleList = 0xfffff800`02e96e50
Debug session time: Sat Aug 14 11:07:33.097 2010 (UTC + 7:00)
System Uptime: 0 days 0:13:04.798
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880043efd38, fffff88002137858, fffff880021370c0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+1c )

Followup: MachineOwner
---------

Regard,

Tuan

ok. i downloaded that program, removed all drivers and re downloaded and installed the new drivers.

still having bsods, ill attach all the latest.

bsods only while gaming. playing free trial of WoW

i can start a new thread if it will help. i believe the original problem has been fixed. i'm looking into getting a new graphics card. possibly two since the new mobo i just ordered can handle it

Definitely the graphic card, Let's try different graphic card then Same stop code as the previous one with dxgmms1.sys (Directx) as well as your graphic card driver were blamed.

BUGCHECK SUMMARY:

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff88004578ce5, fffff880021306a8, fffff8800212ff10}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+19 )

Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff88004bef70e, fffff88006c9f7e0, 0}

Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+35e70e )

Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff80002cb8863, fffff8800824b0b0, 0}

Probably caused by : ntkrnlmp.exe ( nt!EtwpFindGuidEntryByGuid+73 )

Followup: MachineOwner
---------
BugCheck C2, {b, fffffa80085f9070, c, fffffa80085f9e00}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264 )

Followup: MachineOwner
---------
BugCheck 1E, {0, 0, 0, 0}

Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d )

Followup: MachineOwner
---------