NMI_HARDWARE_FAILURE mavi ekran

H

homelander

Hectopat
Katılım
10 Ekim 2020
Mesajlar
8
Daha fazla  
Cinsiyet
Erkek
Selamlar. Yeni bir bilgisayar aldım ve Windows için yeni bir admin kullanıcı hesabı oluşturmaktan tutun; Discord, herhangi bir oyun veya driver yüklemeye kadar ne zaman yeni bir şey kurmaya çalışsam NMI_HARDWARE_FAILURE kodlu hatayı aldım ve mavi ekran verdi. Açıldıktan sonra aynı işlemi tekrarladığımda mavi ekran almıyorum, normal bir şekilde devam ediyor. Yani tahminim üzere yeni bir kurulum içeren durumlarda veriyor fakat tam da neden kaynaklandığını bilemiyorum. İnternette biraz araştırdım, driverları güncelleyin falan denmiş. 1-2 kez aynı hatayla mavi ekran alarak güncellemeyi tamamladım ama hala bu sorunu yaşıyorum. Çözüm öneriniz var mı?

minidump.rar
 
Son düzenleme:
Tarihe göre sırala Puana göre sırala
Microsoft'un sitesinde hata kodunu arattığımda donanımsal kaynaklı olabileceği yazıyor. Dosyalarda da işlemci kaynaklı bir sorun görünüyor.
Kod: 
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: 4405

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 12285

    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:
fffff802`78e80b38 fffff802`75ab389a     : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff802`78e80b40 fffff802`714e15b0     : 00000000`00000000 ffffce8f`b73e44c8 fffff802`76250760 ffffce8f`b73e44c8 : nt!HalBugCheckSystem+0x7a
fffff802`78e80b80 fffff802`75bb54ae     : 00000000`00000000 fffff802`78e80c29 ffffce8f`b73e44c8 fffff802`76250760 : PSHED!PshedBugCheckSystem+0x10
fffff802`78e80bb0 fffff802`75ab7f52     : 00000000`000000a0 00000000`000000a0 fffff802`76250760 00000000`0000005c : nt!WheaReportHwError+0x46e
fffff802`78e80c90 fffff802`75b0ce12     : 00000000`00000001 fffff802`78e80d10 00000000`00000000 fffff802`75b1f6a0 : nt!HalHandleNMI+0x142
fffff802`78e80cc0 fffff802`759ff582     : 00000000`00000000 fffff802`78e80ed0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x132
fffff802`78e80d10 fffff802`759ff352     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
fffff802`78e80e50 fffff802`8c35138f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x212
fffff802`78e5c5e8 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
---------

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

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 12877

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

    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:
ffffd780`0524db38 fffff800`46ab389a     : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd780`0524db40 fffff800`444015b0     : 00000000`00000000 ffffc68c`b301e848 fffff800`47250760 ffffc68c`b301e848 : nt!HalBugCheckSystem+0x7a
ffffd780`0524db80 fffff800`46bb54ae     : 00000000`00000000 ffffd780`0524dc29 ffffc68c`b301e848 fffff800`47250760 : PSHED!PshedBugCheckSystem+0x10
ffffd780`0524dbb0 fffff800`46ab7f52     : 00000000`000000b0 00000000`000000b0 fffff800`47250760 00000000`0000005c : nt!WheaReportHwError+0x46e
ffffd780`0524dc90 fffff800`46b0ce12     : 00000000`00000001 ffffd780`0524dd10 00000000`00000000 fffff800`46b1f6a0 : nt!HalHandleNMI+0x142
ffffd780`0524dcc0 fffff800`469ff582     : 00000000`00000000 ffffd780`0524ded0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x132
ffffd780`0524dd10 fffff800`469ff352     : 00000000`00000000 00000000`00000000 d2b4b1ac`779dfbfe f2b691ae`579fdbfc : nt!KxNmiInterrupt+0x82
ffffd780`0524de50 fffff800`5fbe138f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x212
fffff20a`ace4f5e8 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
---------

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

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 14075

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

    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:
ffffa900`01f94b38 fffff802`1ceb389a     : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffa900`01f94b40 fffff802`197a15b0     : 00000000`00000000 ffffd004`cd29b8c8 fffff802`1d650760 ffffd004`cd29b8c8 : nt!HalBugCheckSystem+0x7a
ffffa900`01f94b80 fffff802`1cfb54ae     : 00000000`00000000 ffffa900`01f94c29 ffffd004`cd29b8c8 fffff802`1d650760 : PSHED!PshedBugCheckSystem+0x10
ffffa900`01f94bb0 fffff802`1ceb7f52     : 00000000`000000b0 00000000`000000b0 fffff802`1d650760 00000000`0000005c : nt!WheaReportHwError+0x46e
ffffa900`01f94c90 fffff802`1cf0ce12     : 00000000`00000001 ffffa900`01f94d10 00000000`00000000 fffff802`1cf1f6a0 : nt!HalHandleNMI+0x142
ffffa900`01f94cc0 fffff802`1cdff582     : 00000000`00000000 ffffa900`01f94ed0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x132
ffffa900`01f94d10 fffff802`1cdff352     : 00000000`00000000 00000000`00000000 a22fd9f1`2e4cc137 a22ed9f0`2e4dc136 : nt!KxNmiInterrupt+0x82
ffffa900`01f94e50 fffff802`3b33138f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x212
ffffb905`3383f5e8 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
---------

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

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 14910

    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:
ffffb001`d2b94b38 fffff801`484b389a     : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffb001`d2b94b40 fffff801`457415b0     : 00000000`00000000 ffffce07`04b17078 fffff801`48c50760 ffffce07`04b17078 : nt!HalBugCheckSystem+0x7a
ffffb001`d2b94b80 fffff801`485b54ae     : 00000000`00000000 ffffb001`d2b94c29 ffffce07`04b17078 fffff801`48c50760 : PSHED!PshedBugCheckSystem+0x10
ffffb001`d2b94bb0 fffff801`484b7f52     : 00000000`000000b0 00000000`000000b0 fffff801`48c50760 00000000`0000005c : nt!WheaReportHwError+0x46e
ffffb001`d2b94c90 fffff801`4850ce12     : 00000000`00000001 ffffb001`d2b94d10 00000000`00000000 fffff801`4851f6a0 : nt!HalHandleNMI+0x142
ffffb001`d2b94cc0 fffff801`483ff582     : 00000000`00000000 ffffb001`d2b94ed0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x132
ffffb001`d2b94d10 fffff801`483ff352     : 00000000`00000000 00000000`00000000 6fa0ca89`80db147e 6fa0ca89`80db147e : nt!KxNmiInterrupt+0x82
ffffb001`d2b94e50 fffff801`65d2138f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x212
ffffc901`f8a3f5e8 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
---------

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

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 11778

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

    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:
ffff9300`f4194b38 fffff800`270b389a     : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff9300`f4194b40 fffff800`241915b0     : 00000000`00000000 ffffd50f`6540e648 fffff800`27850760 ffffd50f`6540e648 : nt!HalBugCheckSystem+0x7a
ffff9300`f4194b80 fffff800`271b54ae     : 00000000`00000000 ffff9300`f4194c29 ffffd50f`6540e648 fffff800`27850760 : PSHED!PshedBugCheckSystem+0x10
ffff9300`f4194bb0 fffff800`270b7f52     : 00000000`000000a0 00000000`000000a0 fffff800`27850760 00000000`0000005c : nt!WheaReportHwError+0x46e
ffff9300`f4194c90 fffff800`2710ce12     : 00000000`00000001 ffff9300`f4194d10 00000000`00000000 fffff800`2711f6a0 : nt!HalHandleNMI+0x142
ffff9300`f4194cc0 fffff800`26fff582     : 00000000`00000000 ffff9300`f4194ed0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x132
ffff9300`f4194d10 fffff800`26fff352     : 00000000`00000000 00000000`00000000 6fa0ca89`80db147e 6fa0ca89`80db147e : nt!KxNmiInterrupt+0x82
ffff9300`f4194e50 fffff800`426f138f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x212
ffffe507`afc3f5e8 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
---------
 
Artı 0 Eksi
@yika38 Hocam diğer dediklerinizi yaptım fakat Intel Dynamic Platform and Thermal Framework sürücüsünü kurduğumda, kullandığım işletim sisteminin buna uygun olmadığı uyarısını aldım. Şimdilik hata düzeldi mi düzelmedi mi bilemiyorum.
Herhangi bir değişim olmadı devam ediyor maalesef. :(
Bump
 
Son düzenleme:
Artı 0 Eksi
Uyarı! Bu konu 6 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Benzer konular

T
  • Soru
NMI_HARDWARE_FAILURE mavi ekran hatası
2
Mesaj
14
Görüntüleme
423
Taha Ersin
T
MrDoruk
  • Soru
"NMI_HARDWARE_FAILURE" Mavi Ekran Hatası
Mesaj
2
Görüntüleme
267
MrDoruk
MrDoruk
A
  • Soru
NMI_HARDWARE_FAILURE mavi ekran hatası
2
Mesaj
11
Görüntüleme
544
The G.O.A.T
The G.O.A.T
Eren AK
  • Soru
NMI_HARDWARE_FAILURE hatası
Mesaj
3
Görüntüleme
930
Enes3078
Enes3078
SswenzyyY
  • Çözüldü
Çözüldü  NMI_HARDWARE_FAILURE hatası
Mesaj
2
Görüntüleme
440
SswenzyyY
SswenzyyY

Technopat Haberler

Yeni konular

Yeni mesajlar

Geri
Yukarı