How to fix UNEXPECTED_STORECODE_EXCEPTION

Dustin Don Barruela 0 Reputation points
2024-02-04T14:00:19.6+00:00

Hi guys, I recently bought a Gigabyte G5 MF laptop the one with the RTX 4050, and for some reason, every now and then my laptop crashes when I play a game which isn't even close to demanding on my hardware, e.g Sekiro, Dota, hunt showdown..

My laptop specs are:
i5-12th gen
8gb RAM 3200mhz
512 nvme
RTX 4050
Win 11

I've been trying to figure out the cause of the crash and been trying to get a dump file to help. I've debugged the dump file already and would like some help understanding the results? This is only the dump file it has ever generated. Thanks! (see bug check analysis below)

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false
   AllowNugetMSCredentialProviderInstall : false
   AllowParallelInitializationOfLocalRepositories : true

   -- 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.032 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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


Loading Dump File [C:\Windows\Minidump\020424-16281-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff802`49800000 PsLoadedModuleList = 0xfffff802`4a4134a0
Debug session time: Sun Feb  4 14:13:10.800 2024 (UTC + 8:00)
System Uptime: 0 days 17:09:18.879
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
..................................
Loading User Symbols

Loading unloaded module list
...............................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`49c16b00 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff800c`14abeeb0=0000000000000124
2: 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: 0000000000000010, Device Driver Error
Arg2: ffffb98a80d3d028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffffb98a67907b2c
Arg4: ffffb98a678d71a0

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1686

    Key  : Analysis.Elapsed.mSec
    Value: 25740

    Key  : Analysis.IO.Other.Mb
    Value: 7

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 35

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x124

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    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: 0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

    Key  : Failure.Hash
    Value: {37af9407-4a3e-0b08-acdd-dadffdc34c3c}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

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

BUGCHECK_P1: 10

BUGCHECK_P2: ffffb98a80d3d028

BUGCHECK_P3: ffffb98a67907b2c

BUGCHECK_P4: ffffb98a678d71a0

FILE_IN_CAB:  020424-16281-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffff800c`14abeea8 fffff802`49e0e6db     : 00000000`00000124 00000000`00000010 ffffb98a`80d3d028 ffffb98a`67907b2c : nt!KeBugCheckEx
ffff800c`14abeeb0 fffff802`49e0f203     : ffffb98a`66bf6c90 ffffb98a`66bf6c90 ffffb98a`67907b00 ffff800c`14abefe0 : nt!WheaReportHwError+0x37b
ffff800c`14abef80 fffff802`49e0f325     : 00000000`00000000 00000000`000000ba ffffb98a`66bf6c90 ffffb98a`678e4000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xf3
ffff800c`14abefb0 fffff802`4ba30278     : ffff800c`14abf1f0 ffff800c`14abf1f0 ffffb98a`678d7050 00000000`00000001 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffff800c`14abf010 fffff802`4ba299b3     : 00000000`00000000 00000000`00000000 ffffb98a`678d71a0 00000000`00000000 : storport!StorpWheaReportError+0xb8
ffff800c`14abf0a0 fffff802`4ba0c4c6     : ffffb98a`000003e8 ffffb98a`678dc168 00000000`00000000 ffffb98a`678dc010 : storport!StorpMarkDeviceFailed+0x3ff
ffff800c`14abf350 fffff802`4bb0da68     : ffffb98a`678dc010 ffffb98a`678dc010 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x1f346
ffff800c`14abf420 fffff802`4bb0e3dd     : ffffb98a`678dc010 ffffb98a`678dc010 ffff800c`14abf760 ffff800c`14abf760 : stornvme!NVMeControllerInitPart2+0x2a8
ffff800c`14abf520 fffff802`4bb082fa     : ffffb98a`678d71a0 ffffb98a`678dc010 ffff800c`14abf760 fffff802`4b9fb66b : stornvme!NVMeControllerReset+0x145
ffff800c`14abf630 fffff802`4ba178ac     : 00000000`c0000010 ffffb98a`678de1a0 ffffb98a`78df1240 00000000`00000000 : stornvme!NVMeHwResetBus+0x1a
ffff800c`14abf660 fffff802`4ba4180c     : ffffb98a`678de1a0 ffffb98a`678de1a0 00000000`c0000010 ffffb98a`678de1b8 : storport!RaidAdapterResetBus+0x18c
ffff800c`14abf7c0 fffff802`4ba408fa     : ffffb98a`7f9293e0 ffffb98a`678de8d0 ffffb98a`7f9293e0 ffffb98a`7f9293e0 : storport!RaidUnitHierarchicalReset+0x108
ffff800c`14abf880 fffff802`49a2f860     : ffffb98a`7f9293e0 00000000`00000000 ffffb98a`678de050 ffffb98a`7aed2080 : storport!RaidHierarchicalResetWorkRoutine+0x8a
ffff800c`14abf8d0 fffff802`49a34f85     : ffffb98a`64ebcc50 ffffb98a`790eb040 ffff800c`14abfa40 ffffb98a`00000000 : nt!IopProcessWorkItem+0x100
ffff800c`14abf940 fffff802`49b07167     : ffffb98a`790eb040 00000000`000000eb ffffb98a`790eb040 fffff802`49a34e30 : nt!ExpWorkerThread+0x155
ffff800c`14abfb30 fffff802`49c1bb94     : ffffa600`2b9d1180 ffffb98a`790eb040 fffff802`49b07110 00000000`00000000 : nt!PspSystemThreadStartup+0x57
ffff800c`14abfb80 00000000`00000000     : ffff800c`14ac0000 ffff800c`14ab9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {37af9407-4a3e-0b08-acdd-dadffdc34c3c}

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


Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
7,622 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Wesley Li 2,395 Reputation points
    2024-02-05T07:44:08.1266667+00:00

    Hello The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124 and indicates that a fatal hardware error has occurred.   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. If over-clocking has been enabled, try disabling it. Confirm that any cooling systems such as fans are functional. Run system diagnostics to confirm that the system memory isn't defective. It's less likely, but possible, that a driver is causing the hardware to fail with this bug check. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x124---whea-uncorrectable-error It is recommended to contact GIGABYTE officials to confirm the hardware warranty policy.

    0 comments No comments