BSODS are a joy?~

MSINFO32
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.

The minidumps show memory management errors with a couple of other things - to include an error with the video card. I would expect a memory error with the Video RAM. The way to test this is to try another video card.

More info on STOP 0x116 errors: BSOD Index

Older drivers that should be updated (particularly the one from 2006):

Code:

GVTDrv64.sys Tue Sep 05 03:10:02 2006
AODDriver.sys Mon Oct 13 00:38:55 2008
000.fcl      Fri Sep 26 09:11:22 2008

There was also an error in NTFS.SYS - so I'd suggest the following:

CHKDSK /R
Run CHKDSK /R from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry.
Copy/paste the results into your next post.

A free, bootable Hard Drive diagnostic test: HD Diagnostic

Here's the summary of the last 11 memory dumps:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 11:07:22.669 2009 (GMT-5)
System Uptime: 0 days 0:09:15.700
BugCheck 1A, {41790, fffffa8000804810, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  des2svr.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec  6 14:24:15.562 2009 (GMT-5)
System Uptime: 0 days 0:28:22.482
BugCheck 1A, {41790, fffffa80007f8510, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  des2svr.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 15:14:08.310 2009 (GMT-5)
System Uptime: 0 days 0:13:53.341
BugCheck 1A, {41790, fffffa8000805a10, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  des2svr.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 10:57:13.449 2009 (GMT-5)
System Uptime: 0 days 0:25:24.479
BugCheck 1A, {41790, fffffa8000805a10, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  des2svr.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 14:59:22.365 2009 (GMT-5)
System Uptime: 0 days 0:30:32.396
BugCheck 1A, {41790, fffffa8000181ce0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WerFault.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 12:00:02.531 2009 (GMT-5)
System Uptime: 0 days 0:40:07.562
BugCheck 1A, {41790, fffffa8000780210, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33a98 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WerFault.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 13:00:00.443 2009 (GMT-5)
System Uptime: 0 days 0:58:59.474
BugCheck 1A, {41790, fffffa800018dd10, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  VSSVC.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 10:30:59.360 2009 (GMT-5)
System Uptime: 0 days 0:10:13.390
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
BugCheck 116, {fffffa8003e40010, fffff8800495a220, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+e7220 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 13:31:26.893 2009 (GMT-5)
System Uptime: 0 days 0:30:35.924
BugCheck 50, {ffffba80048512c4, 0, fffff8800121d28f, 7}
Probably caused by : Ntfs.sys ( Ntfs!NtfsReleaseFileForCcFlush+2b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  VSSVC.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 14:27:48.977 2009 (GMT-5)
System Uptime: 0 days 0:55:29.008
BugCheck 1A, {41790, fffffa80001f9ce0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  nvSCPAPISvr.ex
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 15:52:13.988 2009 (GMT-5)
System Uptime: 0 days 0:37:14.019
BugCheck 1A, {41790, fffffa8000799a10, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  des2svr.exe

Still undetermined. Also, I hesitate to suggest new hardware because of the financial burden it imposes on the user. If I do suggest hardware, I suggest borrowing functional hardware, or purchasing hardware that you can return for a full refund (in case I'm wrong).

Additionally, I suggest that replacing parts should come after ALL software troubleshooting. Software troubleshooting is usually free (except for your time).

Replacing the video card is a limited test that stands a good chance of resolving the problems - if the error is a video error. This is because it's not just the card that's replaced - the connection to the mobo is redone, the drivers need to accommodate the new card, the connection to the monitor is redone also, etc.

Finally, since the card is only a month old - you've got nothing to lose by replacing it under warranty (RMA). Contact the seller of the card and let them know that it's probably defective.

If you can get another card for free - should you take it? Absolutely!
Should you pay for another card - not at this point.

back with BSODS