BSOD issues, looking for some help or direction please

[Arcangell73]

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:

[FONT=Segoe UI, Arial]System Information (local) [/FONT]
[FONT=Segoe UI, Arial]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


[/FONT]
[FONT=Segoe UI, Arial] Crash Dump Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]usbport.sys[/FONT] (USBPORT+0x2DF3E)
Bugcheck code: 0xFE (0x5, 0xFFFFFA800E84E1A0, 0x10024396, 0xFFFFFA800F194C48)
Error: [FONT=Segoe UI, Arial]BUGCODE_USB_DRIVER[/FONT]
file path: C:\Windows\system32\drivers\usbport.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]usbport.sys[/FONT] (USBPORT+0x2DF3E)
Bugcheck code: 0xFE (0x5, 0xFFFFFA800E7491A0, 0x10024396, 0xFFFFFA800F11CC48)
Error: [FONT=Segoe UI, Arial]BUGCODE_USB_DRIVER[/FONT]
file path: C:\Windows\system32\drivers\usbport.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial] Conclusion [/FONT]
[FONT=Segoe UI, Arial]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
[/FONT]

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

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7FD00)
Bugcheck code: 0xFE (0x5, 0xFFFFFA800E8B61A0, 0x10024396, 0xFFFFFA800F2BAC48)
Error: [FONT=Segoe UI, Arial]BUGCODE_USB_DRIVER[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.




[/FONT]

 

[koolkat77]

Welcome.

Please go through this: http://www.sevenforums.com/crash-lockup-debug-how/175994-solution-fo-bugcode_usb_driver-bsod.html

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: http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html

 

[Arcangell73]

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 !

 

[koolkat77]

Look forward to your results.

 

[Arcangell73]

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?

 

[Arcangell73]

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

[FONT=Segoe UI, Arial]Crash Dump Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7FCD0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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?
[/FONT]

 

[koolkat77]

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

 

[Arcangell73]

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!

 

[koolkat77]

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

 

[Arcangell73]

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.

 

[koolkat77]

Grab all:: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[Arcangell73]

Well, it ran with no BSOD for just over a day, then tonight it just crashed again...Whocrashed info:

[FONT=Segoe UI, Arial]On Tue 1/29/2013 12:01:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012813-35786-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7EFC0)
Bugcheck code: 0xFE (0x5, 0xFFFFFA800ECAB1A0, 0x10024396, 0xFFFFFA800F262C48)
Error: [FONT=Segoe UI, Arial]BUGCODE_USB_DRIVER[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


Also attached is the SF Diag tool results....
[/FONT]

 

[koolkat77]

There's no dump file.

 

[Arcangell73]

I hope that one worked, lots of BSOD's tonight.

 

[koolkat77]

What external devices do you have plugged in to your system?

 

[Arcangell73]

I have a TP-Link wireless adapter, my g35 headset, my microsoft keyboard, and logitech wireless mouse. My brother seems to think its the video card overheating, does this sound like it could be it? I took the side off the tower and the card felt warm but not hot and the fan was running normally. Im at my wits end, I really just wanna smash the thing into the ground to get my frustration out! Anyway, thank you like always Koolkat, glad to have someone to discuss this issue with.

 

[koolkat77]

Can you unplug the devices one by one and see how long you go without a BSOD?

Upload a screenshot of your hard disk using CrystalDiskInfo:

• CrystalDiskInfo - Software - Crystal Dew World
• Speccy - System Information - Free Download
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If Speccy does not show your GPU information, use GPU-z:

• GPU-Z Video card GPU Information Utility

 

[Arcangell73]

Sorry about the lengthy time between posts Koolkat, but I've gone ahead and re installed win7 after reformatting my HD and still having the issues. I'm going to need to re download those programs again to get you the information, but was just giving you a heads up that I have returned (unfortunately).

 

[Arcangell73]

Also wanted to add that someone had mentioned it could be a RAM issue so I've gone ahead and removed 3 of my 4 sticks of ram to test them 1 at a time, will let you know the results of this test as well.

 

[koolkat77]

I see, keep us posted.