BSOD with weird error codes.

[JakeIsTheGuy678]

I keep getting random BSODs, and I don't know how to fix them!

Below is an analysis of my dmp file - please advise!



KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80450a06dc3, The address that the exception occurred at
Arg3: ffffffffffffffff, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3843

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-HL1J1NP

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 3896

Key : Analysis.Memory.CommitPeak.Mb
Value: 76

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80450a06dc3

BUGCHECK_P3: ffffffffffffffff

BUGCHECK_P4: 0

WRITE_ADDRESS: fffff804514fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8045140f330: Unable to get Flags value from nt!KdVersionBlock
fffff8045140f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000000

EXCEPTION_PARAMETER1: ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

BAD_STACK_POINTER: ffffb201bfd99158

STACK_TEXT:
ffffb201`bfd99158 fffff804`50cf4cfe : 00000000`0000001e ffffffff`c0000005 fffff804`50a06dc3 ffffffff`ffffffff : nt!KeBugCheckEx
ffffb201`bfd99160 fffff804`50bfe942 : fffff804`50cf4cdc 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
ffffb201`bfd991a0 fffff804`50b2bf97 : ffffb201`bfd99710 00000000`00000000 ffff9682`1028bc60 fffff804`50bf95ee : nt!RtlpExecuteHandlerForException+0x12
ffffb201`bfd991d0 fffff804`50b2ab86 : ffff9682`1028b798 ffffb201`bfd99e20 ffff9682`1028b798 fffff7b6`00001000 : nt!RtlDispatchException+0x297
ffffb201`bfd998f0 fffff804`50bf6912 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
ffffb201`bfd99fb0 fffff804`50bf68e0 : fffff804`50c07ba5 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffff9682`1028b658 fffff804`50c07ba5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`0005b36f : nt!KiExceptionDispatchOnExceptionStackContinue
ffff9682`1028b660 fffff804`50c035b1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x125
ffff9682`1028b840 fffff804`50a06dc3 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiStackFault+0x331
ffff9682`1028b9d0 fffff804`50bf95ee : ffffffff`00000000 ffffb201`bfd40180 ffffb201`bfd4b340 ffffc605`bb2c7080 : nt!KiRetireDpcList+0x4b3
ffff9682`1028bc60 00000000`00000000 : ffff9682`1028c000 ffff9682`10286000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff80450a06dc5 - nt!KiRetireDpcList+4b5
[ 24:2c ]
1 error : !nt (fffff80450a06dc5)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

MEMORY_CORRUPTOR: ONE_BIT

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: memory_corruption
---------

Continue reading...