Kernel Power 41 (63) in MSI Vector 16 HX A14V

LadyMorrigan

New member
Joined
Aug 4, 2024
Messages
12
Hello,

While playing computer games (simple games like Dave the Diver), my computer crashed 2 times. I noticed that whenever I had an achivement, it crashes but I don't know if it is just a concidence. In the first time, the game got stuck and I could not open task manager with ctrl+shift+esc and I could not press any button because the system did not respond. I had to force restart my laptop after waiting for a while. It happened on 03.08.2024 around 14:14. The second time I was still playing a simple game and it stuck again. Similarly, when I pressed the buttons the system did not respond and there was a sound came from the computer which I can only describe as "stuck" sound. Again, I had to force restart. The second crash happened on 04.08.2024 on 00:03.

I completed all Windows updates after the first crash so I did not expect a second crash. When I look at the event logs around the times I described above, I saw Kernel Power 41 (63) event. Also there is not any minidump file in C/Windows. I am using a balanced power plan and using it in Silent Mode in MSI Center. I also deleted Norton Antivirus. These are the only changes I did after I bought the laptop.

I bought this laptop last week, MSI Vector 16 HX A14V. The system info from MSI Help Desk is:
------------------
System Information
------------------
Product Name: Vector 16 HX A14VHG
OS: Microsoft Windows 11 Home Single Language 64 bit Ver.2009(OS build 22631.3880)
HDI Build: ZS7-15M1KM4-RS5 16.4.L60.34.0.2306.10
BIOS Version: E15M1IMS.90D
BIOS Release Date: 2024/04/12
EC Version: 15M1IMS2.1070204202416:00:15
CPU: Intel(R) Core(TM) i9-14900HX
Memory: 32 GB @ 2800 MHz
- 16 GB, DDR5-5600, Samsung M425R2GA3BB0-CWMOD
- 16 GB, DDR5-5600, Samsung M425R2GA3BB0-CWMOD
Graphics: Intel(R) UHD Graphics, 1024 MB
Graphics: NVIDIA GeForce RTX 4080 Laptop GPU, 4095 MB
Panel: Integrated Monitor(AUO07B2), 2560 X 1600, 240Hz, DPI 150%
VBIOS Version: 95.04.63.00.03
Drive: SSD, NVMe SAMSUNG MZVL81T0HELB-00BTW, 953,87 GB
Network: Realtek Gaming 2.5GbE Family Controller
Win32 SHIFT mode: Unsupported
Power Plan: Power Scheme GUID: 381b4222-f694-41f0-9685-ff5bb260df2e (Dengeli)
UWP User Scenario: Unsupported
UWP Graphic Switch: Unsupported
True Color mode: null

Thank you for your help.
 
Do you encounter the issue while playing Dave the Diver or not just one game?
If you encounter the issue while playing different games, try to clean install Intel & Nvidia Graphics drivers on the MSI website to check if the problem is caused by the generic version.
 
For six days not a single crash happened but yesterday and today, while playing World of Warcraft it crashed twice. I will try the solution you suggested, thank you.
 
Hello again, would you suggest clean setup of the latest intel and nvidia drivers? Because, here is the situation:
I had contacted online MSI Support because of these crashes. They sent me "tested" versions of both drivers manually (as a file) and two FAQ's to how to install them. These were not latest drivers and according to their response, they were tested together and work well. Also they sent application file directly, I mean I did not download Geforce Experience and installed it from there.

It worked for a few days and then crashes happened again randomly while playing WoW. They said that there is nothing with driver side so I should send the laptop to service for hardware check. But the thing is I will move to another country soon and I don't know when I can receive the laptop again if I send it to the service.

All in all, should I try to run latest drivers this time? Or any other suggestions?

Note (after today's crash): I also tried to change power management settings, set the laptop power mode to "best performance" and under the "system"->"power management", I changed the processor power management min max values to 100% (I don't know what I am doing btw I just saw somewhere on the internet that it worked for some people).
 
I’m not sure what test version the technician provided you. If it’s the same as the Intel/Nvidia graphics drivers available on MSI website, then I don't think you need to try updating to the latest graphics driver, as drivers from MSI website are generally verified. However, if you’re still concerned, you can try a clean installation of the latest graphics driver for cross-checking. If different versions of the graphics driver still cause issues, the problem may not be related to the graphics drivers.
You mentioned earlier that you switched to Silent mode. Have you tried switching to Extreme Performance mode to see if the issue persists?
If none of the above suggestions resolve your issue, I recommend checking the laptop's performance by Cinebench R23 and Time Spy.
Because high CPU and GPU temperatures can trigger the system’s protection mechanism and cause it to restart, you can use the benchmark tools I mentioned to check if there are any anomalies with thermal capacity.
Here are the things to note for the test:
1. Switch to Extreme Performance Mode.
2. Ensure the AC Adapter is connected.
3. Close all programs.
4. Make sure the laptop has cooled down before starting the test
 
I didn't tried extreme performance mode because I thought it is doing an overclocking. Is it something different?

It is on balanced mode rn. So far I tried balanced, silent and MSI AI Engine modes. All three had been crashed. I tested with OCCT, it passed all CPU tests. It also crashed today when I did alt tab while in WoW.

I will try the benchmark tools you mentioned. Should I take into consideration any parameters before running the tests?
 
I didn't tried extreme performance mode because I thought it is doing an overclocking. Is it something different?

It is on balanced mode rn. So far I tried balanced, silent and MSI AI Engine modes. All three had been crashed. I tested with OCCT, it passed all CPU tests. It also crashed today when I did alt tab while in WoW.

I will try the benchmark tools you mentioned. Should I take into consideration any parameters before running the tests?
Since you still seem stuck...
Update Nvidia driver to 551.86 https://www.nvidia.com/download/driverResults.aspx/223498/en-us/
In CMD (Run as admin) type sfc /scannow then type afterwards chkdsk /r
Then in start type mdsched (Run as admin)

If your CPU temperature is higher than 94oC, run COOLER BOOST, if your GPU temperature is higher than 84oC, run COOLER BOOST.
If you insist on playing long gaming sessions in WOW, in SILENT MODE, then disable CPU TURBO in your Windows power plan,
by setting the maximum CPU performance to 97%.
 
Thank you for your response!
I run CINEBENCH. It finished with CPU (Multi Core) 27755 pts, Idk what to expect with this ranking..
How can I run Cooler Boost? In MSI Center I don't have User settings as I saw on the internet the Cooler Boost is available through User Settings.
About CPU TURBO for Windows power plan, should I disable it on BIOS? Because Windows has only one power plan it is "balanced".
1724248759220.png
 
Hello again, I run scannow and chckdsk. In chkdsk there were 5 files which had been corrupted and windows automatically fixed them. In mdsched, no files were corrupted.
I am planning to play games like WoW, Baldurs Gate 3, indie games, RDR2 etc for long hours. It doesn't matter which mode I use actually, it only matters that I am not overclocking or harm some parts of the laptop. Also if performance does not drop very significantly, I am OK with it (I also don't mind playing these games in Ultra, I even decreased GPU settings in the game because of the crashes)
That is why, I opened the Balanced Mode in MSI Center. I disabled CPU TURBO in BIOS. I set the max CPU performance to %97. I can put it to Silent mode as you suggested but as I mentioned, I don't mind the sound anymore as long as it does not crash or harms the laptop.
I am adding SS, hopefully I did the settings correct. Also, I found Cooler Boost setting under high performance in MSI Center but it is a different mode than balance and silent. Can I open Cooler Boost and use it in balance mode at the same time? Does it make sense?
1724268564727.png


Edit 1 after testing: I was playing WOW for 5 minutes and there are small FPS drops happening while flying fast. Also, previously most of the graphic settings in default were in Ultra. Now the default became Low. Is that normal, it feels like computer does not use RTX 4080 anymore...

Edit 2: I kept playing for 30 minutes. It crashed again and I am pretty sure it is not about temperature. Because last I checked CPU temp was around 70 degrees, also keyboard was not as warm as previous crashes. I went to event manager and saw volmgr 161 error. Before that there are 3 DeviceSetupManager 131 errors.
1724272229637.png
 
Last edited:
Hello again, I run scannow and chckdsk. In chkdsk there were 5 files which had been corrupted and windows automatically fixed them. In mdsched, no files were corrupted.
I am planning to play games like WoW, Baldurs Gate 3, indie games, RDR2 etc for long hours. It doesn't matter which mode I use actually, it only matters that I am not overclocking or harm some parts of the laptop. Also if performance does not drop very significantly, I am OK with it (I also don't mind playing these games in Ultra, I even decreased GPU settings in the game because of the crashes)
That is why, I opened the Balanced Mode in MSI Center. I disabled CPU TURBO in BIOS. I set the max CPU performance to %97. I can put it to Silent mode as you suggested but as I mentioned, I don't mind the sound anymore as long as it does not crash or harms the laptop.
I am adding SS, hopefully I did the settings correct. Also, I found Cooler Boost setting under high performance in MSI Center but it is a different mode than balance and silent. Can I open Cooler Boost and use it in balance mode at the same time? Does it make sense?
View attachment 191944

Edit 1 after testing: I was playing WOW for 5 minutes and there are small FPS drops happening while flying fast. Also, previously most of the graphic settings in default were in Ultra. Now the default became Low. Is that normal, it feels like computer does not use RTX 4080 anymore...

Edit 2: I kept playing for 30 minutes. It crashed again and I am pretty sure it is not about temperature. Because last I checked CPU temp was around 70 degrees, also keyboard was not as warm as previous crashes. I went to event manager and saw volmgr 161 error. Before that there are 3 DeviceSetupManager 131 errors.
View attachment 191947
Are you connected directly to the wall socket or on a power bar?
If on a power bar, try directly to the socket, if a socket, try one in a different room.
Are you using the AC adapter 330W that came with it?

Once finished run the command prompts again.
In CMD (Run as admin) type sfc /scannow then type afterwards chkdsk /r
If you still have errors after the first scan, sfc /scannow, then you might need to re install your Windows, run it another time after IF corrupted files are detected again to confirm.
If you still have errors after the second scan, chkdsk /r, you might have a faulty SSD, run another time after to confirm, If corrupted sectors are again detected, if so,
then replace the SSD, or open an RMA with MSI, if your laptop still under warranty.

 
Last edited:
Hello again, I run scannow and chckdsk. In chkdsk there were 5 files which had been corrupted and windows automatically fixed them. In mdsched, no files were corrupted.
I am planning to play games like WoW, Baldurs Gate 3, indie games, RDR2 etc for long hours. It doesn't matter which mode I use actually, it only matters that I am not overclocking or harm some parts of the laptop. Also if performance does not drop very significantly, I am OK with it (I also don't mind playing these games in Ultra, I even decreased GPU settings in the game because of the crashes)
That is why, I opened the Balanced Mode in MSI Center. I disabled CPU TURBO in BIOS. I set the max CPU performance to %97. I can put it to Silent mode as you suggested but as I mentioned, I don't mind the sound anymore as long as it does not crash or harms the laptop.
I am adding SS, hopefully I did the settings correct. Also, I found Cooler Boost setting under high performance in MSI Center but it is a different mode than balance and silent. Can I open Cooler Boost and use it in balance mode at the same time? Does it make sense?
View attachment 191944

Edit 1 after testing: I was playing WOW for 5 minutes and there are small FPS drops happening while flying fast. Also, previously most of the graphic settings in default were in Ultra. Now the default became Low. Is that normal, it feels like computer does not use RTX 4080 anymore...
If you start experiencing this behavior after limiting the CPU's performance, it is likely that the CPU is causing a bottleneck in the game.
Edit 2: I kept playing for 30 minutes. It crashed again and I am pretty sure it is not about temperature. Because last I checked CPU temp was around 70 degrees, also keyboard was not as warm as previous crashes. I went to event manager and saw volmgr 161 error. Before that there are 3 DeviceSetupManager 131 errors.
View attachment 191947
Did you still not have a minidump?
I am afraid that you might need to perform the system recovery to cross-check.
If the problem still persist, you need to connect the local service center for further inspection.
 
I am adding SS, hopefully I did the settings correct. Also, I found Cooler Boost setting under high performance in MSI Center but it is a different mode than balance and silent. Can I open Cooler Boost and use it in balance mode at the same time? Does it make sense?
Set to BALANCED MODE in MSI Center.
FN + up arrow (activates COOLER BOOST)
Page 2-15


View attachment 191944

Edit 1 after testing: I was playing WOW for 5 minutes and there are small FPS drops happening while flying fast. Also, previously most of the graphic settings in default were in Ultra. Now the default became Low. Is that normal, it feels like computer does not use RTX 4080 anymore...
If the TURBO is disabled, the CPU will become the bottleneck and performance of the RTX 4080, will be reduced because of this.
 
Last edited:
Hello, during this time I sent computer to local service. I listed everything that I tried and all problems but local service could not find anything. They said that they changed termal paste, updated bios to the latest (it was already the upgraded) and updated all intel drivers (I did that too when MSI international support advised me, too). They also said that they run some stress tests and could not find anything (no crashes). They also performed system recovery before handing over the laptop.

So yesterday I downloaded WOW again and today, it just randomly had an error "Access violation, memory could not be read". I tought OK, it may be about Blizzard or WoW so I closed the game and while searching the error online, computer froze...
1725029913312.png


Then, I force restarted laptop, immediately after restart, I clicked start button and it froze AGAIN. It all happened in 2-3 minutes or so. I force restarted it 3rd time...

Are you connected directly to the wall socket or on a power bar?
If on a power bar, try directly to the socket, if a socket, try one in a different room.
Are you using the AC adapter 330W that came with it?

Once finished run the command prompts again.
In CMD (Run as admin) type sfc /scannow then type afterwards chkdsk /r
If you still have errors after the first scan, sfc /scannow, then you might need to re install your Windows, run it another time after IF corrupted files are detected again to confirm.
If you still have errors after the second scan, chkdsk /r, you might have a faulty SSD, run another time after to confirm, If corrupted sectors are again detected, if so,
then replace the SSD, or open an RMA with MSI, if your laptop still under warranty.

About electricity socket, I tried using it in with power bar and directly to the wall socket. With different houses. It froze in all cases.
I am using the AC adapter it came, always played games with AC plugged in otherwise there was major FPS drop.
Nothing had been found for sfc /scannow.
I will try chkdsk /r , I tried this one before sending laptop to the service but it had found nothing. I will run it again.

If you start experiencing this behavior after limiting the CPU's performance, it is likely that the CPU is causing a bottleneck in the game.

Did you still not have a minidump?
I am afraid that you might need to perform the system recovery to cross-check.
If the problem still persist, you need to connect the local service center for further inspection.
I checked now and I have a DumpStack.log file under C. But I can not open it, it says permission missing. I still don't have a minidump file under Windows folder.

Edit: I tried chkdsk /r, not from cmd because it said, system is using it and can not perform this rn so do you want to perform it while restarting? I chose yes and it performed it during restart. I could not understand whether it found something or just scanned it. It did not show me any sector or file names.
 
Last edited:
Hello again, today I had multiple soft-freezes and finally I could see BSOD. I checked Minidump files again and saw 3 minidump files two of them belong yesterday's crashes and one of them (083124-19140-01.dmp) belongs today's BSOD. I downloaded WinDBG, here I am sharing it's analysis. Thank you for your help so far.
Also, all three minidump files: https://drive.google.com/drive/folders/1Q874H8qJKlLV9aSP-QIYAgZWGkn5LZlH?usp=sharing

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

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

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


Loading Dump File [C:\Windows\Minidump\083124-19140-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 (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff806`64400000 PsLoadedModuleList = 0xfffff806`650134f0
Debug session time: Sat Aug 31 23:08:11.607 2024 (UTC + 3:00)
System Uptime: 1 days 4:34:10.571
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................................................
Loading User Symbols
PEB address is NULL !
Loading unloaded module list
.......................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`64815cb0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffeb88`7d54e440=0000000000000154
10: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_STORE_EXCEPTION (154)
The store component caught an unexpected exception.
Arguments:
Arg1: ffffc90c79c68000, Pointer to the store context or data manager
Arg2: ffffeb887d54e4f0, Exception information
Arg3: 0000000000000001, Reserved
Arg4: 0000000000000000, Reserved

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


KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 734

Key  : Analysis.Elapsed.mSec
Value: 9951

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

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

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

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

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

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

Key  : Bugcheck.Code.LegacyAPI
Value: 0x154

Key  : Bugcheck.Code.TargetModel
Value: 0x154

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: 0x154_c0000420_nt!ST_STORE_SM_TRAITS_::StDmPageRecordRemove

Key  : Failure.Hash
Value: {b82a73ea-d098-8451-8193-a5c6604483ac}

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

BUGCHECK_P1: ffffc90c79c68000

BUGCHECK_P2: ffffeb887d54e4f0

BUGCHECK_P3: 1

BUGCHECK_P4: 0

FILE_IN_CAB:  083124-19140-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

FAULTING_THREAD:  ffffc90c79c8c080

EXCEPTION_RECORD:  ffffeb887d54f4e8 -- (.exr 0xffffeb887d54f4e8)
ExceptionAddress: fffff806649c428c (nt!ST_STORE<SM_TRAITS>::StDmPageRecordRemove+0x00000000000000dc)
   ExceptionCode: c0000420 (Assertion failure)
ExceptionFlags: 00000000
NumberParameters: 0
Assertion: (((NTSTATUS)(Status)) >= 0)

EXCEPTION_PARAMETER1:  00000000bb4403a8

EXCEPTION_PARAMETER2:  0000000000001161

CONTEXT:  ffffeb887d54ed00 -- (.cxr 0xffffeb887d54ed00)
rax=00000000c0000225 rbx=ffffc90c79c680e8 rcx=ffffc90c74d99000
rdx=00000000000002f4 rsi=0000000000000000 rdi=ffffc90c79c68050
rip=fffff806649c428c rsp=ffffeb887d54f720 rbp=ffffc90c79c680d0
r8=000000000000037a  r9=00000000bb4403a8 r10=0000000000001161
r11=0000000000000009 r12=ffffc90c79c68090 r13=0000000000001000
r14=000000000006f4a2 r15=ffffc90c8b56e7b0
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00040282
nt!ST_STORE<SM_TRAITS>::StDmPageRecordRemove+0xdc:
fffff806`649c428c cd2c            int     2Ch
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MemCompression

ERROR_CODE: (NTSTATUS) 0xc0000420 - Onaylama hatas  olu tu.

EXCEPTION_CODE_STR:  c0000420

EXCEPTION_STR:  0xc0000420

STACK_TEXT:
ffffeb88`7d54f720 fffff806`649c27ad     : ffffc90c`79c68050 00000000`0022c2b0 ffffc90c`8cb6d858 ffffc90c`70066088 : nt!ST_STORE<SM_TRAITS>::StDmPageRecordRemove+0xdc
ffffeb88`7d54f760 fffff806`649c2623     : ffffc90c`79c68050 ffffeb88`7d54f810 ffffc90c`70066138 ffffc90c`70066088 : nt!ST_STORE<SM_TRAITS>::StDmCombinePageRecords+0x85
ffffeb88`7d54f790 fffff806`649c2a4d     : ffffc90c`00000000 ffffc90c`70066000 ffffc90c`79c680a8 ffffc90c`70066000 : nt!ST_STORE<SM_TRAITS>::StDmCombineBufferProcess+0x25f
ffffeb88`7d54f840 fffff806`649c579c     : ffff64b4`00000000 ffffc90c`79c68050 ffffc90c`70066000 ffffc90c`74b4a748 : nt!ST_STORE<SM_TRAITS>::StDmCombineRegion+0x20d
ffffeb88`7d54f8b0 fffff806`649c53e6     : ffffc90c`79c68050 ffffeb88`7d54f959 ffffc90c`79c68050 fffff806`64a59a31 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageFindSpace+0x5c
ffffeb88`7d54f8f0 fffff806`649c3fd3     : ffffc90c`88915000 ffffc90c`79c8c770 ffffc90c`79c68000 ffffc90c`74b4a710 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageAdd+0x8e
ffffeb88`7d54f9c0 fffff806`649c7337     : 00000000`00000000 fffff806`00000050 ffffc90c`88915000 fffff806`646e6d4c : nt!ST_STORE<SM_TRAITS>::StDmPageAdd+0xa3
ffffeb88`7d54fa20 fffff806`648ce1aa     : ffffc90c`79c68000 ffffeb88`7d54fac8 00000000`00000001 ffffc90c`74637000 : nt!ST_STORE<SM_TRAITS>::StWorkItemProcess+0x383
ffffeb88`7d54fa70 fffff806`647563c1     : ffffc90c`00000000 ffffc90c`00000000 ffffc90c`79c8c080 ffffc90c`00000002 : nt!SMKM_STORE<SM_TRAITS>::SmStWorker+0x177a26
ffffeb88`7d54fb00 fffff806`64754d07     : ffffc90c`79c68000 fffff806`647563b0 ffffeb88`7d4b7078 006fe47f`b19bbdff : nt!SMKM_STORE<SM_TRAITS>::SmStWorkerThread+0x11
ffffeb88`7d54fb30 fffff806`6481ae24     : ffff8000`383dc180 ffffc90c`79c8c080 fffff806`64754cb0 00000000`00000000 : nt!PspSystemThreadStartup+0x57
ffffeb88`7d54fb80 00000000`00000000     : ffffeb88`7d550000 ffffeb88`7d549000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!ST_STORE<SM_TRAITS>::StDmPageRecordRemove+dc

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.4036

STACK_COMMAND:  .cxr 0xffffeb887d54ed00 ; kb

BUCKET_ID_FUNC_OFFSET:  dc

FAILURE_BUCKET_ID:  0x154_c0000420_nt!ST_STORE_SM_TRAITS_::StDmPageRecordRemove

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b82a73ea-d098-8451-8193-a5c6604483ac}

Followup:     MachineOwner
---------
 
Last edited:
Hello again, today I had multiple soft-freezes and finally I could see BSOD. I checked Minidump files again and saw 3 minidump files two of them belong yesterday's crashes and one of them (083124-19140-01.dmp) belongs today's BSOD. I downloaded WinDBG, here I am sharing it's analysis. Thank you for your help so far.
Also, all three minidump files: https://drive.google.com/drive/folders/1Q874H8qJKlLV9aSP-QIYAgZWGkn5LZlH?usp=sharing

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

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

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


Loading Dump File [C:\Windows\Minidump\083124-19140-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 (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff806`64400000 PsLoadedModuleList = 0xfffff806`650134f0
Debug session time: Sat Aug 31 23:08:11.607 2024 (UTC + 3:00)
System Uptime: 1 days 4:34:10.571
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................................................
Loading User Symbols
PEB address is NULL !
Loading unloaded module list
.......................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`64815cb0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffeb88`7d54e440=0000000000000154
10: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_STORE_EXCEPTION (154)
The store component caught an unexpected exception.
Arguments:
Arg1: ffffc90c79c68000, Pointer to the store context or data manager
Arg2: ffffeb887d54e4f0, Exception information
Arg3: 0000000000000001, Reserved
Arg4: 0000000000000000, Reserved

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


KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 734

Key  : Analysis.Elapsed.mSec
Value: 9951

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

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

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

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

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

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

Key  : Bugcheck.Code.LegacyAPI
Value: 0x154

Key  : Bugcheck.Code.TargetModel
Value: 0x154

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: 0x154_c0000420_nt!ST_STORE_SM_TRAITS_::StDmPageRecordRemove

Key  : Failure.Hash
Value: {b82a73ea-d098-8451-8193-a5c6604483ac}

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

BUGCHECK_P1: ffffc90c79c68000

BUGCHECK_P2: ffffeb887d54e4f0

BUGCHECK_P3: 1

BUGCHECK_P4: 0

FILE_IN_CAB:  083124-19140-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

FAULTING_THREAD:  ffffc90c79c8c080

EXCEPTION_RECORD:  ffffeb887d54f4e8 -- (.exr 0xffffeb887d54f4e8)
ExceptionAddress: fffff806649c428c (nt!ST_STORE<SM_TRAITS>::StDmPageRecordRemove+0x00000000000000dc)
   ExceptionCode: c0000420 (Assertion failure)
ExceptionFlags: 00000000
NumberParameters: 0
Assertion: (((NTSTATUS)(Status)) >= 0)

EXCEPTION_PARAMETER1:  00000000bb4403a8

EXCEPTION_PARAMETER2:  0000000000001161

CONTEXT:  ffffeb887d54ed00 -- (.cxr 0xffffeb887d54ed00)
rax=00000000c0000225 rbx=ffffc90c79c680e8 rcx=ffffc90c74d99000
rdx=00000000000002f4 rsi=0000000000000000 rdi=ffffc90c79c68050
rip=fffff806649c428c rsp=ffffeb887d54f720 rbp=ffffc90c79c680d0
r8=000000000000037a  r9=00000000bb4403a8 r10=0000000000001161
r11=0000000000000009 r12=ffffc90c79c68090 r13=0000000000001000
r14=000000000006f4a2 r15=ffffc90c8b56e7b0
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00040282
nt!ST_STORE<SM_TRAITS>::StDmPageRecordRemove+0xdc:
fffff806`649c428c cd2c            int     2Ch
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MemCompression

ERROR_CODE: (NTSTATUS) 0xc0000420 - Onaylama hatas  olu tu.

EXCEPTION_CODE_STR:  c0000420

EXCEPTION_STR:  0xc0000420

STACK_TEXT:
ffffeb88`7d54f720 fffff806`649c27ad     : ffffc90c`79c68050 00000000`0022c2b0 ffffc90c`8cb6d858 ffffc90c`70066088 : nt!ST_STORE<SM_TRAITS>::StDmPageRecordRemove+0xdc
ffffeb88`7d54f760 fffff806`649c2623     : ffffc90c`79c68050 ffffeb88`7d54f810 ffffc90c`70066138 ffffc90c`70066088 : nt!ST_STORE<SM_TRAITS>::StDmCombinePageRecords+0x85
ffffeb88`7d54f790 fffff806`649c2a4d     : ffffc90c`00000000 ffffc90c`70066000 ffffc90c`79c680a8 ffffc90c`70066000 : nt!ST_STORE<SM_TRAITS>::StDmCombineBufferProcess+0x25f
ffffeb88`7d54f840 fffff806`649c579c     : ffff64b4`00000000 ffffc90c`79c68050 ffffc90c`70066000 ffffc90c`74b4a748 : nt!ST_STORE<SM_TRAITS>::StDmCombineRegion+0x20d
ffffeb88`7d54f8b0 fffff806`649c53e6     : ffffc90c`79c68050 ffffeb88`7d54f959 ffffc90c`79c68050 fffff806`64a59a31 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageFindSpace+0x5c
ffffeb88`7d54f8f0 fffff806`649c3fd3     : ffffc90c`88915000 ffffc90c`79c8c770 ffffc90c`79c68000 ffffc90c`74b4a710 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageAdd+0x8e
ffffeb88`7d54f9c0 fffff806`649c7337     : 00000000`00000000 fffff806`00000050 ffffc90c`88915000 fffff806`646e6d4c : nt!ST_STORE<SM_TRAITS>::StDmPageAdd+0xa3
ffffeb88`7d54fa20 fffff806`648ce1aa     : ffffc90c`79c68000 ffffeb88`7d54fac8 00000000`00000001 ffffc90c`74637000 : nt!ST_STORE<SM_TRAITS>::StWorkItemProcess+0x383
ffffeb88`7d54fa70 fffff806`647563c1     : ffffc90c`00000000 ffffc90c`00000000 ffffc90c`79c8c080 ffffc90c`00000002 : nt!SMKM_STORE<SM_TRAITS>::SmStWorker+0x177a26
ffffeb88`7d54fb00 fffff806`64754d07     : ffffc90c`79c68000 fffff806`647563b0 ffffeb88`7d4b7078 006fe47f`b19bbdff : nt!SMKM_STORE<SM_TRAITS>::SmStWorkerThread+0x11
ffffeb88`7d54fb30 fffff806`6481ae24     : ffff8000`383dc180 ffffc90c`79c8c080 fffff806`64754cb0 00000000`00000000 : nt!PspSystemThreadStartup+0x57
ffffeb88`7d54fb80 00000000`00000000     : ffffeb88`7d550000 ffffeb88`7d549000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!ST_STORE<SM_TRAITS>::StDmPageRecordRemove+dc

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.4036

STACK_COMMAND:  .cxr 0xffffeb887d54ed00 ; kb

BUCKET_ID_FUNC_OFFSET:  dc

FAILURE_BUCKET_ID:  0x154_c0000420_nt!ST_STORE_SM_TRAITS_::StDmPageRecordRemove

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b82a73ea-d098-8451-8193-a5c6604483ac}

Followup:     MachineOwner
---------
ntoskrnl.exe error might be related to Intel or Nvidia graphics drivers or other factors. Since the settings of your laptop was likely restored by the service center, I’m not sure what you’ve done afterward, like updating drivers or adjusting settings. If you’ve updated to the generic version of Intel and Nvidia graphics drivers, I recommend using the DDU tool to cleanly install the Intel and Nvidia graphics drivers from the MSI website for cross-verification.
 
I only deleted Norton Antivirus after the second system restore because I don't use antivirus software normally. I did not touch drivers whatsoever. However according to technician's note, they clean installed all Intel drivers and updated BIOS (which was already up to date, there were only 3 months between the BIOS dates but the BIOS version was same). This action seemed unnecessary because before sending laptop to local support, I contacted with MSI Global Support and they checked BIOS, drivers, apps that have been installed etc. and have clean installed Intel and NVIDIA drivers using the DDU. They also had sent me driver files manually. It did not work either so they advised me to send the laptop to local support to hardware check. Then the second system restore occurred. I am back to square one. I asked for a refund second time but technicians said that there is not any hardware problems according to tests so I don't know what to do. I am thinking that this may be a chronic issue but I couldn't find anyone online using this exact laptop model, also from where I live, there are only two laptops of this model have been sold physically.
 
I only deleted Norton Antivirus after the second system restore because I don't use antivirus software normally. I did not touch drivers whatsoever. However according to technician's note, they clean installed all Intel drivers and updated BIOS (which was already up to date, there were only 3 months between the BIOS dates but the BIOS version was same). This action seemed unnecessary because before sending laptop to local support, I contacted with MSI Global Support and they checked BIOS, drivers, apps that have been installed etc. and have clean installed Intel and NVIDIA drivers using the DDU. They also had sent me driver files manually. It did not work either so they advised me to send the laptop to local support to hardware check. Then the second system restore occurred. I am back to square one. I asked for a refund second time but technicians said that there is not any hardware problems according to tests so I don't know what to do. I am thinking that this may be a chronic issue but I couldn't find anyone online using this exact laptop model, also from where I live, there are only two laptops of this model have been sold physically.
Hello,

The problem is that Gen 13 and 14 intel chips are crap, this is why intel stock is falling. Anyone buying those chips has the same problem as you (me included), but intel has only after 8 months come and said, yes it was us on the desktop CPUs. It is quite obvious the the same laptop CPUs are failing. But since they have not even acknowledged the problem on laptops, we have no solution.

 
Hello,

The problem is that Gen 13 and 14 intel chips are crap, this is why intel stock is falling. Anyone buying those chips has the same problem as you (me included), but intel has only after 8 months come and said, yes it was us on the desktop CPUs. It is quite obvious the the same laptop CPUs are failing. But since they have not even acknowledged the problem on laptops, we have no solution.

i doubt that this is the problem here, problem with 13th and 14th gen is slow degradation, it takes time for cpu to start failing, and laptop should not even reach high enough voltage for dmg to occur so it would probably take even longer
 
So are we just waiting for a possibility for an announcement, as a result a refund and our only option is buying a different gaming laptop? The distributor does not take refund currently because they claimed nothing is wrong on MSI's end.
 
Back
Top