Multiple BSOD New Computer Windows 7 64Bit

There is a very good chance that was the cause or one of the causes. Run your system and see how it does.

Be sure to post back in two or three days and give us an update. If you have another BSOD, upload it ASAP. I hope your troubles are behind you. :)

By the way, I see you are a fellow Floridian.

Please remove Norton/Symantec antivirus. Stop code is 50, which suggest antivirus is potential cause.
Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support
If you need an alternative AV that is BSODs free, try Microsoft security essential
http://www.microsoft.com/security_essentials <---MSE

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$DI01.746\080110-16068-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e51000 PsLoadedModuleList = 0xfffff800`0308ee50
Debug session time: Sun Aug  1 18:48:56.697 2010 (UTC + 7:00)
System Uptime: 0 days 0:00:29.821
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8800f331960, 0, fffff880047065a2, 2}


Could not read faulting driver name
Probably caused by : HTTP.sys ( HTTP!UlCopyRequestToBuffer+486 )

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

Also, update your networking driver if you can

Let us know if you need help

Tuan