WHAT IS GOING ON HERE?!?!

[wayliff]

***STOP:0x000000D1 (0x00001018, 0x00000002, 0x00000000, 0xEB6BABA4)

***Address EB6BABA4 base at EB6B8000 DatesetupStamp 3cc7ab4a - uhcd.sys

Beginning dump of physical memory

HELP APPRECIATED THANKS!!

 

[Sunner]

Originally posted by: wayliff
***STOP:0x000000D1 (0x00001018, 0x00000002, 0x00000000, 0xEB6BABA4)

***Address EB6BABA4 base at EB6B8000 DatesetupStamp 3cc7ab4a - uhcd.sys

Beginning dump of physical memory

HELP APPRECIATED THANKS!!

Uhh, info please?

Not to sound rude, but your post is about as informative as walking into a car repair shop and screaming "My car doesn't work!!!".

 

[larciel]

win2k or xp BSOD?

 

[crisp82]

XP BSOD if memory serves. On a restart is when I suffered most, while loading the GUI. Normally was ok after a reboot, but was caused by my overclocking.

 

[Booter]

***STOP:0x000000D1 (0x00001018, 0x00000002, 0x00000000, 0xEB6BABA4)

***Address EB6BABA4 base at EB6B8000 DatesetupStamp 3cc7ab4a - uhcd.sys

Beginning dump of physical memory

HELP APPRECIATED THANKS!!

reinstall your USB drivers.

 

[ProviaFan]

That appears to be your USB driver that is causing the problem. Try reinstalling them.

 

[Booter]

jliechty, thats what i posted

 

[Need4Speed]

Originally posted by: Booter
jliechty, thats what i posted

well then i think he should reinstall the usb drivers

 

[Yomicron]

you may want to try re-installing your USB drivers

 

[Booter]

..hehe thats right

 

[wayliff]

THANKS GUYS...
it is happening in Win2k SP3...and i do not have more info...it is just the windows scary blue screen with that info...

 

[Smilin]

Go to microsoft, find the knowledge base in technet and lookup these articles:

Q242062
Q306788
Q246755

I think someone also mentioned reinstalling your usb drivers...spose you could do that too