• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

PC had a hard reboot and blue screen, I don't know enough about PCs to any info in the dmp file. I'd appreciate if anyone can decipher it.

Joined
Feb 14, 2024
Messages
44 (0.12/day)
IMG_20250212_195421.jpg

I've never had a BSOD like this before, if the happen, they're just the normal solid ones.

This is the Dropbox file for the dmp file that was created. I'd appreciate any help I can get

Specs:
CPU: Ryzen 5 5600
GPU: Radeon 6650XT
Motherboard: MSI B550m PRO-VDH
RAM: 32GB (4×8GB) Kingston FURY Beast
SSD: 1TB Lexar NM620 M.2
PSU: 700 Watt be quiet! System Power 9
OS: Windows 10 Pro
 
Last edited:
Joined
Jun 2, 2017
Messages
9,743 (3.46/day)
System Name Best AMD Computer
Processor AMD 7900X3D
Motherboard Asus X670E E Strix
Cooling In Win SR36
Memory GSKILL DDR5 32GB 5200 30
Video Card(s) Sapphire Pulse 7900XT (Watercooled)
Storage Corsair MP 700, Seagate 530 2Tb, Adata SX8200 2TBx2, Kingston 2 TBx2, Micron 8 TB, WD AN 1500
Display(s) GIGABYTE FV43U
Case Corsair 7000D Airflow
Audio Device(s) Corsair Void Pro, Logitch Z523 5.1
Power Supply Deepcool 1000M
Mouse Logitech g7 gaming mouse
Keyboard Logitech G510
Software Windows 11 Pro 64 Steam. GOG, Uplay, Origin
Benchmark Scores Firestrike: 46183 Time Spy: 25121
What are the System specs? People can help you way more if they know what hardware you are using.
 
Joined
Feb 14, 2024
Messages
44 (0.12/day)
What are the System specs? People can help you way more if they know what hardware you are using.
Sorry about that, completely forgot to add them.
Specs:
CPU: Ryzen 5 5600
GPU: Radeon 6650XT
Motherboard: MSI B550m PRO-VDH
RAM: 32GB (4×8GB) Kingston FURY Beast
SSD: 1TB Lexar NM620 M.2
PSU: 700 Watt be quiet! System Power 9
OS: Windows 10 Pro
Added them to the original post as well
 

Solaris17

Super Dainty Moderator
Staff member
Joined
Aug 16, 2005
Messages
27,259 (3.83/day)
Location
Alabama
System Name RogueOne
Processor Xeon W9-3495x
Motherboard ASUS w790E Sage SE
Cooling SilverStone XE360-4677
Memory 128gb Gskill Zeta R5 DDR5 RDIMMs
Video Card(s) MSI SUPRIM Liquid X 4090
Storage 1x 2TB WD SN850X | 2x 8TB GAMMIX S70
Display(s) 49" Philips Evnia OLED (49M2C8900)
Case Thermaltake Core P3 Pro Snow
Audio Device(s) Moondrop S8's on schitt Gunnr
Power Supply Seasonic Prime TX-1600
Mouse Razer Viper mini signature edition (mercury white)
Keyboard Monsgeek M3 Lavender, Moondrop Luna lights
VR HMD Quest 3
Software Windows 11 Pro Workstation
Benchmark Scores I dont have time for that.
Code:
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: ffffb779a9809ffc, Virtual address for the attempted write.
Arg2: 8a00000000200121, PTE contents.
Arg3: ffffde85d5acf140, (reserved)
Arg4: 000000000000000b, (reserved)

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1031

Key : Analysis.Elapsed.mSec
Value: 2652

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

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

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

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Bugcheck.Code.LegacyAPI
Value: 0xbe

Key : Bugcheck.Code.TargetModel
Value: 0xbe

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: AV_nt!MiSystemFault

Key : Failure.Hash
Value: {d80c40a2-5000-439f-696b-1bd8abb14be3}


BUGCHECK_CODE: be

BUGCHECK_P1: ffffb779a9809ffc

BUGCHECK_P2: 8a00000000200121

BUGCHECK_P3: ffffde85d5acf140

BUGCHECK_P4: b

FILE_IN_CAB: 021225-9718-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

FAULTING_THREAD: ffff96050fcbb040

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: services.exe

TRAP_FRAME:  ffffde85d5acf140 -- (.trap 0xffffde85d5acf140)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb779a9809ffc rbx=0000000000000000 rcx=ffffb779a980a024
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8026b414bf0 rsp=ffffde85d5acf2d8 rbp=ffffde85d5acf470
r8=000000000000002a r9=0000000000000008 r10=ffffb779a980a020
r11=0000000078050136 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe nc
nt!memset+0x30:
fffff802`6b414bf0 4a895408f8 mov qword ptr [rax+r9-8],rdx ds:ffffb779`a9809ffc=????????????????
Resetting default scope

STACK_TEXT:
ffffde85`d5acee98 fffff802`6b445f1b : 00000000`000000be ffffb779`a9809ffc 8a000000`00200121 ffffde85`d5acf140 : nt!KeBugCheckEx
ffffde85`d5aceea0 fffff802`6b238cd0 : ffffde85`d5acf000 00000000`00000003 ffffde85`d5acf1c0 00000000`00000000 : nt!MiSystemFault+0x1ce47b
ffffde85`d5acefa0 fffff802`6b40ea6d : ffffffff`ffffffff 00000000`00000001 ffffa781`10dc4180 fffff802`6b2a3245 : nt!MmAccessFault+0x400
ffffde85`d5acf140 fffff802`6b414bf0 : fffff802`6b2bbc18 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x36d
ffffde85`d5acf2d8 fffff802`6b2bbc18 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!memset+0x30
ffffde85`d5acf2e0 fffff802`6b8d4a27 : 00000000`00000157 00000000`78050137 00000000`7804ffe0 00000000`00000000 : nt!RtlClearBitsEx+0x98
ffffde85`d5acf310 fffff802`6b8d49ac : ffff9605`16225010 00000000`00000001 00000000`00000000 00000000`0000156a : nt!MiMarkRetpolineBits+0x63
ffffde85`d5acf340 fffff802`6b82fe86 : ffff9605`16225010 ffff9605`16225010 ffffde85`d5acf470 00000000`00000001 : nt!MiMarkKernelImageRetpolineBits+0x34
ffffde85`d5acf370 fffff802`6b7755b1 : 00000000`00000000 fffff802`ffffffff ffff509e`00000001 ffffce87`ade672c0 : nt!MiUnloadSystemImage+0x134e9e
ffffde85`d5acf510 fffff802`6b7754de : ffff9605`08c5be00 ffffde85`d5acf840 00000000`00000000 ffffde85`d5acf9b0 : nt!MmUnloadSystemImage+0x41
ffffde85`d5acf540 fffff802`6b632c80 : ffff9605`08c5be00 ffffde85`d5acf840 ffff9605`08c5be00 fffff802`6b666ddf : nt!IopDeleteDriver+0x4e
ffffde85`d5acf590 fffff802`6b25a1a7 : 00000000`00000000 00000000`00000000 ffffde85`d5acf840 ffff9605`08c5be30 : nt!ObpRemoveObjectRoutine+0x80
ffffde85`d5acf5f0 fffff802`6b25a0ce : ffff9605`08c5be30 ffffde85`d5acf9b0 ffff9605`08c5be00 00000000`00060001 : nt!ObfDereferenceObjectWithTag+0xc7
ffffde85`d5acf630 fffff802`6b76d538 : ffff9605`08c5be30 ffffde85`d5acf840 ffffde85`d5acf9b0 00000000`c0000001 : nt!HalPutDmaAdapter+0xe
ffffde85`d5acf660 fffff802`6b89ef0b : ffff9605`0fcbb040 00000000`00000000 00000000`00000001 ffff9605`08c5be30 : nt!IopUnloadDriver+0x250
ffffde85`d5acf790 fffff802`6b412908 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffce87`b07d2060 : nt!NtUnloadDriver+0xb
ffffde85`d5acf7c0 fffff802`6b4036e0 : fffff802`6b84848c ffff9605`0fcbb040 fffff802`6b61851d 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
ffffde85`d5acf958 fffff802`6b84848c : ffff9605`0fcbb040 fffff802`6b61851d 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
ffffde85`d5acf960 fffff802`6b89ef0b : ffff9605`0fcbb040 000000c3`63cfed44 00000000`00000000 00000000`00000000 : nt!IopUnloadDriver+0xdb1a4
ffffde85`d5acfa90 fffff802`6b412908 : 00000000`00004000 ffffde85`d5acfb40 ffffde85`d5acfb40 00000000`00000000 : nt!NtUnloadDriver+0xb
ffffde85`d5acfac0 00007ffe`3f130de4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000c3`63cfecf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`3f130de4


SYMBOL_NAME: nt!MiSystemFault+1ce47b

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.5369

STACK_COMMAND: .process /r /p 0xffff96050ebab200; .thread 0xffff96050fcbb040 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 1ce47b

FAILURE_BUCKET_ID: AV_nt!MiSystemFault

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d80c40a2-5000-439f-696b-1bd8abb14be3}

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

this is a mini dump so not much but

IMAGE_NAME: ntkrnlmp.exe

FAILURE_BUCKET_ID: AV_nt!MiSystemFault

nt!MmAccessFault+0x400

This looks like a memory access fault. This is usually vram or ram related. If you are running an overclock dial it back and update your drivers.
 
Joined
Nov 27, 2023
Messages
2,823 (6.36/day)
System Name The Workhorse
Processor AMD Ryzen R9 5900X
Motherboard Gigabyte Aorus B550 Pro
Cooling CPU - Noctua NH-D15S Case - 3 Noctua NF-A14 PWM at the bottom, 2 Fractal Design 180mm at the front
Memory GSkill Trident Z 3200CL14
Video Card(s) NVidia GTX 1070 MSI QuickSilver
Storage Adata SX8200Pro
Display(s) LG 32GK850G
Case Fractal Design Torrent (Solid)
Audio Device(s) FiiO E-10K DAC/Amp, Samson Meteorite USB Microphone
Power Supply Corsair RMx850 (2018)
Mouse Razer Viper (Original) on a X-Raypad Equate Plus V2
Keyboard Cooler Master QuickFire Rapid TKL keyboard (Cherry MX Black)
Software Windows 11 Pro (24H2)
To add to what @Solaris17 said, if you are NOT running an OC on memory or if dialing it down doesn’t help, running a full MemTest might be prudent.
 
Joined
Sep 24, 2005
Messages
391 (0.06/day)
That bluescreen looks identical to my recent bluescreen issue. Mine was occurring on a dual boot windows 10 pro / windows 11 pro system. The windows 11 pro installation is an upgrade from windows 10 pro installation. The bluescreen has been happening immediately when I try to restart windows 11 pro. I allowed windows to do check disc and repair to that SSHD and the bluescreen issue has not reappeared. My windows 11 pro installation is for testing use mainly and I don't know what the main cause for the bluescreen is yet.
 
Top