Question BSOD: "Page Fault in Nonpaged Area Windows 10 NTFS.sys" ?

johnny15

Distinguished
Mar 20, 2015
19
0
18,510
I recently upgraded my PC, and it has been functioning well for 20 days. However, I've encountered two blue screens with the following message: " Page Fault in Nonpaged Area Windows 10 NTFS.sys "

Do you have any ideas about what might be causing this problem? It appeared randomly, and I wasn't playing any games.
Update: I recently received a new blue screen "critical structure corruption" while installing a game in epic games.
I am really confused because I bought the CPU the RAM and the motherboard from a friend , and on his pc everything was working properly.
To avoid trouble I didn't remove them from his motherboard. I took the motherboard with everything installed on it and placed them in my pc.

My PC is this:
Motherboard: ASUS ROG MAXIMUS XII HERO (WI-FI)
CPU:Intel® Core™ i9-10900K
GPU:NVIDIA GeForce GTX 1060 6GB
RAM:G.Skill Trident Z Neo 32GB (2x16) DDR4 3600 (running speed at 3200)
PSU: Corsair RM850X 850W

Also I have a water cooler from corsair
OS: Windows 10 Pro 64 bit (Version 22H2 OS Build 19045.3803)

Thanks for your time

Giannis
 
I recently upgraded my PC, and it has been functioning well for 20 days.
What specs were you on prior to the upgrade? If you swapped the motherboard, you will need to reinstall the OS, after recreating the bootable USB installer for the OS using Windows Media Creation Tools.
 
My friend kept his drives + GPU.
I took his RAM, CPU, Motherboard and PSU, also formatted my main ssd and did a fresh install from zero.
I also have 1 HDD and 1 SSD as secondary storage options, but they don't have any Windows installed on them. I kept those intact.
 
I'm pretty sure that your problem is most likely to be bad RAM. A couple of those dumps even flag bad RAM in the triage analysis...
Code:
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
There are also many application errors in your Application log with memory (RAM) related exceptions (0xC0000005 for example) and several RADAR_PRE_LEAK_64 errors - these are also memory (RAM) related.

However, the other two dumps show that the BSOD occurred during drive access attempts - we see the Windows ntfs.sys driver called in both. It's thus possible that your problem isn't RAM but the system drive, and the apparent memory errors are actually pagefile errors.

I would suggest the first off you test your RAM...
  1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
  2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
  3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86, and do another four iterations.
This will find about 95% of RAM issues. Even a single bit error is a failure.

You don't say what system drive you have? We can't suggest a testing tool for your system drive until we know what make and model it is.
 
  • Like
Reactions: johnny15
These are my 3 drives. (info taken from speccy)
465GB Samsung SSD 860 EVO 500GB (SATA (SSD))
931GB Crucial CT1000BX500SSD1 (SATA (SSD)
1863GB Seagate ST2000DM008-2FR102 (SATA (SSD)))

The OS is installed on the Samsung, and the other two are just for storage; Crucial is for games, and Seagate is for movies, anime, etc.
Something I did not mention is that I am having trouble installing Nioh from Epic Games. More specifically, the installation takes way too long, and from 47 GB, it goes to 60 and then continues to increase.
I am not sure if it is related to the problem, but I wanted to inform you of that issue as well.
I will do the RAM test and reply. Also, something else that I forgot to tell you is that I had tweaked the virtual memory and the total paging size for all drives; someone said that it might fix the problem.
 
If the virtual memory tweak was to make the pagefile 1.5 times the RAM size then you were badly advised. That may have been useful in the XP days but it's no longer advised. Windows 10/11 manages virtual memory way better than XP (or 7) ever did. You should check the box to 'Automatically manage paging file size for all drives' and leave it at that.

Could you please enter the command msinfo32 into the Run command box. When the System Information dialog opens, click File > Save, pick a convenient folder and call the file msinfo (a .nfo suffix will be added). Upload the msinfo.nfo file to a cloud service with a link to it here. Be sure to make it public so we don't need to login to download it./
 
  • Like
Reactions: johnny15
The Windows memory diagnostic (which is not a very thorough tool) is detecting errors...
Code:
Log Name:      System
Source:        Microsoft-Windows-MemoryDiagnostics-Results
Date:          02/01/2024 17:09:11
Event ID:      1102
Task Category: None
Level:         Error
Keywords:     
User:          SYSTEM
Computer:      DESKTOP-O1ML7Q5
Description:
The Windows Memory Diagnostic tested the computer's memory and detected hardware errors. To identify and repair these problems, contact the computer manufacturer
Both test runs are the same. If the Windows memory diagnostic is reporting errors then you definitely have bad RAM or incompatible RAM and the only solution is to replace it.

Be sure to check that any new RAM you buy is on the QVL of your motherboard. I just did a quick search there for G.Skill 2x16 3600 RAM and found no hits. It's possible that your existing RAM isn't fully compatible with this board.
 
Some people say that it might not be compatible with my cpu also, which supports up to 2933MHz, I guess I will have to be careful of that also. The thing that bugs me though is why it didn't show blue screens on my friends computer who owned the same motherboard. But never mind I will have to check for a new set. By the way I did the tests you asked me with memtest86. When I had both sticks on slots A and B the test didn't complete (10000 errors). With 1 stick on slot A it showed 749 errors and with the other ram on slot A 10000 errors again. I haven't tested the slots B, C, D do you think I should? Or go straight for another set of Ram?
Thanks a lot for your patience and time 🙏😊
 
It's clear that your having memory problems and 99% of the time that's because the RAM is bad. You could try the RAM in other slots but on some boards the RAM must be in specific slots to function properly. You might as well try however, what do you have to lose?

If this were me I'd be buying new RAM, the chances of it being a slot problem are small.
 
  • Like
Reactions: johnny15