Error nvlddmkm.sys. Blue screen of Windows 7 after driver installation

Unfortunately, very many users, in particular those who like modern games, face, as it seems, with a terrible problem: for no reason either in the process of the game or at the start of the system gives the error nvlddmkm.sys (blue screen Windows 7, 8 , XP, Vista). What is it, and how to fix this situation, we briefly and try to consider.

Problem with file nvlddmkm.sys (blue screen of BSOD death): general symptoms

Of course, the appearance of the death screen is a hard-hitting situation, but it is by no means hopeless. The error nvlddmkm.sys itself signals that there was a failure when trying to access the type of memory to be unloaded at the so-called level of IRQL processes (interrupts).

As shown by practical studies, in most cases this is due to incorrect driver addresses. What is most sad, such failures are typical only for video chips NVIDIA and most often appear in 64-bit versions of the "seven" and "eight". In such cases, the system gives the error 0x00000116 for the error.

Less often this kind of errors can be manifested in the same "exish" if errors in the file NETIO.SYS, responsible for implementing the IPv4 / IPv6 network stacks. However, the "Seven" is not immune from this. It can also easily produce a similar error, but with a different code: nvlddmkm.sys (blue screen of Windows 7 0x000000d1). In general, these failures are similar, but the methods for eliminating the problems in both cases are radically different.

Problems with drivers for NVIDIA graphics cards

As for drivers, there is a double situation. Problems can occur directly when the driver is installed, or the nvlddmkm.sys (blue screen) fails after installing the driver. And in that, and in another case, when eliminating the problem, one must act very cautiously.

Some "experts" recommend simply reinstalling the driver in the standard way from the "Device Manager" or simply replace the desired object nvlddmkm.sys in the folder System32 \ Drivers. In general terms, the train of thoughts is correct, but here the method of eliminating the problem by the standard method, alas, does not work. Here you need to act a little differently.

Troubleshooting the nvlddmkm.sys file (blue screen of Windows 7 0x00000116): preliminary actions

So, proceed from the situation that the system boots normally. Suppose a crash in the file nvlddmkm.sys (blue screen of Windows 7, 8) appears already in the process of work. First, we need to remove all existing video card drivers. As already mentioned, the standard method is not suitable for this.

First, download and install two utilities: Driver Sweeper and CCleaner (not necessarily just them, you can use other similar software). In principle, if you find it, you can use portable versions.

Now we load Windows in safe mode (F8 key at startup). Then, using the Driver Sweeper program, we completely remove the video card drivers (sometimes you will need to remove the accompanying software, as well as drivers for the HDMI sound).

Next, use the utility CCleaner, more precisely, its section of automatic search for errors in the system registry with subsequent automatic correction of problems. All. The system is ready to install fresh drivers.

Installing fresh drivers

You can install the drivers in the standard way through the "Device Manager" with the system searching for the most suitable drivers for the video card, and then start the update (provided you are constantly connected to the Internet). But the best option is to download the latest version of the driver directly from the manufacturer's website (by numbering your model of the graphics adapter), and then installing in manual mode.

In principle, at this stage, you can use automated utilities that can access the developer resources themselves, find and install updated drivers for absolutely all devices, including a video adapter.

If the problem occurs after installing the driver (the same failure in the nvlddmkm.sys file, the blue screen of Windows 7, etc.), you can try to roll back to a specific restore point when there was no problem. However, as practice shows, this situation can arise only in the case of either an incorrect installation or installation of an unsuitable device driver. Hence - the conclusion: you need to find exactly the driver that fully corresponds to the video chip.

Sometimes this method may not work. It happens that a blue screen can easily appear when you start Windows with an error nvlddmkm.sys. Then you will have to load the downloaded driver archive into the NVIDIA folder on the C drive, boot from the installation or recovery disk, use the Recovery Console, and then use the command line to unpack the required file with the command: expand.exe, with space - nvlddmkm. Sy_, and after a space - nvlddmkm.sys, and then transfer the new file to the Drivers folder located in the System32 directory. Then restart the computer system.

Additional actions may require reinstallation, for example, of HD Audio drivers, and if necessary, installation of an accompanying service package for NVIDIA chips called PhysX.

Upgrading DirectX

Quite often, even with the above operations, the error appears again and again. In all likelihood, this may be due to a conflict between the driver files of the graphics card and the libraries and system files of DirectX. Most often, there are two files in the error message: dxgkrnl.sys and dxgmms1.sys.

As you already know, the simplest way out of this situation will be either a full reinstallation or an upgrade of the DirectX package. You can download it, in principle, anywhere, but it's better to use Microsoft's official resource.

A variation of the error (code 0x000000d1)

Another type of conflict of this type is the same error with code 0x000000d1. As mentioned earlier, it is related to the incorrect operation of the system file NETIO.SYS. But do not be scared, and there is a solution to eliminate the problem.

In principle, it all boils down to just disabling the IPv6 protocol if it is not being used.

How to fix the problem

First, we reinstall the network card drivers, and then we use the "Run" menu (or the command line, if desired) in the working system, where we write the sfc / scannow command. In principle, it should work without disabling IPv6.

In extreme cases, go to the properties of the wireless connection (if, for example, it is used that way) and remove the tick from the line of the IPv6 protocol, after which we overload the system. You can get to this section through the standard "Control Panel" if you use the Network status view and change the properties of the network adapter.

Other possible causes and solutions

Basically, now we briefly considered the most possible causes and situations when the nvlddmkm.sys file crashes (blue screen of Windows 7, 8, etc.). As already clear, to begin with you need to determine the essence of the problem itself. To do this, it is enough to pay attention to the error code, because in both described cases the common name remains the same.

On the other hand, the problems may not end there. Here you will have to test the RAM. Often, conflicts with the slats of the "operative" can also lead to such results. In this case, you need to remove all the slats and insert them into the slots, then load the system in turn, until the error appears again. As soon as it arises, it will immediately become clear that the problem is in the "operative". Naturally, it is better to replace the non-working or conflicting bar. But this mostly applies to stationary computers, not laptops, especially since access to them is limited, and to disassemble the laptop itself, and if it is also a guarantee, it seems a matter of quite ungrateful.

In some cases, you may need to reset the BIOS settings of the video card itself. If the card has been overclocked, it is better to reduce its frequency to the factory settings. For this, a small utility called Riva Tuner is perfect.

However, in some cases (especially in Windows XP) a successful solution to the problem may be the installation of the last service pack, and for the "seven" and above - the usual update. Incidentally, it should be added that problems can be caused by programs such as Sygate Personal Firewall or other similar firewalls from third-party developers. The problem is solved by usual uninstallation.

In any case, do not despair, because for each specific situation has its own solution to the problem.