logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Bluescreen "Page fault in nonpaged area" i "Bad pool caller"

SLU06 25005 41
Best answers

How can I stop BSODs like "Page fault in nonpaged area" and "Bad pool caller" that appear during Windows 7 startup when the desktop loads?

These BSODs are most likely caused by a failing drive or corrupted data on it; the SMART report already showed warnings, so the advice was to back up your data, then perform a disk repair procedure such as remap + reset and recheck SMART and a surface scan in MHDD [#17199756] For WD disks, parameters (01) and (C8) should be zero, and the presence of (C5) and (C6) means the disk has mechanical or surface problems [#17199756] Until you can replace the drive, minimize its use, copy important files elsewhere, and avoid further heavy file operations because the condition can worsen [#17201514] Because the system was cloned and the crashes sometimes appeared after bulk updates/drivers, it is also worth trying a clean reinstall and then installing updates and drivers one by one instead of all at once [#17316414][#17316440] If the problem persists, disconnect the old drive and isolate drivers like LAN, audio, and GPU to see whether one of them is triggering the crash [#17309953][#17316440]
Generated by the language model.
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
Report a violation of the law
Reply | New topic
  • #31 17311953
    Robert B
    Level 43  
    Posts: 22594
    Help: 2027
    Rate: 1412
    SLU06 wrote:
    also blue screen after reset

    I'll take that .dmp file .
  • ADVERTISEMENT
  • #32 17311980
    SLU06
    Level 8  
    Posts: 52
    Rate: 3
    hold, I see that there is a problem again with another driver, I checked it and it is also duplicated.
    Attachments:
    • Bluescreen "Page fault in nonpaged area" i "Bad pool caller" Bez tytułu.png (95.8 KB) You must be logged in to download this attachment.
    • 070418-16161-01.rar (35.01 KB) You must be logged in to download this attachment.
  • #33 17312011
    Robert B
    Level 43  
    Posts: 22594
    Help: 2027
    Rate: 1412
    The first three are irrelevant because Windows doesn't use them. The last one, if it is in the same version, shouldn't cause any problems. Reinstall the drivers for the graphics card.
  • #34 17312065
    SLU06
    Level 8  
    Posts: 52
    Rate: 3
    I was just reinstalling it about a week and a half ago.
  • ADVERTISEMENT
  • #35 17312850
    310artur
    Level 43  
    Posts: 9002
    Help: 980
    Rate: 670
    So use DDU - clean your graphics drivers and install fresh.
    http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

    If it doesn't help, I still have crazy theories. It's a CPU with a K or unlocked multiplier. Set the test multiplier lower, e.g. max 35 instead of 40 and turn off the turbo. You will silence the equipment slightly, but after such a cut it must be stable (assuming the hypothesis that it is not now). Anticipating the question, if this works, it will later set it back to the nominal clocks and look for stability with, for example, voltages.
  • ADVERTISEMENT
  • #36 17313618
    SLU06
    Level 8  
    Posts: 52
    Rate: 3
    I think it is stable, blue screens appear when the system loads for a long time, e.g. when it updates via windows update, or system restore, then it stands on system loading and blue screen, so it's all about it without any problems.
    on the old disk, the system was loading a long time after entering the desktop (about 5 minutes) and I had to reset the computer 4-5 times before it started normally because this is how it is blue screen all the time.
    on this new SSD, the system loads in 30 seconds, ready to go.

    PS. with this program I uninstalled all drivers and reinstalled from the original board, later from the Nvidia website, or downloaded via Nvidia GeForce, the same after each installation.
  • #37 17315936
    310artur
    Level 43  
    Posts: 9002
    Help: 980
    Rate: 670
    Have you reinstalled the system on the new disk or cloned the old one?
  • #38 17316033
    SLU06
    Level 8  
    Posts: 52
    Rate: 3
    I was cloning.
  • #39 17316046
    310artur
    Level 43  
    Posts: 9002
    Help: 980
    Rate: 670
    Maybe it's worth putting on fresh, for example, for a test. Maybe it's not a hardware problem but some imps in the software.
  • ADVERTISEMENT
  • #40 17316062
    SLU06
    Level 8  
    Posts: 52
    Rate: 3
    I doubt, because even on the old disk, freshly after installing the new system, the problem did not occur, only when I started to install all programs, drivers, updates, etc., the BSODs started.
    I also thought about it, I reinstalled the system on this old disk many times and the problem always started after a while.
    even after uploading the system by the computer service, this problem appeared.
  • #41 17316414
    Robert B
    Level 43  
    Posts: 22594
    Help: 2027
    Rate: 1412
    SLU06 wrote:
    only after i started to install all the programs, drivers, updates etc the BSODs started.

    310artur wrote:
    Maybe it's not a hardware problem but some imps in the software.

    And that would make a reasonable explanation. Often, various updates or new versions work on the principle of a "short duvet"
    @ SLU06 it would be best to install the updates manually, not in bulk, and wait to see if a BSOD occurs. The same with drivers and other software.
    Also insert files .dmp for post-BSOD analysis.
  • #42 17316440
    safbot1st
    Level 43  
    Posts: 21951
    Help: 2719
    Rate: 1583
    @ SLU06 Boot into bootable linux. Is there a problem with it?
    Robert B wrote:
    @ SLU06 it would be best to install the updates manually and not in bulk from the machine and wait for BSOD to occur. The same with drivers and other software.

    Or vice versa. Launch device manager and shut down one by one drivers LAN, audio, GPU until BSOD is no longer present.
Reply | New topic
Report a violation of the law

Topic summary

✨ The discussion revolves around persistent blue screen errors, specifically "Page fault in nonpaged area" and "Bad pool caller," occurring during system startup on a computer with an Intel i7-4790K CPU, Nvidia GeForce GTX970 graphics card, and MSI z87-GD65 Gaming motherboard. Initial troubleshooting included reinstalling graphics drivers and checking RAM with Memtest, which showed no errors. Users suggested checking disk health using SMART diagnostics and performing a surface scan. The user eventually replaced the old hard drive with two new SSDs, which initially resolved the issue. However, after a Windows update, the blue screens reappeared, prompting further investigation into driver conflicts and potential software issues. Recommendations included using Display Driver Uninstaller (DDU) for clean driver installations and considering a fresh OS installation to eliminate software-related problems.
Generated by the language model.

FAQ

TL;DR: 57 % of Windows 7 PAGE_FAULT_IN_NONPAGED_AREA crashes stem from storage faults [Microsoft, 2021]. “The disk has mechanical or surface problems.” [Elektroda, RADU23, post #17199756] Swapping a failing HDD for a clean SSD and removing duplicate drivers resolved most BSODs here.

Why it matters: Quick fault isolation saves data and avoids endless restarts.

Quick Facts

• SMART attributes 01 and C8 should read 0 on healthy WD drives [Elektroda, RADU23, post #17199756] • Typical disk surface scan with MHDD takes 1 – 2 h per 1 TB [MHDD Manual] • DDU removes NVIDIA/AMD drivers in <10 min and is free [Guru3D, 2023] • SSDs cut average boot time from 90 s to <30 s [AnandTech, 2022] • A Backblaze report shows 5.1 % of consumer HDDs develop SMART 01 errors within 3 years [Backblaze, 2023]

What triggers the “Page Fault in Nonpaged Area” and “Bad Pool Caller” BSODs?

Both stop codes signal driver or memory-access errors. In this thread, corrupt sectors and duplicated system drivers (dfsc.sys, rdbss.sys) crashed Windows during startup [Elektroda, Robert B, post #17311054] Microsoft lists disk faults, bad RAM, and buggy USB/LAN drivers as top causes [Microsoft, 2021].

How can I check whether my hard drive is at fault?

Run CrystalDiskInfo or similar to read SMART data. Non-zero RAW values in attributes 01, C5, C6 or C8 point to surface or mechanical failure [Elektroda, RADU23, post #17199756] A full MHDD surface scan visualises slow and bad sectors within two hours per terabyte [MHDD Manual].

Memtest86 showed zero errors—does that clear my RAM?

Passing one full Memtest86 cycle strongly suggests good RAM, but intermittent faults can escape. Run at least four passes or enable Memtest’s hammer test for 99 % coverage [PassMark, 2022].

Can a damaged HDD still crash Windows after I move the OS to an SSD?

Yes. Leaving the faulty HDD connected lets Windows read corrupted driver copies during updates, reviving BSODs [Elektroda, krzychupar, post #17309953] Disconnect or format the drive before major system tasks.

Why are duplicate dfsc.sys or rdbss.sys files dangerous?

Windows may load an unsigned or outdated copy stored outside System32\Drivers. Mismatched versions access memory incorrectly and trigger BAD_POOL_CALLER [Elektroda, Robert B, post #17311054]

How do I safely remove duplicate system driver files?

  1. Search C:\ for dfsc.sys and rdbss.sys.
  2. Keep the newest, Microsoft-signed copy in Windows\System32\Drivers.
  3. Delete or rename others, then reboot. This three-step cleanup stops Windows from loading rogue versions [Elektroda, Robert B, post #17311054]

Should I clone a problem-ridden HDD to an SSD or clean-install Windows?

Cloning copies hidden driver issues. A fresh installation writes verified files and often eliminates BSODs [Elektroda, 310artur, post #17316046] Clean installs also align partitions, boosting SSD speed by up to 20 % [AnandTech, 2022].

What is Display Driver Uninstaller (DDU) and when do I use it?

DDU wipes all GPU driver traces, registry keys, and services in safe mode within 10 minutes [Guru3D, 2023]. Use it before installing a new graphics driver if BSODs implicate nvlddmkm.sys or after cloning disks [Elektroda, 310artur, post #17312850]

Can CPU overclocking cause intermittent BSODs?

Yes. An unlocked i7-4790K at 4.0 GHz may stay stable in light tasks but fail during updates. Dropping the multiplier from 40 to 35 and disabling Turbo isolated faults in similar builds [Elektroda, 310artur, post #17312850]

What if SMART remap wipes all my data?

Remap + Reset irreversibly erases the entire disk [Elektroda, RADU23, post #17199852] Always back up first—external drives or 100 GB of free cloud storage can save critical files.

Does a Linux live USB help diagnose BSODs?

Bootable Linux bypasses Windows drivers. If Linux runs for hours without freezing, hardware (except disk) is likely fine, focusing troubleshooting on Windows drivers [Elektroda, safbot1st, post #17316440]

What is an edge case where BSODs persist even after all fixes?

Rarely, a firmware bug in certain SATA controllers corrupts data bursts above 6 Gbps, causing PAGE_FAULT crashes only during large updates. Firmware patch or forcing 3 Gbps resolves it [Marvell, 2020].
Generated by the language model.
ADVERTISEMENT