Error NMI_HARDARE_FAILURE Windows 10

  • Thread starter Thread starter yuraima esperanzavelasquez de tovar
  • Start date Start date
Y

yuraima esperanzavelasquez de tovar

Guest
Good afternoon, this error started since I upgraded from Windows 7 to Windows 10. In 2015.

After I updated, about 1 year later, the error began to appear, and I had not downloaded anything at all, so I started to format it and also already had little disk space.

After formatting, the pc was super fast. 1 year passed and it started to overheat so my son cleaned it. I am super fast. 2 years later, I started getting that NMI_HARDWARE_FAILURE error with a blue screen.

Since I don't know anything about that, my son checked the problem was the video card, so I updated and improved it but then IRQL_NOT_LESS_QUAL started to appear (with a blue screen), so I formatted the pc and no more errors came out.

Now in 2020, 4 days ago the NMI_HARDWARE_FAILURE error started to appear again (with blue screen). I am scared since I am a teacher and I need the computer to teach online, so my son has already updated the drivers, eliminated viruses, made updates (except the version of Windows 10 2004, we have 1909), I defragment it and I clean the disk and the registry, I check the hardware of all the devices (we have nothing but mouse, keyboard and monitor, just that), I check the health of the hard disk, processor, video card, sound card, ram card, etc. I don't know what else can be done please help me. thanks

Specs:

The system report was written at: 09/11/20 12:51:39
System name: YURAIMA
[System summary]

Element Value
OS name Microsoft Windows 10 Home
Version 10.0.18363 Build 18363
Additional OS description Not available
OS manufacturer Microsoft Corporation
YURAIMA system name
BIOSTAR Group system manufacturer
System model A780L3C
X64-based PC system type
System SKUs To Be Filled By O.E.M.
Processor AMD Sempron (tm) 145 Processor, 2800 Mhz, 1 main processors, 1 logic processors
BIOS Version and Date American Megatrends Inc. 080014, 12/6/2012
SMBIOS version 2.6
Integrated Controller Version 255.255
Legacy BIOS mode
BIOSTAR Group motherboard manufacturer
Motherboard Product A780L3C
Motherboard version
Platform role Desktop
Safe boot state Not supported
PCR7 configuration Link not possible
Windows directory C: \ Windows
System directory C: \ Windows \ system32
Boot Device \ Device \ HarddiskVolume1
Regional configuration Spain
Hardware abstraction layer Version = "10.0.18362.752"
Username YURAIMA \ Yuraima Velazquez
Time Zone Venezuela Standard Time
Installed physical memory (RAM) 4.00 GB
Total physical memory 3.75 GB
Available physical memory 1.46 GB
Total virtual memory 5.17 GB
Available virtual memory 2.64 GB
Paging file space 1.42 GB
Paging file C: \ pagefile.sys
Kernel DMA Protection Disabled
Virtualization-based security Not enabled
Device encryption support Reasons for automatic device encryption failure: TPM cannot be used, PCR7 binding is not supported, Hardware security test interface failed. The device is not in modern standby mode., DMA-compliant device or bus detected that is not allowed., TPM cannot be used
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V -Data Execution Protection Yes

And here I leave the minidump file of the blue screen and its content:


110920-27203-01


Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run
!analyze -v
nt!KeBugCheckEx:
fffff807`195c2ce0 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff807`1d480b80=????????????????
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: 0000000000000000, Status Byte
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4609

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on YURAIMA

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 8335

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

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 80

BUGCHECK_P1: 4f4454

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (
!blackboxbsd)


BLACKBOXNTFS: 1 (
!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

STACK_TEXT:
fffff807`1d480b78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


MODULE_NAME:
AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x80_4F4454_AuthenticAMD_NOERRREC_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ec7c4e30-0424-14b7-e620-7ca0ec9a908c}

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



Continue reading...
 
Back
Top