- Jan 17, 2014
- 13
- 0
- 18,510
Newly formatted install with all fresh drivers. Frequent BSODs (the ones I put in the title) which often occur in bundles when I first boot up for the day; but then rarely happen after that... (wtf?)
Windows 10 Pro
I5 12600k
Gigabyte z690 UD DDR4
Nvidia 2060 RTX
Every time this has happened, Vivaldi (my browser) has been open. Memory.DMP /Event viewer do not identify the driver responsible. Here's the Memory.DMP from the most recent one:
-------------------
Microsoft (R) Windows Debugger Version 10.0.22473.1005 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 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802
Debug session time: Mon Dec 6 09:27:15.397 2021 (UTC + 0:00)
System Uptime: 0 days 0:01:33.017
Loading Kernel Symbols
...............................................................
.....Page 883914 not present in the dump file. Type ".hh dbgerr004" for details
...........................................................
................................................................
.......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000c8
SYMBOL_NAME: nt!MiRaisedIrqlFault+14264c
MODULE_NAME: nt
STACK_COMMAND: .cxr; .ecxr ; kb
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID_FUNC_OFFSET: 14264c
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
---------
Windows 10 Pro
I5 12600k
Gigabyte z690 UD DDR4
Nvidia 2060 RTX
Every time this has happened, Vivaldi (my browser) has been open. Memory.DMP /Event viewer do not identify the driver responsible. Here's the Memory.DMP from the most recent one:
-------------------
Microsoft (R) Windows Debugger Version 10.0.22473.1005 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 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802
79800000 PsLoadedModuleList = 0xfffff8027a42a2d0Debug session time: Mon Dec 6 09:27:15.397 2021 (UTC + 0:00)
System Uptime: 0 days 0:01:33.017
Loading Kernel Symbols
...............................................................
.....Page 883914 not present in the dump file. Type ".hh dbgerr004" for details
...........................................................
................................................................
.......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000c8
6e1d1018). Type ".hh dbgerr001" for details
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff80279bf72a0 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff3878d73f4e0=00000000000000be
13: kd> !analyze -v
*******************************************************************************
[LIST]
[*]*
[*]Bugcheck Analysis *
[*]*
[/LIST]
*******************************************************************************
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: fffff80279a9fa85, Virtual address for the attempted write.
Arg2: 0a00000002e001a1, PTE contents.
Arg3: fffff3878d73f6d0, (reserved)
Arg4: 000000000000000f, (reserved)
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1530
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 4078
Key : Analysis.Init.CPU.mSec
Value: 671
Key : Analysis.Init.Elapsed.mSec
Value: 105135
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
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
FILE_IN_CAB: MEMORY.DMP
BUGCHECK_CODE: be
BUGCHECK_P1: fffff80279a9fa85
BUGCHECK_P2: a00000002e001a1
BUGCHECK_P3: fffff3878d73f6d0
BUGCHECK_P4: f
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: vivaldi.exe
TRAP_FRAME: fffff3878d73f6d0 -- (.trap 0xfffff3878d73f6d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=492074c085c86348 rbx=0000000000000000 rcx=492074c085c86348
rdx=492074c085c86348 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80279a78b8d rsp=fffff3878d73f860 rbp=fffff3878d73fac0
r8=cfffffffffffffff r9=fffff80279a9fa85 r10=ffff9e0f2ceb3900
r11=ffffe271389c4fff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!MiUnlockPageTableInternal+0x7d:
fffff80279a78b8d f0490fb109 lock cmpxchg qword ptr [r9],rcx ds:fffff80279a9fa85=492074c085c86348
Resetting default scope
STACK_TEXT:
fffff3878d73f4d8 fffff80279c75828 : 00000000000000be fffff80279a9fa85 0a00000002e001a1 fffff3878d73f6d0 : nt!KeBugCheckEx
fffff3878d73f4e0 fffff80279a9f47f : fffff3878d73f640 0000000000000003 fffff3878d73f750 0000000000000000 : nt!MiRaisedIrqlFault+0x14264c
fffff3878d73f530 fffff80279c0545e : 0000000000000040 fffff3878d73f7c0 00005c3e00168000 0000000000000000 : nt!MmAccessFault+0x4ef
fffff3878d73f6d0 fffff80279a78b8d : 0000000000001000 fffff3878d73fa40 ffff800000000000 0000000000000000 : nt!KiPageFault+0x35e
fffff3878d73f860 fffff80279a9f17a : 00007ff5a3c12000 0000000000000000 00000000c0000016 0000000000000000 : nt!MiUnlockPageTableInternal+0x7d
fffff3878d73f8a0 fffff80279c0545e : ffff9e0f2d2f0000 ffff9e0f2bd64080 0000022b290b0b50 ffff9e0f00000000 : nt!MmAccessFault+0x1ea
fffff3878d73fa40 00007ff6b86ac7e5 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x35e
000000c8779fdc20 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff6b86ac7e5SYMBOL_NAME: nt!MiRaisedIrqlFault+14264c
MODULE_NAME: nt
STACK_COMMAND: .cxr; .ecxr ; kb
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID_FUNC_OFFSET: 14264c
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
---------
- my BSODs are very similar to 
Facebook
Twitter
Instagram