Page fault in non paged area


I've got a problem.. When windows boots up it comes up with the following error message:

A problem has been detected and windows has been shut down
the problem caused by VDDIDECR.sys
Page fault in non paged area
Check new hardware / software in installed
Stop 0X00000050 (0x8000007c, 0x00000000, 0xF9653F1E, 0x00000000)
VDDIDECR.sys - Address F965F1E at F964C000 datestamp 37b38a62
Beggning dumb of physical memory

I have no idea what 'VDDIDECR.sys' is and a google seach does not find anything either.

I am thinking that there is either a problem with my memory or virtual memory.  Or perhaps doing an XP repair might solve the problem.

Any advise much appreciated.

Justin Davis
Who is Participating?
burrcmConnect With a Mentor Commented:
Page fault in non paged area typically points to RAM - faulty or incompatible, but it can also refer to a driver issue. This looks a bit like the problem here. Find VDDIDECR.sys, right click it and look for a version tab. The detail within may tell you manufacturer etc which might point to the device which is trying to use it. I can't find anything on it either - maybe double check the spelling? Is this a new system or has it been running OK previously. If it was OK, have you added / installed anything lately?

Chris B
OnyxTecAuthor Commented:
Problem solved!!

There was a recently installed program and the VDDIDECR.sys was part of that installation.  I booted into safe mode, found the sys file in the depths of the Windows/system32 directory, renamed it ~temp.sys and upon next reboot all was well.

I did however notice two msconfig startup items; dumprep 0 -k & dumprep 0 -u (dumprep.exe forms a part of Microsoft Windows XP (and later versions), in-built fault logging software. Upon serious errors this program will write the details to a text file and request the information be sent to Microsoft.)  However after two reboots it had self removed itself I assume from successfully rebooting.

Thanks for the help Chris.
I am facing similar problem on my machine when I am installing a proprietary driver. This driver installs fine on Win2K. When I try to install on XP it crashes with the ‘blue’ screen. It gives me the same error as OnyxTec has put in his mail. I could not understand the solution well. Can you please explain this for me.
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

OnyxTecAuthor Commented:
Get the blue screen up and make a note of the error message..  It'll probably refer to a missing or corrupt file.  Make a note of that file name (for me it was VDDIDECR.sys).

Boot into Safe mode (F8 while booting the computer)... In Windows Explorer go into C:/Windows/System32 and file the file the blue screen referes to.  Right click the file and rename it (I suggest just putting a symbol such as ~ in front of the existing name just in case you need to refer back to it at a later date for whatever reason).

Reboot the computer and see if this has solved the problem.

Please return to this forum to conclude if it worked or not.
OnyxTecAuthor Commented:
Sorry that last post should have read "In Windows Explorer go into C:/Windows/System32 and find the file the blue screen referes to."
Thanks for your quick response.
Sorry, I did not explain the scenario well. The machine crashes when I try to install one proprietary driver. This installation has vddidecr.sys, and installs this file into WINNT/System32/Drivers folder (XP Professional). I can see this file in the folder when I reboot after crash.
I cannot rename or remove this file, as this is needed for the driver to work.
I know the installer is meant for Win2K. And it installs the driver without any error on Win2K machines. Now I am trying to make it run on WinXP.
If you can help me with this issue, it would be great. I don’t what can be the changes with regard to this .sys from Win2K to WinXP. Any suggestion is welcome. I will try it out.
Thanks for your support.
OnyxTecAuthor Commented:
My explanation was simply to stop the blue screen using a roll back type fix, i.e. removing the drivers.

I'm afriad I wouldn't know what to suggest trying to get W2k drivers working on a WXP machine...  Although one option which I have used and set up for clients needing old bespoke software which is not supported on new OS's; using a terminal OS via Microsoft's Virtual PC (an application where you can run multiple PC-based operating systems simultaneously on one workstation)... Links below.

Hope this helps to some degree.

Virtual PC Home Page:

45 day Trial:

Advice generated via
Thanks OnyxTec.
Let me try few things out. I will update this forum, if I got some solution.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.