Getting BSOD While Gaming and Chrome No idea Caused By...

xiaotk1

Prominent
Dec 18, 2017
17
0
510
Getting BSOD on Gaming and Chrome watching videos any solution fix it or possible hardware problem?Just New Build PC within 1 month .
OS-Window 10 Pro
CPU-AMD RYZEN 5 1400 Quad-Core Processor
Motherboard-MSI B350M PRO-VD PLUS
RAM-16GB G.Skill Aegis DDR4-2400 one stick*
Graphic-GTX 1060 Gigabyte Mini ITX OC 3G
PSU-Gigabyte PB 500W
SSD-GALAX TA1D0120A 120GB
HDD-WD Blue 1TB Desktop Hard Disk Drive - 7200 RPM

MEMTEST86 been running for many passed
tried chkdsk /r
system restore
I changed SSD,Graphic,RAM from store i bought once between one month 1 on 1 trade still having same issue of bsod.When i changed SSD the shop seller told me ssd possible corrupted,and trade me a new one and i using it first day nth happend ,when third day getting BSOD 5 times .

-----------------------------------------------------------------------------------------------------------------------------------
This is some Analysis File and Whocrashed report

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


Loading Dump File [C:\Users\Jerry\Desktop\121817-8781-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Temp*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Temp*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff801`1b684000 PsLoadedModuleList = 0xfffff801`1b9e5ff0
Debug session time: Mon Dec 18 19:54:59.420 2017 (UTC + 8:00)
System Uptime: 0 days 0:01:44.118
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8011b6f6221, ffff81850ffd1cf0, 0}

Probably caused by : memory_corruption ( nt!MiGetProtoPteAddress+b1 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8011b6f6221, Address of the instruction which caused the bugcheck
Arg3: ffff81850ffd1cf0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.125 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd

SYSTEM_PRODUCT_NAME: MS-7B38

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 2.20

BIOS_DATE: 09/20/2017

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd

BASEBOARD_PRODUCT: B350M PRO-VD PLUS (MS-7B38)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8011b6f6221

BUGCHECK_P3: ffff81850ffd1cf0

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP:
nt!MiGetProtoPteAddress+b1
fffff801`1b6f6221 49837f4000 cmp qword ptr [r15+40h],0

CONTEXT: ffff81850ffd1cf0 -- (.cxr 0xffff81850ffd1cf0)
rax=0000000000004000 rbx=ffffcb01fd601380 rcx=00000000000000ff
rdx=0000000000000005 rsi=ffffcb01fc907a90 rdi=f800000000000005
rip=fffff8011b6f6221 rsp=ffff81850ffd26e0 rbp=0000000000000009
r8=0000000000000009 r9=ffff81850ffd2828 r10=00000007ff7e4de0
r11=00000007ff7e4de5 r12=0000000000002000 r13=0000000000000000
r14=ffff81850ffd2828 r15=3fffcb01fc907a10
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!MiGetProtoPteAddress+0xb1:
fffff801`1b6f6221 49837f4000 cmp qword ptr [r15+40h],0 ds:002b:3fffcb01`fc907a50=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: c80

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: sdiagnhost.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-VVP4MR1

ANALYSIS_SESSION_TIME: 12-18-2017 22:04:50.0667

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

LAST_CONTROL_TRANSFER: from fffff8011b6f69ec to fffff8011b6f6221

STACK_TEXT:
ffff8185`0ffd26e0 fffff801`1b6f69ec : 00007ff7`e4de5000 00000000`00000000 ffff9f3f`fbf276f8 00000000`00002000 : nt!MiGetProtoPteAddress+0xb1
ffff8185`0ffd2760 fffff801`1b6f66ee : 00007ff7`e4de5000 ffff9f3f`fbf276f8 80000005`ffff0000 00000000`00000001 : nt!MiQueryAddressState+0x14c
ffff8185`0ffd27e0 fffff801`1bb60cf4 : ffff8185`0ffd2948 00000000`00000001 00000000`00000000 ffff8185`00000001 : nt!MiQueryAddressSpan+0x16e
ffff8185`0ffd28a0 fffff801`1bb6057d : ffffa32a`697fd4b0 00000225`a3420000 00000045`bfeff070 00000000`10000000 : nt!MmQueryVirtualMemory+0x764
ffff8185`0ffd2a40 fffff801`1b7f3553 : ffffcb01`f82a2ac0 00000225`a3430000 ffffa32a`77566d4d ffff8185`0ffd2a00 : nt!NtQueryVirtualMemory+0x25
ffff8185`0ffd2a90 00007ffa`390502a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000045`bfefedf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`390502a4


THREAD_SHA1_HASH_MOD_FUNC: a22d8e68cf5884e53d4034657dcbf2734838ad57

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 002a05641ae6720856b76f5618ce1c260ff84afd

THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_IP:
nt!MiGetProtoPteAddress+b1
fffff801`1b6f6221 49837f4000 cmp qword ptr [r15+40h],0

FAULT_INSTR_CODE: 407f8349

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiGetProtoPteAddress+b1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5a29b8d4

IMAGE_VERSION: 10.0.16299.125

STACK_COMMAND: .cxr 0xffff81850ffd1cf0 ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: b1

FAILURE_BUCKET_ID: 0x3B_nt!MiGetProtoPteAddress

BUCKET_ID: 0x3B_nt!MiGetProtoPteAddress

PRIMARY_PROBLEM_CLASS: 0x3B_nt!MiGetProtoPteAddress

TARGET_TIME: 2017-12-18T11:54:59.000Z

OSBUILD: 16299

OSSERVICEPACK: 125

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: 2017-12-08 05:55:32

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.125

ANALYSIS_SESSION_ELAPSED_TIME: f52

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_nt!migetprotopteaddress

FAILURE_ID_HASH: {f849bf23-b342-adf9-1683-8c398b58058b}

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

-----------------------------------------------------------------------------------------------------------------------------------

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


Loading Dump File [C:\Users\Jerry\Desktop\121817-5781-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Temp*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Temp*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff801`e6a12000 PsLoadedModuleList = 0xfffff801`e6d73ff0
Debug session time: Mon Dec 18 19:28:30.369 2017 (UTC + 8:00)
System Uptime: 0 days 3:24:28.068
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41201, fffffd00426ba0b0, 8100000131101867, ffff800c49fb96f0}

Probably caused by : memory_corruption ( nt!MiGetPageProtection+126e1e )

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffffd00426ba0b0
Arg3: 8100000131101867
Arg4: ffff800c49fb96f0

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.125 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd

SYSTEM_PRODUCT_NAME: MS-7B38

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 2.20

BIOS_DATE: 09/20/2017

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd

BASEBOARD_PRODUCT: B350M PRO-VD PLUS (MS-7B38)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

BUGCHECK_P1: 41201

BUGCHECK_P2: fffffd00426ba0b0

BUGCHECK_P3: 8100000131101867

BUGCHECK_P4: ffff800c49fb96f0

BUGCHECK_STR: 0x1a_41201

CPU_COUNT: 8

CPU_MHZ: c80

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: chrome.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-VVP4MR1

ANALYSIS_SESSION_TIME: 12-18-2017 22:22:29.0817

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

LAST_CONTROL_TRANSFER: from fffff801e6bac82e to fffff801e6b760e0

STACK_TEXT:
ffff9205`39a84708 fffff801`e6bac82e : 00000000`0000001a 00000000`00041201 fffffd00`426ba0b0 81000001`31101867 : nt!KeBugCheckEx
ffff9205`39a84710 fffff801`e6a84b5e : 00000000`00001000 ffff800c`49fb96f0 81000001`31101867 0a000001`b00c3025 : nt!MiGetPageProtection+0x126e1e
ffff9205`39a84760 fffff801`e6a846ee : 00000084`d7416000 fffffd00`426ba3f8 ffff37cc`16d5cc00 00000000`00000004 : nt!MiQueryAddressState+0x2be
ffff9205`39a847e0 fffff801`e6eeecf4 : ffff9205`39a84948 00000000`00000004 00000000`00000001 00000000`00000004 : nt!MiQueryAddressSpan+0x16e
ffff9205`39a848a0 fffff801`e6eee57d : 0000020f`b2d40b30 fffff801`e6ef8f4f ffff800c`00001000 0000004b`00000004 : nt!MmQueryVirtualMemory+0x764
ffff9205`39a84a40 fffff801`e6b81553 : fffffd7e`bf4041f0 fffffd7e`bf5fa020 ffff37cc`16d5c325 00000000`000002f0 : nt!NtQueryVirtualMemory+0x25
ffff9205`39a84a90 00007ff8`b72d02a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000004b`691fedb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`b72d02a4


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: daeab5d68ba3ecb3234b5b8938d47aee75235996

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 0d28b06c5c96d6e1a8df441c9be36c7aca14997e

THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6

FOLLOWUP_IP:
nt!MiGetPageProtection+126e1e
fffff801`e6bac82e cc int 3

FAULT_INSTR_CODE: b08d4dcc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiGetPageProtection+126e1e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5a29b8d4

IMAGE_VERSION: 10.0.16299.125

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 126e1e

FAILURE_BUCKET_ID: 0x1a_41201_nt!MiGetPageProtection

BUCKET_ID: 0x1a_41201_nt!MiGetPageProtection

PRIMARY_PROBLEM_CLASS: 0x1a_41201_nt!MiGetPageProtection

TARGET_TIME: 2017-12-18T11:28:30.000Z

OSBUILD: 16299

OSSERVICEPACK: 125

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: 2017-12-08 05:55:32

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.125

ANALYSIS_SESSION_ELAPSED_TIME: 5a8

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1a_41201_nt!migetpageprotection

FAILURE_ID_HASH: {c1fe3b27-3ba8-d99e-656f-85f3d58dc669}

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

------------------------------------------------------------------------------------------------------------------------------------
WhoCrash Report

On Mon 12/18/2017 7:54:59 PM your computer crashed
crash dump file: C:\Windows\Minidump\121817-8781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8011B6F6221, 0xFFFF81850FFD1CF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 12/18/2017 7:54:59 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8011B6F6221, 0xFFFF81850FFD1CF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 12/18/2017 7:28:30 PM your computer crashed
crash dump file: C:\Windows\Minidump\121817-5781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x1A (0x41201, 0xFFFFFD00426BA0B0, 0x8100000131101867, 0xFFFF800C49FB96F0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 12/18/2017 4:03:22 PM your computer crashed
crash dump file: C:\Windows\Minidump\121817-5812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x1A (0x61941, 0x6DEDA484, 0xD, 0xFFFF918C284A7B00)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

------------------------------------------------------------------------------------------------------------------------------------

 
all of the bugchecks are in your virtual memory subsystem.
update your sata drivers/ chipset drivers for your motherboard, check you data cables for proper connection to the SATA drive. I would also go into control panel and turn off virtual memory, reboot, delete the hidden c:\pagefile.sys then turn virtual memory back on.

you might run crystaldiskinfo.exe to check the status of your drive and to find out the firmware version then check to see if there is a firmware update you might need to apply.

you might consider putting your drive on a different sata controller and port and also make sure your power cable to the drive is not loose.

make sure there is plenty of free space on your SSD, then boot into BIOS and leave the drive powered and not in use for a few hours. after 5 minutes, the drive will start it firmware cleanup routines (garbage collections) Sometimes these get behind or get blocked and the drive does not respond.
 

xiaotk1

Prominent
Dec 18, 2017
17
0
510
when i update the drivers i get this bsod

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


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


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Temp*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Temp*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff800`8d683000 PsLoadedModuleList = 0xfffff800`8d9e4ff0
Debug session time: Tue Dec 19 13:20:52.191 2017 (UTC + 8:00)
System Uptime: 0 days 0:00:35.889
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 139, {0, 0, 0, 1ffff80e4b76df00}

Probably caused by : ntkrnlmp.exe ( nt!guard_icall_bugcheck+1b )

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

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

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000000, A stack-based buffer has been overrun.
Arg2: 0000000000000000, Address of the trap frame for the exception that caused the bugcheck
Arg3: 0000000000000000, Address of the exception record for the exception that caused the bugcheck
Arg4: 1ffff80e4b76df00, Reserved

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.125 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd

SYSTEM_PRODUCT_NAME: MS-7B38

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 2.20

BIOS_DATE: 09/20/2017

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd

BASEBOARD_PRODUCT: B350M PRO-VD PLUS (MS-7B38)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 1ffff80e4b76df00

TRAP_FRAME: 0000000000000000 -- (.trap 0x0)

EXCEPTION_RECORD: 0000000000000000 -- (.exr 0x0)
Cannot read Exception record @ 0000000000000000

CPU_COUNT: 8

CPU_MHZ: c80

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x139

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-VVP4MR1

ANALYSIS_SESSION_TIME: 12-19-2017 13:29:06.0346

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

LAST_CONTROL_TRANSFER: from fffff8008d7ed5db to fffff8008d7e70e0

STACK_TEXT:
ffffb30d`96245938 fffff800`8d7ed5db : 00000000`00000139 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffb30d`96245940 fffff800`8d6cfb63 : ffffb781`c809f180 00000000`00000000 ffffb30d`96245b18 00000000`00000000 : nt!guard_icall_bugcheck+0x1b
ffffb30d`96245970 fffff800`8d6d0bfd : 00000000`0000001e 00000000`00000000 00000000`002faf06 ffffb781`c809f180 : nt!KiProcessExpiredTimerList+0x153
ffffb30d`96245a60 fffff800`8d7ea23a : ffffffff`00000000 ffffb781`c809f180 00000000`00000000 ffffb781`c80abcc0 : nt!KiRetireDpcList+0x43d
ffffb30d`96245c60 00000000`00000000 : ffffb30d`96246000 ffffb30d`96240000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 82ccc3cee3206f68bc85a2292d997ccb422b45e2

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e0c3fa7fc1b60688a4d24b30670fa9d8f5024bd8

THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84

FOLLOWUP_IP:
nt!guard_icall_bugcheck+1b
fffff800`8d7ed5db 90 nop

FAULT_INSTR_CODE: ccccc390

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!guard_icall_bugcheck+1b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5a29b8d4

IMAGE_VERSION: 10.0.16299.125

BUCKET_ID_FUNC_OFFSET: 1b

FAILURE_BUCKET_ID: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_bugcheck

BUCKET_ID: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_bugcheck

PRIMARY_PROBLEM_CLASS: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_bugcheck

TARGET_TIME: 2017-12-19T05:20:52.000Z

OSBUILD: 16299

OSSERVICEPACK: 125

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: 2017-12-08 05:55:32

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.125

ANALYSIS_SESSION_ELAPSED_TIME: 569

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x139_0_legacy_gs_violation_nt!guard_icall_bugcheck

FAILURE_ID_HASH: {9bee41a7-2ef9-07ca-7e59-7d5a0c6e2d05}

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

On Tue 12/19/2017 1:20:52 PM your computer crashed
crash dump file: C:\Windows\Minidump\121917-6328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x139 (0x0, 0x0, 0x0, 0x1FFFF80E4B76DF00)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 12/19/2017 1:20:52 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x0, 0x0, 0x0, 0x1FFFF80E4B76DF00)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.