cancel
Showing results for 
Search instead for 
Did you mean: 

Asus Strix X470-F Gaming owners thread

AniChatt
Level 8
Hello guys, I am starting this thread for all Stix X470-F owners to discuss their overclock settings, issues etc. So that everyone get help quickly in a organised way. Installed my old 1600x in this mobo with 4011 bios and flareX 3200 with default docp and it works just fine without any issues so far. One thing to mention The board pushes 1.15v soc default docp profile. Is it normal seems a bit high for me as I have upgraded from B350-F gaming.
However a small issue I believe, the asus lighting control is not behaving normal. I mean just after login to windows it is taking a bit time to start (5min) before that if I try to on Lighting Control by clicking it, program crash window appears after few seconds. But when it starts on it's own then I can open asus lighting control. Anyone experiencing similar issue???
Also tried to use older version.
486 Views
2,438 REPLIES 2,438

Obt1mus
Level 9

Hi,

So i've been using that new BIOS version  (ROG STRIX X470-F GAMING BIOS 6063) for about a month now without issues. (r7 5800x + 3070ti)
Ram seems stable, using exactly the same OC as previous bios. 
Things I noticed, maybe faster experience overall, system feels a bit snappier on my end. 

The downside: 
Noticing very high cpu temps since i upgraded the bios. 
Idle about 40 degree Celsius,  gaming about 80 average, Max temp when stress testing or high cpu usage>>
92 degree. 
Overall i would say 5-10 degree more since i updated the bios. Anyone else experience that? 

Please share your experience too! Curious about your temps. 

Filters
Level 9

Im surprise from this mobo, i have it since my first 1600x then 2600x then 3600x and now whit a 5700g and i was also able to push ram to 3800c16 stable whit 1.4 volt 😄

Didnt think was even possible 

 

P.S.

Stable whit latest bios but had to format the drive after changing cpu

I also run cl16 3800 🙂 @1.43v
I started with a R5 3600 but was only able to do cl16 3600 on zen 2 

Knightpt
Level 7

Initialy had a 2600x and had ram @ DDR3200@CL14, then i upgraded to a 5600 and now have DDR3600@CL16-16-16, everything works fine for 4 years now. 

This is a good stable mobo. I will probably upgrade one last time in a few years for a 5800x3d as the last breath on this mobo, if it holds out that long that is. So far, so good. Can't beat this investment cost...

Hello jetherjr,

In the bios on the AI Tweaker tab, set the AI Overclock Tuner from Auto to X.M.P.

Hi....

Without success the problem continues I don't know what else to do... I've already reinstalled the updated windows drives, all the tests done by the CMD without finding any problems with the drives, I've bought new memories, I've already lowered the frequency of the memories, I've tested different VDP standby voltages and anything. I'm starting to believe the motherboard is having problems... since I bought this motherboard I can't access any games... always giving an error (System Service Exception). I already asked Microsoft for help, I posted my last minidunp and nothing was found... They told me to ask for help here on the ASUS Community Forum. I do not know what else to do.

any further help is welcome. I'm posting the link of my latest minidump files.

https://drive.google.com/drive/folders/1Ug4DKV3oR6hakq_TIsrmKBZKHCgR3yrL

Any

Filters
Level 9

I can agree, since I’m having water cooling loop on gpu and cpu, I was looking for a last upgrade the monoblock from EK

https://www.ekwb.com/shop/ek-fb-asus-strix-x470-rgb-monoblock-nickel?___store=default

 

But sadly is out of stock from a while ! 
Im also using a water temp sensor that work super good for setup fans in bios 

Price hurts tho but it's nice. Try Ali Express, usually cheaper and the quality is good depending on the shop. Recommend watching all reviews ^^ 

jetherjr
Level 7

Hello everybody !!!

Well, I've been trying to fix this blue screen for a while without success.
Less than a year ago I thought it was GPU problems so I bought another one, but the problem persists when I access Simulators, or games like DCS, IL2 and others.

I use an X470F-Gmaning Ryzen 7 2700 32Gb Hyperx HX426c16fb/16 Gigabyte RTX 3070Ti GPU.
I know that these memories are not on the QSL List and I believe that is the problem. But if possible, I would like your help to read the memory dump minidump file so that those who know can identify where the error really comes from.


Here's the link to the minidump file:

PS. I opted for the complete memory dump (I don't know if it's the right one)

https://drive.google.com/file/d/1FJZRo43zUNUHcp8VRPuODUS96R-Vb-a_/view?usp=share_link

Thanks and appreciate any and all help

 

What do I get from the minidump complete run file

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false

   - Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true


************* Waiting for Debugger Extensions Gallery to Initialize **************
.
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25324.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\052323-28734-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 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Kernel base = 0xfffff801`3fa00000 PsLoadedModuleList = 0xfffff801`40613490
Debug session time: Tue May 23 16:45:08.923 2023 (UTC - 3:00)
System Uptime: 0 days 0:55:41.579
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
...............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`3fe2be30 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffaf07`de563240=000000000000003b
8: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000006, Exception code that caused the BugCheck
Arg2: fffff8014018ec1c, Address of the instruction which caused the BugCheck
Arg3: ffffaf07de563b90, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*** WARNING: Check Image - Checksum mismatch - Dump: 0x19972, File: 0x246b4 - C:\ProgramData\Dbg\sym\bfs.sys\E766A3C214000\bfs.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3843

    Key  : Analysis.Elapsed.mSec
    Value: 4173

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Failure.Bucket
    Value: 0x3B_C0000006_nt!HvpGetCellPaged

    Key  : Failure.Hash
    Value: {68f3db38-ae8e-4bae-c37a-85819946495f}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000006

BUGCHECK_P2: fffff8014018ec1c

BUGCHECK_P3: ffffaf07de563b90

BUGCHECK_P4: 0

FILE_IN_CAB:  052323-28734-01.dmp

CONTEXT:  ffffaf07de563b90 -- (.cxr 0xffffaf07de563b90)
rax=000001d077df9000 rbx=0000000000f78478 rcx=000001d077df9478
rdx=ffffc48e83d97340 rsi=ffffaf07de564618 rdi=0000000000000000
rip=fffff8014018ec1c rsp=ffffaf07de5645b0 rbp=ffffaf07de564770
 r8=ffffaf07de56461c  r9=0000000000000178 r10=ffffc48e81e8f000
r11=ffffaf07de5645d0 r12=0000000000000001 r13=ffffc48e94660d10
r14=ffffc48e81e8f000 r15=ffffc48e879b2230
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
nt!HvpGetCellPaged+0x7c:
fffff801`4018ec1c 8b01            mov     eax,dword ptr [rcx] ds:002b:000001d0`77df9478=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Registry

STACK_TEXT:  
ffffaf07`de5645b0 fffff801`4018e8ec     : 00000000`00000000 00000000`00000000 ffffaf07`de564770 fffff801`3fc34379 : nt!HvpGetCellPaged+0x7c
ffffaf07`de5645e0 fffff801`4018e616     : ffffaf07`de564770 ffffc48e`94660d10 ffffaf07`de564820 00000000`00000000 : nt!CmpFindNameInListFromIndex+0x7c
ffffaf07`de564670 fffff801`4009f101     : 00000000`00000008 00000000`00000000 00000000`00000000 ffffc48e`879aec01 : nt!CmQueryValueKey+0x1e6
ffffaf07`de5647a0 fffff801`3fe40be8     : 00000000`00000000 00000000`00000000 00000000`00000001 000000f5`0fefeb60 : nt!NtQueryValueKey+0x541
ffffaf07`de564a70 00007ffc`6952ef34     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000f5`0fefe6f8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`6952ef34


SYMBOL_NAME:  nt!HvpGetCellPaged+7c

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1680

STACK_COMMAND:  .cxr 0xffffaf07de563b90 ; kb

BUCKET_ID_FUNC_OFFSET:  7c

FAILURE_BUCKET_ID:  0x3B_C0000006_nt!HvpGetCellPaged

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {68f3db38-ae8e-4bae-c37a-85819946495f}

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

Try a few things, first - Go into BIOS and disable XMP. See if that fixes the issue. If it doesn't, try these steps.

Second, run cmd. Click Start - Type CMD - Right-click and run as administrator - Type sfc /scannow and allow that to work. If it fixes corrupted fixes, reboot, then try gaming again. Let us know what happens.