Kitz Forum
Computer Software => Windows => Topic started by: tuftedduck on January 30, 2009, 09:22:58 AM
-
I wonder if some kind soul can help a befuddled Kitizen.
Running WinXP SP2
I daily find an error report in the event viewer "viaagp1 failed to load"
I am questioning the "via" part of that.
I had to replace my motherboard some time ago.
The old mobo was an AsRock K7VM2 2.00 with on-board graphics S3 Graphics ProSavage DDR which I believe is a Via
Technology Product.
My new mobo is an Asrock AliveNF6G-VSTA with onboard graphics nVidia GeForce 6150SE
Back to the non-loading viaagp1. I find a driver named viaagp1.sys in c\:windows\system32\drivers and the properties of that
tell me it is a "via nt agp filter"
My question is whether that via item is a hangover from the old Via Technology days and can therefore be deleted (?) or is it
a required driver whatever graphic are installed.
I have googled, but the responses I read are above my head, so I would really appreciate some plain English advice.
Thank you.
-
Is there a entry for it it in the System Configuration Utility (type msconfig in the run box on the start menu to open it)
If there is you could try disabling it first (prior to removing it) as it certainly sounds like a leftover piece of software.
Don't forget to backup......................
-
Thanks OF.
Nothing for it in msconfig.
Am going now to set sysrestore point then delete that driver ( can recover from recycle bin if needs be), and I see a similarly titled entry in the registry so it is going too.
Will then reboot and see what happens.
Thanks again.
-
:fingers:
-
I'm back.
Well followed plan A above..........rebooted without problem, got the same error message again in event viewer and...... Windows has put the driver is back from whence it came.
That driver then appears to be a sympton not a cause .
Off under the bonnet again to some more tinkering.
-
The problem could also be that the information for that file is in the "boot.ini" and is therefore trying to load it at startup, so basically that entry also needs to be either removed or disabled in the boot.ini file file.
There is a section in the "System Configuration Utility" for checking or altering the boot.ini file.
-
Thanks, OF.
I had a look at boot.ini..................and I don't understand anything in there so will leave well alone.
I did do the "check all boot paths" thing and nothing untoward was shown.
Will leave alone for the rest of the day........getting tired tinkering now, have another go tomorrow. :)
-
Yes it can be confusing if not knowing what to do.
When we used to use DOS and Win95/95 I was forever into those type of files, but to be honest it's been that long ago I have forgotten exactly what to do, except:
You can open the boot.ini file with notepad, then if and when you find the line you want to disable just type:
REM followed by a space at the start of the line. (it's not case sensitive)
rem xxxxxxxxxxxxxxxxxxx
This will then disable that particular line/entry from the startup process without actually having to remove the text, very useful just for testing purposes.
It will possibly be a hidden file also, so you need to enable hidden files and folders.
*******************
edit
I just searched my PC and I do not appear to have a boot.ini file, although I do have a backup of one. "Strange"
-
There might be a left-over registry entry which is trying to load that driver, and it fails with the error message because there's no hardware to match it. If you're brave you could search the registry for any references to viaagp1.
-
Thank you again, OF, and roseway.
Will try these procedures tomorrow..........want to relax now, the old bones and brain have had enough for today. :)
-
Thank you again, OF, and roseway.
Will try these procedures tomorrow..........want to relax now, the old bones and brain have had enough for today. :)
Well at least the 'skip' option hasn't been mentioned .....................................yet :scare: :comp:
-
@ unkyUb.................... :D
Well, it won't go into a skip but I am going to clear all my files off it, uninstall Photoshop and then try and sell it or, failing that, give it to some worthy cause.
But, to do that must clear this wee problem.
-
If that is going to be the final out-come (to get rid of it) then you could always chose the easy option of re-installing windows.
Maybe not the quickest (but then again), but it should solve the problem.
-
Following on from the above, I went into regedit and looked for any relevant registry keys. I found one, deleted it but that made no difference.
I then did what I had never done before, downloaded and installed a registry cleaner.
I ran that, having told it to look for entries appertaining to viaagp1, viaagp, via technology, prosavage ddr and it found dozens of entries tucked away in the nether regions of the registry.
I shut my eyes, held my breath and told it to delete the lot ( making a backup before doing so.)
This am, the machine started just fine, and the error report in the event viewer did not occur..........woohoo :)
Not only that, yesterday I spent a lot of time using Photoshop which has been a recipe for a non-shutdown situation and.....................the machine shut down normally and correctly. :clap2:
It is possible then that the opening and closing errors were linked and, I say this quietly in case the machine hears me, that getting rid of all these old registry keys has sorted two problems in one. Time will tell.
Fingers crossed. :fingers:
-
Fortune favours the brave :clap2:
-
Excellent news TD :fingers:
I bet there were a few beads of sweat on the old brow after pressing 'delete all' :D
TD gets well done 'pat' from the management
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fdl9.glitter-graphics.net%2Fpub%2F1121%2F1121599a5jt2gizin.jpg&hash=ea6ee24789927a4a44ca7be8ec68e8f0498ae1c5) (http://www.glitter-graphics.com)
-
@ unkyUb.............beads of sweat indeed, and the need to do some laundry as well. :D
Fingers crossed that the probs are cured..........if so TD might even consider keeping this machine. :)
-
I love the picture :lol:
-
A quick update, if I may.
Following the advice from the man with the penguin, and after having done a good clean out of the registry, I can report that my machine is now starting and shutting down properly. ;D
Thank you, roseway, and all others who assisted and advised. :)
-
Thats great news TD. :thumbs:
ps,don't forget to cancel the skip. :D
-
Excellent :)
-
;D
@ unkyUb...........I have cancelled the skip..................but have retained an option on it in case of future need.. >:(