[SOLVED] Constant BSOD and cant run updates

Toggle sidebar Toggle sidebar
Nicksega

Nicksega

Jul 4, 2021
1
0
10
I'm having tons of issues with my system blue screening, failing to update, and failing to be able to do system checks like sfc of dism. I get memory managment BSOD most of the time.

I have two M.2 NVMe SSDs one of which I boot windows with, one SATA SSD and a 2TB hard drive. If you need any other info please let me know!

Code: 
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`4f400000 PsLoadedModuleList = 0xfffff806`5002a230
Debug session time: Thu Jul  1 11:36:49.138 2021 (UTC - 6:00)
System Uptime: 0 days 0:00:21.748
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`4f7f6c20 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffec86`b9a300d0=000000000000001a
8: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
    the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffffbc00dcdaab30
Arg3: 0000080000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3077

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 13753

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

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

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

    Key  : MemoryManagement.PFN
    Value: 80000000

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  1a

BUGCHECK_P1: 41792

BUGCHECK_P2: ffffbc00dcdaab30

BUGCHECK_P3: 80000000000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR:  ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  HxT

STACK_TEXT: 
ffffec86`b9a300c8 fffff806`4f64423a     : 00000000`0000001a 00000000`00041792 ffffbc00`dcdaab30 00000800`00000000 : nt!KeBugCheckEx
ffffec86`b9a300d0 fffff806`4f642a6f     : ffffbd84`2cc1c700 00000000`00000000 ffffbc00`00000002 00000000`00000000 : nt!MiDeleteVa+0x153a
ffffec86`b9a301d0 fffff806`4f612c10     : 00000000`00000001 ffffec86`00000000 ffffbd84`2cc1c550 ffffbd84`2c7a60c0 : nt!MiDeletePagablePteRange+0x48f
ffffec86`b9a304e0 fffff806`4fa00b49     : ffffbd84`2cdb4b60 00000000`00000000 ffffbd84`00000000 ffffbd84`00000000 : nt!MiDeleteVad+0x360
ffffec86`b9a305f0 fffff806`4fa001e0     : ffffbd84`2cdb4b60 ffffbd84`2c942d20 ffffbd84`2c7a60c0 00000000`00000000 : nt!MiUnmapVad+0x49
ffffec86`b9a30620 fffff806`4f9fe4af     : ffffbd84`2cdbeb60 ffffbd84`2cdbeb60 ffffbd84`2cdb4b60 ffffbd84`2cc1c080 : nt!MiCleanVad+0x30
ffffec86`b9a30650 fffff806`4fac9388     : ffffffff`00000001 ffffffff`ffffffff 00000000`00000001 ffffbd84`2cc1c080 : nt!MmCleanProcessAddressSpace+0x137
ffffec86`b9a306d0 fffff806`4fa5b886     : ffffbd84`2cc1c080 ffffab8f`629ca060 ffffec86`b9a30920 00000000`00000000 : nt!PspRundownSingleProcess+0x20c
ffffec86`b9a30760 fffff806`4faa56c8     : 00000000`00000001 00000000`00000001 00000000`00000000 000000a2`738ee000 : nt!PspExitThread+0x5f6
ffffec86`b9a30860 fffff806`4f60f0d7     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x38
ffffec86`b9a308a0 fffff806`4f7fb1c0     : 00000000`00000000 ffffec86`b9a30950 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x487
ffffec86`b9a30950 fffff806`4f80865f     : 00000000`00000000 ffffec86`b9a30b80 ffffbd84`2c7a60c0 00000000`00000000 : nt!KiInitiateUserApc+0x70
ffffec86`b9a30a90 00007ffd`ecaed974     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
000000a2`751ff7f8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`ecaed974


MODULE_NAME: hardware

IMAGE_NAME:  memory_corruption

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
Code: 
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`50600000 PsLoadedModuleList = 0xfffff806`5122a230
Debug session time: Thu Jul  1 11:33:55.442 2021 (UTC - 6:00)
System Uptime: 0 days 0:00:29.052
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`509f6c20 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8c05`5e436bb0=000000000000001a
6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: ffffb6800bc4f390
Arg3: 00000000000001ff
Arg4: 0000000000000200

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4062

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 13895

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

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

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

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  1a

BUGCHECK_P1: 41790

BUGCHECK_P2: ffffb6800bc4f390

BUGCHECK_P3: 1ff

BUGCHECK_P4: 200

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  SearchApp.exe

STACK_TEXT: 
ffff8c05`5e436ba8 fffff806`50a626bf     : 00000000`0000001a 00000000`00041790 ffffb680`0bc4f390 00000000`000001ff : nt!KeBugCheckEx
ffff8c05`5e436bb0 fffff806`509ee328     : 00000000`00000200 ffffb680`0bc4c0c0 ffffb680`0bc4f390 00000000`00000000 : nt!MiDecreaseUsedPtesCount+0x173cfb
ffff8c05`5e436bf0 fffff806`5083b38a     : 00000000`003ec404 80000000`00000000 00000000`00000001 00000000`00000004 : nt!MiReducePteUseCount+0x30
ffff8c05`5e436c20 fffff806`5093898c     : ffff8c05`5e436f90 ffffbd04`728400c0 00000000`00000000 ffff8c05`5e437910 : nt!MiDeletePteList+0x88a
ffff8c05`5e436d00 fffff806`50bf9bed     : ffffbd04`7340f040 ffffbd04`72dce528 ffffbd04`00000000 ffffbd04`00000000 : nt!MiDecommitPages+0x3bc
ffff8c05`5e4378d0 fffff806`50bf9253     : ffff8c05`5e437a50 00000000`00000000 ffff8c05`5e437a50 ffffbd04`72dce500 : nt!MiDecommitRegion+0x7d
ffff8c05`5e437950 fffff806`50bf8b45     : 00000000`00000000 ffff8c05`5e437b80 ffffc467`a3dec9f9 00000000`00000000 : nt!MmFreeVirtualMemory+0x6d3
ffff8c05`5e437aa0 fffff806`50a085b8     : ffffbd04`7340f040 00000000`00000000 ffff8c05`5e437b80 0000001f`c0000034 : nt!NtFreeVirtualMemory+0x95
ffff8c05`5e437b00 00007ffe`eb7cd1e4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000001f`c5efccd8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`eb7cd1e4


SYMBOL_NAME:  nt!MiDecreaseUsedPtesCount+173cfb

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.1052

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  173cfb

FAILURE_BUCKET_ID:  0x1a_41790_nt!MiDecreaseUsedPtesCount

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3a4e374b-adfe-575c-a9c4-4050eb1047a4}

Followup:     MachineOwner
---------
Code: 
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`73a00000 PsLoadedModuleList = 0xfffff803`7462a230
Debug session time: Thu Jul  1 11:32:48.206 2021 (UTC - 6:00)
System Uptime: 0 days 0:13:41.816
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`73df6c20 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffce01`f46987e0=00000000000000be
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the BugCheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffc980645b90e8, Virtual address for the attempted write.
Arg2: 8a00000004400121, PTE contents.
Arg3: ffffce01f46989d0, (reserved)
Arg4: 000000000000000a, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4203

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 10210

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

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

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

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  be

BUGCHECK_P1: ffffc980645b90e8

BUGCHECK_P2: 8a00000004400121

BUGCHECK_P3: ffffce01f46989d0

BUGCHECK_P4: a

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  ffffce01f46989d0 -- (.trap 0xffffce01f46989d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=7fffffffffffffff rbx=0000000000000000 rcx=800000000000004c
rdx=3fffffffffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80373f5369a rsp=ffffce01f4698b60 rbp=ffffce01f4698c49
 r8=ffffc98005e95d50  r9=fffff80374650b00 r10=ffff808000000000
r11=ffffce01f4698df0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiBuildForkPte+0x62e:
fffff803`73f5369a f0490fba6d183f  lock bts qword ptr [r13+18h],3Fh ds:00000000`00000018=????????????????
Resetting default scope

STACK_TEXT: 
ffffce01`f46987d8 fffff803`73e56cbe     : 00000000`000000be ffffc980`645b90e8 8a000000`04400121 ffffce01`f46989d0 : nt!KeBugCheckEx
ffffce01`f46987e0 fffff803`73d282ff     : 8a000000`04400121 00000000`00000003 ffffce01`f4698a50 00000000`00000000 : nt!MiRaisedIrqlFault+0x184042
ffffce01`f4698830 fffff803`73e04d5e     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff803`73cefd2c : nt!MmAccessFault+0x4ef
ffffce01`f46989d0 fffff803`73f5369a     : 81000021`73daf005 ffffce01`00000000 ffff870d`05064940 ffffb885`93020701 : nt!KiPageFault+0x35e
ffffce01`f4698b60 fffff803`73f54583     : ffffb885`92e88080 ffffb885`93020080 ffff80bf`ffe356d8 ffffc980`078f3930 : nt!MiBuildForkPte+0x62e
ffffce01`f4698c90 fffff803`742d63b1     : ffffb885`92e88080 ffffce01`f4698f99 ffffb885`93020080 ffffb885`93020080 : nt!MiCloneVads+0x4ab
ffffce01`f4698f20 fffff803`741faa77     : 00000000`00000000 ffffce01`00000000 00000000`00000000 00000000`00000000 : nt!MiCloneProcessAddressSpace+0x261
ffffce01`f4699000 fffff803`7401209f     : 00000000`00002ab0 ffffce01`f4699b80 00000000`00000000 00000000`00000000 : nt!MmInitializeProcessAddressSpace+0x19bbbb
ffffce01`f46991f0 fffff803`741ba972     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspAllocateProcess+0x1c4f
ffffce01`f4699760 fffff803`74304435     : ffff4ec3`c7170d83 ffff4ec3`c7170c23 00000000`00000000 00000000`00000000 : nt!PspCreateProcess+0x242
ffffce01`f4699a30 fffff803`73e085b8     : 00000000`00000000 00000000`00000000 00000000`77566d4d ffffce01`f4699ae8 : nt!NtCreateProcessEx+0x85
ffffce01`f4699a90 00007fff`df90d7c4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000000a`028df308 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`df90d7c4


SYMBOL_NAME:  nt!MiRaisedIrqlFault+184042

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.1052

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  184042

FAILURE_BUCKET_ID:  0xBE_nt!MiRaisedIrqlFault

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1c5b4d11-09e0-def3-d2d0-70a11d69b92d}

Followup:     MachineOwner
---------
 
Solution
Colif
what are specs of the PC?

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .

which version of win 10
  1. right...
Sort by date Sort by votes
Colif

Colif

Win 11 Master
Moderator
Jun 12, 2015
65,180
6,433
168,090
what are specs of the PC?

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .

which version of win 10
  1. right click start
  2. choose run...
  3. type winver and press enter
  4. current version is 21H1
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom