開機後不久BSOD igdkmd64.sys和win32k.sys

抱歉，以為已上傳到OneDrive並共用minidump檔案，你們就看得到

Debug session time: Wed Jan  1 00:32:39.159 2020 (UTC + 8:00)

                     Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {100000032, 8, 0, fffff80756624863}

*** WARNING: Unable to verify timestamp for igdkmd64.sys

*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys

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

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : memory_corruption

Followup:     memory_corruption

---

0: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high.  This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: 0000000100000032, memory referenced

Arg2: 0000000000000008, IRQL

Arg3: 0000000000000000, bitfield :

 bit 0 : value 0 = read operation, 1 = write operation

 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

Arg4: fffff80756624863, address which referenced memory

Debugging Details:

---

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  1.0

BIOS_DATE:  09/05/2019

BASEBOARD_PRODUCT:  H310M PRO-VH PLUS (MS-7C13)

BASEBOARD_VERSION:  1.0

BUGCHECK_P1: 100000032

BUGCHECK_P2: 8

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80756624863

READ_ADDRESS: fffff80756b733b8: Unable to get MiVisibleState

 0000000100000032

CURRENT_IRQL:  8

FAULTING_IP:

nt!KeInsertQueueDpc+3

fffff807`56624863 384533          cmp     byte ptr [rbp+33h],al

CPU_COUNT: 4

CPU_MHZ: e10

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: b

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  AV

PROCESS_NAME:  System

ANALYSIS_VERSION: 10.0.10240.9 amd64fre

TRAP_FRAME:  fffff8075aaaac40 -- (.trap 0xfffff8075aaaac40)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=ffff970d268e26e8

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff80756624863 rsp=fffff8075aaaadd8 rbp=00000000ffffffff

 r8=0000000000000000  r9=0000000000000000 r10=fffff80756624860

r11=ffff970d2663e91c r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei pl zr na po nc

nt!KeInsertQueueDpc+0x3:

fffff80756624863 384533          cmp     byte ptr [rbp+33h],al ss:0018:0000000100000032=??

Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff807567d32e9 to fffff807567c14e0

STACK_TEXT: 

fffff8075aaaaaf8 fffff807567d32e9 : 000000000000000a 0000000100000032 0000000000000008 0000000000000000 : nt!KeBugCheckEx

fffff8075aaaab00 fffff807567cf62b : 0000000000000034 000000000001aa8b 0000000000000033 0000000000000008 : nt!KiBugCheckDispatch+0x69

fffff8075aaaac40 fffff80756624863 : fffff8075ad4516e ffff970d268e2030 0000000000000000 0000000000000000 : nt!KiPageFault+0x46b

fffff8075aaaadd8 fffff8075ad4516e : ffff970d268e2030 0000000000000000 0000000000000000 ffff970d26702000 : nt!KeInsertQueueDpc+0x3

fffff8075aaaade0 fffff8075e0c4eb1 : 000009e92ba58b58 0000000000000000 0000000000000000 ffff970d00000000 : dxgkrnl!DpQueueDpc+0x4e

fffff8075aaaae10 000009e92ba58b58 : 0000000000000000 0000000000000000 ffff970d00000000 0000000000000000 : igdkmd64+0x54eb1

fffff8075aaaae18 0000000000000000 : 0000000000000000 ffff970d00000000 0000000000000000 0000000000400a02 : 0x000009e9`2ba58b58

STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt

    fffff80756624841 - nt!PpmPerfAction+3e1

 [ 7c:7f ]

    fffff80756624851 - nt!PpmPerfAction+3f1 (+0x10)

 [ cc:4c ]

    fffff80756624861 - nt!KeInsertQueueDpc+1 (+0x10)

 [ 83:b3 ]

    fffff80756624869 - nt!KeInsertQueueDpc+9 (+0x08)

 [ 24:30 ]

    fffff80756624871 - nt!KeInsertQueueDpc+11 (+0x08)

 [ 48:2c ]

    fffff80756624879 - nt!KeInsertQueueDpc+19 (+0x08)

 [ cc:e8 ]

    fffff80756624ba4-fffff80756624ba5  2 bytes - nt!KiInsertQueueDpc+324 (+0x32b)

 [ 48 ff:4c 8b ]

    fffff80756624bab-fffff80756624bae  4 bytes - nt!KiInsertQueueDpc+32b (+0x07)

 [ 0f 1f 44 00:e8 f0 2e a9 ]

    fffff80756624bb7-fffff80756624bb8  2 bytes - nt!KiInsertQueueDpc+337 (+0x0c)

 [ 48 ff:4c 8b ]

    fffff80756624bbe-fffff80756624bbf  2 bytes - nt!KiInsertQueueDpc+33e (+0x07)

 [ 0f 1f:e8 ad ]

    fffff80756624bc1 - nt!KiInsertQueueDpc+341 (+0x03)

 [ 00:a9 ]

    fffff807567c3048-fffff807567c3049  2 bytes - nt!KiInterruptDispatch+b8 (+0x19e487)

 [ 48 ff:4c 8b ]

    fffff807567c304f-fffff807567c3052  4 bytes - nt!KiInterruptDispatch+bf (+0x07)

 [ 0f 1f 44 00:e8 1c 60 8f ]

23 errors : !nt (fffff80756624841-fffff807567c3052)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup:     memory_corruption

你得拿回商場要求保固。

您好！

我們了解到您關於Windows操作系統出現藍屏的問題，

我們需要您提供您的dump文件來為您分析您系統藍屏的原因，

建議你嘗試以下方案進行操作：

打開控制臺>>系統>>進堦系統設定>>進階>>啓動及修復>>設定，

寫入偵錯咨詢>>选择“小記憶體傾印（256KB）”，傾印檔案選擇默認，確定。

完成後重新啟動您的電腦，使設定生效；再次出現這個問題，前往檔案C:\Windows\Minidump提取即可。

我們將通過私人訊息聯繫您，請注意查收。