nvlddmkm error and freezing

notasandwich · Jul 15, 2013

Ever since I assembled my newish PC i have been receiving random freezes, some of them lasting longer then a few minutes and forcing me to restart. Other times my screen goes black for a few minutes before eventuating turning back own again. I have checked the dump files/event view to see what the problem was and most of the errors have originated from an nvlddmkm error. When I tried to install a beta version of my GPU's drivers (had the most recent one installed, figured installing an older one would fix the problem), the system restarted on me. I checked the dump file and I got a "PAGE FAULT IN NONPAGED AREA" error. All of my hardware, except for the nvidia 460 GTX card, is basically brand new and I had no issues like this with my previous rig. What can I do to fix the problem?

My specs:
ASUS p8b75-v motherboard
Intel Core i3-2100 Sandy Bridge 3.1GHz LGA 1155
Crucial Ballistix Sport 8GB 240-Pin DDR3 SDRAM DDR3 1600

Tom Tancredi · Jul 15, 2013

Depends what your 'doing' when it freezes. If your trying to push a heavy duty gaming graphics level with that card on a i3 Core you will expect to get these issues. If it is just surfing websites and writing your new resume in Word that this happens that is a different story. If it is the latter, then would be best to uninstall Nvidia. Use Driver Sweeper to completely remove all NVIDIA. Reboot and should be in VGA , download 320.49 (it is WHQL), and install and then use a benchmark / stress test program to see what happens.

You didn't list the HDDs on this rig or if they are 'new' or not, remember the drivers, Windows, etc. all reside on the HDD, if it has bad sectors, worn out, failing, that would be the source of the issue not your Graphics card.

notasandwich · Jul 15, 2013

Tom Tancredi :

I have three hard drives:
WD Blue WD800JB 80GB
Western Digital WD Blue WD10EALS 1TB
Seagate Barracuda 7200.7 Plus ST3160023A 160GB

I only use the 80GB one for windows or driver installations and I just recently installed Windows 7 64bit so I somehow doubt their are bad previous drivers on it

Also how do I go about using a stress test program? I am currently using Furmark, using the Burn In test. What should I be looking out for?

Tom Tancredi · Jul 15, 2013

The 80GB is ancient FYI, and the Barracuda is 'old', both would be under the worn or / watch for replacement. I would run in CMD prompt E:\ then chkdsk /f , D:\ chkdsk /f and C: chkdsk / f (need a reboot) on each drive, as a way to 'stress' and check the drives.

Did you install 7-x64 as a clean wipe of the 80GB drive or just 'over it'. Makes a big difference. Even though it is a recent install of OS, drivers installing can go sideways even on fresh builds, so I would still suggest the specific remove NVIDIA run through (especially Driver Sweeper) to clear out any potential possibility of just one stupid file hanging around unexpectantly/

FurMark is a good test you can try after the drivers are reinstalled, since the problem as you noted is a specific NVidia file going bad, so this would help test it once you really cleaned it out IF the HDD is up to snuff.

notasandwich · Jul 15, 2013

Is there some way in finding out why the computer is freezing? I am not sure it is related to the GPU problem. It happens often whenever I am online. Sometimes it last a few minutes while other times it last long enough that I get fed up and just restart the machine

Tom Tancredi · Jul 15, 2013

WAIT. So the problems can repeat each time your playing a online game? But when you play solo (with the Internet disabled for example) you don't have the issue?

notasandwich · Jul 15, 2013

Tom Tancredi :

Wait what. No, I barely play online games anymore. These issues pop whenever I am nearly browsing the internet

Tom Tancredi · Jul 16, 2013

What is your current Antivirus? Is it up to date or did you let it lapse? Download Malwarebytes and do a scan please.

notasandwich · Jul 16, 2013

Tom Tancredi :

I have Microsoft Security Essentials and Malwarebytes. I will update MSE and I am currently running a full scan of Malewarebytes after having performed a clean boot. I will also attempt to update the bio at some point soon just in case

edit:
Finished scanning with both Malwarebytes and MSE. Found nothing wrong

notasandwich · Jul 16, 2013

Checking the even log, I keep find this error:
"Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D"

I have also gotten this a few times

"Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected."

both of these happen around whenever the computer freezes.

Tom Tancredi · Jul 16, 2013

Okay try this, Uninstall MSE and instead install AVAST! (my preference) or AVG. Then give the computer a scan under those. I am suspecting MSE got corrupted or worse compromised, personally I never had faith in their attempt, but with these errors I believe we need to rule out MSE and see if there is a change with another AntiAV product. Remember only 1 AV software can be installed at a time, but you can have as many AntiMalware as you like

Tom Tancredi · Jul 16, 2013

Hello, I just rereviewed what we discussed here and I am not sure what solution your 'looking for' as your initial statement was about "most of the errors have originated from an nvlddmkm error." the NV are the signature beginning characters for NVidia driver / software files. I suggested "uninstall Nvidia. Use Driver Sweeper to completely remove all NVIDIA. Reboot and should be in VGA , download 320.49 (it is WHQL), and install and then use a benchmark / stress test program to see what happens. "

You have not stated you did these steps, but respond back "I just recently installed Windows 7 64bit so I somehow doubt their are bad previous drivers on it" and "Is there some way in finding out why the computer is freezing? I am not sure it is related to the GPU problem." YES the problem you mentioned (see above) IS related to the GPU software related (not saying the card is bad yet just saying software has a issue) and could have occurred at anytime. We want to see the results if you follow these steps, so that is my repeated suggestion to do these simple steps and lets see what changed (note just don't remove reinstall you need to use Driver Sweeper to remove all traces of the drivers).

Other potential problems here is the legacy small drive your insisiting on using for your OS and Drivers. As the Drivers are software and need to 'load' from the drive (just like the OS files do as well) and if the drive is not performing 100%, or is a FULL drive, then the loading could be faulty and in turn cause a file (nvlddmkm) to repeatedly fail). This potentially could be the real problem and both the reinstallation of files and
as I suggested "run in CMD prompt E:\ then chkdsk /f , D:\ chkdsk /f and C: chkdsk / f (need a reboot) on each drive".

Lastly, I asked "Did you install 7-x64 as a clean wipe of the 80GB drive or just 'over it'. Makes a big difference." This was never responded to and could be the entire issue as well, as trying to install 'over' a x32 OS with a x64 OS would cause all sorts of files (like nvlddmkm) that were already on the drive, to cause problems because they are coded for a x32 OS not a x64 OS. The only solution would be a CLEAN WIPE of the drive and just start over.

notasandwich · Jul 17, 2013

Tom Tancredi :

Yes, I cleared all out all previous nvidia drivers (except for the chipset drivers which I am fairly sure belong to the the motherboard) using drive sweeper and reinstalled the the latest version of the video drives. Twice. I am still seeing nvlddmkm errors in the event log (though I cannot be sure whether that is what is causing the computer to freeze). I have also ran benchmark test (the burn-in test with the Furmark program) and I did not notice any irregularities or the card tempurature going higher then 86 after running it for at least 15 minutes.

When I installed the current version of Windows 7 it was a clean install, meaning I reformatted the hard drive before installing it. I have also run chkdsk on all three drive and it found nothing wrong with any of them (though I believe their was an "SYSTEM_SERVICE_EXCEPTION" error after It finished scanning the 1GB drive in DOS)

Lastly, I tried running memtest and after two passes it found no errors

Tom Tancredi · Jul 17, 2013

"I believe their was an "SYSTEM_SERVICE_EXCEPTION" error after It finished scanning the 1GB drive"
Did you mean 160GB? Run it again and see if it reproduced that error, which would suggest 1) the 160GB is failing and needs to be replaced 2) your Windows on the 80GB bad installed and the 'DOS' command even is failing, which inclusive of a 'CLEAN INSTALL' of Windows indicates usually the drive is bad (a clean Windows install, clean drivers, with no tweaks mods etc. with known good / new equipment normally runs perfectly fine till it wears out).

So 1) The clean install and correct drivers don't correct a 'software' problem with the hardware. That leads to the hardware being suspect.
2) Try with a different NVidia card, are the results the same. If NO, then the card was really the problem.
3) Look up power requirements for all components, are you low in power? Normally at least 500W, and with multiple drives I would believe probably 650-750W might be necessary.
4) Chkdsk isn't working on a single drive (the 160GB) 100%, take the 160GB out of the system, as this indicated it is failing.
5) if all these don't change anything then this goes back to the OS/Drivers being installed on the 80GB even with a clean install we have issues. As noted this is indicitive of HDD failure, though Windows isn't telling you that specifically is the problem (it can't by the way even if it knew it was) remove the 80Gb and install Windows to the 1TB. Do things change at all?

notasandwich · Jul 17, 2013

I rand chkdsk /f on all the drives from the command prompt and no errors where found. Scheduling check disk to run before windows start up however yields that error message I mentioned above (and I am almost certain it happen after it was done scanning the 1GB drive only). Also in regards to the power supply, I have a 750TX COSAIR Enthusiast Series PSU, so I think I have enough wattage to support all my hardware. I will try using another card to see what happens

Another thing I just noticed: Occasionally the computer freezes but for only a few seconds. When this happens I notice that the mouse cursor does not stay as the regular pointer shape. Sometimes It becomes the symbol one uses when entering text into a word document. Other times its that same symbol but sideways. Other times it becomes distorted and discolored, like a graphical error. All these instances the cursor becomes difficult to see before the computer freezes entirely for a few seconds

Tom Tancredi · Jul 17, 2013

Well that is why I asked #2 to test with a different video card to validate your current card works fine (past performance doesn't mean anything if somehow a static shock went across the GPU and damaged it just enough). BUUUUTTTT... the cursor like the file that errors is stored as software on the drives that are having chkdsk problems. SO, I am very very confident you need to #4 and #5 to finally resolve this. Those are the steps I would perform, and it is what I still suggest (nice eliminating #3!).

notasandwich · Jul 17, 2013

Tom Tancredi :

Are you saying a faulty hard drive could cause the mouse to mess up? I don't see how a drive that has never had mouse drivers installed on it would affect the mouse.

Also I tried doing a scan disk on the 1GB D: drive (scheduled to star before windows boots up) so that it would scan for bad sectors and fix them and I got the same system service exception error (it also rebooted into startup recovery first). Dunno if that helps

Tom Tancredi · Jul 18, 2013

In order for Windows, a Operating System, to Operate a piece of Hardware it needs the information on what it is, how it works and what output / input it will do, even if Microsoft provided drivers automatically. If no drivers EVER install for the mouse, then it is listed in the Hardware list as unknown device and won't work. So you always need 'software' off the HardDrive evertytime Windows starts to load into windows to tell it what a mouse is and how to use the inputs to do the function it is assigned.

So if the mouse driver, the Nvidia file, the continuing errors on the most basic ChkDsk, then the drive is failing and needs to be removed. The simpliest VALIDATION to this, remove the bad drive, and install Windows on another drive (in this case the TB) and does the issue persist?

notasandwich · Jul 19, 2013

Just an update: I haven't had any freezes or crashes in the past two days. I am not sure if its just coincidence or I actually inadvertently did something that fixed the issue but so far I haven't go wrong. Really the only issue I've noticed was an "Display driver nvlddmkm stopped responding and has successfully recovered" error that caused the screen to go black for a few seconds. The only thing I've done differently to fix the problem was to back up the important data that was on the 1TB drive and format it before running chkdsk /f and chkdsk /r.

notasandwich · Jul 19, 2013

Hate to double post but this is probably the only way to bump the thread

Anyway I spoke too soon and it happened again. I don't want to bother checking the even log to see what happened since I don't know what error could help in indicating why the computer froze. For now I am going to try using my motherboards onboard video output but I may not know if this'll change anything for maybe a few days, depending on what happens. At this point I don't know what else to do: the three hard drives are fine, at least according to chkdsk. I have stress tested the GPU and the the RAM and both seem ok. I'm not really sure what error message I could look for in event log that could help give a clue what the problem is. What the heck should I do?

notasandwich · Jul 23, 2013

Its still happening. Reformatted the drive, reinstalled windows 7 and ran a bunch of updates and made sure their where no left over NVIDIA drives before reinstalling the most recent nvidia drivers but it is still happening. Going by the even log the last error message to pop up around the exact time that I noticed the freeze was:

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Not sure what that is or what to do about it. Please someone help

Tom Tancredi · Jul 23, 2013

Which drive did you 'reformat'?
My suggestion was NOT to reformat any drives, but instead remove ALL drives BUT the 1TB and install Windows on it.
Reason: Reinstalling/reformatting (a software operation) does not fix hardware (bad disk sector, wear and tear, etc.) problems with Hard Drives.

If you did this and the 1TB is also 'failing' with a wipe and clean install then we have eliminated Windows / Software / Drivers as the issue and need to focus on the hardware.
If the 1TB wiped and Win7 install failed, as it did on both other legacy drives then that suggests the I/O controller (since EVERY drive we try is failing) on the Mobo is failing. As the initial issue was Video Card drivers failing to talk to the Video card, and if the Mobo is failing, this would also cause that issue as both I/O (for the software on the HDDs) and Video card connect over it. Further you said you were going to use the Mobo Video and take the GPU out of the picture, did the issue continue?

If the answer is yes, we eliminated the HDDs, Windows, Drivers, RAM and GPU (according to your own words), which leaves the MOBO connecting all this together, CPU processing and Power Supply as the culprits. I am not really thinking the PSU would be the problem perse, especially if it is a V2, not the OLDER 750TX moved into this sytem with the other legacy equipment (see this and note the differences here http://www.hardocp.com/article/2011/04/27/corsair_enthusiast_series_tx750_v2_psu_review/ ).

notasandwich · Jul 23, 2013

Tom Tancredi :

I don't understand why you are insisting on this being a hard drive issue even after I scanned all three HDD with chkdsk and seatools and found nothing wrong with any of them but I will try installing windows 7 on the 1TB drive. Something I forgot to mention that I think may be of interest when solving this issue: both the IDE drives are connected to the motherboard via an IDE to Sata adaptor. I occasionally get a "bootmgr missing" message when load windows and I had to do a lot of fiddling with the cables in order for the computer to detect the seagate IDE drive

Tom Tancredi · Jul 23, 2013

notasandwich :

You just answered your own question with the "Something I forgot to mention". The point of my suggestion is to 'rule out' parts, but you can't do what with everything plugged in. We repeatedly have had issues with the Legacy Drives, now your adding again another "I had to do a lot of fiddling with the cables in order for the computer to detect the seagate IDE drive".

I am not understanding your insistance you HAVE TO use the IDEs? Add this 'jury rigging' now suddenly revealed only adds more evidence to eliminate potential issues to determine the problem. Remember software isn't 100% accurate nor reliable, if it gets not 1 or 0 but 2 as a response it will give you inaccurate information back. Hardware is straight forward, does it work or doesn't it, period. So if we eliminate the hardware and things work consistantly, then the problem is that eliminated hardware no matter what the software says.

notasandwich · Jul 24, 2013

Installed Win7 on the 1TB SATA drive. Made sure to install the nvidia drivers last. Still got a complete system freeze. Last error to show up on the event viewer was

The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video5
!06d7(2648)

which happened at the exact time as the system free and has shown up before. What do now?

nvlddmkm error and freezing

Distinguished

Judicious

Distinguished

Judicious

Distinguished

Judicious

Distinguished

Judicious

Distinguished

Distinguished

Judicious

Judicious

Distinguished

Judicious

Distinguished

Judicious

Distinguished

Judicious

Distinguished

Distinguished

Distinguished

Judicious

Distinguished

Judicious

Distinguished

Share this page