10-04-2022 06:30 AM - last edited on 12-02-2024 10:18 PM by Silent_Scone
ill use this thread to collect some new test bioses for the boards, maybe also to explain some less understood options
to disable cores ccd go here and choose ccd xx bit map down core.
each ones stand for an enabled core
best to disable from the back, ie:
110000
instead of 0011000
after selection press downcore apply changes or discard if made mistake
ocpak/octools
FAQ:
7950x not boosting pass 5.5G -> check that CStates is not disabled
Detailed Explanation on CState Boot Limiter
Test BIOSes:
new:
X3D OC Preset for those MB with asynch BCLK Support: (for simple slight perf boost for X3D)
DOCP/EXPO Tweaked: (for simple timings tightening)
strixe-e 1515
for crosshair and strix e-e:
explanation of segment2 Loadline:
customize a heterogenous loadline for a dual segment workload range.
example above shows loadline=L6 when current is in range of 0~40A, and Level4 when current is above 40A.
Adds for x3d
dynamic ccd priority switch with core flex, os / driver agnostic so win10 win11 ok
Algo as follows:
If condition reached and ccd0 specified, then check current mem/cache activity > threshold and hysteresis reached, if fulfilled then switch
If condition reached and ccd1 specified, then check current mem/cache activity <=threshold and hysteresis reached,, if fulfilled then switch
Default hysteresis =4
Can combine multiple algos for ccd priority so combinations are wide
works on non x3d too but of course senseless on it. detailed explanation here.
Solved! Go to Solution.
01-16-2025 12:56 AM
your missing the asmedia usb 4 host hub and root hub ...
try installing the usb drivers
01-16-2025 02:36 AM
Hi, where I can find these drivers?
01-16-2025 03:00 AM
This is caused by firmware not driver, install all USB related FW on boards page under BIOS downloads.
01-16-2025 05:41 AM - edited 01-16-2025 06:20 AM
I have already installed all USB related FW on boards page under BIOS downloads, but nothing changes, the USB error is still there...
I own a ROG CROSSHAIR X670E HERO.
01-16-2025 05:48 AM
Well i had exact same error and FW solved it, make sure it actually ran, did tool open and it showed successful flash and asked for reboot?Also there are 4 different FW files to flash, atleast for my board (ROG STRIX X870-F GAMING WIFI).
01-16-2025 03:52 PM
My computer rebooted from a bugcheck, I believe this might be related to idle states / failure to enter sleep mode?
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000004, 0x0000000000000258, 0xffffe40f7497e300, 0xffffcd04130572a0).
I'm using BIOS Version 3201 (beta) on a X670E-I
Chipset 7.01.08.129 (the one shared by SAFEDISK in this thread)
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42
Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\011625-12281-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 26100 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff804`efc00000 PsLoadedModuleList = 0xfffff804`f0af4870
Debug session time: Thu Jan 16 18:02:33.664 2025 (UTC - 5:00)
System Uptime: 0 days 9:14:03.527
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`f00b85d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffcd04`13054b00=000000000000000a
16: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: ffffe40f7497e300, The thread currently holding on to the Pnp lock.
Arg4: ffffcd04130572a0, nt!TRIAGE_9F_PNP on Win7 and higher
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for amdfendr.sys
Implicit thread is now ffffe40f`7497e300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1093
Key : Analysis.Elapsed.mSec
Value: 4530
Key : Analysis.IO.Other.Mb
Value: 20
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 25
Key : Analysis.Init.CPU.mSec
Value: 437
Key : Analysis.Init.Elapsed.mSec
Value: 7268
Key : Analysis.Memory.CommitPeak.Mb
Value: 92
Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000
Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2408.27.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x9f
Key : Bugcheck.Code.TargetModel
Value: 0x9f
Key : Dump.Attributes.AsUlong
Value: 31808
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: 0x9F_4_amdfendr!unknown_function
Key : Failure.Hash
Value: {8a421ea4-a07b-a3dd-525a-7b642e7361eb}
Key : Hypervisor.Enlightenments.ValueHex
Value: 7497cf94
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 1
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 38408431
Key : Hypervisor.Flags.ValueHex
Value: 24a10ef
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 3f7
BUGCHECK_CODE: 9f
BUGCHECK_P1: 4
BUGCHECK_P2: 258
BUGCHECK_P3: ffffe40f7497e300
BUGCHECK_P4: ffffcd04130572a0
FILE_IN_CAB: 011625-12281-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x31808
Kernel Generated Triage Dump
FAULTING_THREAD: ffffe40f7497e300
DRVPOWERSTATE_SUBCODE: 4
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffcd04`13054af8 fffff804`f028dce9 : 00000000`0000000a 00000000`00000300 00000000`000000ff 00000000`000000e0 : nt!KeBugCheckEx
ffffcd04`13054b00 fffff804`f0288fa8 : 00000000`00000000 ffffcd04`13054cb0 00000000`00003000 ffffe40f`776fd000 : nt!KiBugCheckDispatch+0x69
ffffcd04`13054c40 fffff804`efff9939 : fffff804`effc0d26 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x468
ffffcd04`13054dd8 fffff804`effc0d26 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpApic1WriteIcr+0x9
ffffcd04`13054de0 fffff804`efe134db : ffffe40f`00000000 00000000`00000200 ffffcd04`13054f00 ffffe40f`4f977c90 : nt!HalpApicRequestInterrupt+0x96
ffffcd04`13054e50 fffff804`efebb7c0 : ffffcd04`130552e0 00000000`00000000 00000000`00000000 fffff804`d1f61bc7 : nt!HalpInterruptSendIpi+0x13b
ffffcd04`13055170 fffff804`efebb221 : 0000ffff`f804d1f6 ffffe40f`5a0cb880 00000000`00000000 00000000`00000008 : nt!KiInsertQueueDpc+0x590
ffffcd04`13055270 fffff804`d1f60e0b : ffffe40f`5a0cb001 ffffcd04`13055300 ffffe40f`5a0cb880 00000000`00029dd3 : nt!KeInsertQueueDpc+0x11
ffffcd04`130552b0 ffffe40f`5a0cb001 : ffffcd04`13055300 ffffe40f`5a0cb880 00000000`00029dd3 00000000`00000000 : amdfendr+0x10e0b
ffffcd04`130552b8 ffffcd04`13055300 : ffffe40f`5a0cb880 00000000`00029dd3 00000000`00000000 00000000`00000002 : 0xffffe40f`5a0cb001
ffffcd04`130552c0 ffffe40f`5a0cb880 : 00000000`00029dd3 00000000`00000000 00000000`00000002 00000000`00000000 : 0xffffcd04`13055300
ffffcd04`130552c8 00000000`00029dd3 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xffffe40f`5a0cb880
ffffcd04`130552d0 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : 0x29dd3
SYMBOL_NAME: amdfendr+10e0b
MODULE_NAME: amdfendr
IMAGE_NAME: amdfendr.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 10e0b
FAILURE_BUCKET_ID: 0x9F_4_amdfendr!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8a421ea4-a07b-a3dd-525a-7b642e7361eb}
Followup: MachineOwner
---------
01-16-2025 07:52 PM - last edited a month ago
edit
01-16-2025 11:56 PM
So we waited more than 1 month for a proper bios. and now we got second update before even fully tuning the first beta. lol
01-17-2025 02:50 AM
Nobody is forcing you to update?
All releases so far work fine for me on my 8000MT m die kit.
01-16-2025 07:53 PM - last edited a month ago
edit