Blue Screen Error

Question

Just got blue screen error since recent a couple of days, please help

thank you in advance!

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: ffff87062963b530, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2936

    Key  : Analysis.Elapsed.mSec
    Value: 8054

    Key  : Analysis.IO.Other.Mb
    Value: 18

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 20

    Key  : Analysis.Init.CPU.mSec
    Value: 546

    Key  : Analysis.Init.Elapsed.mSec
    Value: 27860

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x7a

    Key  : Bugcheck.Code.TargetModel
    Value: 0x7a

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: 0x7a_c000000e_nt!MiWriteComplete

    Key  : Failure.Hash
    Value: {fcc12098-ee04-35bd-5cea-593a2c6ec31d}

BUGCHECK_CODE:  7a

BUGCHECK_P1: 20

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: ffff87062963b530

BUGCHECK_P4: 0

FILE_IN_CAB:  051324-8703-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

ERROR_CODE: (NTSTATUS) 0xc000000e - <Unable to get error code text>

DISK_HARDWARE_ERROR: There was error with disk hardware

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffca85`d613a598 fffff805`24659b46     : 00000000`0000007a 00000000`00000020 ffffffff`c000000e ffff8706`2963b530 : nt!KeBugCheckEx
ffffca85`d613a5a0 fffff805`2455822b     : 00000000`00000000 00000000`c000000e 00000000`00000000 00000000`00100000 : nt!MiWriteComplete+0x18efc6
ffffca85`d613a650 fffff805`244c7bab     : ffff8706`23bcc4c0 fffff805`245581e0 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x4b
ffffca85`d613a680 fffff805`24439297     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff805`00000000 : nt!KiDeliverApc+0x27b
ffffca85`d613a740 fffff805`2443849f     : 00000000`0000001a 00000000`0000000f ffffca85`d613a930 00000000`00000000 : nt!KiSwapThread+0x827
ffffca85`d613a7f0 fffff805`244ca40e     : ffff8706`00000000 fffff805`00000000 00000000`02000100 00000000`00000000 : nt!KiCommitThreadWait+0x14f
ffffca85`d613a890 fffff805`245bf30e     : ffff8706`00000000 fffff805`24e50c40 fffff805`24e50c40 ffffd881`000000ba : nt!KeWaitForMultipleObjects+0x2be
ffffca85`d613a9a0 fffff805`2454ef55     : ffff8706`23bcc4c0 ffff8706`23bcc4c0 00000000`00000080 fffff805`245bf200 : nt!MiModifiedPageWriter+0x10e
ffffca85`d613abd0 fffff805`24606a48     : ffffd881`f9e79180 ffff8706`23bcc4c0 fffff805`2454ef00 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffca85`d613ac20 00000000`00000000     : ffffca85`d613b000 ffffca85`d6134000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME:  nt!MiWriteComplete+18efc6

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.4291

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  18efc6

FAILURE_BUCKET_ID:  0x7a_c000000e_nt!MiWriteComplete

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {fcc12098-ee04-35bd-5cea-593a2c6ec31d}

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

Answer 1

Thanks for the update.

Are there no dump files generated?

Answer 2

good day mate

after i use cmd to launch drivert verification

Windows only gives me blue screen and Windows cant be loaded correctly

so i have to restore my system

should i give driver verification another try？

Answer 3

You're welcome, please keep me updated.

Answer 4

Thanks for your time and your help, I'm going to do the driver verification now and I'll reply as soon as I finish

Thank you again!

Answer 5

Hello, I'm here to help.

The information you have provided indicates a problem with the system kernel, usually caused by a driver, which we need to verify further. Please first create a restore point for your system, then please refer to this article: https://learn.microsoft.com/en-us/windows-hardw... to enable driver verifier. In the third step select "Automatically select all drivers installed on this computer", wait for a couple of new blue screens and then collect 2-3 new dump files and share the new dump files with me.

If the computer has any automatic overclocking features enabled (including XMP, PBO, etc.) or manual overclocking, please restore the defaults first.

Driver verifier puts heavy pressure on the drivers in your system to troubleshoot drivers that are in poor condition or misbehaving. It is normal for your computer to run slowly after driver verifier is turned on. The computer will also crash more frequently and generate dump files during this process.

If your system fails to boot after driver verifier is turned on, please restore via the restore point.

If you have any questions, please feel free to let me know. This is not a live chat channel and I may be in a different time zone than you. As a result, replies may be delayed and I may respond minutes to hours later.