win10 1803 360AP导致蓝屏

今天上午突然蓝屏，然后查看minidump，其中存在360AP字样。附上minidump文字和文件百度云地址。地址：链接: https://pan.baidu.com/s/1UBUtJcmnUdwMa_uTW_mOlg 密码: m7m7

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a39ff35db9372533, 0, fffff80141fc7000, 114}

Probably caused by : ntkrnlmp.exe ( nt!KiRaiseAssertion+280 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
\"bp\", can only be set if the debugger is attached at boot time. Hardware
breakpoints, \"ba\", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a39ff35db9372533, Reserved
Arg2: 0000000000000000, Reserved
Arg3: fffff80141fc7000, Failure type dependent information
Arg4: 0000000000000114, Type of corrupted region, can be
0   : A generic data region
1   : Modification of a function or .pdata
2   : A processor IDT
3   : A processor GDT
4   : Type 1 process list corruption
5   : Type 2 process list corruption
6   : Debug routine modification
7   : Critical MSR modification
8   : Object type
9   : A processor IVT
a   : Modification of a system service function
b   : A generic session data region
c   : Modification of a session function or .pdata
d   : Modification of an import table
e   : Modification of a session import table
f   : Ps Win32 callout modification
10  : Debug switch routine modification
11  : IRP allocator modification
12  : Driver call dispatcher modification
13  : IRP completion dispatcher modification
14  : IRP deallocator modification
15  : A processor control register
16  : Critical floating point control register modification
17  : Local APIC modification
18  : Kernel notification callout modification
19  : Loaded module list modification
1a  : Type 3 process list corruption
1b  : Type 4 process list corruption
1c  : Driver object corruption
1d  : Executive callback object modification
1e  : Modification of module padding
1f  : Modification of a protected process
20  : A generic data region
21  : A page hash mismatch
22  : A session page hash mismatch
23  : Load config directory modification
24  : Inverted function table modification
25  : Session configuration modification
26  : An extended processor control register
27  : Type 1 pool corruption
28  : Type 2 pool corruption
29  : Type 3 pool corruption
2a  : Type 4 pool corruption
2b  : Modification of a function or .pdata
2c  : Image integrity corruption
2d  : Processor misconfiguration
2e  : Type 5 process list corruption
2f  : Process shadow corruption
101 : General pool corruption
102 : Modification of win32k.sys

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


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER:  MSI

SYSTEM_PRODUCT_NAME:  MS-7996

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  1.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1.C0

BIOS_DATE:  04/20/2017

BASEBOARD_MANUFACTURER:  MSI

BASEBOARD_PRODUCT:  B150M PRO-VD (MS-7996)

BASEBOARD_VERSION:  1.0

DUMP_TYPE:  2

BUGCHECK_P1: a39ff35db9372533

BUGCHECK_P2: 0

BUGCHECK_P3: fffff80141fc7000

BUGCHECK_P4: 114

FAULTING_IP:
nt!KiRaiseAssertion+280
fffff801`41fc7000 c3              ret

CPU_COUNT: 4

CPU_MHZ: c78

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: BE\'00000000 (cache) BE\'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x109

PROCESS_NAME:  360AP.exe

CURRENT_IRQL:  e

ANALYSIS_SESSION_HOST:  DESKTOP-21OKSV6

ANALYSIS_SESSION_TIME:  05-18-2018 08:33:19.0315

ANALYSIS_VERSION: 10.0.17134.12 amd64fre

STACK_TEXT:  
ffffe200`b5c70388 fffff801`41e2eb5d : 00000000`0000001e ffffffff`c000001d fffff801`41fc7000 ffffb405`1eb4d640 : nt!KeBugCheckEx
ffffe200`b5c70390 fffff801`41fc8902 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x58d
ffffe200`b5c70a40 fffff801`41fc2b52 : 00000000`00000246 fffff801`41e8005e 00000000`00000001 ffffe200`b5c54180 : nt!KiExceptionDispatch+0xc2
ffffe200`b5c70c20 fffff801`41fc7000 : ffffb405`276e7784 ffffe200`b5c70ea0 fffff801`41fbd310 00000000`0012020e : nt!KiInvalidOpcodeFault+0x392
ffffe200`b5c70db8 ffffb405`276e7784 : ffffe200`b5c70ea0 fffff801`41fbd310 00000000`0012020e 00000000`00dcc000 : nt!KiRaiseAssertion+0x280
ffffe200`b5c70dc0 ffffe200`b5c70ea0 : fffff801`41fbd310 00000000`0012020e 00000000`00dcc000 00000000`00b9fda0 : 0xffffb405`276e7784
ffffe200`b5c70dc8 fffff801`41fbd310 : 00000000`0012020e 00000000`00dcc000 00000000`00b9fda0 ffffb405`27700722 : 0xffffe200`b5c70ea0
ffffe200`b5c70dd0 fffff801`41fbd005 : 8a000002`67ccc021 8a000000`0386b863 8a000000`0586c863 8a000000`0386d863 : nt!KiIpiInterruptSubDispatch+0x80
ffffc6f1`005ae328 00000000`00000001 : ffffb405`200c49b8 ffffb405`200c49b8 00000002`00010401 ffffb405`23b98240 : nt!KiIpiInterrupt+0x385
ffffb405`23b983b0 ffffb405`200c49b8 : ffffb405`200c49b8 00000002`00010401 ffffb405`23b98240 ffffb405`200c49b0 : 0x1
ffffb405`23b983b8 ffffb405`200c49b8 : 00000002`00010401 ffffb405`23b98240 ffffb405`200c49b0 00000000`00000000 : 0xffffb405`200c49b8
ffffb405`23b983c0 00000002`00010401 : ffffb405`23b98240 ffffb405`200c49b0 00000000`00000000 ffffb405`24593088 : 0xffffb405`200c49b8
ffffb405`23b983c8 ffffb405`23b98240 : ffffb405`200c49b0 00000000`00000000 ffffb405`24593088 ffffb405`24593088 : 0x00000002`00010401
ffffb405`23b983d0 ffffb405`200c49b0 : 00000000`00000000 ffffb405`24593088 ffffb405`24593088 008ecec9`00020401 : 0xffffb405`23b98240
ffffb405`23b983d8 00000000`00000000 : ffffb405`24593088 ffffb405`24593088 008ecec9`00020401 ffffb405`23b98240 : 0xffffb405`200c49b0


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80141fc7000-fffff80141fc7007  8 bytes - nt!KiRaiseAssertion+280
[ ff ff ff 48 83 c4 08 e8:c3 c3 c3 c3 c3 c3 c3 c3 ]
8 errors : !nt (fffff80141fc7000-fffff80141fc7007)

THREAD_SHA1_HASH_MOD_FUNC:  d4e506d8afc3e72d3843793dcd46ba11f9d9c833

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  8f37bc3a7586a2173bb58651d49483f2d1cd8199

THREAD_SHA1_HASH_MOD:  30a3e915496deaace47137d5b90c3ecc03746bf6

FOLLOWUP_IP:
nt!KiRaiseAssertion+280
fffff801`41fc7000 c3              ret

FAULT_INSTR_CODE:  c3c3c3c3

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KiRaiseAssertion+280

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5ae3f148

IMAGE_VERSION:  10.0.17134.48

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  280

FAILURE_BUCKET_ID:  0x109_114_nt!KiRaiseAssertion

BUCKET_ID:  0x109_114_nt!KiRaiseAssertion

PRIMARY_PROBLEM_CLASS:  0x109_114_nt!KiRaiseAssertion

TARGET_TIME:  2018-05-18T00:20:07.000Z

OSBUILD:  17134

OSSERVICEPACK:  48

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:  2018-04-27 20:58:00

BUILDDATESTAMP_STR:  180410-1804

BUILDLAB_STR:  rs4_release

BUILDOSVER_STR:  10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME:  1a3c

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x109_114_nt!kiraiseassertion

FAILURE_ID_HASH:  {52353013-ac98-6d31-df2e-307e16179689}

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

楼主您好，请您下载驱动精灵软件，找到您的网卡驱动，现将驱动备份，然后升级。
然后右键“我的电脑”—属性—高级系统设置—高级—设置—将写入调试信息改成核心内存转储。然后手动安装驱动。试一下看看问题是否能解决。