NVSTOR32 - 64 errors

[iconSYS1]

Computer :
EVGA 680i Motherboard
Q6600
4GB of Ram
3 Hard drives 1) seagate 1TB 1) WD 250GB (C 1)WD500GB
Running windows 7 64Bit

About 6 months ago, when I was running Windows 7 32bit, I would be working on my computer, all of a sudden everything would freeze and I would here a "click" looking in event viewer, i'd get Event ID 11 and Event ID 129 together. One is referrring to NVSTOR32 another is referring to \DEVICE\HARDDISK3\DR3. I would need to hard boot the computer, upon rebooting, the computer would show "NTLM missing or corrupt error" I'd go into the BIOS and have to change the 1st boot disk to the correct one because somehow it had changed. I figured my hard disk was bad, replaced the hard disk. 2 Months later, it happened again, same exact symptoms. I then Changed the hard disk again , and loaded Windows 7 64Bit.. everything was fine for another 2 months and now I'm getting the same exact symptoms again with a new hard disk only now it's Event ID 51 , and NVSTOR64 which is Event ID 3. I've gone through 3 hard drives.. i'm thinking it has to be something else.

I've looked and looked and looked and cannot find an answer for this. I have the newest Nvidia storage drivers. Anyone have any ideas? My next option is getting a new motherboard? I really don't want to.

 

[BadBigBen]

the nVidia controller may be flaky.

suggestion:

update the BIOS to the latest version...


if a BIOS update does not fix the issue, then get a PCIe RAID controller card, e.g. this one

or as you mentioned another mainboard...

Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"

 

[iconSYS1]

Bios update sounds like a good idea, since I was on P31 bios, I've flashed up to p33 bios and will let you know if that fixes it.

 

[iconSYS1]

Well , had constant BSOD's while on the P33 Bios , no resolution I could find that worked other than downgrading. I downgraded to the P32 Bios and so far things are running well. In the past 24 hours i've seen Event ID 51 about 12 times.. this is "An error was detected on device <device path> during a paging operation", but it's all by it's self and doesn't cause freezes like the NVSTOR64 errors were causing. Will keep updating this issue as I see new info.

 

[BadBigBen]

It's a step forward at least...

as to the EID 51, it could be the pagefile having become corrupt, I would go ahead and clear out the PAGEFILE.SYS ...

actually can't delete that file until you create another one on a different Partition and disable that one on the C drive...

http://www.techmixer.com/pagefilesys-how-to-remove-pagefilesys-from-windows/

Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"

 

[flyboytim]

NTLM is a legacy NT LAN Manager Authentication Protocol, for the most part superseded by Kerberos. That seems to be a Red Herring.

Check the S.M.A.R.T. status of the drive by downloading a utility like:

http://www.ariolic.com/activesmart/hard-disk-smart-status.html.

Use a utility like SpeedFan

http://www.almico.com/speedfan.php

to make sure things are not getting too hot - CPU, GPU, Main and Hard Drives. Memory should be checked by using Memtest etc.

NVSTORxx problems are sometimes caused by a mix of drivers of different origins for the chipset (original OEM plus Windows Automatic Update fixes plus third party programs plus attempted upgrades to fix problems).

Gamers often report similar problems.

Unless there are special reasons - like running RAID storage for example, there is no need for storage drivers, the storage firmware and bios handle this via generic drivers.

The reported fix is to download the most recent drivers from Nvidia for the chipset, and then to uninstall the drivers (add/remove programs) and remove the hardware from device manager, and reboot. Make sure you get the Drivers for Graphics and Ethernet (and anything else) if they are Nvidia-based too!

Download and install a program called Driver Sweeper

http://download.cnet.com/Driver-Sweeper/3000-2094_4-75219868.html

There may be other similar utilities available.

On restart, force a reboot into safe mode (F8 after bios before Windows splash screen) If you miss this, perform a reset or power off which should trigger a safe boot option on the subsequent boot following the partial start-up. You don't want Windows to try to install your hardware yet.

Use Driver Sweeper to remove traces of the old drivers and then reboot.

When windows restarts, use the downloaded drivers to reinstall the chipset, but do not install the storage drivers, letting the hardware take care of itself with the generic drivers.

Possibly, the graphics drivers may need re-installation too.

If things continue badly, the motherboard, and PSU should be checked by a competent technician to eliminate/identify them as the source of the problem.