On Thu, 15 Mar 2007 12:22:55 -0400, "Mr.E Solved!"
<Iamsingle DeleteThis @askme.out> wrote:
>Recovering from STR and STD (sleep and hibernation modes) to an error
>free operating state is wonderful in theory and unlikely in practice.
>
>That your video drivers, or portions of it are responsible is no surprise.
It is the first time that I have tried using STR or STD, but there are
the odd glitches with it!
>
>If you would like to see which sys files and other files are being
>loaded during boot, either use a utility such as autoruns (google) or
>boot with the bootlog switch in your boot.ini file and examine ntbtlog.txt
Will try Googling for the utility you mentioned (Autoruns), it will be
interesting to see what exactly is loading during boot.
>
>You will likely find nvport in your windows\system32\drivers directory,
>but merely deleting it might not delete all instances and all references
>to it.
When I uninstalled the nVidia Purevideo decoder 'nvport.sys' was
automatically removed from the windows\system32\drivers directory.
It would appear that there is an attempt to try and load a
non-existent driver (nvport.sys) which is causing the problem, I have
noticed that in the registry there are two folders one is 'nvport' the
other is 'Legacy_nvport'.
Have posted a question on the nVidia website asking if it is safe to
delete these references to 'nvport' from the registry.
Thanks for the suggestions.
Cheers - Agzee
>> Stay informed about: nVidia PureVideo decoder