Bsod On Boot

Hello again,

SO i bought the OEM Win 7 32-bit for my system (a few posts down..)
Install went fine, drivers installed went fine.
Worked great for a day.
yesterday i turn it on during the morning and then walk to go get coffee or something. return and the screen that says "windows did not shut down properly, want to start normally or do a disk repair(recommended)" screen comes up. I do disk repair, wait, no problems found, restart and its fine. Since then, everytime i start windows it hangs, restarts, and the same screen comes up. When i click start windows normally, everything is fine.
So i turned off/on and watched very closely. Noticed a blue screen. went in, turned off automatic restart.

Driver_irql_not_less_or_equal

and the culprit appears to be nvstor32.sys

so i turn off, turn on, same thing.
now it wont let me get into the OS.
start up in safe mode, and boot with last good setting
it BSODS, but then automatically restarts and everything is fine.

i havent added any hardware, this is with everything unplugged (except AC cable. at first i thought i was trying to boot from my external HD, but when i saw in the BIOS that the priority is below optical boot and that HD boot was the first.. this is before i noticed the bsod)
i have minimal programs installed, nothing fancy (firefox, AVG, skype, winamp) all up-to-date.

basically, it was running fine OOB, and the only difference i can think of was Automatic Windows Updates.

I am not sure what to do now. I looked in c:\windows\minidump for the dumpfile but couldnt find the directory. Does 7 have "safety" features like vista did?


any help is appreciated!!

 

yea i figured.
but why? and what do i do to fix?

 

download the most recent drivers for your video card NVIDIA drivers

 

Just to clarify what the others have said its not always the GPU driver thats causing the issue, do you have a NVIDIA chipset MOBO, you need to try and enter safe mode and re install the chipset and Ethernet drivers and GPU drivers

 

I do have an Nvidia chipset MOBO, at least, 80% sure.
After trying to system restore, delete windows updates and such, i rolled back my driver through windows from the 2009 release to the 2006 release. So the problem was a windows update that installed a driver that i guess isn't compatible.

i am a little concerned about running such an "out of date" driver, but if it aint broke, dont fix it right?

 

Still a good rule to follow!

 

It is a good rule to follow providing it works for you.

I personally prefer everything to be up to date as the drivers are revised for a reason, some address performance issues, some address compatibility issues etc.

It depends if everything is working as it is meant to...

 

The thing is, Dalo, you are not a typical user. (There is a reason why you are our Senior Technical Specialist :snckr: ) What may not work for you will not even be noticed by the likes of me.