A Windows Server 2022 file server has begun crashing several times a day with a blue screen that shows the bug-check STOP 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA) and lists ntfs.sys as the faulting module. The crashes happen only when users copy large amounts of data, no new drivers or patches were installed, SMART reports no disk problems, and CPU temperature stays under 60 °C. Which action should you take next to confirm the most likely hardware cause of the blue-screens?
Update the server's UEFI firmware to the newest revision and then clear the CMOS settings.
Disable jumbo frames on the 10 GbE network adapter and install its latest driver.
Replace the system's primary SSD and restore the latest image backup.
Boot the server into Windows Memory Diagnostic and run the extended test suite.
Bug-check 0x50 indicates that the operating system tried to access invalid or corrupt memory. Microsoft documentation notes that defective RAM is a common root cause and specifically recommends running Windows Memory Diagnostic to verify physical memory. Because storage, CPU temperature, and recent driver changes have already been ruled out, testing the server's DIMMs is the most direct way to confirm or eliminate memory as the culprit.
Replacing the system SSD (option 2) targets disk corruption, which is not supported by SMART data or the error code. Adjusting network adapter settings and drivers (option 3) addresses potential NIC issues but would not produce 0x50 crashes tied to ntfs.sys. Updating firmware and clearing CMOS (option 4) may be done later, but first gathering evidence from a memory test follows the CompTIA troubleshooting methodology of forming and validating a theory before making changes.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What does the PAGE_FAULT_IN_NONPAGED_AREA (STOP 0x00000050) error mean?
Open an interactive chat with Bash
How does Windows Memory Diagnostic help identify defective RAM?
Open an interactive chat with Bash
Why is replacing the SSD or updating network drivers incorrect in this scenario?