Those minidump files also indicate memory (RAM) corruption no specific driver is listed
The best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello can sameone help me?
My computer sometimes encounters BSOD problems when starting up. If I restart the computer via the restart button, the blue screen problem occurs repeatedly and I cannot enter the system. But when I shut down completely and start the computer with the start button it doesn't trigger the blue screen issue, which confuses me. Below is my Minidump file.
4: 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: fffff901267f97ff, memory referenced.
Arg2: 0000000000000010, 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: fffff901267f97ff, 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: Execute
Key : Analysis.CPU.mSec
Value: 1828
Key : Analysis.Elapsed.mSec
Value: 1825
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 327
Key : Analysis.Init.Elapsed.mSec
Value: 5160
Key : Analysis.Memory.CommitPeak.Mb
Value: 81
Key : Bugcheck.Code.LegacyAPI
Value: 0x50
Key : Bugcheck.Code.TargetModel
Value: 0x50
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: AV_X_(null)_BAD_IP_nt!MiSystemFault
Key : Failure.Hash
Value: {519102ae-339f-c953-2278-3f0bfcf5aa85}
BUGCHECK_CODE: 50
BUGCHECK_P1: fffff901267f97ff
BUGCHECK_P2: 10
BUGCHECK_P3: fffff901267f97ff
BUGCHECK_P4: 2
FILE_IN_CAB: 050324-16234-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
READ_ADDRESS: fffff801270fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
fffff901267f97ff
MM_INTERNAL_CODE: 2
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: ffffa20c5765f4e0 -- (.trap 0xffffa20c5765f4e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff801267bd000 rbx=0000000000000000 rcx=0000000000040086
rdx=0000000000000080 rsi=0000000000000000 rdi=0000000000000000
rip=fffff901267f97ff rsp=ffffa20c5765f678 rbp=0000000000000000
r8=0000000000000000 r9=00000000ffffffff r10=fffff801267bd0c0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
fffff901`267f97ff ?? ???
Resetting default scope
FAILED_INSTRUCTION_ADDRESS:
+0
fffff901`267f97ff ?? ???
STACK_TEXT:
ffffa20c`5765f238 fffff801`268390db : 00000000`00000050 fffff901`267f97ff 00000000`00000010 ffffa20c`5765f4e0 : nt!KeBugCheckEx
ffffa20c`5765f240 fffff801`2661c2a0 : ffffb10d`c06ec180 00000000`00000010 ffffa20c`5765f560 00000000`00000000 : nt!MiSystemFault+0x1de02b
ffffa20c`5765f340 fffff801`2680db29 : 00000000`00000000 fffff801`267a2d01 ffffb10d`b91d7bb0 ffffa20c`5765f6e0 : nt!MmAccessFault+0x400
ffffa20c`5765f4e0 fffff901`267f97ff : fffff801`267bd0d4 00000000`00000000 0000002b`20eed1a5 00000000`00000000 : nt!KiPageFault+0x369
ffffa20c`5765f678 fffff801`267bd0d4 : 00000000`00000000 0000002b`20eed1a5 00000000`00000000 00000000`00000004 : 0xfffff901`267f97ff
ffffa20c`5765f680 fffff801`2664cf46 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PpmIdleDefaultExecute+0x14
ffffa20c`5765f6b0 fffff801`2664bcf4 : 00000000`00000000 fffff801`0000001e 00000000`01050102 00000000`00000000 : nt!PpmIdleExecuteTransition+0x10d6
ffffa20c`5765fab0 fffff801`268024f4 : ffffffff`00000000 ffff8001`988e7840 ffffb10d`b4e5a140 00000000`000002ca : nt!PoIdle+0x374
ffffa20c`5765fc20 00000000`00000000 : ffffa20c`57660000 ffffa20c`57659000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54
SYMBOL_NAME: nt!MiSystemFault+1de02b
MODULE_NAME: nt
IMAGE_VERSION: 10.0.19041.4291
STACK_COMMAND: .cxr; .ecxr ; kb
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID_FUNC_OFFSET: 1de02b
FAILURE_BUCKET_ID: AV_X_(null)_BAD_IP_nt!MiSystemFault
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {519102ae-339f-c953-2278-3f0bfcf5aa85}
Followup: MachineOwner
---------
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Those minidump files also indicate memory (RAM) corruption no specific driver is listed
The best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors
050324-16234-01.rar Yes, there are two more files here, one from 3 days ago and the other from 2 months ago. I think they happened under the same circumstances.
Your one minidump file just listed generic RAM corruption errors, no specific cause for that crash was listed, do you have any more minidump files you can upload for analysis?
Hi, I am Dave, I will help you with this.
Please upload any minidump files you have for analysis, I will check those to see if they provide any insight into a potential cause of the system crashes.
Open Windows File Explorer.
Navigate to C:\Windows\Minidump
Copy any minidump files onto your Desktop, then zip those up.
Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.
Then post the link here to the zip file, so we can take a look for you.