Windows 7: BSOD issues, looking for some help or direction please

Hello all, just a quick summary of what has happened. It started about a week ago (around Jan 10th or so) while playing Guild Wars 2. I built this system app. 2 1/2 years ago and it was running great up until recently. Below is a copy / paste of WhoCrashed:

System Information (local)
computer name: ARCANGELL-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) II X2 250 Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 17177890816 total
VM: 2147352576, free: 1993220096





Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 1/22/2013 10:34:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012213-34913-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2DF3E)
Bugcheck code: 0xFE (0x5, 0xFFFFFA800E84E1A0, 0x10024396, 0xFFFFFA800F194C48)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 1/22/2013 2:02:04 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012113-39546-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2DF3E)
Bugcheck code: 0xFE (0x5, 0xFFFFFA800E7491A0, 0x10024396, 0xFFFFFA800F11CC48)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



Conclusion
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.



Also, here is the requested SF Diagnostic tool zipped and attached to this post. I've searched online and seen this error occur many times with different answers / results, so I'm hoping maybe someone can give me some insight as to what can be causing this and how to fix it. Thank you for your time and help in advance.

Updated: System Specs have been updated using System Specs by:Brink


Edit: I downloaded new mouse driver (thought this was the USB issue) and got another BSOD with the following from WhoCrashed...

On Wed 1/23/2013 2:25:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012213-36114-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xFE (0x5, 0xFFFFFA800E8B61A0, 0x10024396, 0xFFFFFA800F2BAC48)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Welcome.

Please go through this: solution fo 'BUGCODE_USB_DRIVER' bsod

Your msinfo file is corrupt.

Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.

You might find this tutorial helpful as well: USB Driver - General Fix for Problems

Thank you Koolkat for the quick reply. Here is the zipped info you asked for. I am currently in the process of reading the links you sent me on how to fix this issue, though I'm kind of a rookie when it comes to this type of thing Hopefully I can figure it out or with your help, we can solve this issue, I've been going out of my mind for like a week now trying to figure it out, again thank you !

Look forward to your results.

Thank you Koolkat, I went ahead and ran the update to windows sp1 and so far so good. I'm keeping my fingers crossed and will marked this as solved for now. Thank you very much for the direction and attention to this matter. If I have further issues, I will be sure to start a new thread and let you know?

Ok so it lasted about an hour to an hour and a half then i got another BSOD with the following message from whocrashed.....

Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 1/25/2013 2:23:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012413-38797-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FCD0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



what do you think Koolkat?

You need to upload new dump files as you did earlier.

Ok so I tried to do the msinfo32 as earlier and got an error stating....
System Information is unable to open this .nfo file. The file might be corrupt or incompatible with this version of System Information.
So I clicked ok anyway and let it run (not sure if it worked or not) and followed the rest of the steps to zip it and attach it here. Hopefully it turned out ok and if not, just let me know and I'll try again. Thank you again for your time and continued support in this matter!

Yup it's corrupted
Can you upload the BSOD dump files

I used the SF diagnostic tool and came up with the attached zipped folder. If this is not the correct info, please advise as to what else you require, thank you Koolkat.