Question NMI_HARDWARE_FAILURE ntoskrnl.exe+416b40

[Dia4lit]

Hi! I've had this BSOD for a while now, but somehow it stopped for a while and now it's back after my Win11 update. And it's waaaay more frequent than before.
I think I can rule out hardware problems since I checked everything with Lenovo Vantage, Lenovo Diagnostic Tool, the memory test, hard drive tests. Everything seemed always alright.
This thing happen only when I'm watching something, this is a gaming laptop so I've used it to play and no problem whatsoever. Never a BSOD while gaming or editing on Sony Vegas, which is a very heavy program. Only when I'm watching something (on browser or a video player), but mostly on browser. I've changed browser and that didn't fix it. I updated all the drivers that I could update. I thought this could be a codec issue maybe, but I didn't find a way to solve it. My BIOS is definitely not up to date, there was one update, but I forgot to update it before updating to Win11 and now I don't have it anymore, probably they didn't make it for Win11.

So here I am.
The laptop is a Lenovo y540 and this is my configuration:

Windows 11 Pro 64-bit
CPU
Intel Core i5 9th @ 2.40GHz
RAM
8,00GB
Scheda Madre
LENOVO LNVNB161216 (U3E1)
Grafica
Intel UHD Graphics 630 (Lenovo)
4095 MBNVIDIA GeForce GTX 1650 (Lenovo)
Memorizzazione
238GB SAMSUNG MZVLB256HBHQ-000L2 ((SSD))
931GB Seagate ST1000LM049-2GH172

And these are my latest BSOD dumps:

==================================================
Dump File : 060122-10515-01.dmp
Crash Time : 01/06/2022 19:31:18
Bug Check String : NMI_HARDWARE_FAILURE
Bug Check Code : 0x00000080
Parameter 1 : 00000000004f4454 Parameter 2 : 00000000000000a0
Parameter 3 : 0000000000000000 Parameter 4 : 0000000000000000
Caused By Driver : PSHED.dll
Caused By Address : PSHED.dll+10c0
File Description : Driver errori hardware specifici di piattaforma
Product Name : Sistema operativo Microsoft® Windows®
Company : Microsoft Corporation
File Version : 10.0.21388.1000 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+416b40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\060122-10515-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 22000
Dump File Size : 1.971.836
Dump File Time : 01/06/2022 19:31:51
==================================================


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


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Dump completed successfully, progress percentage: 100

Symbol search path is: srv*
Executable search path is:
Page 2001fa6f4 too large to be in the dump file.
Windows 10 Kernel Version 22000 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff8046ac00000 PsLoadedModuleList = 0xfffff8046b829b90
Debug session time: Wed Jun 1 19:31:18.787 2022 (UTC + 2:00)
System Uptime: 0 days 2:58:26.604
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............................
Loading User Symbols

Loading unloaded module list
...............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff8046b016b40 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffac00c518eb50=0000000000000080
4: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

NMI_HARDWARE_FAILURE (80)
This is typically due to a hardware malfunction. The hardware supplier should
be called.
Arguments:
Arg1: 00000000004f4454, 'TDO'
Arg2: 00000000000000a0, Status Byte
Arg3: 0000000000000000
Arg4: 0000000000000000

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: Record *
• *

*

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5796

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 10901

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

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

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

Key : Bugcheck.DumpVsMemoryMatch
Value: True

Key : Dump.Attributes.AsUlong
Value: 1000

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1


FILE_IN_CAB: MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1000

BUGCHECK_CODE: 80

BUGCHECK_P1: 4f4454

BUGCHECK_P2: a0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffac00c518eb48 fffff8046b1015f0 : 0000000000000080 00000000004f4454 00000000000000a0 0000000000000000 : nt!KeBugCheckEx
ffffac00c518eb50 fffff8046d6b10c0 : 0000000000000000 ffffac00c518ec29 ffffbd828d2b98c8 ffffbd828d2b98c8 : nt!HalBugCheckSystem+0x90
ffffac00c518eb90 fffff8046b23f9f3 : 0000000000000000 ffffac00c518ec29 ffffbd828d2b98c8 fffff8046b8549f0 : PSHED!PshedBugCheckSystem+0x10
ffffac00c518ebc0 fffff8046b105dfa : 00000000000000a0 00000000000000a0 fffff8046b8549f0 fffff8046ae24b24 : nt!WheaReportHwError+0x393
ffffac00c518ec90 fffff8046b062cc0 : 0000000000000000 ffffac00c518ed10 0000000000000004 ffffac00c518ed10 : nt!HalHandleNMI+0x14a
ffffac00c518ecd0 fffff8046b022b82 : 0000000000000000 ffffac00c518eed0 0000000000000000 0000000000000004 : nt!KiProcessNMI+0x23ef00
ffffac00c518ed10 fffff8046b022903 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KxNmiInterrupt+0x82
ffffac00c518ee50 fffff804a2f6153f : fffff804a2f61594 ffffbd828d35d090 000017618a3571bd ffffac00c5100180 : nt!KiNmiInterrupt+0x243
ffffbc860245f498 fffff804a2f61594 : ffffbd828d35d090 000017618a3571bd ffffac00c5100180 ffffbd829d75c000 : intelppm!MWaitIdle+0x1f
ffffbc860245f4a0 fffff8046ae89061 : 0000000000000064 0000000000000000 0000000000000000 00000000000000a0 : intelppm!AcpiCStateIdleExecute+0x24
ffffbc860245f4d0 fffff8046ae88876 : ffffac00c529f180 fffff8046ae2a32a 0000000000000000 0000000000000000 : nt!PpmIdleExecuteTransition+0x661
ffffbc860245f970 fffff8046b01aa44 : 0000000000000000 ffffac00c510c240 ffffbd8292aee080 00000000000005b2 : nt!PoIdle+0x3a6
ffffbc860245fb40 0000000000000000 : ffffbc8602460000 ffffbc8602459000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x54


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x80_4F4454_GenuineIntel_NOERRREC_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d5ef3836-2107-b7ec-b4d4-4d2ae9fc0e02}

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

NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2205.18001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2205.18001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\ObjectiveC.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2205.18001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2205.18001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2205.18001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2205.18001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2205.18001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2205.18001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2205.18001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2205.18001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2205.18001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2205.18001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis'

 

[johnbl]

normally with this problem you would:
reset your bios to defaults or update the bios.
update your intel drivers
Intel® Driver & Support Assistant
-make sure the cpu is not overheating (check that the fans are running)
-remove all overclocking drivers.

most of the "fixes" are in the hope that it is a overheating problem with a component.

the assumption for this error is a hardware problem.