Windows 10: I always gets memory management when i play valorant?? Why

The pc works good in 2 week then it has some error and always gets memory management when play valorant

:)

 

Valorant BSOD - Error Code: Page Fault In Nonpaged Area

Hi, yesterday I started getting BSOD when Trying to play Valorant, it seems to be a Memory related issue. I've tried every possible solution so far but I´d like to see if anyone can help me with this.

• When does this happen ?
  
  • When trying to play the game, during gameplay my monitors will turn almost black with high contrast and freeze for a few seconds before restarting my PC.
    
• What Code does Windows Reliability Monitor show ?
  
  • Code: 0x00000050
    
• My Dump Files:
  
  • 121522-12234-01.dmp
    

So far I´ve tried:

1. Giving vgk.sys access to everything
   
2. Setting Valorant to "Run as Administrator"
   
3. Reinstalling Valorant
   

Things I haven't checked:

1. Re inserting RAM sticks
   

EDIT: This is only happening with Valorant, no other game is giving me the same problem, so I assume re installing the Ram will not have much of an effect.

 

BSOD- memory management

Upon checking the dump file, the issue is being caused by ntoskrnl.exe. Ntoskrnl.exe is the one responsible for memory management that is why you're having the Memory Management error. We suggest that you follow the steps found in the link that we provided
in our last reply to resolve the issue. Please take note that if you're overclocking your processor or video card, kindly reset their settings to default.

Let us know the outcome after performing the provided steps.

 

Memory management

Hi Daniel,

Missing/outdated driver and error with your PC memory (RAM) are some of the factors that may cause the blue screen due to Memory Management error. To effectively assist you with your concern, we'd like to ask the following:

• Have you made any recent changes on your device prior to your concern?
• What are other troubleshooting steps have your performed to resolve your concern?

While checking for the dump file that you've sent, we suggest that you run a full scan on your device using the
SFC and DISM command to automatically fix any corrupted files that my possibly trigger the error. The steps can be found on this

Wiki Article created by community MVP ZigZag3143. Once you're done, check if the issue persists.

We'll appreciate if you can send us an update.