Kung.... I've the never ending blues

[Voyager]

Kung, if you are around and don't mind helping me out, I'm willing to give anything a try to fix this computer of mine.

You may recall that I have talked with you before about the blue screen of death.
You suggested to uninstall the last installed hardware which was my external DVD. I did do that and I haven't reinstalled it, leaving it off my computer.

Still having problems I up dated the video card and sound card. I was told by another tech that the video card is usually the problem, so after updating I was excited and thinking it would be all over. WRONG!

Here's the info from my last Blue screen of Death....

*** Stop 0x0000000D1 (0x06530478, 0x0000002,
0x00000001, 0xF68B7286)
*** USBPort.sys - Address F68B7286 base at F68AF000,
Date stamp 41107d62


I'm beyond frustrated with this computer.

I have XP Pro service pack 2


If you can help me out great.. if it's a lot of trouble just let me know and I will try to save up and take it to a shop.

Voyager

[Kung]

Well, with these 0x0000000D1 errors, they're 'usually' attributable to hardware problems, and considering you'd just removed/replaced the DVD burner @ the time, it was the obvious suspect.

However, that's obviously not the case here.

I would take your case side off, make sure that there is *NO* dust in there, clean the vanes of the heatsink for the processor, etc. If that still doesn't work, if you have more than one memory stick in there, take the other one out, and leave it out for a while to see if you can replicate the problem (or not). Then repeat with the other stick.

Let us know if that has any effect.

[zzdust]

Actually D1 indicates a driver issue. It means that a function in usbport.sys is being called at "high IRQL" (DPC level most likely, in response to an incoming USB packet) - most likely offender is another driver in stack for the USB port.

What USB device do you tend to be using when this happens?

[Voyager]

Hi Nethog,

Going to re-write my reply...
I had a camera and my printer plugged into the usb ports. Both were not being used when I got my blue screen of death.
I just unplugged my camera.

[Kung]

Actually D1 indicates a driver issue. It means that a function in usbport.sys is being called at "high IRQL" (DPC level most likely, in response to an incoming USB packet) - most likely offender is another driver in stack for the USB port.

What USB device do you tend to be using when this happens?

Really? I've had this before and it's *NEVER* been a driver issue. Or rather, I've replaced any and all drivers that could even remotely be related; and to no avail. Only removing the offending device worked.

Then again, you sort of know the OS better than I do :heh so I will defer to your wisdom.

I'd meant to say that they were usually attributable to hardware or driver problems (not software) but leaned towards hardware.....but obviously I was wrong on this one.

[zzdust]

Yeah, I know this bugcheck really well... really really well...

[Voyager]

Nethog,

Bugcheck???

[zzdust]

Bugcheck is the official name for the BSOD. On unix systems, it's called a "panic". It means that the kernel has identified a bug that it cannot continue from. It is better to crash the machine than corrupt data.

The first number identifies what the issue is, and the following numbers give more context.

[Voyager]

What can I do about it? Should I take it to a shop?

[zzdust]

Well, per previous question, is there a specific USB device you're using when the bugcheck occurs?

E.g. video camera, thumb drive, external CD Rom, etc.