Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Noh Luciola
|
Posted - 2010.07.15 06:41:00 -
[1]
So I've been troubleshooting this issue for almost two weeks but haven't come up with very much - I've google'd for info as well but with similar results.
My problem in a nutshell is that at specific moments during flight all of my USB devices will die. Kaput. PS/2 devices stay connected and the game (usually) continues running (I've been using an old PS/2 key/mouse as a backup for when this problem occurs).
This issue typically occurs when I warp or undock from a station.
XP registers the following error type when this occurs:
Event Type:Error Event Source:Disk Event Category:None Event ID:11 Date:7/14/2010 Time:11:24:43 PM User:N/A Computer:HAMMERHEAD Description: The driver detected a controller error on \Device\Harddisk1\D.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 0f 00 68 00 01 00 b6 00 ..h...¦. 0008: 00 00 00 00 0b 00 04 c0 .......+ 0010: 03 01 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 8e 03 22 00 00 00 00 00 Ä."..... 0030: ff ff ff ff 06 00 00 00 .... 0038: 40 00 00 00 00 00 00 00 @....... 0040: ff 20 06 12 08 01 30 10 ....0. 0048: 00 00 00 00 14 00 00 00 ........ 0050: 00 00 00 00 38 9e 62 89 ....8Pbë 0058: 00 00 00 00 00 37 60 89 .....7`ë 0060: 00 00 00 00 00 00 00 00 ........ 0068: 00 00 00 00 00 00 00 00 ........ 0070: 00 00 00 00 00 00 00 00 ........ 0078: 00 00 00 00 00 00 00 00 ........ 0080: 00 00 00 00 00 00 00 00 ........ 0088: 00 00 00 00 00 00 00 00 ........
The drive is new - less than 6 months old and I have run a slew of diagnostic tests trying to see if it has any kind of problems... but again, nil results.
This issue seems to be occurring only with Eve (other games such as L4D and Dead Space run fine) and only since the last patch. I've tried reinstalling all of the motherboard and USB device drivers - additionally I've repaired and reinstalled Eve several times now.
I'm running a Microsoft Natural Ergonomic Keyboard 4000 & Microsoft Trackball Explorer Mouse... however I've tested it with other USB interface devices with the same results.
My other hardware specs are as follows:
Gigabyte GA-MA790FXT-UD5P Asus Radeon 4870 / Antec 800W PSU AMD Phenom X3 720 / 4GB Corsair DDR3 2TB Hitachi SATA Drive / Windows XP PRO SP3
I've also had other devices connected but I've tested with everything disconnected except for the USB key/mouse with the same failure.
Has anyone here run into a similar issue - any advice as to a possible remedy or perhaps troubleshooting suggestions that I may not have thought of?
|
Noh Luciola
|
Posted - 2010.07.15 06:54:00 -
[2]
I forgot to add - at times the USB failure is partial, sometimes just the mouse or keyboard will fail.
Also, I am running a dual monitor setup with Eve running in windowed mode in the primary and my desktop on the secondary (in fact doing this as I write this very post).
|
thatbloke
Gallente
|
Posted - 2010.07.15 10:38:00 -
[3]
How many/What USB devices do you have connected at the same time?
Do you have enough or are you perhaps right on the limit of the USB bandwidth that your motherboard has to offer?
If you bring up your device manager, then expand the USB controllers tree, and select properties on the Host Controllers and Root Hubs, one of the tabs it displays should tell you how much power and bandwidth the various devices you have connected to each hub are using - it's possible maybe that something is spiking and trying to draw too much power at one time, which I know can cause windows to kill that whole USB hub...
The funny thing about this sentence is that by the time you've finished reading it, it's too late for you to realise it doesn't say anything. |
Elysarian
Minmatar dudetruck corp
|
Posted - 2010.07.15 18:03:00 -
[4]
We all know what a graphics card killer Eve is...
This issue *could* be related (bear with me here!) - is it possible that Eve's demands on your PSU (via your gfx card(s) of course) could be causing a "sag" on the 5v line? - before anyone points out that gfx cards use the 12v rail for most of their power, I am aware of this but some cheapo PSU's just put a 5v regulator on the 12v rail to supply the 5v. ===================================== It smells of spoon! ===================================== |
Noh Luciola
|
Posted - 2010.07.16 17:45:00 -
[5]
Edited by: Noh Luciola on 16/07/2010 17:55:06
Originally by: thatbloke How many/What USB devices do you have connected at the same time?
Do you have enough or are you perhaps right on the limit of the USB bandwidth that your motherboard has to offer?
If you bring up your device manager, then expand the USB controllers tree, and select properties on the Host Controllers and Root Hubs, one of the tabs it displays should tell you how much power and bandwidth the various devices you have connected to each hub are using - it's possible maybe that something is spiking and trying to draw too much power at one time, which I know can cause windows to kill that whole USB hub...
I checked this out last night - I've got a single device pulling ~39% of my USB bandwidth and the rest are idling @ 10%... does this sound normal?
I've run into this issue just running the keyboard/mouse so I'm hoping this isn't the case - I'd imagine that the USB bus on my motherboard should at least be able to hand these devices. Additionally, I've tried swapping out both the key/mouse to no avail.
Originally by: Elysarian We all know what a graphics card killer Eve is...
This issue *could* be related (bear with me here!) - is it possible that Eve's demands on your PSU (via your gfx card(s) of course) could be causing a "sag" on the 5v line? - before anyone points out that gfx cards use the 12v rail for most of their power, I am aware of this but some cheapo PSU's just put a 5v regulator on the 12v rail to supply the 5v.
I was wondering this myself... I do have an 800W PSU running but I have to check the brand, I think it was one I bought during the Circuit City closeout awhile back, and the problem seems to occur during the "loading" phase for gfx... namely during undock and warp.
Then again, all of this was working stellar before v1.0.3 and, from the patch notes, it doesn't seem like there way anything terribly gfx intensive added (unlikely regardless since it's just maintenance patch).
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |