New
#11
Well, it ran with no BSOD for just over a day, then tonight it just crashed again...Whocrashed info:
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: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xFE (0x5, 0xFFFFFA800ECAB1A0, 0x10024396, 0xFFFFFA800F262C48)
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.
Also attached is the SF Diag tool results....
I hope that one worked, lots of BSOD's tonight.
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.
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
- Screenshots and Files - Upload and Post in Seven Forums
If Speccy does not show your GPU information, use GPU-z:
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).
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.