Processors
Intel® Processors, Tools, and Utilities
14537 Discussions

blue screen of death in TurboMode

ghost1
Beginner
6,146 Views

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

ghost1_0-1678096834204.gif

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 Inter tech Argus GOLD


Every time when i Enable Turbo mode in Bios, periodically my system become unstable and i have black screen of death 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?

ghost1_1-1678096834298.gif

 

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,

 

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 = 0xfffff800`49800000 PsLoadedModuleList = 0xfffff800`4a42a2d0
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:
fffff800`49bfa090 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff9000`1c75b8f0=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:  
ffff9000`1c75b8e8 fffff800`49cb688a     : 00000000`00000124 00000000`00000000 ffffb90f`e5703028 00000000`b2000000 : nt!KeBugCheckEx
ffff9000`1c75b8f0 fffff800`48b015b0     : 00000000`00000000 ffffb90f`e5703028 ffffb90f`dfef1d80 ffffb90f`e5703028 : nt!HalBugCheckSystem+0xca
ffff9000`1c75b930 fffff800`49db8a9e     : 00000000`00000000 ffff9000`1c75b9d9 ffffb90f`e5703028 ffffb90f`dfef1d80 : PSHED!PshedBugCheckSystem+0x10
ffff9000`1c75b960 fffff800`49cb81b1     : ffffb90f`ec40a500 ffffb90f`ec40a500 ffffb90f`dfef1dd0 ffffb90f`dfef1d80 : nt!WheaReportHwError+0x46e
ffff9000`1c75ba40 fffff800`49cb8523     : 00000000`00000001 ffffb90f`dfef1dd0 ffffb90f`dfef1d80 00000000`00000001 : nt!HalpMcaReportError+0xb1
ffff9000`1c75bbb0 fffff800`49cb8400     : ffffb90f`dfb960b8 fff275b0`00000001 00000000`00000000 14740000`0580b739 : nt!HalpMceHandlerCore+0xef
ffff9000`1c75bc00 fffff800`49cb8651     : 00000000`00000010 00000000`00000001 00000000`00000000 33000005`18878b4d : nt!HalpMceHandler+0xe0
ffff9000`1c75bc40 fffff800`49cb78bb     : 00000000`00000000 00000000`00000000 ffff9000`1c75bed0 44894800`00019885 : nt!HalpMceHandlerWithRendezvous+0xc9
ffff9000`1c75bc70 fffff800`49cba105     : ffffb90f`dfb960b8 20244489`48000001 4d000004`408f8b4d 8b480000`0550878b : nt!HalpHandleMachineCheck+0x5f
ffff9000`1c75bca0 fffff800`49d0fb99     : 48ffc340`5de8a0eb 688f8d49`0e74c085 ffc33f18`e8000004 00000014`a14819eb : nt!HalHandleMcheck+0x35
ffff9000`1c75bcd0 fffff800`49c0acba     : 000008a1`48000004 878949ff`fff78000 c27197e8`00000900 0000b024`8c8b48ff : nt!KiHandleMcheck+0x9
ffff9000`1c75bd00 fffff800`49c0a977     : ffffe688`00000000 fffff800`49c0a8ac ffffb90f`f860fc88 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffff9000`1c75be40 fffff800`4f95b95b     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
fffffd00`75265d70 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 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
---------

0 Kudos
25 Replies
ghost1
Beginner
4,996 Views

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

 

sincerely Bogdan,

 

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 ?

0 Kudos
Jocelyn_Intel
Employee
4,988 Views

Hello, @ghost1  

 

Thank you for posting on the Intel® communities.  

 

I am sorry to hear what is happening with your processor, I will gladly assist you here. 

 

This bug check is typically related to physical hardware failures. It can be heat related or a result of defective hardware, memory, or even a processor that's beginning to fail or has failed, as per the Microsoft website. There are some recommendations you can find on their website regarding this error too. 

 

  1. Did you make sure you have the latest BIOS version (3701)
  2. Try reinstalling the Operating System and let us know the results. 
  3. Please test and run these utilities and attach the reports and screenshots to have more information about how is your system working, check on the notes: 

 

Intel® Processor Diagnostic Tool 

Note: As soon as you run it, it will start testing, please attach the complete Screenshot or click on "File", select the "View Results File" option, save and attach the report. 

 

Intel® Extreme Tuning Utility (Intel® XTU) 

Note: Click on "Stress Test" tab and "Start Testing" and then, attach a complete screenshot. 

 

Intel® System Support Utility for Windows. 

Note: Make sure to mark the box that says "everything" before pressing the Scan button. After that, click on "Next>" and select "Save" and then, attach the .txt file. 

 

Best regards,  

Jocelyn M.   

Intel Customer Support Technician. 


0 Kudos
ghost1
Beginner
4,974 Views

like i said before,i already tested my 7820x with intel soft diagnostic tool...and my CPU passed without problem.My BIOS version was never flashed to the latest version.My version of Bios is from 8/8/2017 .I'm scare to flash my bios because i don't have an UPS

My problem was solved from BIOS,i set CPU Core Ratio to AUTO,and bsod problem dissapear.With Core usage settings ,cpu become unstable don't know why..so the problem is from another location,in my case my motherboard dislike my cpu with: Core Usage settings...he like only on AUTO !!!

I will test CPu with Intel Extreme tuning Utility and i post here

Anyway,in the future i planning to change my cpu to i9 7960x.....

 

https://imgupx.com/mvbwUNfN"

0 Kudos
ghost1
Beginner
4,965 Views

p.s . I tested my CPU with Intel XTU and is passed without problem....so my CPU is OK right?

 

 

 

0 Kudos
ghost1
Beginner
4,957 Views

i saved all report of scan here:

 

https://www.mediafire.com/file/a9drsq8zfd16hb8/sys+inf+text.txt/file

 

p.s Also in Device Manager  all devices is working and installed properly......so ??All seems to be fine...The problem is from my Bios i think....

 

0 Kudos
Jocelyn_Intel
Employee
4,945 Views

Hello, @ghost1  

 

Thank you for the information provided. 

 

Since all the tests passed without problems, it seems not to be a processor issue. 

 

I understand your concern about updating the BIOS version, however, please be aware that this is an important step to make sure everything in the system is running up to date with the most recent updates that, most of the time, these ones fix several issues. 

 

We suggest you to contact your Motherboard Manufacturer to perform a BIOS update in a safe way. If the issue persists, please provide us with a new/updated Intel® SSU report so we can continue investigating with your system fully updated. 

 

Best regards,  

Jocelyn M.   

Intel Customer Support Technician. 


0 Kudos
ghost1
Beginner
4,914 Views

today i change my thermal degree paste with Arctic Silver 5 ,and now in Prime95 stress test i have 52-54 degree....This paste AS 5 is the best....

 

0 Kudos
Jocelyn_Intel
Employee
4,893 Views

Hello, @ghost1  

 

Thank you for the information provided. 

 

Just to understand your last post, what is the issue with those temperatures? They are normal temperatures, as the maximum is 100 degrees as you can see here

 

In any case, have you updated your BIOS version yet? 

 

Best regards,  

Jocelyn M.   

Intel Customer Support Technician. 


0 Kudos
ghost1
Beginner
4,878 Views

Tjunction of 99 degree is a maximum temp. allowed for this processor before fries,and at this temp is not normal and result in thermal protection with restart for sure,but in my knowledge, anything over 75-80 degree is not recommended for ANy processor in this world....because anything over 75 degree is not safe-Throtling.For any proccessor to run Ok,it must be as cold as possible,that's why many people made Delid process for better potential room overclock

 

I will update my BIOS soon,when i own an UPS,without Unintreruptible power supply  i'm afraid to do this step......

0 Kudos
n_scott_pearson
Super User
4,863 Views

Let's state this properly. The Tjmax (Maximum Junction) Temperature is the point where throttling to protect the processor starts to happen. If temperatures continue to rise, even with throttling occurring, you reach another temperature threshold, called THERMTRIP, where the processor powers off to protect itself from meltdown. The problem is that (a) the processor's DTS sensors do not represent temperatures above Tjmax and (b) Intel does not publish the THERMTRIP temperature thresholds. We thus know nothing about when THERMTRIP will reached or occur. We know temperatures are at Tjmax, but do not know if it is above Tjmax.

Previously, Intel published (via MSR) a Tcontrol temperature for the processor. This is the threshold above which the processor fan should be at 100% to ensure that the processor temperature stays below its Thermal Load Line as much as possible. Unfortunately, Intel is no longer providing a Tcontrol temperature (the MSR essentially says Tcontrol == Tjmax). This I don't like. But, what I can tell you is that Tcontrol was typically set 10-15 degrees below Tjmax, so, for the general case (where Tjmax is ~100c), concerning temperatures are above 85c.

Hope this helps,

...S

0 Kudos
ghost1
Beginner
4,840 Views

so,from what i read,you say 85 degree is still a safe temperature for a desktop processor?In my knowdledge 75 degree is a maximum temp. allowed for a desktop processor to run OK without errors and without throtling.At 80 or 85 degree is become very dangerous and result in overheating

From what i know mobile processor by construction are made to be strongest to resist at higher temperatures like 85-90degree without problems.Desktop processor are more sensitive

But general speaking, excesive heat destroy anything and permanently electronical part over time in his path,that;s why every degree,even 1 degree made the differences in anything.From what i see, for example, a cold processor with 40 degree in full load are more responsive and fastest like same processor with 60 or 65 degree in same aplication,trust me

Any processor run OK with max 55-60 degree in full load or 70-75 in stress test program,or Cinebench23.But anything over 75 degree for CPU is not OK !I mean is ok even at 75 degree,but is becoming unresponsive and lagging like a hell...

I don't understand why many people run their CPu's at 80 or 90 degree without cares about their CPU life..!!!For me it's a dillema.For me even 75 degree is a dangerous zone honest.

0 Kudos
n_scott_pearson
Super User
4,834 Views

Trust you? No, you are incorrect. *I* know; I spent years at Intel responsible for thermal and acoustic management in their Desktop Board products.

85 is NOT what I would consider dangerous. Your processor will be fat, dumb and happy running at that temperature. No thermal degradation will be occurring that will disaffect the lifetime of the processor. Desktop processors are NOT more sensitive; these days, it is essentially the same silicon that is used in the mobile and embedded processors.

Look, you want to spend your money putting in a premium cooling solutions that meet your lower targets, go ahead; it's your money to waste.

...S

0 Kudos
ghost1
Beginner
4,812 Views

ok,i'm not user retired employee like you,maybe i'm wrong and you are right, but please tell why more and more people want to make DELID/RELID at their CPU,if this discussion about degree are not so important?

If 85 degree are NOT so dangerous,why most of  people want DELID at their processor?

As for me,the apperances cheat.I'm not a rich guy,My cooling system is an used Corsair H115i at 50$ + 5$ thermal degree paste Arctic Silver 5.Total 55$.

You consider this 55$ a waste of money?

0 Kudos
AlHill
Super User
4,810 Views

@ghost1    "why most of people want DELID at their processor?"

Where in the world do you get your data?  Show the data that supports this, or stop this ridiculous discussion now.   You have been given the best answer you will ever get on this subject, and you do not like it because you were simply wrong.

Go and spend your money on whatever you want to achieve your flawed goal.

 

Doc (not an Intel employee or contractor)
[Maybe Windows 12 will be better]

0 Kudos
ghost1
Beginner
4,794 Views

 AlHill  can u STOP please to be so arrogant with me?U are ridiculous not the discussion or me or other.If u don't like this topic u can LEAVE and don't come back

The best answer only GOD can have it, not you or any man on this world.This is a discussion forum,and anybody can have opinion not only you or "smart guys"

I spend my money whatever i want,and i discuss whatever i want  OK?I don't think i  need to ask your permission  to share MY OPINION OK?

The truth is RELATIVE !!

 

AlHill added to ignore list !!

0 Kudos
AlHill
Super User
4,791 Views

@ghost1 This is a community forum.   And, you can stop making up data to support your incorrect beliefs.  You simply learned the wrong way, and you need to accept facts, not what you believe.

 

You can add me to the ignore list as much as you want, but your incorrect assumptions and beliefs still exist on this thread.  Perhaps you need to go to some other site and spew your drivel.

 

Doc (not an Intel employee or contractor)
[Maybe Windows 12 will be better]

0 Kudos
ghost1
Beginner
4,786 Views

yes this is a forum comunities and anybody here can share their opinion,even magiciens and stupid people like me...........not only "gods like you"

Can u stop offtopic in this thread>?If u don't have anything constructive to say about this discussion, u can leave now  and nobody especially me will miss you,trust meI hate arrogant people like you!!!!!

All forum sites are full of arrogant like you , which belief they hold the truth...

 

Ok ,a moderator can close or delete this topic ! Thanks,

i'm tired of arrogants people!

0 Kudos
AlHill
Super User
4,780 Views

I asked you to provide data on your statement that most people DELID their processor, and you could not because you made that up.  When you make up things, no one will ever trust you.

Then, you tried turning this into a discussion about how you spend your money.

 

Your question has been answered.  Time for you to move on.

 

And, I thought you were ignoring me?<G>

 

Doc (not an Intel employee or contractor)
[Maybe Windows 12 will be better]

0 Kudos
ghost1
Beginner
4,771 Views

You say :  Then, you tried turning this into a discussion about how you spend your money

Your question has been answered.  Time for you to move on.

-----------------------------------------------------------------------------------------------------------------------------------------

If this all you understood form this discussion,i'm sorry for you ,but your IQ is equal to ZEROOOO !! and threats don't scare me,relax.I know u are probably friends with moderator,is nothing new for me.But always i will hate arrogant people like you,and i will always say what i have to say at any risk ,don't forget this !i'm not a sheep like you.

 

Is the last reply for you.I spent precious time with you .................bye

go to report me and spare me!!

0 Kudos
AlHill
Super User
4,767 Views

@ghost1 If you want to correct or amend your statement on the number of people who DELID, please do.  However, you know that you made that up.  I did not misunderstand that. 

 

Again, you said you are ignoring me, right?<G>

 

Doc (not an Intel employee or contractor)
[Maybe Windows 12 will be better]

0 Kudos
Reply