Windows xp error page fault in nonpaged area

Fast Startup reduces Windows startup time. However, this feature might cause numerous blue or black screen problems on your Windows PC. You can try this method only when you can boot up your PC normally or you can boot into safe mode. After then, tap "Additional Power Settings".

Step 4: Click "Change settings that are currently unavailable". After then, uncheck "Tap on fast startup" and click the "Save changes" button. Below is how to increase virtual memory:. If drivers have compatibility issues, then you could encounter Windows page fault in Nonpaged error. To fix the error, you can try updating device drivers. Of course, this method is applicable when your PC can boot normally or you can boot into Safe Mode.

Step 2: Expand the right directory to locate the culprit driver. After then, you need to right-tap the driver and select "Update Driver". You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question 8. Report abuse. Details required :. Cancel Submit. Hope this information helps. How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site. I have not tried a BIOS update, but that certainly would make sense. I will do that later today. In reply to Ken Corp's post on March 30, I think all The Support Engineer did was just use Bing to search for 0x and then post the first Microsoft knowledgebase article that came up. As he rightly points out many people have issues with Norton. If you decide to uninstall keep in mind you'll have to then use their special Removal Tool for your version that Norton had to make special because even if you uninstall it the software leaves remnants of itself behind.

Yes, removal or reinstall of Norton is worth a try. However, now we know more about your PC Did you run memtest on individual sticks as instructed, and all passed??. That would be perfectly normal, BUT they might not work well together! I recommend you only use 2 of the identical ram sticks for a period of time several days if nothing happens. Even then, it will be worth while to run 2Gb for a period and see if the problem goes away.

Obviously, try the other pair then too Also the bios is very likely to be out of date. If you feel capable, go to the Dell update site, key in your PC identity code and ask for the latest bios. Then install it according to the instructions given when you unzip the package. Sorry, yet another point - Route44 asked you a very important question I am looking for 'added more ram' 'updated to SP3' 'installed norton ' and so forth. I see you claim no changes, but think hard!!

Or did you lose power or maybe lock up and have to shut down with the main power button? I thought I was supposed to get an email when someone responds to a post. After that I wall pull the two Kingston sticks. I will let my box run for a week and see what happens. I have another computer that I will use for that week, so we can solve this problem. I have done this several times before on many computers without any problems. The last time I checked which was not that long ago, I had the latest update.

If I still get the problems after this, I will uninstall Norton with the special removal tool. The local power grid is bad about going off for a few seconds and then turning back on. Thanks for both of your help. Look at all of the! If multiple dump files are available, compare information to look for common code that is in the stack. Use debugger commands such as use kb Display Stack Backtrace to investigate the faulting code.

Use the d, da, db, dc, dd, dD, df, dp, dq, du, dw Display Memory command to investigate the areas of memory referenced by parameter 1 and parameter 3. In this case doesn't look like there is data in this area of memory in parameter 1, which is the area of memory that was attempting to be read.

Use u, ub, uu Unassemble Dissasemble with parameter 3, to examine the which referenced the bad memory. For more information on X64 processor and assembly language see The x64 Processor. Use the r Registers command to examine what was being executed as the system bug checked. Driver Verifier is a tool that runs in real time to examine the behavior of drivers. For example, Driver Verifier checks the use of memory resources, such as memory pools. If it sees errors in the execution of driver code, it proactively creates an exception to allow that part of the driver code to be further scrutinized.

The driver verifier manager is built into Windows and is available on all Windows PCs. To start the driver verifier manager, type Verifier at a command prompt. You can configure which drivers you would like to verify. The code that verifies drivers adds overhead as it runs, so try and verify the smallest number of drivers as possible.

For more information, see Driver Verifier.