Blue screen with nvlddmkm.sys after Windows update Nvidia drivers to 335.23

My Windows 7 (32bit) update has recently put new drivers for Nvidia (335.23). After restarting the computer nvlddmkm.sys error/blue screen/kernel dump appears and it restarts again. "Shutting down" message appears.
My video card is Nvidia GT 220.

As far as I can see this new driver 335.23 cannot work with PAE mode enabled. I use PAE mode on my windows machine, to be able to work with all available 4GB RAM with my 32bit Windows.

I downloaded the drivers from Nvidia, and made a clean install, but it did not work again :(
Newer driver is not yet available :(

Solution N1: Rollback to the old driver. (According to Nvidia documents using Device Manager to rollback driver is not a good idea - see My solution)
Solution N2: Boot without PAE (if you can).

My solution: Downgrade to version 332.21. Just download it from NVIDIA web site, and choose advanced setup, with check "Perform clean install". Of course in SAFE MODE. You are not able to boot anyway. Here are some screens:

Update 05.01.2017
I installed 64-bit Windows 7, and won't follow this issue any more

Update 23.04.2016
Driver 341.95 - does NOT work!

Update 09.12.2015
Driver 341.81 - does NOT work!
Driver 341.92 - does NOT work!

Update 07.03.2015
Driver 341.44 - does NOT work!
Scrambled. I am surprised that there is a new driver!

Update 20.09.2014
The newly released driver 344.11 supports only graphic cards Series 400 and above. Does that mean Nvidia cut-off support for the older models? Unfortunately yes - http://nvidia.custhelp.com/app/answers/detail/a_id/3473
So in my case I have to stay with the stable driver or Install Windows 7 64bit.

Update 30.07.2014
Driver 340.52 - does NOT work!
Same as 337.88.

Update 01.07.2014
Driver 340.43 (beta) - does NOT work!
Same as 337.88.

Update 27.05.2014
Driver 337.88 - does NOT work!
It crashed in blue screen during installation, while trying to restore the resolution. I tried to run the installation again and it finished. But after the reboot it tried again to switch to native resolution, artefacts on screen appear, crashed again with BSOD. Works without PAE.Going back to 332.21, my precious...

Update 21.05.2014
I recieved an answer from Nvidia today. They were able to recreate the issue, but as I expected, developers refuse to work on that issue, because it is due to kernel patch, NOT supported by Microsoft. However they are working on a similar issue on Windows Server 2003, where PAE is enabled and supported by Microsoft. They hope that it will resolve my issue too. I will wait, test and post results here :)

Update 29.04.2014
Several weeks ago I contacted Nvidia with this issue. During this time they asked for a lot, a lot of information, which I provided. They were able to locate the issue, and developers are working on it. I will keep you informed, as they keep me informed!
Very special thanks to Nvidia Support Team and nameley - Ray!

Further notices, first tries to fix it:
1. The famous youtube video https://www.youtube.com/watch?v=YrOKlh9fC9g
made the problem worse - Windows loops on "Shutting down" screen, and does not restart or issue kernel dump.
2. On 07.Apr.2014 , version 337.50 beta was released - did NOT solve the problem.
3. Downgraded to version 334.89 - did NOT solve the problem


  1. Hello. Any new news? I have the same exact problem with nvlddmkm.sys with nvidia 335.23 and also with beta 337.50. I tried everything possible, rollback, update bios, clean install of OS, and even take out the card (gtx460) to search for bad capacitors. None worked and now i cant use the PC ..when i open web browser or a picture or anything similar it goes into blue screen.
    Please keep up to date with a fix..if there is one. Cheers

    1. Have you tried older driver - 332.21 like me? I am also able to work if I start Windows without PAE. Perhaps your problem is slightly different because you said "when i open web browser". In my case the PC does not start at all, only in safe mode - so i could change the driver (actually you have to INSTALL the old one 332.21, rollback in device manager won't work according to Nvidia).

    2. Same described problem

      Chipset: nVidia ION
      CPU: Dual Core Celeron U2300
      OS: Windows 7 Pro 32bit With PAE enabled

      I've same problem on a ION chipset with Dual Core Celeron U2300
      Those new drivers functions only with PAE disabled.. ..and previous drivers occasionally rebooted the system..

      ..if there isn't a solution I'll reinstall an older driver :(

      are they patching the kernel as INTEL do just to give noises?

    3. I am using a 64 bit system with 8gb ram so PAE not activated. From my previoua message now my computer doesnt start at all only in Safe Mode. I made some custom bios for the GPU with increased voltage but that doesnt work either. I ordered the GTX750 Ti but i am still interested to resolve this problem because it intrigues me. Next step is to remake all conections from the GPu with hot air and special flux "glue" ..

    4. Oh my! I used safe mode to install the old driver, an it works. I wonder why you have to take hardware measures. I also have to say that one day I forgot my computer on and because of that driver problem it was restarting all day, luckily it is not damaged. No answer from Nvidia yet. It is interesting that when I open the list of drivers for my 220GT, it seems that in the past they issued a new driver every month, or even twice a month. Now - almost 2 months - no new driver! Only one beta release. Something is going on...

  2. I rarely write these, but I have to say thanks. Your instructions worked perfectly for me and saved me a lot of time and probably my company a lot of money. I appreciate the amount of time (and frustration) you spent on this.

  3. The Nvidia developers are refusing to work on this because their management did not allocate time and budget to resolve this issue and the management is likely not aware of this issue at all. Someone got to contact either their CEO or a boss couple of levels below and explain him that this prevents many customers, who MUST use PAE patch for hardware compatibility issues, from buying nvidia cards, and that they are losing money on it! And that this is in behalf of a big community. If they acknowledge the problem, then they will order the developing department to fix it and they will fix it.

  4. This comment has been removed by the author.

  5. Thanks so much for posting this! My Windows machine (32-bit) recently started getting frequent blue screens after installing an update. I ended up reinstalling Windows (and the 340.52 Nvidia drivers), only to have the problem come right back. I was ready to give up and buy new hardware when I found this blog via Google. I tried downgrading my drivers to 332.21 and sure enough, it worked! My system has been running for over a week now without a single crash. :-)

  6. Hello. The same issue for me - Windows8.1 + Nvidia 347.88 driver (gt440)

    1. Did you fix it, by replacing the driver?

    2. Yes, downgraded to 332.21

    3. 332.21 seems to be a 64 bit driver. I looked it up on the nVidia website. If I'm wrong could you send in a link to the download page?

    4. Please disregard. I found the web page

    5. Thanks a ton for publishing this driver version as being a 'stable' driver. It worked for my Win7 x64 laptop with a GT555m.

      I started getting BSOD's last week after a forced windows update and I have tried about 7 drivers since (including ones that worked after a previous windows update caused BSOD's). This one finally worked, thankfully!!!

      In the past year or so I have run into this problem about 3-4 times. Usually I just wait a few days and a new windows update comes out that fixes the BSOD,..then I can reinstall the old driver and things work again. Sometimes I have to try a totally up to date driver to get things working again. Things didn't work out this time until I used this exact driver.

      Now, if you try telling MS that they have messed up the driver, they will probably give you the run around and say it isn't their update that broke things, but this is really consistent here and it really is windows update that causes the problem over and over again.

      Did I mention that I hate Win sometimes :)


  7. Problem exists at the latest driver (10/02/2015). So sad that we can't update drivers because if issue.