I recently swapped out some parts on my computer and it's been fine for about a month. However, I realized I didn't have any way to control fan speeds and other such settings other than through the BIOS on startup. Given that I have an AORUS gaming motherboard, I want ahead and installed their "App Center" program to allow me to control these settings in a more easier fashion. However, within day one of setting this up and leaving everything on default, I've gotten to bluescreens when attempting to open a program or game (it doesn't seem specific to any one program or game; just open anything and there's a chance I bluescreen). Additionally, the bluescreen doesn't happen instantly; instead I get this loud buzzing sound in my headphones and the screen freezes up for about 5 to 10 seconds before finally bluescreening. I believe it might be a voltage issue, but I'm not super tech savy (I had help building this computer), so I was hoping someone here could point me in the right direction?
Basic System Specs:
-Motherboard: GIGABYTE Z590 AORUS ELITE AX
-CPU: Intel(R) Core(TM) i9-10900KF CPU @ 3.70GHz (20 CPUs), ~3.7GHz
-Cooler Master MasterLiquid ML360 Mirror ARGB Close-Loop AIO CPU Liquid Cooler on the CPU (fans for the rest of the system; I have not had any issues with overheating as I keep track of my temperatures with HWMonitor)
-GPU: Nvidia RTX 3070 8GB VRAM
-RAM: 64 GB
-Power Supply: EVGA 220-G3-0750-X1 Super Nova 750 G3, 80 Plus Gold 750W
-Case: Corsair iCUE 5000X RGB Tempered Glass Mid-Tower ATX PC Smart Case
DxDiag:
https://pastebin.com/FzMfKFCr
The minidump:
Basic System Specs:
-Motherboard: GIGABYTE Z590 AORUS ELITE AX
-CPU: Intel(R) Core(TM) i9-10900KF CPU @ 3.70GHz (20 CPUs), ~3.7GHz
-Cooler Master MasterLiquid ML360 Mirror ARGB Close-Loop AIO CPU Liquid Cooler on the CPU (fans for the rest of the system; I have not had any issues with overheating as I keep track of my temperatures with HWMonitor)
-GPU: Nvidia RTX 3070 8GB VRAM
-RAM: 64 GB
-Power Supply: EVGA 220-G3-0750-X1 Super Nova 750 G3, 80 Plus Gold 750W
-Case: Corsair iCUE 5000X RGB Tempered Glass Mid-Tower ATX PC Smart Case
DxDiag:
https://pastebin.com/FzMfKFCr
The minidump:
Code:
Microsoft (R) Windows Debugger Version 10.0.22415.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\101621-10796-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 19041 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`52800000 PsLoadedModuleList = 0xfffff806`5342a270
Debug session time: Sat Oct 16 20:42:23.440 2021 (UTC - 5:00)
System Uptime: 0 days 13:42:14.088
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`52bf71b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc601`9cb4d910=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
WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff9c0588964028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3109
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 9831
Key : Analysis.Init.CPU.mSec
Value: 500
Key : Analysis.Init.Elapsed.mSec
Value: 96994
Key : Analysis.Memory.CommitPeak.Mb
Value: 90
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: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffff9c0588964028
BUGCHECK_P3: be000000
BUGCHECK_P4: 800400
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffc601`9cb4d908 fffff806`52cb448a : 00000000`00000124 00000000`00000000 ffff9c05`88964028 00000000`be000000 : nt!KeBugCheckEx
ffffc601`9cb4d910 fffff806`50b815b0 : 00000000`00000000 ffff9c05`88964028 ffff9c05`7edafc30 ffff9c05`88964028 : nt!HalBugCheckSystem+0xca
ffffc601`9cb4d950 fffff806`52db612e : 00000000`00000000 ffffc601`9cb4d9f9 ffff9c05`88964028 ffff9c05`7edafc30 : PSHED!PshedBugCheckSystem+0x10
ffffc601`9cb4d980 fffff806`52cb5db1 : ffff9c05`88923940 ffff9c05`88923940 ffff9c05`7edafc80 ffff9c05`7edafc30 : nt!WheaReportHwError+0x46e
ffffc601`9cb4da60 fffff806`52cb6123 : 00000000`00000001 ffff9c05`7edafc80 ffff9c05`7edafc30 00000000`00000001 : nt!HalpMcaReportError+0xb1
ffffc601`9cb4dbd0 fffff806`52cb6000 : ffff9c05`7e4fa9c8 13d7d5e6`00000001 00000000`00000000 129fd5ae`59cd418b : nt!HalpMceHandlerCore+0xef
ffffc601`9cb4dc20 fffff806`52cb6251 : 00000000`00000014 00000000`00000001 00000000`00000000 3757bb34`a3f2927e : nt!HalpMceHandler+0xe0
ffffc601`9cb4dc60 fffff806`52cb54bb : 00000000`00000000 00000000`00000000 ffffc601`9cb4def0 b9d37fe2`f381cbc7 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffc601`9cb4dc90 fffff806`52cb7d05 : ffff9c05`7e4fa9c8 22409faf`e47113cc a24c1fa7`645993c4 a2481fa7`647993c4 : nt!HalpHandleMachineCheck+0x5f
ffffc601`9cb4dcc0 fffff806`52d0d419 : e2595db6`2468d3d5 c2595fb6`2468d3d5 9c934264`ff8b8455 bc926265`df8aa454 : nt!HalHandleMcheck+0x35
ffffc601`9cb4dcf0 fffff806`52c062fa : feb22045`9daae674 deb00047`bda8c676 5e908067`3d884652 5e908067`3d884656 : nt!KiHandleMcheck+0x9
ffffc601`9cb4dd20 fffff806`52c05fb7 : 00000000`00000000 fffff806`52c05eec 00000000`00000002 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffc601`9cb4de60 fffff806`6dba138f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
fffff387`9882f5b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x1f
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .thread ; .cxr ; 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
---------
Last edited:
Facebook
Twitter
Instagram