View Single Post
Old 10-12-2008, 05:57 AM   #6 (permalink)
jcgriff2
Moderator, Microsoft Supp
 
jcgriff2's Avatar
 
Join Date: Sep 2007
Location: Palm Springs, California / Southern New Jersey
Posts: 10,062
OS: Windows 7, Vista Ultimate

My System

Re: Vista Unexpected Shutdown

Quote:
Originally Posted by generalle View Post
Hi,
Again thank u for ur kind help
I have found that the driver u pointed me to was GENIUS MOUSE NAVIGATOR 335 driver
I have uninstalled the whole iOLO centre(genius software) and instead of it I am now using standard driver chosen by windows
Is it possible that this was the problem ...that computer has restarting and showing unexpected error blue screen error because of this?
I have also downloaded regcure and cleaned registry several times

I hope it would work and the comp will be fine
...please lt me know what do u think about this

Kind regards
Hi. . .

Thank you for posting back.

Yes, I do believe that the driver gHidPnP.sys was the primary probable cause of the BSODs in question here as I found it in the stack text of the dump:
Code:
514f3 8039de88 gHidPnp+0x22c0
513f0 8497a200 0x852513f0
606f8 00000000 nt!IopfCompleteRequest+0x11d
513f0 925829d8 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6cb
85043 8487dbf8 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x4f5
7dbf8 8487d002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0x122
76478 00000000 USBPORT!USBPORT_Xdpc_Worker+0x274
7dbf8 00000000 sptd+0x11d54
00000 00000000 nt!KiRetireDpcList+0x147
00000 00000000 nt!KiDispatchInterrupt+0x45
7850f bb830000 0x91a13778
ghidpnp.sys was the primary cause and its sibling driver gmouusb.sys was the runner-up. They are kernel mode drivers (they run in the protected area of the Vista OS) and absolutely had the ability to cause the 0xd1 bugcheck, which in turn led to the blue screen and your system re-starting.

As far as registry cleaners go, I would advise that you do not use any of these products. They are an absolute waste of money (if you paid for one) and they could end up corrupting your registry. The BSODs nor the drivers that caused them had no ill effect on the registry whatsoever.

The items that a registry cleaner flags as "errors" are not errors at all - just entires in the registry that currently have no association to them. They hurt nothing, take up very little space and cause minimal time loss during boot-up (< 1 second, if that!) when the registry is assembled from files found on your hard drive. We are talking about a fraction of a second.

The few hundred items or maybe 1,000+ items out of the Vista NT Registry which can easily contain 500,000 entries represents 0.2% of the total.

To give you an example of how some of these "errors" occur - assume that you have no use for Microsoft Word. A registry scanner/cleaner would then pick up anything associated with MS Word and its files, whose file extensions are .doc (= Word 2003) or .docx (Word 2007) files. If you were to un-install Word, the file extension relations found in the registry would still exist, but have no program to open should a doc/x file be clicked on.

I suggest that you leave the registry alone. There may be a time in the future after the installation/un-installation of hundreds of programs where this becomes necessary, but then should only be done so under the instructions of someone familiar with registry cleaners.

I myself have never cleaned the registry of a Vista system, but have done so on several 3 & 4 year-old XP systems. If you do proceed with a registry cleaner - please make sure the registry is backed up first.

Again, thanks for posting back and letting me know your BSODs have now gone. Too often it is the case that I never learn the outcome.

Good Luck to you.

Regards. . .

jcgriff2

.
__________________
. . . . . . . .

B
Expecting a reply and waiting > 36 hours ? Send a PM to me containing a link to your thread
My availability will be limited through ~ December 1, 2009
jcgriff2 is offline   Reply With Quote