whea problem that didnt happen before upgrding my ssd

[hamzart]

having a problem that was not present here when i used to have a normal ssd but now i get crashes constantly after uprading to an nvme ssd (samsung ssd 970 evo plus 1t) 

and i couldnt pinpoint the problem but i got this when i used the debuging tool to open a dmp file from 19th of may 

and found this and it says intel 

i googled and found some saying it was a faulty cpu but mine worked just fine and it's 2 months old only and bought it new

some said gpu some said drivers 

i am confused tbh 

i need help to stop these crashes

my pc specs are 

gigabYTE B760M GAMING X DDR4

i7 12700k

4070 super 12gb 

64gb ram 

1tb samsung ssd 970 evo plus 1tb driver

asus-tuf-gaming-750w-bronze psu

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

EnableRedirectToV8JsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.031 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.125 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 29

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

Loading Dump File [C:\Windows\LiveKernelReports\WHEA\WHEA-20240519-1951.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 19045 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff800`6ae00000 PsLoadedModuleList = 0xfffff800`6ba2a7c0
Debug session time: Sun May 19 19:51:36.353 2024 (UTC + 1:00)
System Uptime: 0 days 0:00:08.973
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
PEB is paged out (Peb.Ldr = 000000cd`21993018). Type ".hh dbgerr001" for details
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
12: 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: 0000000000000007, BOOT Error
Arg2: ffffd58fc122d150, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1608

Key : Analysis.Elapsed.mSec
Value: 1666

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x124

Key : Dump.Attributes.AsUlong
Value: 18

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: LKD_0x124_7_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

Key : Failure.Hash
Value: {5ea80f6a-69bf-5d6f-8fd2-cd87deb91a03}

BUGCHECK_CODE: 124

BUGCHECK_P1: 7

BUGCHECK_P2: ffffd58fc122d150

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB: WHEA-20240519-1951.dmp

DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

PROCESS_NAME: smss.exe

STACK_TEXT:
ffff9209`30a370d0 fffff800`6b7609ff : ffffd58f`c122d130 00000000`00000000 ffffd58f`c122d150 00000000`00000022 : nt!LkmdTelCreateReport+0x139
ffff9209`30a37610 fffff800`6b7608f6 : ffffd58f`c122d130 fffff800`00000000 000000cd`00000000 000000cd`21b7f760 : nt!WheapReportLiveDump+0x7b
ffff9209`30a37650 fffff800`6b5d57bd : 00000000`00000001 ffff9209`30a37ac0 000000cd`21b7f760 00000000`000002a0 : nt!WheapReportDeferredLiveDumps+0x7a
ffff9209`30a37680 fffff800`6b47b3f7 : 00000000`00000000 ffffd58f`c42a37a0 00000000`00000103 00000000`00000000 : nt!WheaCrashDumpInitializationComplete+0x59
ffff9209`30a376b0 fffff800`6b211b05 : ffffd58f`c4670000 ffffd58f`c79ca060 ffff9209`30a37ac0 ffffd58f`00000000 : nt!NtSetSystemInformation+0x1f7
ffff9209`30a37a40 00007ffa`7b150624 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000cd`21b7f708 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`7b150624

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: LKD_0x124_7_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5ea80f6a-69bf-5d6f-8fd2-cd87deb91a03}

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

12: kd> lmvm GenuineIntel
Browse full module list
start end module name
Mini Kernel Dump does not contain unloaded driver list

[LeonWaksman]

1. In order to get better information about your system, please download the Intel System Support Utility (SSU). Run the SSU scan (check "Everything") and save the results. The .txt file with the results please attach to your post.

2. What is the P/N of the old SSD?

3. Was the Windows reinstalled or the drive was cloned?

Leon

[hamzart]

1 i did attach the file here

2 my ssd was an hp s750 2.5" 1tb P/N: 16L54AA#UUF

3 windows was reinstaled then cracked instead of activated i didnt have a copy at that time now i do but ig it messed some files

and as i sid before the ssd i never had any crash 

[LeonWaksman]

1. Download and install the driver for your SSD.  From the same page, download and install Magician Software for Windows. With this software you may update  the SSD firmware and check the healthyness status.

2. "Cracked Windows" - I don't know if we can help you. Any way try to repair the Windows installation with An in-place upgrade.

Leon