Question Blue screen of death when Turbo Mode is enabled ?

[ghost86]

hi all,
I encounter a weird problem with my new rig setup and is annoying

my setup:
cpu i7 7820x with used AIO Corsair H115i-is not new,is second hand
RAm: 24 Gb
video: R9 Fury X
mobo:Asus Strix x299 E-Gaming
power supply: 750w Intertech Argus GOLD

Every time when i Enable Turbo mode in Bios, periodically my system become unstable and i have BSOD with next error: Whea uncorectable error 124-GenuineIntel.sys
.So this error is from proccesor for sure,so i checked stability and health of my CPU with Intel diagnostic program,but all test are fine,he PASSED without problem.
If i disable Turbo mode from BIOS,i have NO more BSOD problem anymore,but in Device manager it show me i must activate.
This whea 124 error is just because my CPU is overhiting,or i must made DELIDED for him,or my used AIO Corsair H115i is not good?
The funny things,is i checked temperature with Real Temp,and when i receive this bsod it's always when i browsing in Opera and it never goes over 40-45 degree.When i play light game like Diablo 3 for example, i never have this bsod 124 error,

I don't understand this WEIRD BEHAVIOR.Another weird thing, ichecked my temperature in idle mode and for example now i have 19-23 degree and over 1 second it goes to29-36 degree.It is posible to thermal degree is not good?I applied Arctic Mx-4
It's possible even my CPU PASS the IntelDiagnostic test,to have HIDDEN PROBLEM under the Turbo mode and is a defective CPU?


I must DELID the processor for TurboMode,or is not necessary?
I was so haping with my new rig until now when i encounter this problem.......
I never manualy overclocking any voltages in BIOS,i always let on AUTO

thanks in advance for any sugestion if u have,

report of BSOD:

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


Loading Dump File [C:\Users\bogdan\Desktop\030623-8671-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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80049800000 PsLoadedModuleList = 0xfffff8004a42a2d0
Debug session time: Mon Mar 6 01:39:45.535 2023 (UTC + 2:00)
System Uptime: 0 days 0:19:26.172
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff80049bfa090 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff90001c75b8f0=0000000000000124
1: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffb90fe5703028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000070005, Low order 32-bits of the MCi_STATUS value.

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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *
• *

*
*

• *
• *
• 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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *
• *

*

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4202

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 6745

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: 1155

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x124

Key : Bugcheck.Code.Register
Value: 0x124

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


FILE_IN_CAB: 030623-8671-01.dmp

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffb90fe5703028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 70005

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: WmiApSrv.exe

STACK_TEXT:
ffff90001c75b8e8 fffff80049cb688a : 0000000000000124 0000000000000000 ffffb90fe5703028 00000000b2000000 : nt!KeBugCheckEx
ffff90001c75b8f0 fffff80048b015b0 : 0000000000000000 ffffb90fe5703028 ffffb90fdfef1d80 ffffb90fe5703028 : nt!HalBugCheckSystem+0xca
ffff90001c75b930 fffff80049db8a9e : 0000000000000000 ffff90001c75b9d9 ffffb90fe5703028 ffffb90fdfef1d80 : PSHED!PshedBugCheckSystem+0x10
ffff90001c75b960 fffff80049cb81b1 : ffffb90fec40a500 ffffb90fec40a500 ffffb90fdfef1dd0 ffffb90fdfef1d80 : nt!WheaReportHwError+0x46e
ffff90001c75ba40 fffff80049cb8523 : 0000000000000001 ffffb90fdfef1dd0 ffffb90fdfef1d80 0000000000000001 : nt!HalpMcaReportError+0xb1
ffff90001c75bbb0 fffff80049cb8400 : ffffb90fdfb960b8 fff275b000000001 0000000000000000 147400000580b739 : nt!HalpMceHandlerCore+0xef
ffff90001c75bc00 fffff80049cb8651 : 0000000000000010 0000000000000001 0000000000000000 3300000518878b4d : nt!HalpMceHandler+0xe0
ffff90001c75bc40 fffff80049cb78bb : 0000000000000000 0000000000000000 ffff90001c75bed0 4489480000019885 : nt!HalpMceHandlerWithRendezvous+0xc9
ffff90001c75bc70 fffff80049cba105 : ffffb90fdfb960b8 2024448948000001 4d000004408f8b4d 8b4800000550878b : nt!HalpHandleMachineCheck+0x5f
ffff90001c75bca0 fffff80049d0fb99 : 48ffc3405de8a0eb 688f8d490e74c085 ffc33f18e8000004 00000014a14819eb : nt!HalHandleMcheck+0x35
ffff90001c75bcd0 fffff80049c0acba : 000008a148000004 878949fffff78000 c27197e800000900 0000b0248c8b48ff : nt!KiHandleMcheck+0x9
ffff90001c75bd00 fffff80049c0a977 : ffffe68800000000 fffff80049c0a8ac ffffb90ff860fc88 0000000000000000 : nt!KxMcheckAbort+0x7a
ffff90001c75be40 fffff8004f95b95b : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277
fffffd0075265d70 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : Ntfs!TxfAccessCheck+0xdb


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}

Followup: MachineOwner
🙁

 

[rgd1101]

Inter Tech Argus?

How good is Inter Tech Argus exactly? I've heard many reviews and most of them said they are not that bad, but not exactly what you would buy if you cared for your pc. I want to know your opinion on this PSU exactly: https://inter-tech.de/en/products/psu/atx/argus-rgb-750w-cm-ii as it offers 750W...

linustechtips.com

test with a better quality psu?

 

[ghost86]

I change in BIOS :
CPU Core ratio set to Auto
AI Overclocker Tuner set to Auto
.When i encounter bsod with Turbo Mode Enabled,CPU core ratio was set to By Core usage,and the weird thing is when i load DEFAULT settings in bios ,he choose automatically By Core Usage not Auto,and with settings Core usage, AVX is set to 4500Mhz,AVX 512 set to 4500mhz and Turbo mode the same 4500.With AUTO settings, AVX is set automatically to 3800mhz and AVX 512 to 3600mhz and no more BSOD.......
And from yesterday until now,i don't have anymore BSOD,my CPU is stable now....but i'm not sure 100% yet if bsod don't come back
The only thing which bother me is this CPU tend to be HOT,and is not summer yet.....With Corsair H115i in idle mode i have 30-35 degree,sometime jump to 40 degree...Is too much for idle



p.s Right now i have Arctic Mx-4 applied on CPU.If i change paste with Arctic Silver 5 or Thermal Grizzly Kryonaut Extreme is better for this hot cpu 7820x ?