Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Novice
2,292 Views

USB device connect/disconnect

I have USB device connect/disconnect problems for nearly 1 year on my home built Intel system. I have been living with the problem but it does appear to be growing worse as time goes on. Where once it would bing-bong at random times it now does-so similarly but in fits of 40 per hour, particularly while gaming, and it is not cured by a reboot, rather the dc's will just carry-on immediately following the windows XP welcome screen.

PnPmon.exe monitoring USB devices observes an endless string of these events, the following representing a few minutes and carrying on like this for the duration of an hour or so, after which the problem disappears for anywhere from a few minutes to a few weeks.

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEREMOVECOMPLETE

DBT_DEVTYP_DEVICEINTERFACE

Category: 'HIDs'

Name: \\?\HID# Vid_2185&Pid_0102# 7&1d8c6c7a&0&0000# {4d1e55b2-f16f-11cf-88cb-001111000030}

-----------------------------------------------

** DBT_DEVICEREMOVECOMPLETE

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_2185&Pid_0102# 6&bc0d3f6&0&2# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEARRIVAL

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_2185&Pid_0102# 6&bc0d3f6&0&2# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEARRIVAL

DBT_DEVTYP_DEVICEINTERFACE

Category: 'HIDs'

Name: \\?\HID# Vid_2185&Pid_0102# 7&1d8c6c7a&0&0000# {4d1e55b2-f16f-11cf-88cb-001111000030}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEREMOVECOMPLETE

DBT_DEVTYP_DEVICEINTERFACE

Category: 'HIDs'

Name: \\?\HID# Vid_04d9&Pid_1702&MI_01&Col02# 8&20ba2fce&0&0001# {4d1e55b2-f16f-11cf-88cb-001111000030}

-----------------------------------------------

** DBT_DEVICEREMOVECOMPLETE

DBT_DEVTYP_DEVICEINTERFACE

Category: 'HIDs'

Name: \\?\HID# Vid_04d9&Pid_1702&MI_01&Col01# 8&20ba2fce&0&0000# {4d1e55b2-f16f-11cf-88cb-001111000030}

-----------------------------------------------

** DBT_DEVICEREMOVECOMPLETE

DBT_DEVTYP_DEVICEINTERFACE

Category: 'Keyboards'

Name: \\?\HID# Vid_04d9&Pid_1702&MI_00# 8&387dbc13&0&0000# {884b96c3-56ef-11d1-bc8c-00a0c91405dd}

-----------------------------------------------

** DBT_DEVICEREMOVECOMPLETE

DBT_DEVTYP_DEVICEINTERFACE

Category: 'HIDs'

Name: \\?\HID# Vid_04d9&Pid_1702&MI_00# 8&387dbc13&0&0000# {4d1e55b2-f16f-11cf-88cb-001111000030}

-----------------------------------------------

** DBT_DEVICEREMOVECOMPLETE

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_04d9&Pid_1702# 6&bc0d3f6&0&3# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEREMOVECOMPLETE

DBT_DEVTYP_VOLUME

Applies to media

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

It rotates through my USB devices favoring no particular item in the broad outlook but rather picking on one repeatedly only to randomly switch to another when it gets bored. The two prime suspects listed above are my game controller and my USB keyboard, it lacks a functioning third choice as my Video capture is quite typically not in use and my USB mouse plugs in through the ps2 port and remains unaffected.

During one recent mass of disconnects the windows XP 'safely remove hardware' icon which usually lives on the far right of my task bar shifted advancing to the left, ahead of recently opened program icons like mirc, as though the remove icon had just closed and reopened after those other icons. I mention this as this icon is used typically in relation to removing USB drives.

99% of the time the disconnected devices reconnect within 5-20 seconds with only once needing a reboot to reconnect the keyboard. Most disconnects are simply a loss of function while remaining powered even though there only source of power is the usb port itself.

Early on it was as likely to suffer connect/disconnect issues while idling quietly in the middle of the night as it was in the heat of battle or while typing furiously but now it seems to do so mostly while being used

My USB disconnect notes: During recycle bin empty, big fan on and off, fan off again 1 day later, after turning on hottub, completion of brief download or fan off, definitely big fan off. opened a cannot render video file now named USB_Burps.mpg in Programs - did not repeat when done again, no other power usage spikes at the time, Turning on heat pad while top fan ran from overnight, 1 hour later sitting quietyl doing nothing at all. and again 5 minutes later still doing little jsut checking emails, and one horu later while emptying recycle bin which made no sound, just the dc ding-dong which did not trigger when emptied again a minute later which did use the recycle bin emptying sound. usb dc many times during lightning storm, once at monitor power on.

I have power my system on two separate circuits. This is a new house with professional wiring of the highest quality using 10 amp breakers, I have no electrical issues, no high draw items that run automatically.

This computer is all box new, otherwise functioning very well, bought in 2013 from amazon and newegg (only the video card was used and reshrink wrapped to be sold as new by not-so-newegg)

Windows XProsp3ntfx4

Intel i3-3225 Processor HD4000

Intel DH61CRB3 Motherboard - Drivers: Bios - BEH6110H.86A.0118.EB, Chipset - INF_allOS_9.4.0.102, MEI_allOS_8.1.0.1248_1.5M_PV <--(Latests as of 2013-10-20) & AUD_XP_5.10.0.6710_PV, GFX_XP32_6.14.10.5437 with HD4000 disabled and 1024MB RAM alloca...

Tags (1)
0 Kudos
17 Replies
Highlighted
Valued Contributor III
39 Views

Re: USB device connect/disconnect

At this point you should check if this issue would be software or hardware related.

So, have you tried using a separate partition or hard drive to test another install of Microsoft* Windows* XP? Or tested using Microsoft* Windows* 7 on it? (Keep in mind that this motherboard is not validated for XP so unintended issues may happen)

Additionally, you could check if this related to a grounding issue testing the system out of the chassis, however it may not apply as this is so random, but this is just to cover all basics.

Highlighted
Novice
39 Views

Re: USB device connect/disconnect

I'll look into each one of the solutions you suggest, thanks for not holding back it could really be anything and probably the more simple the more likely. With this problem i live in a constant state of trying and waiting, one solution 'til it fails, then another, these ideas of yours and any to follow will join my list of wait and sees. 'Not XP validated' seems my favorite at the moment as i have long suspected, with no cause, that this is a voltage issue, that the board is shutting down, or being told to shut down the devices as a safety measure resulting from power usage fluctuation not common to the newer operating systems it was built for but well within the eXPerience at hand. how does the motherboard decide to disconnect? is this an OS or bios decision? Who's pulling the trigger?

0 Kudos
Highlighted
Valued Contributor III
39 Views

Re: USB device connect/disconnect

In this case it would be hard to tell which could be the reason on this (software/hardware). So try the troubleshooting mentioned which would help to isolate this.

0 Kudos
Highlighted
Novice
39 Views

Re: USB device connect/disconnect

You were specifically instructed not to preach the party-line upgradism. win7 is not now or ever in this system's future, and by your own words a ground fault is highly unlikely. What we have here is bad bios software, and a manufacturer who misrepresented compatibility... yet again. First HD4000 was represented as running direct x 10+ on XP, a well known impossibility, now a usb bug that will not stop because your bios voltage tolerances are incompatible with XP despite you having XP specific drivers your tolerances are too finicky.

30% of the world's Desktops will be running windows XP, today Oct 30th 2013. http://en.wikipedia.org/wiki/Usage_share_of_operating_systems Usage share of operating systems - Wikipedia, the free encyclopedia Can you imagine representing yourself to only 70% of a potential market and being considered with kinder words. Fix your bios drivers to be tolerant to greater voltage fluctuation, and greater line resistance tolerances.

If any productive solutions occur to you I will look back in, but the simple fact is you've failed again Intel. Don't sell products you will not support 100% because you think you can bully people into upgrading past your lack of proper debugging.

XP Today, XP Tomorrow, XP Forever!!!

0 Kudos
Highlighted
Valued Contributor III
39 Views

Re: USB device connect/disconnect

Thank you for your feedback on this matter, we will forward it to the appropriate channel for future consideration.

0 Kudos
Highlighted
Novice
39 Views

Re: USB device connect/disconnect

Plugging into the motherboards USB ports has not solved the problem as I had hoped, but in doing so I am confronted with an old techies tale; is there a line length limit to USB cords? If so what might that be and why? Is this a matter of resistance? I was able to cure a fit of USB disconnects, 40+ per hour by reducing the line length from 10' + 6 feet to just 10. These are top notch cords almost as thick as a pencil. Alas my problem predates the 6 foot extension I recently added but i still ask, is a stock 10 foot USB cord too long? And why wouldn't my winxp Intel Blue Mountain II have ever once suffered this trouble, while using identical peripherals featuring the same 10 foot cords, which may cause this on my winxp DH61CR?

0 Kudos
Highlighted
Valued Contributor III
39 Views

Re: USB device connect/disconnect

We haven't test or validated with such long cables, which makes me wonder now, are you only seeing the issue when these cables are being used or this also happens when using normal USB cables directly connected to the motherboard?

0 Kudos
Highlighted
Novice
39 Views

Re: USB device connect/disconnect

Both my joysticks, one new one old are ten foot cables stock, my keyboard is 4 foot with a 3 foot extension. When i removed the 6 foot cable extensions from my joysticks the disconnects abruptly stopped; then later switched back to bing-bonging my keyboard which is at 7 feet total plugged into my motherboard directly, it had not dc'd my keyboard in months previously. as i write it is disconnecting my joystick once a minute even though it is on the stock cable but it is plugged into my motherboards stock ports. I just now moved that same joystick to my motherboards optional ports provided by my new Gino mainboard 4 port usb 2.0 to 9 pin and it resumed disconnecting that same joystick 3 minutes later, once per minute as though i were in the heat of battle not sitting idle while i am typing in wordpad.

It started disconnecting my keyboard yesterday immediately following an idle reboot, a reboot preceded by a black screen reboot, perhaps unrelated but occurs 1 out of 10 reboots or more, and is only cured by another reboot. My usb has disconnected 30 times while typing this, but was silent since yesterdays reboot/episode. It was silent through heavy cpu usage and hours of game time. It was silent through hours of typing and I am guessing will go silent again soon, until next time it chooses to bing-bong for no associable reason. I'm a programmer and tinkerer, i know how to debug problems... this thing is alive and throws tantrums for no specific reason and not associated with any outside occurrence. middle of day, dark of night, all day or not for a week.

This board was represented as fully supporting Windows XP.

0 Kudos
Highlighted
Valued Contributor III
39 Views

Re: USB device connect/disconnect

At this point I suggest you only test using the USB ports in the system, remove any other USB front panel or card to provide additional USB ports, no extensions and no hubs at all. If the problem persists you can try an install of a validated operating system and if the problem continues, check with your local support center to replace the motherboard.

For contact information please check at http://www.intel.com/support/9089.htm Contact Support

0 Kudos
Highlighted
Novice
39 Views

Re: USB device connect/disconnect

"At this point" of you doing absolutely everything except offering a recoded solution to your lousy USB voltage thresholds you mean. Further you would suggest I only use the board's stock ports.. always have until this week. I've removed all extensions, I have no hubs, the problem continued until it stopped entirely, mysteriously, and has remained absolutely silent for one week, following my reversion to a previous OS image with slightly older drivers that will absolutely be as big a problem at some totally random time in the future as they always were at some totally random time in the past. To which you advise: that I take your last board made that, fully supports Windows XP, and you cannot deny this board physically absolutely, fully supports Windows XP, was designed and built a decade beyond XP's inception specifically as an XP board, and update it to a newer OS for which its architecture is totally inadequate to run properly, because you've after the time of sale decide that you don't want to write software that supports it anymore, because it is a discontinued and probably short sighted piece of hardware that did not perform as economically well as it was thought it would.

The proper response you should have given me would have been tough s*** sucker.

So, you've ripped me off. Let's be clear about this one fact. You've sold me hardware for which you are willing to say it supports XP but not physically willing to support it with proper software, to which I might say... YET AGAIN. Because the fact is you did this same thing with my Windows XP running HD4000, all fully supported mind you, with words, just not software. To which I had to spend another $150 dollars on a new video card that shocker among shockers completely supports windows XP even here at the cusp of 2014 nVidia is still writing for XP, like any good company that stands by what it says it does.

You owe me a refund, you've sold me an $90 dollar board that does not behave well, and a $150 chip with HD4crap that would not stop crashing when confronted with anything complex that ultimately cost me more than the whole chip to bypass. Perhaps you've something better suited to my absolutely XP needs, to exchange with, because as for my "local support center" I'm look at them right now. I bought this from amazon and newegg over one year ago and there are no warranties left for this long headache. Only my dwindling opinion of you. Leave me hanging and that will last forever despite my bulletproof P4 idling quietly through its 11th year, you've changed Intel. Any wonder you've lost such market share? You're not going to make it up by shorting me, I professionally write exposes about malfeasant companies.

Be better, support what you say you would or flat out give me my money back now, and I'll never trouble you again. Fail me, and our troubles have only just begun.

0 Kudos
Highlighted
Novice
39 Views

Re: USB device connect/disconnect

Another fit following a day of silence, this time only associated with static in my speakers i have long associated with sunspot activity as that same static was prevalent all summer but lately not at all, though the USB fits were.

This is half a day idle, followed by a 15 minute fit of disconnects, during which my keyboard and joystick trade disconnections evenly,all while i try to type quietly away at my keyboard exposing companies that shouldn't be trusted...

Monitoring 'USB Devices'...

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEREMOVECOMPLETE

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_04d9&Pid_1702# 6&2e29fa0f&0&2# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEREMOVECOMPLETE

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_2185&Pid_0102# 6&2e29fa0f&0&1# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEARRIVAL

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_2185&Pid_0102# 6&2e29fa0f&0&1# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEARRIVAL

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_04d9&Pid_1702# 6&2e29fa0f&0&2# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------...

0 Kudos
Highlighted
Novice
39 Views

Re: USB device connect/disconnect

This is my USB report, with one 5 foot USB mouse cord plugged into my good old serial port via adapter. My 10' stock gamepad cord plugged into the port next to it, and my 4 foot keyboard cord plugged into the port next to that, minus its previous 3 foot extension cord featured during that last fit. This batch of disonnects has mostly occurred during a keyboard disconnect that did not register on the pNpmon output below, and required a reboot to resolve. All stock ports, no extensions, no USB 2.0 mainboard attached, and keyboard reduced from seven feet to four feet stock; it now picks on the gamepad's stock cable.

Tonight's fits of USB disconnects are following static in speakers exactly, though not always, one brief crackle saw three disconnects in 3 seconds

** DBT_DEVNODES_CHANGED

-----------------------------------------------

Monitoring 'USB Devices'...

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEREMOVECOMPLETE

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_2185&Pid_0102# 6&bc0d3f6&0&2# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEARRIVAL

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_2185&Pid_0102# 6&bc0d3f6&0&2# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEREMOVECOMPLETE

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_2185&Pid_0102# 6&bc0d3f6&0&2# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEARRIVAL

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_2185&Pid_0102# 6&bc0d3f6&0&2# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEREMOVECOMPLETE

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_2185&Pid_0102# 6&bc0d3f6&0&2# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEARRIVAL

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_2185&Pid_0102# 6&bc0d3f6&0&2# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEREMOVECOMPLETE

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_2185&Pid_0102# 6&bc0d3f6&0&2# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEARRIVAL

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_2185&Pid_0102# 6&bc0d3f6&0&2# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEREMOVECOMPLETE

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_2185&Pid_0102# 6&bc0d3f6&0&2# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEARRIVAL

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_2185&Pid_0102# 6&bc0d3f6&0&2# {a5dcbf10-6530-11d2-901f-00c04fb951ed}

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVNODES_CHANGED

-----------------------------------------------

** DBT_DEVICEREMOVECOMPLETE

DBT_DEVTYP_DEVICEINTERFACE

Category: 'USB Devices'

Name: \\?\USB# Vid_2185&Pid_0102# 6&bc0d3f6&0&2# {a5dcbf10-6530-...

0 Kudos
Highlighted
Valued Contributor III
39 Views

Re: USB device connect/disconnect

When I mentioned the local support group I was referring to Intel's support in your region, not your place of purchase. In this case, you can check with the support center closest to you from the following site and check with them for the replacement options they may offer.

http://www.intel.com/support/9089.htm http://www.intel.com/support/9089.htm

The Microsoft* Windows* XP support for this unit has been marked "As-is" since the motherboard came out in the market, which means that in respect to features, function, debugging and usability with recently released Intel® Desktop Boards, Intel will no longer provide technical support for them.

Only previous generations of motherboards (Intel(R) 5 series chipset based) have been fully validated for Microsoft* Windows* XP.

0 Kudos
Highlighted
Novice
39 Views

Re: USB device connect/disconnect

See how easy that was to say, thank you. Your support is now As-Is, supporting my point, because at the time of sale and the point of sale it was not. It was clearly stated that this board supports XP, Vista, 7 & 8 by not only newegg where i purchased this board but no such disclaimer of as-is was available on the intel website as of Nov 2012. So what you owe me then is one 5 series chipset board to try out... leaving only this question, which board would you recommend to take fully advantage of the LGA1155 i3-3225 with HD4000 that this board was meant to reliably support? which board will provide equally spectacular performance as i get now (remember mine out performs by little bro's i7 win7 by 15%) but with the simple solution that for some strange reason you will no longer provide me, that of no annoying usb disconnects, and HD4000 that will not critically crash when suddenly confronted with complex objects from half a decade ago?

I hope you take the time to consider what a hassle this has not only been for yourselves but for me as well, this board represents a tremendous loss of my time and angst to me. Support what you said you would support at the time of sale and do not think you can revise your way out of such with post-sale terms such as "As-Is", we get it, your tired of writing proper drivers for XP and are dropping support. Which is why you owe me a brand new and freely shipped 5 series board of suitably impressive performance, to see my board returned once compatibility is confirmed, and loud mouthed and publicly embarrassing exposes into Intel's trustworthiness averted.... I publish in 67 languages 😉 ...PCIe 2.0x16, 240-ddr3 please.. recommend as many optimal matches as will give the best supported most reliable eXPerience, which is all i ever asked of you. Give me what I trusted you for Intel, 10 more years of productivity on the world's most compatible OS.

0 Kudos
Highlighted
Novice
39 Views

Re: USB device connect/disconnect

This page was referenced from the DH61CR page when i copied materials pertaining to my choice of the DH61CR motherboard and its completely supported compatibility with windows xp. Intel it appears you are refusing to support a product. Do I understand this correctly? Are you not as good as your word? You will fully validate this exact motherboard for windows XP or suitably compensate me for its troubles and my ever increasing time lost validating your incompetence on this matter.

This is the part i found most intersting from this verbatim page grab i personally took from your website on my date of purchase 11/15/2012 please Page Search: "When you see the "Designed for Windows XP" logo"

----------

Taken Nov 2012 from: http://www.intel.com/support/motherboards/desktop/sb/CS-028426.htm http://www.intel.com/support/motherboards/desktop/sb/CS-028426.htm

-

Desktop Boards

Troubleshooting operating system issues

General information

Operating system compatibility

Intel® Desktop Boards and Microsoft Windows* Hardware Quality Lab (WHQL)

Loading RAID driver at OS installation

Virtual floppy drive and CD related to Intel® Active Management Technology

137 GB drive size limitation

Setting up a dual boot system

Moving a hard drive to a new PC

Slipstreaming Windows* XP to include Service Pack 2

Memory limits in Windows

Troubleshooting

Operating system installation issues

Cannot load RAID/AHCI drivers on system without floppy connector

Stop error on PCI.SYS during Windows XP installation

Error "The BIOS in this system is not fully ACPI compliant"

Windows XP setup can't find hard drive (STOP: 0x0000007B)

Unable to install Windows* from certain PATA (IDE) DVD-ROM drives

Errors in device manager

Error on LPC interface controller

Error on unknown device

Error on PCI simple communications controller

Error on PCI serial port

Error on SM Bus controller

Processor information incorrect in device manager

Errors on Other Devices and Ports

Other operating system issues

Inaccessible boot device error after changing drive's SATA mode

Audio driver installation issue with Windows* XP 64-Bit edition

Shutdown problem after installing USB 2.0 drivers

Additional resources

General information

Operating system compatibility

Refer to Supported Operating Systems to find the driver/operating system support for your Intel® Desktop Board.

Note

Some desktop boards include features that are supported only under certain operating systems.

Windows Server* 2003 and Server 2008: Intel® Desktop Boards do not support either Windows Server 2003 or Server 2008. There are no drivers available for these operating systems.

Windows XP*: If your desktop board includes PCI Express* capability, you must use Windows XP with Service Pack 2, which includes support for PCI Express.

Windows XP 64-Bit Edition and Windows Vista*: Availability of Windows XP 64-Bit Edition or Windows Vista drivers may be limited for some Intel Desktop Boards. All board features (audio, video, LAN, etc.) may not be supported. Refer to the download page for your board.

Windows* 2000: Availability of Windows 2000 drivers may be limited for some Intel Desktop Boards. All board features (audio, video, LAN, etc.) may not be supported. Refer to the download page for your board.

LINUX*: All information and software contained herein is provided "AS IS" to Intel customers. Intel Corporation disclaims all express or implied warranties and liabilities for the use of this document, the software and the information contained herein, and assumes no responsibility for any errors which may appear in this document or the software, nor does Intel make a commitment to update the information or software contained herein. Intel reserves the right to make changes to this document or software at any time, without notice.

Intel® Desktop Boards and WHQL

Intel® Desktop Boards are submitted to Microsoft* Windows* Hardware Quality Lab (WHQL) for participation in the Motherboard Logo Program (MLP). Successful passage of the WHQL tests results in the "Designed for Windows" logo for qualifying boards. Click here to view MLP reports.

When you see the "Designed for Windows XP" logo, as you do with Intel Desktop Boards, it signifies that the board meets Microsoft's standard for hardware compatibility with Windows XP. For more information, you can visit the Microsoft Windows Catalog*. For the system integrator desiring a WHQL qualified system, starting with an Intel Desktop Board makes certifying your own system considerably easier.

Loading RAID driver at OS installation

Unless you are using Windows Vista, the Intel® Matrix Storage Manager driver must be loaded during operating system installation using the F6 installation method. This is required in order to install an operating system onto a hard drive or RAID volume when in RAID mode or onto a hard drive when in AHCI mode.

If using Microsoft Windows Vista, this is not required, as the operating system includes a driver for the AHCI and RAID controllers.

Refer to Chapter 5 of the Intel® Matrix Storage Manager User's Manual for complete instructions.

Virtual floppy Drive and CD related to Intel® Active Management Technology

With Intel® Desktop Boards that support Intel® Active Management Technology, if you set Wake on LAN from S5 to "Stay off", Windows* detects an Intel Virtual Floppy and an Intel Virtual CD. See images below.

These virtual devices also appear in the BIOS Boot menu, in the selection list for CD/DVD-ROM Drive Order.

The drives (related to the Intel® Active Management Technology) are inaccessible drives and are seen only at the first cold boot. If you restart Windows, they disappear. However, if you shutdown and restart the PC from a cold boot, they reappear.

The virtual devices appear because power to the Intel® AMT chip is provided if Wake on LAN is enabled. The system then believes that AMT is turned on, even if it is not. Therefore it is looking for AMT components and tries to enable them. If AMT is not enabled too, the components are not accessible.

To eliminate these virtual devices:

During boot, enter the BIOS setup by pressing F2.

In the Power menu, set Wake on LAN from S5 to Power On.

Press F10 to Save and Exit.

137 GB drive size limitation

The original Windows XP or 2000 CDs can only support a maximum hard drive capacity of 137 GB. To install a hard drive larger than 137 gigabytes on your computer you need Windows 2000 Service Pack 3 or later or Windows XP Service Pack 1 or later.

Setting up a dual boot system

You can install more than one operating system on your computer and choose which operating system you want to use every time you start your computer. This is often called a dual-boot or multiple-boot configuration.

Resources:

How to create a multiple-boot system in Windows XP*

Install more than one operating system (multiboot)*

Change the default operating system for startup (multiboot)*

Preparing For Dual Boot with Windows 2000 Professional*

Moving a hard drive to a new PC

If you have a PC with Windows XP configured just the way you want it and then upg...

0 Kudos
Highlighted
Novice
39 Views

Re: USB device connect/disconnect

Please tell me what part of "Designed for Windows XP" I misinterpreted as you clearly state to really be meaning "As-Is". I'd invite you to look down at this point. This is the deliciousness exposes are fueled by for your hands are quite red. You've rewritten the rules after the point of sale. The options i see on the table are to pay for my now two dozen hours lost on this and previous related HD4000 issues as well as replacement cost for all equipment i purchased that can not be used to run the eXPerience you designed it for and you might go so far as to steal my thunder by actually living up to your word, validating this motherboard for XP. it is as I said much earlier, quite clearly designed for XP, useless for all other purposes except expose fuel that without proper resolution will run perfectly by my own design.

0 Kudos
Highlighted
Novice
39 Views

Re: USB device connect/disconnect

Intel DH61CR Motherboard USB 2.0 device connect/disconnect on Windows 7 (as well as XP)

continued here; https://communities.intel.com/thread/47578 https://communities.intel.com/thread/47578

0 Kudos