Getting random BSOD, Windows 7 Ultimate (dumps inside)

aq5i1c39.sys is listed in the stack in one of the BSOD's. I can't find anything about it with a Google search - so that makes it suspicious to me. Please post over in the Security forums to make sure that you're not infected: System Security - Windows 7 Forums

Additionally, the build for this system is:

Built by: 7600.16397.amd64fre.win7_gdr_staging.090720-1852

The dump files don't have the correct symbols associated with them (lot's of errors trying to access the symbols when running the debugger).
This is not the normal build info for the RTM - so the question is where did the build come from?
If it's from a torrent, then I'd have to suggest getting a hold of a legitimate copy.

Several of the BSOD's point to video issues - so I'd suggest updating your video drivers.

I'd also suggest updating this older driver:

AsIO.sys Mon Dec 17 04:11:49 2007

Here's the summary of the dump files:

Code:

*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Tue Nov 24 13:56:38.457 2009 (GMT-5)
System Uptime: 0 days 0:39:18.924
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck D1, {e1c, 2, 0, fffff880049409d0}
*** 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+c59d0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Tue Nov 24 15:05:54.076 2009 (GMT-5)
System Uptime: 0 days 1:07:49.684
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck A, {ffffffffffffffff, 0, 0, fffff80002b0d848}
Probably caused by : ntoskrnl.exe ( nt+b8848 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16397.amd64fre.win7_gdr_staging.090720-1852
Debug session time: Wed Nov 25 18:09:56.721 2009 (GMT-5)
System Uptime: 0 days 0:22:51.329
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck D1, {1, 2, 1, fffff88003d755d8}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcCompletedPacket+1b4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16397.amd64fre.win7_gdr_staging.090720-1852
Debug session time: Wed Nov 25 17:44:49.501 2009 (GMT-5)
System Uptime: 0 days 0:07:55.108
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck D1, {ffc23340, 2, 1, fffff88003c65f3f}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+37b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16397.amd64fre.win7_gdr_staging.090720-1852
Debug session time: Wed Nov 25 17:35:53.850 2009 (GMT-5)
System Uptime: 0 days 0:38:59.458
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 3B, {c000001d, fffff80002dbc242, fffff88008824fb0, 0}
Probably caused by : ntoskrnl.exe ( nt+369242 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

You can run a free memory test: Memory Diagnostics

Because of the unknown stuff that's showing up - and the symbol issues - I'd have to suggest breaking out the recovery disks and reinstalling Windows with a clean install.

Where did you get the system from? What's the make and model of the system? Where'd you get the Win7 disk from?