175.16 Nvidia Drivers Cause WinXP 64 to Freeze at Boot Screen

[airhendrix13]

I recently reformatted my PC because I wanted to put XP64 on my PC. The install went fine, then I installed my nForce drivers, which went fine, but when I installed the new 175.16 drivers and restart, it gets as far as the windows boot screen (with that blue loading bar) and just continuously loads. I know the computer hasn't froze because the bar is still moving.

My first thought was to boot into safe mode and remove the driver but I can't even get into safe mode!

I don't think it is any of my hardware because everything works perfectly as long as the 175.16 drivers aren't installed.

Any suggestions?

Thanks,

Ryan

 

[airhendrix13]

bump

 

[unr3al]

Safe mode is there mainly to allow for driver troubleshooting. So if it doesn't work in safemode, you most likely don't have a driver problem. But play it safe and install a previous version? And see if it boots. I am using x64 myself so I am pretty glad I read this, if I buy an nV card anytime soon.

 

[taltamir]

did you try waiting a few minutes?

Sometimes a major install or some upgrades cause the boot screen to freeze, but it is actually applying updates, if you wait a few minutes it will go into windows and stop "freezing" in future reboots.

One of the reason I love having a top of the line CPU is that it significantly cuts down the wait time... so I can resolve a lot of "freezing" situations by waiting...

For example, some days ago I did something funky in firefox 3 RC2 and it froze for 3 minutes and then finished the operation and continued. And this is on an E8400 and 4GB of ram. It could have easily taken much longer on a slower machine.

A month ago I installed a driver update and windows vista SP1 "froze" on the boot screen (the bar wasn't mooving) for 2 whole minutes before finishing. it did not freeze in subsequent restarts.

 

[airhendrix13]

Hey guys, thanks for the responses! I was able to solve it by physically removing the video card itself, then putting it back in. It must of been something in the CMOS settings? But it works! Thanks again!

Ryan