PAGE_FAULT_IN_NONPAGED_AREA While Loading Halo: MCC

Hello all,

I got this BSOD when loading Halo: MCC.

I had connected my laptop to my TV via HDMI to play the game on the big screen using my XBOX One controller through bluetooth. I loaded up the game, and closed the display to make everything go on the TV, which I have done a number of times without an issue. This was when I got the BSOD.

The laptop restarted, I tried loading it up again and doing the same thing, worked fine.

I keep the laptop clean and free of dust. I use HWMonitor to watch the temps. CPU temps were on the high side (75-85C, but no higher) but seemed to be fine still. They are always at this level when playing Halo: MCC or Forza Horizon 4.

This is the first and only time Ive seen this BSOD so its likely just a hiccup. I would still like to know what happened, however.

Laptop specs are filled out. It is the first machine listed. The Precision 3520.

Windows version 21H1 BUild 19043.899

DESKTOP-HO566J5-(2021-04-04_13-31-08).zip

philc43 said:

Are you on an insider build? 21H1 is not yet released to the general public.

The problem that this causes is that the symbols are not yet available for debugging the crash dumps. I would report the crash to Microsoft in the Feedback Hub for now.

Crap, I didnt think about that. Ill have to do that, then. Ill keep an eye on it to see if it does it again. Its been fine since.

RJARRRPCGP said:

That stop code, usually means unstable RAM.

It's time to start a RAM test (A.K.A. memtest) (A.K.A. Windows Memory Diagnostic, IIRC) to check for faults, whether it's the actual RAM, the RAM slot(s) or on-die RAM controller on the CPU.

(I have such problem, with the same stop code on my socket 1366 system and it looks like a problem with the black RAM slot(s). ) (But that one has Windows 7)

I was wondering about a RAM issue as well, but I havent run a memtest yet. I, however, did run a stress test with AIDA64 on the CPU, GPU, RAM, and FPU for an hour and never had an issue. I still havent seen another BSOD happen, so hopefully it was a random hiccup that caused it.

0x50 has many different causes and drivers are quite common, more common than bad memory so RAM wouldn't be the first thing I'd focus on. If the crashes recur, consider what Philc34 mentioned, report it to Microsoft first.