Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer. For general blue screen troubleshooting information, see Blue Screen Data. Typically, the referenced address is in freed memory or is simply invalid.
This cannot be protected by a try - except handler -- it can only be protected by a probe or similar programming techniques. Use the! In this example Parameter 2 indicates that the bug check occurred when an area of memory was being read. 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. I recently created an image that we have used for about 50 Lenovo T Thinkpad laptops with Windows 7 Enterprise x This image was very simple: the OS as stated above , Office and all updates for Win7 and Office.
I also used the ThinkVantage System update to ensure I have the latest driver for everything in the system. I also flashed the BIOS to the current version. I have swapped out the hard drive to another working Lenovo and got the same issue. I ran a memory test came up clean , hard drive check came up clean.
I fully removed any anti-virus software to ensure that was not conflicting. In the last few days, three separate people have contacted our help center I work at a college saying their brand new thinkpad was suddenly blue screening with a 0x50 Page Fault In Non Paged Area and referenced NTFS. SYS they were all based on this image I created. All of these users were running fine when all of a sudden this started to happen. I spent all day researching the issue, trying to figure out what was causing it.
I verified again that all drivers were updated. I'm not saying these services have anything to do with it, but whatever the issue is, seems to be activated a lot sooner when those services are running.
I have many of these Lenovo laptops with the same base image that don't seem to have the problem yet , but I'm scared that since three have all reported the issue within week of them having it, that something is happening and causing it to break. Most of our users are pretty low end users, they are not installing a lot of things, just web, email and documents.
Thanks for any help you can provide! So this is very interesting, I just found out that my crashes seem to do with the System Volume Information folder. Obviously I lost any system restore points, but now the computer is fine. The question is, what messed up this folder in such a way that caused the computers to blue screen after days in the field?
We do use a backup program called "CrashPlan Pro" www. Once I "fix" the computer, it seems to be OK, at least for now. I guess time will tell if the issue comes back again. If so, not sure what to do long term to fix it or how to track down what is causing it. I guess I could disable system restore I don't really like that idea. I think this explains why the system would blue screen even when running the repair windows option, since that tries to access this System Volume Information folder.
Can you uninstall the ThinkVantage Active Protection program on one of the computers having the issue and see if the problem resolves? That the computer works in Safe Mode gives a good indication the problem is a third party driver that loads at startup. Can you first try a "clean boot" and see if that resolves the problem, if necessary configure the clean boot in Safe Mode:.
Download windbg just get one of the older versions instead of the whole WDK. Click or type '! You might get the answer.
I did more or less the steps listed in that Microsoft Article and seemed to narrow it down to the computer working fine if I disabled the "Microsoft Software Shadow Copy Provider" service and the "Superfetch" service.
I have to disable both to get it to be stable, if either one is active, the computer will blue-screen before I even get the full desktop loaded, or will reboot at the login screen if I just let it sit there.
I feel like in my testing one time it did give the blue-screen when I had those two services disabled, but I can't reproduce that now, so maybe I was confused. Since these are two microsoft services, I was not sure what to try next. I downloaded winbg I have never used it before, but I think I figured it out.
I don't see that it is giving me much useful information, but here is what it gave me if I ran it incorrectly, please let me know :.
Microsoft R Windows Debugger Version 6. All rights reserved. Loading User Symbols Loading unloaded module list Could not read faulting driver name Probably caused by : Ntfs. This cannot be protected by try-except, it must be protected by a Probe. This problem can be annoying, as it can appear temporarily repaired by an automatic restart. If left unresolved, this error may grow into bigger issues for your computer. In some cases, users encounter the Page Fault in Nonpaged Area within the minute they boot up.
This results in a harmful restart loop. Here are some of the adverse effects of this error:. Some of the errors you might see include the following:. If you want to fix Page Fault in Nonpaged Area error, keep reading this article and discover various solutions to this problem. Auslogics Driver Updater diagnoses driver issues and lets you update old drivers all at once or one at a time to get your PC running smoother.
With this method, your PC will be able to return to its recent settings before the error began to show up. Here are the steps:. Your computer should start with the settings in their last known good configuration. The Page Fault in Nonepaged Area error should temporarily stop. The command will check the disk for errors and fix any problems on your hard drive.
0コメント