Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
20623 Discussions

BSOD ERROR CODE NMI_HARDWARE_FAILURE while watching netflix,prime,vlc IT SHOWS GenuineIntel.sys

nagi001
Beginner
2,151 Views
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:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                        ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6437

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on LAPTOP-TU3AEUBO

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 27935

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  80

BUGCHECK_P1: 4f4454

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffc301`4a75bb38 fffff803`1cab376a     : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffc301`4a75bb40 fffff803`1bbc15b0     : 00000000`00000000 ffffd40c`73474808 fffff803`1d250760 ffffd40c`73474808 : nt!HalBugCheckSystem+0x7a
ffffc301`4a75bb80 fffff803`1cbb532e     : 00000000`00000000 ffffc301`4a75bc29 ffffd40c`73474808 fffff803`1d250760 : PSHED!PshedBugCheckSystem+0x10
ffffc301`4a75bbb0 fffff803`1cab7e22     : 00000000`000000b0 00000000`000000b0 fffff803`1d250760 00000000`0000005c : nt!WheaReportHwError+0x46e
ffffc301`4a75bc90 fffff803`1cb0cc02     : 00000000`00000001 ffffc301`4a75bd10 00000000`00000000 fffff803`1cb1f4b0 : nt!HalHandleNMI+0x142
ffffc301`4a75bcc0 fffff803`1ca00e82     : 00000000`00000002 ffffc301`4a75bed0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x132
ffffc301`4a75bd10 fffff803`1ca00c52     : 00000000`00000002 00000000`00000000 afafafaf`afafafaf afafafaf`afafafaf : nt!KxNmiInterrupt+0x82
ffffc301`4a75be50 fffff803`3c10138f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x212
ffff8887`c725f5b8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x1f


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x80_4F4454_GenuineIntel_NOERRREC_IMAGE_GenuineIntel.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

0 Kudos
3 Replies
Sebastian_M_Intel
Moderator
2,054 Views

Hello nagi001, 

 

Thank you for posting on the Intel® communities.   

 

In order to better assist you, please provide the following: 

 

1. Run the Intel® System Support Utility (Intel® SSU) and attach the report generated:   

  • Open the application, check the "Everything" box, and click on "Scan" to see the system and device information. By default, Intel® SSU will take you to the "Summary View".    
  • Click on the menu where it says "Summary" to change to "Detailed View".    
  • To save your scan, click on "Next", then "Save".    
  • Use the option under the reply window to attach the report to the thread (Drag and drop here or browse files to attach).   

 

2. Provide the Report for Intel® Graphics Drivers, follow this link

3. Can you provide details about how the issue occur? Is it watching any type of content using Netflix, Amazon Prime, and VLC media player? Does it happen only with these applications?  

 

Regards, 

 

Sebastian M  

Intel Customer Support Technician


0 Kudos
Sebastian_M_Intel
Moderator
2,045 Views

Hello nagi001,  

 

Were you able to check the previous post and get the information requested? Please let me know if you need more assistance.   

 

Regards,  

  

Sebastian M  

Intel Customer Support Technician


0 Kudos
Sebastian_M_Intel
Moderator
2,036 Views

Hello nagi001,  

  

We have not heard back from you, so we will close this inquiry. If you need further assistance or if you have additional questions, please create a new thread and we will gladly assist you.  

 

Regards,  

  

Sebastian M  

Intel Customer Support Technician 


0 Kudos
Reply