Question Set up crashes when nvidia control panel NOT set to 'prefer max performance' (RTX 4090). Any Advice?

[montesinos7]

Hi all, first caveat I have never built a PC before and just did so for the first time so I am still learning about how things work, so if I say anything wrong please forgive me. I did build it with a friend who has done it many times before so I am not too worried that I did something drastically wrong.

The issue I am having is that my set up seems to randomly crash to a black screen. Sometimes this happens before I can even log in, usually it takes around 15-20 minutes, sometimes it takes 1-2 hours. I have to manually press the power button to turn it off and then power it back on again. Sometimes the audio from the computer itself is distorted/delayed when this happens. The interesting this is that this does not happen when I am playing anything intensive, in fact it only seems to happen while I am idling, surfing the web, watching videos, calling a friend. etc. I have been checking the the temperature of the graphics card and CPU regularly and they are definitely not overheating. One other random thing to note that is probably not relevant is that when I turn the power supply itself on (not the computer) the LEDs on the fans flash for a brief moment and then turn off. Everything then runs as normal after that. Windows event viewer always returns the same errors when this happens: Event ID 63, Event ID 41, keyword (70368744177664),(2) and bugcheckCode 278.

I have tried making sure drivers are up to date, unplugging and replugging in all the cords to the power supply and socket itself, monitoring the temperatures, and turning off automatic restarts on windows (I am planning on testing with a different power supply soon as well). There is only one single fix that seems to solve the issue - opening the NIVIDIA control panel and setting the power settings to 'prefer max performance'. This leads me to believe the problem is with the GPU, but wanted to consult and see what people suggest here before I RMA anything. I could just leave it on 'prefer max performance' at all times I guess but that seems like a bandaid fix and plus it would stress the system long term.

Thanks for the help ahead of time!

My specs are the following:
Processor: 13th gen Intel(r) Core (TM) i5-13600K 3.50 Ghz
Graphics Card: Asus GeForce RTX 4090
PSU: EVGA SuperNOVA 1000 GT 80 Plus 1000W Fully Modular Power Supply
Ram Sticks: Trident Z5 RGB x 2 (32gb total)
Memory: 980 Pro PCIe 4.0 NVMe M.2 SSD
Motherboard: Gigabyte Z790 Aero G
Cooler: TH240 ARGB Sync
Case: Ceres 500 TG ARGB

 

[JohnBonhamsGhost]

PSU: EVGA SuperNOVA 1000 GT 80 Plus old

what do you mean by "old".
are you referring to the age of the power supply itself?

if so, what exactly is the age and what components was it previously running?

 

[montesinos7]

what do you mean by "old".
are you referring to the age of the power supply itself?

if so, what exactly is the age and what components was it previously running?

This was a typo, my bad. It is a totally new power supply.

 

[montesinos7]

'Genuineintel' bugcheck code 124 causes crashes, is this a faulty cpu ( i5-13600K)?

Hi all,

I recently built a new PC that has been crashing to a black screen randomly. However, this only happened when the nvidia control panel was not set to 'prefer maximum performance'. Initially, this led me to believe that the issue was with the GPU. However, someone recommended that I check the minidump folder and see if I can find more information about the crashes. After analyzing those files with windows debugger, the error comes up as bugcheck code 124 and the issue is with 'GenuineIntel.sys'. I am attaching the text of this file with the full readout of the error at the bottom of the post, in the hopes that someone here will know how to read it since I do not really know what I am looking at.

For some further context, initially the PC was crashing to a black screen randomly. Then, I updated the system to windows 11, updated the VBios from the Asus website, and updated the chipset driver for the motherboard. Now, the same issue happens, but instead of crashing to a black screen the computer freezes and I have to manually power it on and off or sometimes even reset the power supply to get it on again. Again, all of this only seems to happen when not on the 'prefer maximum performance' setting in the NVIDIA control panel.

Here are my specs:
Processor: 13th gen Intel(r) Core (TM) i5-13600K 3.50 Ghz
Graphics Card: Asus GeForce RTX 4090
PSU: EVGA SuperNOVA 1000 GT 80 Plus 1000W Fully Modular Power Supply
Ram Sticks: Trident Z5 RGB x 2 (32gb total)
Memory: 980 Pro PCIe 4.0 NVMe M.2 SSD
Motherboard: Gigabyte Z790 Aero G
Cooler: TH240 ARGB Sync
Case: Ceres 500 TG ARGB

TEXT FROM WINDOWS DEBUGGER READING OF THE MINIDUMP FILE:

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


Loading Dump File [C:\Users\Sebastian\Desktop\041023-9015-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 22621 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Machine Name:
Kernel base = 0xfffff80159c00000 PsLoadedModuleList = 0xfffff8015a813430
Debug session time: Mon Apr 10 23:18:17.122 2023 (UTC - 4:00)
System Uptime: 0 days 0:15:42.744
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
0: 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: 0000000000000004, PCI Express Error
Arg2: ffffc10989f6c028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2531

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2646

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

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

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

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Timestamp
Value: 2022-05-06T12:50:00Z

Key : WER.OS.Version
Value: 10.0.22621.1


FILE_IN_CAB: 041023-9015-01.dmp

BUGCHECK_CODE: 124

BUGCHECK_P1: 4

BUGCHECK_P2: ffffc10989f6c028

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff8015e186c48 fffff8015a0f403b : 0000000000000124 0000000000000004 ffffc10989f6c028 0000000000000000 : nt!KeBugCheckEx
fffff8015e186c50 fffff80156dc10c0 : ffffc10989f6c028 fffff8015e186d59 ffffc10989f6c028 ffffc10989f699c0 : nt!HalBugCheckSystem+0xeb
fffff8015e186c90 fffff8015a1fde66 : ffffc10989f6c028 fffff8015e186d59 ffffc10989f6c028 ffffc10989f69960 : PSHED!PshedBugCheckSystem+0x10
fffff8015e186cc0 fffff8015a1fe255 : 0000000000000000 0000000000000000 ffffc10989f6c028 ffffc10989f43964 : nt!WheaRecoveryBugCheck+0x56
fffff8015e186cf0 fffff8015c91dac9 : ffffc10989f43964 ffffc10989f43964 0000000000000000 0000000000000407 : nt!WheaReportHwError+0x3d5
fffff8015e186dc0 fffff8015c919741 : 0000000000000130 ffffc10989f69150 0000000000000000 ffffc10989f92190 : pci!PciRpRcecHandleAerInterrupt+0x2e9
fffff8015e186e20 fffff8015c919ba6 : ffffd200c5f4bc00 fffff8015e186ed0 fffff80155951180 fffff8015a841910 : pci!ExpressRootPortAerInterruptRoutine+0xa1
fffff8015e186e90 fffff8015c919c69 : ffffd200c5f4bc80 00000002320177b4 00000000001f095a fffff8015a095d00 : pci!ExpressRootPortInterruptRoutine+0x46
fffff8015e186ef0 fffff80159f5d5b1 : fffff80155951180 fffff8015a94c6c0 0000000000000246 fffff8015e177350 : pci!ExpressRootPortMessageRoutine+0x9
fffff8015e186f20 fffff80159f453cb : 0000000000000000 fffff80159edb37c 0000000000000000 ffffd200c5f4bc80 : nt!KiInterruptMessageDispatch+0x11
fffff8015e186f50 fffff8015a02b2df : fffff8015e177350 ffffd200c5f4bc80 0000000000000000 0000000000000000 : nt!KiCallInterruptServiceRoutine+0x16b
fffff8015e186f90 fffff8015a02b5a7 : 0000000000000000 fffff8015e177438 fffff8015e177300 fffff8015e177318 : nt!KiInterruptSubDispatch+0x11f
fffff8015e1772d0 fffff80187144002 : fffff80187145710 0000000000000000 00000000000fffff 0000000000000000 : nt!KiInterruptDispatch+0x37
fffff8015e177468 fffff80187145710 : 0000000000000000 00000000000fffff 0000000000000000 00000000ffffffff : intelppm!C1Halt+0x2
fffff8015e177470 fffff801871415c4 : 0000000000000000 0000000000000000 fffff80155951180 0000000000000002 : intelppm!C1Idle+0x30
fffff8015e1774a0 fffff80159e2adf7 : 0000000000000091 0000000000000000 ffffc1098e2cede0 0000000000000000 : intelppm!AcpiCStateIdleExecute+0x24
fffff8015e1774d0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!PpmIdleExecuteTransition+0x1137


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_4_GenuineIntel_PCIEXPRESS_UNSUPPORTED_REQUEST_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b18ac8da-121f-91e6-9956-cf4674a1bbda}

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