I had to reboot in safe mode and uninstall SP3 to get back to normal,
which is Service Pack 2. The PC is an HP Compaq SR1520NX with 1GB
Ram and 160GB HD with plenty of room. The only hardware I had a bit
of trouble with was an Nvidia AGP card which they helped me with
updating the driver several months ago. I don't seem to have any
problems otherwise with it. Also, I installed a Pinacle USB TV
Tuner. I've had some problems getting it to recognize the tuner
occasionally. Sometimes when I unplug it and re-plug it, it works.
How can I tell (from the error code) what is causing the stop screen?
I appreciate any input...thanks!
My advice to anyone trying to use sp3 or what I think, always when installing a update like this, is log in as admin not your user account with admin rights. I've used sp3 since the first release and I have not had any install issues with any of them most of the stops errors is a function that has been called upon and one or more drivers was not able to update or file because it was running upon update so now there would be 2 files of the same kind running.
------------------------------WAITING FOR THE NEXT MOMENT TO STRIKE
Reply to gomerpile
Thanks for the feedback guys. Noron, I thought SP3 was finilized. Gomerpile, I might have a driver issue as you suspect. I did have a problem with a AGP card and it's driver I installed a few months ago. I finally got it in and working, but that's the only thing I could think of regarding drivers. Is there any way I can determine if this driver is the problem?
Don
I hope this helps I'd go wiff unsigned driver
http://support.microsoft.com/kb/330182 log in as admin and uninstall, the admin account does not have nvidia video drivers installed
Do this reg tweak to get admin account to welcome screen
HKEY_LOCAL_MACHINE
Key: SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\SpecialAccounts\UserList
Name: Administrator
Type: REG_DWORD
Value: 1 display on userlist
second is when your in the welcome screen hit
crtl-alt-del twice and this pops up a login screen
Message edited by gomerpile on 05-04-2008 at 12:29:56 PM
------------------------------WAITING FOR THE NEXT MOMENT TO STRIKE
Reply to gomerpile
You can try running verifier.exe to see if you have any problems with drivers.
It will cause a BSOD and give you the name of the problem driver, if any:
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.