Overclock.net banner

1 - 13 of 13 Posts

·
Registered
Joined
·
51 Posts
Discussion Starter · #1 · (Edited)
Hey guys I was downloading something on steam and using chrome, and then all of a sudden my PC blue screened. And I got the error:

PAGE_FAULT_IN_NONPAGED_AREA

Please see the image below.

I have not made any recent changes to my system (Hardware or software overclock)

My specs are:

  • Asus Dark Hero Motherboard
  • Ryzen 5950X
  • Asus Rog Strix 3090
  • GSkill 3800 CL14 Ram (4X8GB) 32 GB
  • Western Digital M.2

Any idea what causes this error? And what I can do?

I’m currently running my GSkill 3800 ram at 3800mhz, 1900 FCLK with a mild overclock (just dropping the voltage from the advertised 1.5v to 1.38v and tightening some of the timings)
I have tested the overclock extensively for stability with TM5 etc and it should be stable. I have been running the same setting for about 2 months with no previous crashes or issues.

After the BSOD I ran CHKDSK, Windows Memory Diagnostic tool and did a SFC scan. All reported back with no errors.

Here are my Minidump files. If anyone could take a look at them to help me diagnose the issue that would be great!

Minidump files

any help would be greatly appreciated!


2488732
 

·
Senior OCN Member
Joined
·
41,072 Posts
Just because you get a single BSOD does not mean there is anything wrong with your hardware BSOD´s can be caused by a million things
The error you are getting can be any number of things so if it has only happen once just ignore it

If its a common problem that happens often then there might be a hardware problem but even than its often a software problem
 
  • Rep+
Reactions: Bravoroni

·
Registered
Joined
·
51 Posts
Discussion Starter · #3 ·
Hey thanks so much for your reply. Ok I will keep an eye on things, and hopefully this is just a one off occurrence.
 

·
Registered
Joined
·
394 Posts
I had a few of these when I upgraded my CPU/Motherboard... After awhile, they never came back. Maybe it's the windows updates... I'm not totally sure
 

·
Registered
Joined
·
51 Posts
Discussion Starter · #5 ·
Thanks for the reply. Yeah I’m praying it doesn’t happen to me again, and that it’s just a one time occurrence.

I will keep you guys updated if it happens again.

thanks so much!
 

·
Registered
Joined
·
158 Posts
It's most likely ram related, go into your bios and set ram voltage manually, if using xmp profile set it to whatever is printed on the label on the ram module. You said you've undervolted from the printed voltage? If so that could be your issue.

Try 1.45v with vref 0.725v for both channels or if that doesn't work go with the printed 1.5v and 0.75 vref. If your mobo boosts ram voltage like mine does you need to set it a bit lower, for example if I set 1.38v it runs at 1.4v so for 1.45 you'd set 1.43v with the vref 0.725

With 4 sticks you need a bit more juice, it's likely that you're using more ram now and your system is using another module and I'm guessing you're getting the bsod because there's not enough voltage to run multiple modules at once.
 

·
Premium Member
Joined
·
10,125 Posts
I personally wouldn't advise lowering RAM voltage for the sake of anything. The power savings are nil, the increase in potentially lapsing stability is higher, and when you are running a full set of DIMMs you should be sure to test even more so than you would a two-module kit because of the increased demand on the memory controller.

FWIW~
 

·
Registered
Joined
·
51 Posts
Discussion Starter · #8 ·
Thanks for all the replies! I will definitely try and raise my voltage to around 1.475 - 1.500
 

·
Senior OCN Member
Joined
·
41,072 Posts
Dont do anything unless you get the same error again
If you do then you can try stuff
 

·
Registered
Joined
·
51 Posts
Discussion Starter · #10 ·
Yeah, so far it’s been good. So in just gonna leave it. If I get another BSOD then I’ll work on the RAM voltage to see if that helps. Thanks again!
 

·
Overclock.net user
Joined
·
455 Posts
Following the debug files, the file that have the error was dxgmm2.sys and seems related to the graphic card and the directX.
This is the debug:
Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Lic\Desktop\Minidump\042621-7531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


* Path validation summary **
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`60c00000 PsLoadedModuleList = 0xfffff801`6182a3d0
Debug session time: Mon Apr 26 15:00:59.774 2021 (UTC + 2:00)
System Uptime: 0 days 1:46:56.365
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
.....
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`60ff5e40 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe204`327b6170=000000000000001e
14: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8017386a79d, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000011, Parameter 1 of the exception

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3749

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 29217

Key : Analysis.Init.CPU.mSec
Value: 624

Key : Analysis.Init.Elapsed.mSec
Value: 43529

Key : Analysis.Memory.CommitPeak.Mb
Value: 79

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8017386a79d

BUGCHECK_P3: 0

BUGCHECK_P4: 11

READ_ADDRESS: fffff801618fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000000011

EXCEPTION_PARAMETER2: 0000000000000011

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Overwatch.exe

TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
ffffe204`327b6168 fffff801`6109177f : 00000000`0000001e ffffffff`c0000005 fffff801`7386a79d 00000000`00000000 : nt!KeBugCheckEx
ffffe204`327b6170 fffff801`61007eac : 00000000`00001000 ffffe204`327b6a10 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x166d1f
ffffe204`327b6830 fffff801`61004043 : ffffe204`327b6a50 00000000`00000000 00000000`00000081 00000000`00000000 : nt!KiExceptionDispatch+0x12c
ffffe204`327b6a10 fffff801`7386a79d : 08ffffe2`04327b6d 00000000`00000000 b0000000`00000000 60ffffba`0469ccfc : nt!KiPageFault+0x443
ffffe204`327b6ba1 00000000`00000000 : 04ffffe2`04327b6e 08000000`00000000 01ffffe2`04327b6e 10000000`00000000 : dxgmms2!VidSchSubmitSignalToHwQueue+0x31d


SYMBOL_NAME: dxgmms2!VidSchSubmitSignalToHwQueue+31d

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.928

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 31d

FAILURE_BUCKET_ID: 0x1E_c0000005_R_dxgmms2!VidSchSubmitSignalToHwQueue

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b8e2015b-de1e-f5c4-6382-3339fce5aa6a}

Followup: MachineOwner
---------
 

·
Registered
Joined
·
51 Posts
Discussion Starter · #12 ·
Thanks for the info, but what does that mean? Do I need to reinstall directX? Is it an issue with my GPU? Or is it just something that happens?
 

·
Premium Member
Joined
·
10,125 Posts
Debug files can pinpoint the driver/related system files (DX) but that doesn't mean it wasn't triggered by bad data (RAM). Just FYI~
 
1 - 13 of 13 Posts
Top