Page Fault In Nonpaged Area Windows Xp Solved Assignment

Page fault in nonpaged area endless loop

12 answers Last replyBest Answer
More aboutpage fault nonpaged area endless loop
  1. Try running http://www.memtest86.com/ on ram, its slightly more scientific

    page faults are memory errors which might be hardware or just as likely old drivers. Download Live Update 6 and run it to see what drivers need replacing: Win 8 drivers (yes, I know, its win 10 but motherboard doesn't appear to have win 10 drivers so these will do)

    download and run who crashed: http://www.resplendence.com/whocrashed
    it looks at bsod and gives a summary

    copy/paste here
  2. If you aren't able to boot into Windows, even in safe mode, you might try booting from the install disk and repairing your system.
  3. Try F8 then log on onto windows, run msconfig then click on the startup tab. uncheck any program(s) that you don't know (maybe dump..). Then right click on Computer-->properties-->Advance-->At the performance, click settings-->Advance-->At Virtual Memory, click change-->uncheck Automatically-->select c:\ drive-->select system manage-->click on set-->ok, restart computer.
  4. Thanks for the quick replies guys. Unfortunately the system will not let me get into my home page to try what colif suggested, I am currently attempting a system restore to see if that helps. If it does not then I will try the other two suggestions. I will keep you posted. I'm starting to think I will just have to replace my system, however I'd like to know if I have to replace everything or if there are some things I can keep?
  5. On another PC, download the Windows 10 media creation tool and use it to make a win 10 installer on USB
    change boot order so USB is first, hdd second
    boot from installer
    on screen after languages, choose repair this pc, not install.
    choose troubleshoot
    choose advanced
    choose command prompt
    type chkdsk /f /r C: and press enter - this will fix errors on hdd

    Page file errors either drivers, hdd or possibly ram. its hard to tell without a dump file.

    the non paged area is generally ram, the paged area is hdd if I not mistaken. IT doesn't mean problem is hardware though, it can be drivers as I said.
  6. Try running http://www.memtest86.com/ on ram, its slightly more scientific

    page faults are memory errors which might be hardware or just as likely old drivers. Download Live Update 6 and run it to see what drivers need replacing: Win 8 drivers (yes, I know, its win 10 but motherboard doesn't appear to have win 10 drivers so these will do)

    download and run who crashed: http://www.resplendence.com/whocrashed
    it looks at bsod and gives a summary

    copy/paste here


    Crash dump directory: C:\WINDOWS\Minidump

    Crash dumps are enabled on your computer.

    On Tue 9/27/2016 6:49:16 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\092716-29078-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0B0)
    Bugcheck code: 0x50 (0xFFFFF800C748EA70, 0x10, 0xFFFFF800C748EA70, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Tue 9/27/2016 6:49:16 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: dtldrvprotect64.sys (DtlDrvProtect64+0x6EAE)
    Bugcheck code: 0x50 (0xFFFFF800C748EA70, 0x10, 0xFFFFF800C748EA70, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: dtldrvprotect64.sys .
    Google query: dtldrvprotect64.sys PAGE_FAULT_IN_NONPAGED_AREA


    What is dtldrvprotect64.sys ?
  7. I'm kind of scared of restarting my computer. It finally let me in. I've been on for about 25 mins and so far it hasn't crashed. Should I try the other suggestions mentioned above?
  8. The first dump is a general system fault that could be caused by any number of things. The second references a process related to the program DriveTheLife. I have no idea what this software is or does (driver updates?) but I would start by uninstalling it. As long as the PC is running, I would also run Malwarebytes and a couple of online virus scans and go from there.
  9. its one of those driver updaters, which are really good at getting the wrong drivers. Yes, they make it easy to get driver updates without looking yourself but they not always right with their choices.
  10. Thanks for the help everyone. It just kicked me off mid malware bytes scan. However this time it is letting me back in. I will try to run malawarebytes once more and see what's going on... Nope it just kicked me off again almost immediately after loading in
  11. Best answer
    If you do have a driver updater, then you probably have an issue with a bad drivers as Colif pointed out above. If you can keep it running long enough, reinstall the motherboard drivers from MSI's website and check to see if you have the latest AMD graphics driver.

Read More

scrippie10
My computer keeps crashing and I keep getting "Your PC ran into a problem and needs to restart. We're just collecting some error info, and then we'll restart you."

Page fault in nonpaged area

I have a feeling my computer is done for, I'm trying to restart and pressing f8 to follow the steps provided on the page shown below to fix the issue, but I have gotten the same loop of error message>restarting>error message>restarting etc for the past 45 mins. I can't seem to get out of the loop.

http://www.technicalnotes.org/how-to-fix-page-fault-in-nonpaged-area-best-fixes/

My question is, should I replace everything or are there any parts that I can keep to save $$

These are my specs:
CPU - AMD FX-6300 3.5GHz 6-Core Processor
Mother board - MSI 970A-G43 ATX AM3+ Motherboard
Memory - G.Skill Ripjaws X Series 8GB (2 x 4GB) DDR3-1600 Memory
Storage - Western Digital Caviar Blue 1TB 3.5" 7200RPM Internal Hard Drive
Video Card - MSI Radeon R9 280 3GB TWIN FROZR Video Card
Case - NZXT Source 210 Elite (White) ATX Mid Tower Case (Came with 1 fan)
Power Suply - Corsair CX 500W 80+ Bronze Certified Semi-Modular ATX Power Supply

Or if you can tell me how to fix the issue that would be even better however, that's not looking likely

PS. I removed the RAM and reinserted it, however that did not help. I'm pretty sure its the drivers that are the issue but I can't load in to fix them.

I appreciate the help!
  • © 2018 Purch All Rights Reserved.

Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA

  • 2 minutes to read
  • Contributors

The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This indicates that invalid system memory has been referenced. Typically the memory address is wrong or the memory address is pointing at freed memory.

Important This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

PAGE_FAULT_IN_NONPAGED_AREA Parameters

1

Memory address referenced

2

0: Read operation

1: Write operation

3

Address that referenced memory (if known)

4

Reserved

If the driver responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver.

Cause

Bug check 0x50 can occur after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another possible cause is the installation of a faulty system service or faulty driver code.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Resolution

Gather Information

Examine the name of the driver if that was listed on the blue screen.

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time window as the blue screen.

Windows Memory Diagnostics

Run the Windows Memory Diagnostics tool, to test the memory. Click the Start button, and then clicking Control Panel. In the search box, type Memory, and then click Diagnose your computer's memory problems.‌ After the test is run, use Event viewer to view the results under the System log. Look for the MemoryDiagnostics-Results entry to view the results.

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.

Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, investigate the Windows repair options. For more information, see Recovery options in Windows 10.

Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update.

Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. Contact the manufacture of the hard driver system to locate any diagnostic tools that they provide for the hard drive sub system.

For general blue screen troubleshooting information, see Blue Screen Data.

Typically, this 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.

0 thoughts on “Page Fault In Nonpaged Area Windows Xp Solved Assignment

Leave a Reply

Your email address will not be published. Required fields are marked *