Windows 11 system blue screen

Question

Windows 11 system blue screen

岩王 0


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


Loading Dump File [C:\Users\17927\Desktop\MEMORY\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Primary dump contents written successfully


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Machine Name:
Kernel base = 0xfffff803`76e00000 PsLoadedModuleList = 0xfffff803`77a13470
Debug session time: Thu May 18 09:15:09.558 2023 (UTC + 8:00)
System Uptime: 2 days 0:48:44.310
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........
Loading User Symbols

Loading unloaded module list
..................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`7722b8f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff918a`a8f37130=0000000000000050
12: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffb50ad5baa0d4, memory referenced.
Arg2: 0000000000000002, X64: bit 0 set if the fault was due to a not-present PTE.
	bit 1 is set if the fault was due to a write, clear if a read.
	bit 3 is set if the processor decided the fault was due to a corrupted PTE.
	bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
	- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
	bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff80377090733, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Write

    Key  : Analysis.CPU.mSec
    Value: 905

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 1642

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x50

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x50

    Key  : Bugcheck.Code.Register
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 1800

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 100

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Timestamp
    Value: 2022-05-06T12:50:00Z

    Key  : WER.OS.Version
    Value: 10.0.22621.1


FILE_IN_CAB:  MEMORY.DMP

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1800

BUGCHECK_CODE:  50

BUGCHECK_P1: ffffb50ad5baa0d4

BUGCHECK_P2: 2

BUGCHECK_P3: fffff80377090733

BUGCHECK_P4: 2

READ_ADDRESS:  ffffb50ad5baa0d4 

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

TRAP_FRAME:  ffff918aa8f37350 -- (.trap 0xffff918aa8f37350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffffb50ad5baa010
rdx=ffff918aa8f37610 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80377090733 rsp=ffff918aa8f374e0 rbp=ffff918aa8f37530
 r8=0000000000000000  r9=7ffffffffffffffc r10=ffffbd0aa930cd20
r11=ffff918aa8f373d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!CcWriteBehindPreProcess+0x207:
fffff803`77090733 f00fc181c4000000 lock xadd dword ptr [rcx+0C4h],eax ds:ffffb50a`d5baa0d4=????????
Resetting default scope

STACK_TEXT:  
ffff918a`a8f37128 fffff803`772a7541     : 00000000`00000050 ffffb50a`d5baa0d4 00000000`00000002 ffff918a`a8f37350 : nt!KeBugCheckEx
ffff918a`a8f37130 fffff803`770eb42c     : ffffbd0a`e9d4b8d0 00000000`00000002 ffff918a`a8f372e9 00000000`00000000 : nt!MiSystemFault+0x1bf031
ffff918a`a8f37230 fffff803`7723c529     : 00000000`00000000 fffff803`770c9ed0 ffffbd0b`19fdae30 00000000`00000000 : nt!MmAccessFault+0x29c
ffff918a`a8f37350 fffff803`77090733     : ffffbd0b`19fdad10 00000000`000000f4 ffffbd0b`19fdad10 ffffbd0b`5ea28a40 : nt!KiPageFault+0x369
ffff918a`a8f374e0 fffff803`770904a4     : 00000000`00000000 ffff918a`a8f37838 ffffbd0a`a930cd20 00000000`00000000 : nt!CcWriteBehindPreProcess+0x207
ffff918a`a8f37570 fffff803`770902d7     : ffffbd0b`19fdad10 00000000`00000000 ffffbd0b`5ea28a40 00000000`00000000 : nt!CcWriteBehindInternal+0x54
ffff918a`a8f376e0 fffff803`7708bff8     : ffffbd0b`5ea28a40 00000000`00000000 ffffbd0a`d54f75d0 00000000`00000000 : nt!CcWriteBehind+0xb7
ffff918a`a8f377e0 fffff803`770162c5     : ffffbd0a`a92db410 ffffbd0b`5a76d040 ffffbd0a`a92db410 fffff803`77b49ac0 : nt!CcWorkerThread+0x6b8
ffff918a`a8f37940 fffff803`7700dc67     : ffffbd0b`5a76d040 00000000`00000304 ffffbd0b`5a76d040 fffff803`77016170 : nt!ExpWorkerThread+0x155
ffff918a`a8f37b30 fffff803`77230854     : ffffce01`bb817180 ffffbd0b`5a76d040 fffff803`7700dc10 ffe9d7de`ffe9d7de : nt!PspSystemThreadStartup+0x57
ffff918a`a8f37b80 00000000`00000000     : ffff918a`a8f38000 ffff918a`a8f31000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!CcWriteBehindPreProcess+207

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  207

FAILURE_BUCKET_ID:  AV_W_(null)_nt!CcWriteBehindPreProcess

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f2bfb7e4-de06-f579-d364-075571c88d24}

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

1 answer

Your answer

Answer 1

Hi, thanks for coming into the forums. I'm also a user like you and I'll be more than happy to help you to the best of my knowledge.

Hold down the power button for 10 seconds to turn off your device.
Press the power button again to turn on your device.
On the first sign that Windows has started (for example, some devices show the manufacturer’s logo when restarting) hold down the power button for 10 seconds to turn off your device.
Press the power button again to turn on your device.
When Windows starts again, hold down the power button for 10 seconds to turn off your device.
Press the power button again to turn on your device.
This time, allow your device to fully start up.
Select Advanced options.
Now that you're in winRE, on the Choose an option screen, select Troubleshoot > Advanced options > Startup Repair > Restart.

If that didn't work, follow the same steps but choose System Restore or Reset PC.

Reference: https://support.microsoft.com/windows/31ce2444-7de3-818c-d626-e3b5a3024da5

If the reply is helpful, please Upvote and Accept it as an answer.

Share via

Windows 11 system blue screen

1 answer

Your answer