使用64bit 系統 dmp文件: https://drive.google.com/file/d/1Lh00vXkU1Mz5mXRjhUEfz2iCBMBEcyZr/view?usp=sharing 試過以下方法: -清理灰塵，重新插入RAM，CPU，顯示卡 -更新驅動 -更新windows系統 -更新BIOS -通過memtest 完全測試，所以應該RAM沒問題吧電腦配置顯示卡:GTX 1060 Motherboard: MSI b250m bazooka CPU: I5-7500 Ram: Kingston ddr4 8gb 2400mhz X2 Power supply: Antec 550w 銅請問可以如何解決呢

Windows 1809版本 ntoskrnl.exe 經常引起藍屏

匿名

好的，我再檢查一次CPU

我試過用Windows 1803的版本還是有類似的情況，所以應該不關Windows事

除了CPU外，主機板接觸不良是不是也有可能呢，我打算一次過拿去送修了

0 則留言

匿名

您好，

兩個日志基本一致，看問題都是從CPU 硬體錯誤檢測構架出來的，

一個硬體端口錯誤，一個函數異常錯誤引發 hard reboot。

hal!HalpMcaReportError

不知道您之前有沒有觸碰過CPU 會不會是沒有放好，但是目前日志顯示是硬體方面存在問題。

如果認爲還是驅動與Windows 10 的 1809 不相容，那麽可以嘗試安裝舊版系統看看有沒有問題。

0 則留言

匿名

剛把顯示卡拆下來，用內顯跑遊戲，跑了一會出現machine check exception，那事情有趣了，硬碟已經用HD TUNE檢查一次沒有壞軌

RAM 我分開2條各用一次還是有藍屏，(有一條還是新買的)

那麼剩下來應該只有驅動程式問題或是主機版吧，也有可能是1809的版本問題，以前的版本也沒那麼多怪事

我不太相信伯是CPU壞，因為CPU壞的機率太低了吧，我沒超頻而且整部電腦只是跑了一半多年。

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

Loading Dump File [C:\Windows\Minidump\030519-27484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 17763 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.1****1
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff****000`3b0ddbf0=000000000000009c
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - Bugcheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: ffff80003b0ddc20
Arg3: 0000000000000000
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER:  MSI

SYSTEM_PRODUCT_NAME:  MS-7A70

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  1.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1.70

BIOS_DATE:  07/03/2018

BASEBOARD_MANUFACTURER:  MSI

BASEBOARD_PRODUCT:  B250M BAZOOKA (MS-7A70)

BASEBOARD_VERSION:  1.0

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: ffff80003b0ddc20

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR:  0x9C_GenuineIntel

CPU_COUNT: 4

CPU_MHZ: d50

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R)  SIG: 8E'00000000 (cache) 8E'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

ANALYSIS_SESSION_HOST:  DESKTOP-DEFL3DP

ANALYSIS_SESSION_TIME:  03-05-2019 17:57:04.0733

ANALYSIS_VERSION: 10.0.18317.1001 amd64fre

BAD_STACK_POINTER:  ffff80003b0ddbe8

LAST_CONTROL_TRANSFER:  from fffff80052ecd00a to fffff800525cc440

STACK_TEXT:  
ffff8000`3b0ddbe8 fffff800`52ecd00a : 00000000`0000009c 00000000`00000000 ffff8000`3b0ddc20 00000000`00000000 : nt!KeBugCheckEx
ffff8000`3b0ddbf0 fffff800`52ecd481 : 00000000`00000004 ffff8000`3b0ddf50 00000000`00000000 00000000`00000004 : hal!HalpMcaReportError+0x10e
ffff8000`3b0ddd40 fffff800`52ecc69c : 00000000`00000000 ffff8000`3b0ddfd0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x131
ffff8000`3b0ddd70 fffff800`52ecd6c7 : ffffdd8d`0be69800 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
ffff8000`3b0ddda0 fffff800`526a53ab : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
ffff8000`3b0dddd0 fffff800`525dae7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0xb
ffff8000`3b0dde00 fffff800`525dab60 : ffff8000`00000000 fffff800`525daa9d 00000000`00000001 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffff8000`3b0ddf40 fffff800`5678136f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x260
ffffc303`a8a3f6a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x1f

THREAD_SHA1_HASH_MOD_FUNC:  7c5c59ad39e6527cb43445b5353a8a9ae211ef69

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  9472cc202531629a24d6dedfb892d90388e60b79

THREAD_SHA1_HASH_MOD:  017fb57dd2c8bb08a42a859207056f83b9fd79be

FOLLOWUP_IP: 
intelppm!MWaitIdle+1f
fffff800`5678136f 4585c9          test    r9d,r9d

FAULT_INSTR_CODE:  75c98545

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  intelppm!MWaitIdle+1f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f330253

IMAGE_VERSION:  10.0.17763.316

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1f

FAILURE_BUCKET_ID:  0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle

BUCKET_ID:  0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle

PRIMARY_PROBLEM_CLASS:  0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle

TARGET_TIME:  2019-03-05T09:51:46.000Z

OSBUILD:  17763

OSSERVICEPACK:  316

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  180914-1434

BUILDLAB_STR:  rs5_release

BUILDOSVER_STR:  10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME:  6e3

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9c_genuineintel_stackptr_error_intelppm!mwaitidle

FAILURE_ID_HASH:  {d82f1232-e6fd-ac41-d01e-ddeec73b684b}

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

2: kd> !blackboxbsd
Version: 168
Product type: 1

Auto advanced boot: FALSE
Advanced boot menu timeout: 30
Last boot succeeded: TRUE
Last boot shutdown: FALSE
Sleep in progrees: FALSE

Power button timestamp: 0
System running: TRUE
Connected standby in progress: FALSE
User shutdown in progress: FALSE
System shutdown in progress: FALSE
Sleep in progress: 0
Connected standby scenario instance id: 0
Connected standby entry reason: 0
Connected standby exit reason: 0
System sleep transitions to on: 0
Last reference time: 0x1d4d336792d4bb0
Last reference time checksum: 0x72f4a082
Last update boot id: 25

Boot attempt count: 1
Last boot checkpoint: TRUE
Checksum: 0xc
Last boot id: 25
Last successful shutdown boot id: 24
Last reported abnormal shutdown boot id: 24

Error info boot id: 0
Error info repeat count: 0
Error info other error count: 0
Error info code: 0
Error info other error count: 0

Power button last press time: 0
Power button cumulative press count: 0
Power button last press boot id: 0
Power button last power watchdog stage: 0
Power button watchdog armed: FALSE
Power button shutdown in progress: FALSE
Power button last release time: 0
Power button cumulative release count: 0
Power button last release boot id: 0
Power button error count: 0
Power button current connected standby phase: 0
Power button transition latest checkpoint id: 0
Power button transition latest checkpoint type: 0
Power button transition latest checkpoint sequence number: 0
2: kd> lmvm intelppm
Browse full module list
start             end                 module name
fffff800`56780000 fffff800`567be000   intelppm # (pdb symbols)          C:\ProgramData\Dbg\sym\intelppm.pdb\2B36D9ACA3A3A2421784F52213564FC81\intelppm.pdb
    Loaded symbol image file: intelppm.sys
    Mapped memory image file: C:\ProgramData\Dbg\sym\intelppm.sys\4F3302533e000\intelppm.sys
    Image path: \SystemRoot\System32\drivers\intelppm.sys
    Image name: intelppm.sys
    Browse all global symbols  functions  data
    Image was built with /Brepro flag.
    Timestamp:        4F330253 (This is a reproducible build file hash, not a timestamp)
    CheckSum:         0004553D
    ImageSize:        0003E000
    File version:     10.0.17763.316
    Product version:  10.0.17763.316
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     intelppm.sys
        OriginalFilename: intelppm.sys
        ProductVersion:   10.0.17763.316
        FileVersion:      10.0.17763.316 (WinBuild.160101.0800)
        FileDescription:  Processor Device Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.

0 則留言

匿名

另外剛剛又藍屏了，懷疑是Google chrome問題，請幫忙看一下

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

Loading Dump File [C:\Windows\Minidump\030519-29328-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 17763 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff802`7421c000 PsLoadedModuleList = 0xfffff802`74637ad0
Debug session time: Tue Mar  5 16:32:42.917 2019 (UTC + 8:00)
System Uptime: 0 days 18:36:04.343
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
..............................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`743cf440 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffff8c00`3ee4ba90=0000000000000124
1: 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
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffca08c23b0028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  17763.1.amd64fre.rs5_release.180914-1434

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffca08c23b0028

BUGCHECK_P3: be000000

BUGCHECK_P4: 100110a

BUGCHECK_STR:  0x124_GenuineIntel

CPU_COUNT: 4

CPU_MHZ: d50

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  f

ANALYSIS_SESSION_HOST:  DESKTOP-DEFL3DP

ANALYSIS_SESSION_TIME:  03-05-2019 16:44:10.0363

ANALYSIS_VERSION: 10.0.18317.1001 amd64fre

STACK_TEXT:  
ffff8c00`3ee4ba88 fffff802`74cce667 : 00000000`00000124 00000000`00000000 ffffca0****c00`3ee4bb00 fffff802`74ccff59 : 00000000`00000728 00000000`00000001 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x25e
ffff8c00`3ee4bb60 fffff802`74cd02de : 00000000`00000010 ffffca08`bb07aa10 ffff8c00`3ee4bd08 00000000`00000001 : hal!HalpMcaReportError+0x5d
ffff8c00`3ee4bcb0 fffff802`74cd01ba : ffffca08`bb07a750 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2
ffff8c00`3ee4bd00 fffff802`74cd0424 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
ffff8c00`3ee4bd40 fffff802`74ccf69c : 00000000`00000000 ffff8c00`3ee4bfd0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
ffff8c00`3ee4bd70 fffff802`74cd06c7 : ffffca08`bb07a750 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
ffff8c00`3ee4bda0 fffff802`744a83ab : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
ffff8c00`3ee4bdd0 fffff802`743dde7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0xb
ffff8c00`3ee4be00 fffff802`743ddb60 : 00000000`00000000 00000000`00000000 00000000`00000010 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffff8c00`3ee4bf40 00007ffd`e5ddd0a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x260
00000042`39bff518 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`e5ddd0a4

THREAD_SHA****b33cb0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

PRIMARY_PROBLEM_CLASS:  0x124_GenuineIntel_PROCESSOR_CACHE

TARGET_TIME:  2019-03-05T08:32:42.000Z

OSBUILD:  17763

OSSERVICEPACK:  316

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  180914-1434

BUILDLAB_STR:  rs5_release

BUILDOSVER_STR:  10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME:  28b3

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_cache

FAILURE_ID_HASH:  {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}

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

0 則留言

匿名

您好，

這是在玩游戲的時候出現的？應該是在玩游戲，猜是Web 游戲，

程式調用顯存位置的時候出現問題，顯示卡驅動可能有問題，也有可能是游戲設計本身有問題。

會不會是windows 1809版本與顯示卡驅動程式會有衝突問題

因為網上很多人都討論有關顯示卡與windows 1809的問題

0 則留言

Windows 1809版本 ntoskrnl.exe 經常引起藍屏

13 個回答