Constants BSOD's on Windows 10

Hi Carlo

My name is Andre Da Costa; an Independent Consultant, Windows Insider MVP and Windows & Devices for IT MVP. I'm here to help you with your problem.

What is the exact make and model?

Open Start, type: system information
Hit Enter
Click System summary
Look in the right pane

Copy the system sku info into reply here.

See example: https://imgur.com/qzektpA

I noticed you recently updated to the latest cumulative update, try removing that update then monitor the system.

If an update is not installing or making your system unstable, I would remove the update and block it from installation.

Due to the millions of configurations out there, some might not be fully compatible with a particular cumulative update.

Press Windows key + R
Type: appwiz.cpl
Hit Enter
Click View installed updates
Select the recent update
Right click it then click uninstall.

Restart into Normal mode then check if stability/functionality is restored. If it is, proceed with the next steps.

What I recommend you do is block the update for the time being and report it in the Feedback Hub so the Windows engineers are aware of the issue.

https://windows10.help/blogs/entry/54-how-to-su...

The update will try to install again, so use the following to block it:
Is there an option or work around to block updates or hardware drivers that might cause problems?
Yes, Microsoft has released a KB update (KB3073930) that will let users block or hide Windows or driver updates.

You can download it at the following link:
https://support.microsoft.com/en-us/kb/3073930

After downloading, launch it, click Next, wait while it detects pending Windows Updates.

Click the Hide Updates menu.

Scroll through the list then select then select the update. Check the box next to the update then click Next to confirm changes.

Hi Andre, as per your request:

OS Name Microsoft Windows 10 Pro

Version 10.0.18362 Build 18362

Other OS Description Not Available

OS Manufacturer Microsoft Corporation

System Name CAOS-I7-8700K

System Manufacturer System manufacturer

System Model System Product Name

System Type x64-based PC

System SKU ASUS_MB_CNL

Processor Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz, 3696 Mhz, 6 Core(s), 12 Logical Processor(s)

BIOS Version/Date American Megatrends Inc. 1105, 6/6/2019

SMBIOS Version 3.2

Embedded Controller Version 255.255

BIOS Mode UEFI

BaseBoard Manufacturer ASUSTeK COMPUTER INC.

BaseBoard Product ROG MAXIMUS XI HERO (WI-FI)

BaseBoard Version Rev 1.xx

Platform Role Desktop

Secure Boot State Off

PCR7 Configuration Binding Not Possible

Windows Directory C:\Windows

System Directory C:\Windows\system32

Boot Device \Device\HarddiskVolume7

Locale United States

Hardware Abstraction Layer Version = "10.0.18362.145"

User Name CAOS-I7-8700K\Carlos Ospina

Time Zone Eastern Daylight Time

Installed Physical Memory (RAM) 32.0 GB

Total Physical Memory 31.9 GB

Available Physical Memory 23.9 GB

Total Virtual Memory 79.9 GB

Available Virtual Memory 68.8 GB

Page File Space 48.0 GB

Page File C:\pagefile.sys

Kernel DMA Protection Off

Virtualization-based security Not enabled

Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable

Hyper-V - VM Monitor Mode Extensions Yes

Hyper-V - Second Level Address Translation Extensions Yes

Hyper-V - Virtualization Enabled in Firmware No

Hyper-V - Data Execution Protection Yes

Hi Carlo,
I am Sumit, an Independent Advisor and a 2-Year Windows Insider MVP here to help.

We need log files(called dump files) that tell us what lead to crash.
Please share them with us for a better analysis of the problem. Instructions can be found here:

https://answers.microsoft.com/en-us/windows/for...
Please let us know if you need any assistance about posting dump files.

I am not seeing any new updates for your hardware. This looks like a compatibility issue.

I recommend you downgrade to Windows 10 1809 for the time being then try upgrading when Windows 10 1903 matures.

Step 1: Go to another working computer with Internet access, download Windows 10 1809 from the following link:
https://tb.rg-adguard.net/index.php?sid=74a7cf5...

Choose the following:

- Windows Final
- Windows 10, version 1809
- Windows 10 Pro + Home
- English
- x64 (64 bit) x32 (32 bit)

Step 2: create a bootable copy
https://answers.microsoft.com/en-us/windows/wik...

Step 3: perform a custom install
http://answers.microsoft.com/en-us/insider/wiki...

Step 4: how to recover your files from Windows.old:
https://answers.microsoft.com/en-us/windows/for...


Windows Update might attempt to upgrade to Windows 10 1903 again. See instructions how to block it:
https://www.groovypost.com/howto/block-windows-...

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

Hi Sumit, this is the most recent memory dump after a kernel security related BSOD:

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*

Executable search path is: 

Windows 10 Kernel Version 18362 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 18362.1.amd64fre.19h1_release.190318-1202

Machine Name:

Kernel base = 0xfffff802`08000000 PsLoadedModuleList = 0xfffff802`084432f0

Debug session time: Sat Jul 13 10:54:47.308 2019 (UTC - 4:00)

System Uptime: 0 days 18:25:59.375

Loading Kernel Symbols

...............................................................

................................................................

................................................................

.....................................................

Loading User Symbols

Loading unloaded module list

...................................

For analysis of this file, run !analyze -v

0: 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: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).

Arg2: ffffb50cee16a5f0, Address of the trap frame for the exception that caused the bugcheck

Arg3: ffffb50cee16a548, Address of the exception record for the exception that caused the bugcheck

Arg4: 0000000000000000, Reserved

Debugging Details:

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

KEY_VALUES_STRING: 1

PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  ASUS_MB_CNL

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1105

BIOS_DATE:  06/06/2019

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  ROG MAXIMUS XI HERO (WI-FI)

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  1

BUGCHECK_P1: 3

BUGCHECK_P2: ffffb50cee16a5f0

BUGCHECK_P3: ffffb50cee16a548

BUGCHECK_P4: 0

TRAP_FRAME:  ffffb50cee16a5f0 -- (.trap 0xffffb50cee16a5f0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=ffffbb09c63c0d98 rbx=0000000000000000 rcx=0000000000000003

rdx=ffffb50cee16a950 rsi=0000000000000000 rdi=0000000000000000

rip=fffff802080b2bf4 rsp=ffffb50cee16a780 rbp=ffffb50cee16a880

 r8=fffff80208462ec0  r9=fffff80208467040 r10=ffffbb09c117d580

r11=0000000000000001 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei ng nz na po cy

nt!MiProcessWorkingSets+0x524:

fffff802`080b2bf4 cd29            int     29h

Resetting default scope

EXCEPTION_RECORD:  ffffb50cee16a548 -- (.exr 0xffffb50cee16a548)

ExceptionAddress: fffff802080b2bf4 (nt!MiProcessWorkingSets+0x0000000000000524)

   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)

  ExceptionFlags: 00000001

NumberParameters: 1

   Parameter[0]: 0000000000000003

Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

CPU_COUNT: c

CPU_MHZ: e70

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

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

BUGCHECK_STR:  0x139

PROCESS_NAME:  System

CURRENT_IRQL:  2

DEFAULT_BUCKET_ID:  FAIL_FAST_CORRUPT_LIST_ENTRY

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000003

ANALYSIS_SESSION_HOST:  CAOS-I7-8700K

ANALYSIS_SESSION_TIME:  07-13-2019 10:59:07.0470

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff802081ce6e9 to fffff802081bc900

STACK_TEXT:  

ffffb50c`ee16a2c8 fffff802`081ce6e9 : 00000000`00000139 00000000`00000003 ffffb50c`ee16a5f0 ffffb50c`ee16a548 : nt!KeBugCheckEx

ffffb50c`ee16a2d0 fffff802`081ceb10 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69

ffffb50c`ee16a410 fffff802`081ccea5 : fffff802`0679f180 fffff802`080350cc 00000048`0412017e 00000000`00000004 : nt!KiFastFailDispatch+0xd0

ffffb50c`ee16a5f0 fffff802`080b2bf4 : 00000000`00000000 ffffb50c`ee16a950 00000000`00000000 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x325

ffffb50c`ee16a780 fffff802`080b0ce0 : fffff802`00000000 00000000`00000000 fffff802`084651c0 ffffbb09`ae03f490 : nt!MiProcessWorkingSets+0x524

ffffb50c`ee16a930 fffff802`082c72a6 : 00000000`00000001 00000000`00000007 00000000`ffffffff 00000000`00000001 : nt!MiWorkingSetManager+0xc8

ffffb50c`ee16a9f0 fffff802`08187fb5 : 00000000`00000007 00000000`ffffffff fffff802`084651c0 00000000`00000124 : nt!MmWorkingSetManager+0x12

ffffb50c`ee16aa20 fffff802`0812f725 : ffffbb09`ae093380 00000000`00000080 fffff802`08187e60 00000000`00000000 : nt!KeBalanceSetManager+0x155

ffffb50c`ee16ab10 fffff802`081c3e6a : ffffdf00`4aa00180 ffffbb09`ae093380 fffff802`0812f6d0 00000000`00000000 : nt!PspSystemThreadStartup+0x55

ffffb50c`ee16ab60 00000000`00000000 : ffffb50c`ee16b000 ffffb50c`ee164000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a

THREAD_SHA1_HASH_MOD_FUNC:  7fb948990ad4bd0260f3ed84eb182e71bbf11503

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  af0e1046bca36f3ad0d23d56de3bd833905b03a0

THREAD_SHA1_HASH_MOD:  bc100a5647b828107ac4e18055e00abcbe1ec406

FOLLOWUP_IP: 

nt!KiFastFailDispatch+d0

fffff802`081ceb10 c644242000      mov     byte ptr [rsp+20h],0

FAULT_INSTR_CODE:  202444c6

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiFastFailDispatch+d0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  3ed0f42

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  d0

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_nt!KiFastFailDispatch

BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_nt!KiFastFailDispatch

PRIMARY_PROBLEM_CLASS:  0x139_3_CORRUPT_LIST_ENTRY_nt!KiFastFailDispatch

TARGET_TIME:  2019-07-13T14:54:47.000Z

OSBUILD:  18362

OSSERVICEPACK:  0

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:  1972-02-02 03:33:06

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  1c30

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x139_3_corrupt_list_entry_nt!kifastfaildispatch

FAILURE_ID_HASH:  {3aede96a-54dd-40d6-d4cb-2a161a843851}

Followup:     MachineOwner

---------

Yes, I wanted to be sure nothing is wrong with the hardware prior to reformat and reinstall everything.

Hi Carlo,

A crash dump file helps us understand an issue better using the Software tools we have. If you have a privacy concern on sharing the dump file, do not worry as these do not contain any private information.

Here, the latest memory.dmp link

https://1drv.ms/u/s!AmV67E-tfAYHgtNa-xHgQjES6-Tm0Q

Hi Carlo,

Sorry to bother you, but it is a bit difficult for us to download a 1.6 GB file. Can you please ZIP it into a folder and then upload to significantly reduce its size?