Tom's Guide > Forum > Windows Vista > Vista General Discussion > Vista Install BSOD nvstor.sys

Vista Install BSOD nvstor.sys

Forum Windows Vista : Vista General Discussion - Vista Install BSOD nvstor.sys

TomsGuide.com: Over 800,000 questions and answers to address all your high-tech questions. Sign up now! Its free!
Word :    Username :           
 

I have been running Vista Home Premium 64 bit for a couple months. I recently got some type of spyware or malware that really slowed down my computer. After my attempts to find and remove the virus were unsuccessful I decided to reformat and reinstall Vista. I successfully reformated the computer however when I try to install Vista, on the "Installing Windows..." screen I get a BSOD. "Copying Windows files" goes fast then when it gets to "Expanding Files" it gets stuck at 1% before the BSOD appears. The BSOD has the following information:

irq less than or equal to

nvstor.sys blah blah blah

*** STOP: 0x0000007F

I have 4GB of RAM and I know Vista's issues with that at installation so I removed 2 GB.

:pfff: :(

Sponsored Links
Register or log in to remove.
- 0 +

In BIOS, take any overclock off you had before you reformatted and tried to reinstall the OS. Then, specifically, use one DIMM of RAM in slot one only to load the OS. An more importantly, In BIOS, set your RAM voltage to specifications, for PC6400 use 2.0-2.1v.

http://support.microsoft.com/kb/137539


Message edited by badge on 06-07-2008 at 01:19:24 AM
Reply to badge
- 0 +

I didn't overclock when I had Vista running properly.

I successfully installed XP 32 bit but now the computer freezes when I try to download a driver or download a windows update. At first I thought it might be because of spyware but now I am thinking its because of a hardware problem, most notibly the hard drive or motherboard. I have always had a problem of my computer locking up then not recognizing the dvd-rom drive.

Ahh, I just want to play cod4.

Reply to sinikal
- 0 +

and I also noticed when I installed XP it only recognized the HDD has 130GB instead of 250GB. I thought that was odd but I continued any way. I just inserted the Vista CD to bring up the command prompt and I am formatting the C: drive, which reads 131,000 MB. There is only one partition on the disk, C:


Message edited by sinikal on 06-07-2008 at 05:54:30 AM
Reply to sinikal
- 0 +

You have a pre-SP1 version of XP... it doesn't recognize more than 137GB.

------------------------------ Desktop: Windows 7 Professional 64-bit; Intel Q6600 CPU; E-VGA 780i SLI motherboard; E-VGA E-GeForce 8800GT; OCZ Vista 4GB dual-channel kit; Ultra X2 750W power supply; 2 x Seagate Barracuda 7200.11 500GB in RAID 0. Laptop: Acer Aspire 8730-6314;
Reply to Zoron

Hi all,

I realise that this post is probably quite old by now, but I recently purchased components to built myself a new PC and started getting a BSOD, telling me that nvstor64.sys was the culprit. I spent days looking for a solution and never found one, so I wanted to share this with other people.

Components used:
Mobo: ASUS Striker Extreme
RAM: OCZ DDR2-PC6400 Reaper (800mhz, CAS4)
CPU: Intel Q6600
GFX: Gigabyte Nvidia 8800GT OC
HDD: Seagate Barracuda 500GB SATAII
DVD: Lite-on DVD/RW
Case: Antec 900

When I came to building the machine, everything went according to plan, until I installed Vista Ultimate 64bit with SP1. At first all seemed to be ok, I installed the OS with no issues, installed my gfx card, then realised I'd not installed my mobo drivers. So, I went to the ASUS site and downloaded and installed all the latest nVidia 680i chipset drivers.

Then I went to install COD4 and I get a BSOD with nvstor.sys as the culprit. Given that I'd just installed the gfx card, I assumed that this was the fault, and did some googleing. After some time looking, it seemed people had had similar issues, but with no concrete solution.

To cut a long strory short, several days passed with much hair pulling and avid internet searching for an answer. I tried installing Vista 32bit and even reverted to Win XP in the event this might be an OS compatability issue.

Eventually, I realised that nvstor.sys (and nvstor64.sys on 64bit O/S) is the driver for the nVidia motherboard chipset, which supports the SATA controller. This is where the issue lay. Whenever I updated the chipset drivers (either manually, or via windows update) I'd end up with a BSOD and nvstor.sys at the culprit. I've now installed Vista 64bit and my machine is running flawlessly. All I have to do is make sure I never update my nVidia SATA drivers.

This experience has been a nightmare, and I'm furious with ASUS for releasing drivers which can cause BSODs as soon as the HDDs are in heavy use (whilst installing, removing drivers etc.). Apparently, this is a known issue that many people with the Striker Extreme/Striker II Extreme and Striker Formula motherboards have been having. I'm simply stunned by the lack of support from ASUS and that no one seems to have provided a solution.

The big issue I found was that if the chipset driver was updated, there seemed to be no way of uninstalling it, without a BSOD presenting itself.

I still don't know whether a driver exists which will allow me to update my motherboard chipset drivers without causing BSOD. If anyone knows otherwise, please let me know!

I hope that this helps anyone who is having the same problem!!

/chuck

Reply to chuck_stones

Thanks Chuck. I keep hearing these nightmares about this MOBO and chipset. I wonder - is this Asus problem or Nvidia's? It does seem to address the OPs issue.

------------------------------ tehhardpro wrote :


notherdude u have an old hand. Having an old hand doesnt make sence. Cuz its old. get a new one.. seems like ur hand doesnt understand what it is writing. So placve it in ur rig instead of vista human orgnoids will amke more sense
Reply to notherdude
- 0 +

I've installed the latest drivers for my 780i... but I didn't get them from E-VGA, I nabbed them from nVidia's site. Never had an issue... unless this is specific to the 680i chipset...

------------------------------ Desktop: Windows 7 Professional 64-bit; Intel Q6600 CPU; E-VGA 780i SLI motherboard; E-VGA E-GeForce 8800GT; OCZ Vista 4GB dual-channel kit; Ultra X2 750W power supply; 2 x Seagate Barracuda 7200.11 500GB in RAID 0. Laptop: Acer Aspire 8730-6314;
Reply to Zoron
- 0 +

Hello,

I am having the same issue with a gigabyte motherboard. BSOD installing vista ultimate, nvstor.sys being the culprit.

There is, to my knowledge, only one way to fix this and that is to get the file you need and install it via a floppy during the install of vista, but I haven't had any luck there yet. There are people who have created drivers that try to "hack" it into working.

There has been a lawsuit between Nvidia and MS, each saying it's the others fault, etc. Windows Ultiamte 7 Beta (which is avail for DL) installs fine on this PC (using it as I type), but the Vista Ultimate I paid for I can't even install :(

The mobo I am using is the Gigabyte M57SLI-S4 Rev 2.0

Oh well, guess we're just screwed since nither Nvidia nor MS want's to help us.

-TheJointChief

Reply to TJC

notherdude wrote :

Thanks Chuck. I keep hearing these nightmares about this MOBO and chipset. I wonder - is this Asus problem or Nvidia's? It does seem to address the OPs issue.



To be honest mate, it must be nvidia, I had the ASUS board with the 790i nvidia chipset and it kept radomly freezing, so the PC shop replaced the MOBO to an MSI P7N2 motherboard, 790i north bridge chip, 570i south bridge chip. It ran awesome for 2 weeks, then vista carried out an update, and tried to update the nvidia drivers. It showed in the log as failed, didnt think nothing of it, tried to start up this morning and got the BSOD stating nvstor.sys as the problem.

Cant boot from safe mode, last known successful boot mode or anything. Cant find any decent solution. Feel really angry and have heard vista and nvidia are both denying it is there fault. Well I am sitting here with a beautifully spec'd PC that doesnt work because of one of these two and am really angry.

I am not an expert and think the only solution I have is to re-format the hard drive, but how do you do that if nothing will boot? Very desperate and upset at the moment, hoping some tech guru is going to come along and save the day for me :)

But the next GPUs, MOBOs that I buy will not have one nvidia item on it that is for sure.

Reply to johnpaulcain
- 0 +

you can always just use the CD-ROM for vista and have it fdisk/reformat the drive, or go to www.bootdisk.com and download an old bootdisk (floppy) and fdisk it the old way. The PC is fine, it's just the OS thats hosed.

I've tried to reinstall countless times, but no go. Windows 7 Beta installs fine though <sighs>.

I'm going to try reinstalling vista again soon, with some drivers I found online. Sadly in my situation I have Vista Ultimate SP1 in-box, it won't install at ALL. I'm going to try what I picked up here. Check out the posts made by "Fernando 1", he made the driver packs I'm going to try and offers some interesting info on the problem in general.

http://www.nforcershq.com/forum/1- [...] c&&start=0

Hope that helps.

-TJC

Reply to TJC
- 0 +

Hi,

you can always just use the DVD-ROM for windows and have it fdisk/reformat the drive, or go to www.bootdisk.com and download an old bootdisk (floppy) and fdisk it the old way. The PC is fine, it's just the OS thats hosed.

I've tried to reinstall countless times, but no go. Windows 7 Beta installs fine though <sighs>.

I'm going to try reinstalling vista again soon, with some drivers I found online. Sadly in my situation I have Vista Ultimate SP1 in-box, it won't install at ALL. I'm going to try what I picked up here. Check out the posts made by "Fernando 1", he made the driver packs I'm going to try and offers some interesting info on the problem in general.

http://www.nforcershq.com/forum/1- [...] c&&start=0

One thing, once you get it working, NEVER EVER EVER let windows update install new SATA drivers! Always do selective updates.

Hope that helps.

-TJC

Reply to TJC
- 0 +

Honestly, it seems to me the problem is a Microsoft one. In each instance, including my own, the nvstore message comes up after a MS update. That is what happened to me as well. I have an ASUS M2N32-Sli Deluxe board. It ran fine until I ran the sata update from Windows Update. I got the nvstore error after that. After rebuilding the PC again, I hid/ignored that update and it has been fine. While most of the board listed here were asus boards, I saw other manufactures as well as other chipsets. My chipset was an nForce 590.

Reply to bhowell

Hey, maybe it is an MS issue, but it doesnt conflict with other manufacturers? So who bows to who, in my view nvidia should change to conform with the norm. i.e. MS. Instead all nvidias customers suffer.

Anyway getting back to the issue. I can boot from the vista install CD but it only ends in a BSOD and nvstor.sys issue. It does not ever give me an option to fdisk/re-format the drive.

So how do I achieve this?

I am thinking I might just buy a new HD, is that teh quickest/easiest option?

Reply to johnpaulcain
- 0 +

Buying a new harddrive isn't your solution. I made another post to your other thread. I think you are just missing something in the process. Maybe my latest post will help John.

Reply to bhowell

Similar problem here with the Asus P5N32-E SLI Plus another lower specced relation to the Striker.

Thought it was something to do with SATA but have also found that I have to disconnect my SATA Blu Ray drive before re-installing Vista Home Premium x64. I guess that means the drivers shipped with Vista are also jaffered or is it the mobo/Asus?

Once the latest Nvidia Nforce drivers are installed no problem can just connect up until today when I flashed my Bios to 1201. Back to 1104 and ok again.

Hmm tempted to upgrade anyway but looking like a move away from Asus again. Had many issues with the old A7A266!

Reply to John_Bones

:)

No its definately the nvidia/MS driver integration that is the issue.

Everyone seems to be fine when downloading nvidia drivers direct, but when windows does it via the update the nvidia drivers shag the OS up by corrupting the sata drivers. Only happens with nvidia chipset boards.

My view, as nvidia and MS cant be arsed to help and the only way of dealing with this is a re-install or plugging your HD into another PC to rectify it is dont buy nvidia stuff anymore out of principle. i.e. shocking customer service.

Reply to johnpaulcain
- 0 +

The answer isn't boycotting Nvidia stuff either. So there is an issue with the sata driver from MS...simply don't download that from Windows update. Simple solution to this problem. Ever since I started ignoring that particular update, I haven't had the issue come back.

Please don't jump on the "don't buy this, don't buy that" bandwagon for something as simple to fix as this. Discover or listen to alternate solutions and run with them.

Reply to bhowell

Simple to fix?

Yes it is simple once you have your system back up and running I agree.

However, to get there I have had to research the issue on forums for hours, submit tickets to support with my motherboard manufacturer. Have them tell me there isnt a fix, had to buy a new HD, re-install windows and all other programmes and only then do I get to your "simple fix" scenario that isnt actually a fix but is more of a way of avoiding it in the future.

All because I bought a motherboard with an nvidia chipset and they are arguing with MS over who's problem it is. Maybe it isnt nvidia, but I could not give a monkeys whose fault it is I just want a quick fix, but nvidia wont give one although they are blatently aware of the problems people are having.

For me i'm not gonna bother with nvidia in future, its not that I know it is definately thier fault, it is beause they cannot be bothered to make an easy fix for me and hundreds of others.

Reply to johnpaulcain
- 0 +

Sure it was a simple fix. Like you, I had my system down, though apparently not as long as you. As soon as I saw the error, I knew what it had to do with, but with a little research, I discovered what was the likely cause...the update from MS. From that point on I ignored that update after I rebuilt my PC. It has been running great ever since. That has been approx 3 weeks now. Rebuilding them sucks after awhile...I typically rebuild mine quarterly.

OK, lets throw another wrench in the works. You say your motherboard has the nvidia chipset...guess what? Nvidia sold the use of that chip to your motherboard manufacturer. Why not blame the MB manufacturer? Maybe they have something on their board that conflicts with the nvidia chipset. Tell you what, lets blame the other chip manufacturers or perhaps even those that make the transisters or capacitors. How about the BIOS manufacturer? How many hands do you think is in the pot for just your motherboard? Think about that. Conflicts happen. Look for a resolution and go with it if it works for you. Again, blaming one manufacturer isn't the solution.

Just because you didn't get a quick fix right then and there doesn't mean one isn't being worked on. Whoever you spoke to may not know what the geeks in the back room are working on. Give them a break. It isn't like Nvidia, ATI, MSI, ASUS, etc can have one of every possible piece of hardware to test their individual component with. They have to make their piece of the puzzle and hope it fits properly with everyone else's. If it doesn't, then they have to work on that piece to determine the cause.

When dealing with components ON the motherboard, go to the MB site for drivers. If you have an individual component, get drivers from that components website. Everything else can be handled by MS unless issues come up. Check for updated drivers quarterly and update them on occasion. Sometimes updated drivers can help you avoid some problems in the future.....and they could, on rare occasions, cause problems. Kinda have to play it by ear.

Reply to bhowell
- 0 +

Do NOT turn Automatic Windows Update on.

 

I have been running Windows Vista (32bit) for over 2 years on one of my PCs. It has never _EVER_ shown a BSOD before I enabled Automatic Updates by mistake. When I started my computer, I would BSOD before explorer.exe (nvstor.sys was the cause)

 

Here's how I fixed it.

 

1. Boot in safe mode. To do this press F8 when you're at the loading screen and select *SAFE MODE*. I'm pretty sure nvstor.sys loads, but it does not cause a bluescreen for whatever reason.

 

2. System Restore. Loadup system restore and look for 'Install: Windows Update'. If you have multiple Windows Updates then you have to guess which one caused your system to bsod. I selected a restore point that 2 days prior to the latest Windows Update.

 

3. Disable Windows Update. This should be in control panel somewhere, titled "Windows Automatic Updates". You may keep Updates enabled but only when you chose to download and install them.

 

good luck.


Message edited by subwar on 07-02-2009 at 06:31:57 PM
Reply to subwar
- 0 +

Never had a problem with Automatic updates and my 780i motherboard. Of course, I only use nVidia's drivers and never the ones from MS Update. Driver updates are almost always considered non-critical and don't usually download through Windows Update unless you tell them to...

------------------------------ Desktop: Windows 7 Professional 64-bit; Intel Q6600 CPU; E-VGA 780i SLI motherboard; E-VGA E-GeForce 8800GT; OCZ Vista 4GB dual-channel kit; Ultra X2 750W power supply; 2 x Seagate Barracuda 7200.11 500GB in RAID 0. Laptop: Acer Aspire 8730-6314;
Reply to Zoron
- 0 +

Agree with Zoron. System Restore from Safe Mode? OP, long gone OP, has a stop...7F error. Very likely incompatible hardware of more likely incompatibly with hardware/driver.

Reply to badge

Is this the problem if it occurs intermittantly? I have had the blue screen with the NVstor.sys as the problem. However, my computer will sometimes boot fine and after a while get this screen. Sometimes it will just turn black and nothing wakes the system up so I can see a screen (after several hours). SOmetimes my computer will not even boot, nothing. SOmetimes it will load to the MSI screen and not go any further.

My screen where it shows my drives and gives me a chance to enter setup, will usually say, "Warning, system overclocked failed, system default reset", when it does boot this far. Though I have never overclocked the board.

Sometiems after a good load up, right when I hit windows and start moving the mouse around my screen will go black. Sounds like everything is working.

If the unit is not booting at all and nothing is heard, if I,turn off power, remove the graphics card and try to boot, I will hear the system give me a series of beeps, indicating its getting power and knows the card is missing. Yet, with the video card in, it wont do anything, no beeps, nothing. This is where my computer is stuck now. The system has worked fine for a couple of years and has been doing this for the last 2 weeks, sometimes working, sometimes leading to above.

So, any ideas, if it is the drivers as talked about here, a bad motherboard or a bad graphics card.

MSI K8n motherboard
AMD dual core processor
8800 gts video card.
vista 32 bit loaded
4gb ram, 2 2gb chips
power supply was adequate (made sure when I built the rig), forgot wattage (650w?) forgot brand
3 harddrives or different sizes hooked up to SATA

Thanks,
Stevil

Reply to Anonymous

The Stop 0x7F message indicates that one of three types of problems occurred in kernel-mode:

• A condition that the kernel is not allowed to have or intercept (also known as a bound trap).

• Software problems.
If it is a Software problem, you can use Registry Easy to solve it.
http://www.keep-pc-clean.com/

• Hardware failures.

Possible Resolutions:

• Stop 0x7F messages are typically due to defective, malfunctioning, or failed memory hardware. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.

• Running the CPU beyond the rated specification, known as "overclocking," can cause Stop 0x7F or other error messages due to heat buildup. When diagnosing problems on overclocked systems, first restore all clock and bus speed settings to the manufacturer recommended values to determine if this resolves the issues.

• The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.

• Stop 0x7F messages can occur after installing incompatible applications, drivers, or system services. Contact the software manufacturer about possible Windows XP specific updates. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.

Reply to xxnideoo
- 0 +

xxnideoo...The original post is from June 2008, more than a year ago. OP is no longer active on this Forum. You posted directly to OP. See the date next to your name. See the date next to the thread starters name? Read the date on the thread before posting direcly to someone who posted a year and a half ago.


Message edited by badge on 10-25-2009 at 05:49:20 AM
------------------------------ "To better understand why you need a personal computer, let's take a look at the pathetic mess you call your life."
Reply to badge
Tom's Guide > Forum > Windows Vista > Vista General Discussion > Vista Install BSOD nvstor.sys
Go to:

There are 6 identified and unidentified users. To see the list of identified users, Click here.

Google ads