BSOD MEMORY_MANAGEMENT

R

ruioke

Member
Joined
Feb 14, 2022
Posts
5
Hi all ,
I'm new on the forum and i'm trying to resolve one issue after i update the RAM on my PC.

I had 2 BSOD in the last 7 days for memory Fault while playing EscapeFromTarkov, but in two different moment.

I've tried to follow some infos I saw on the forum but now my knowledge is blocking me.
[SOLVED] - Need help with random BSOD's (Packard Bell EasyNote ML61)
An old one i know :D

I see that maybe could be a problem with software like DaemonTool and i removed it as fast i read it :)


I attach on the post the dump file extracted of the BSOD error.

I saw that the error is 0x411

2: kd> .bugcheck
Bugcheck code 0000001A
Arguments 00000000`00000411 fffffc80`f93b6ba8 00002001`762df880 fff7fc80`f93b6ba8


I'm blocked to undestand what P2 P3 and P4 stand for

I hope you can help us to understand more of this issue.

Thanks a lot
Fabio
 

Attachments

Rich (BB code): 
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffffc80f93b6ba8 << PTE address
Arg3: 00002001762df880 << PTE Contents
Arg4: fff7fc80f93b6ba8 << PTE address

The first parameter indicates that the PTE is corrupt for some reason, however, I can't see any reason why it would be.

Rich (BB code): 
2: kd> !pte fffffc80f93b6ba8
                                           VA 000001f276d75000
PXE at FFFFFCFE7F3F9018    PPE at FFFFFCFE7F203E48    PDE at FFFFFCFE407C9DB0    PTE at FFFFFC80F93B6BA8
contains 0A000001A08AE867  contains 0A00000310AD0867  contains 1A000002AE087867  contains 00002001762DF880
pfn 1a08ae    ---DA--UWEV  pfn 310ad0    ---DA--UWEV  pfn 2ae087    ---DA--UWEV  not valid
                                                                                  Transition: 2001762df
                                                                                  Protect: 4 - ReadWrite

Rich (BB code): 
2: kd> dt _MMPTE_TRANSITION fffffc80f93b6ba8
nt!_MMPTE_TRANSITION
   +0x000 Valid            : 0y0
   +0x000 Write            : 0y0
   +0x000 Spare            : 0y0
   +0x000 IoTracker        : 0y0
   +0x000 SwizzleBit       : 0y0
   +0x000 Protection       : 0y00100 (0x4)
   +0x000 Prototype        : 0y0
   +0x000 Transition       : 0y1
   +0x000 PageFrameNumber  : 0y001000000000000101110110001011011111 (0x2001762df)
   +0x000 Unused           : 0y0000000000000000 (0)

From the call stack:

Rich (BB code): 
2: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff205`83f3f658 fffff807`170a9932 nt!KeBugCheckEx
01 fffff205`83f3f660 fffff807`170a133e nt!MiResolveTransitionFault+0xca2
02 fffff205`83f3f720 fffff807`1709f259 nt!MiDispatchFault+0x3fe
03 fffff205`83f3f860 fffff807`1720545e nt!MmAccessFault+0x189
04 fffff205`83f3fa00 000001ed`d31cdc75 nt!KiPageFault+0x35e
05 00000021`835bc5d0 00000000`00000000 0x000001ed`d31cdc75

Rich (BB code): 
2: kd> !irql
Debugger saved IRQL for processor 0x2 -- 2 (DISPATCH_LEVEL)

It seems that the IRQL would have been too high as well.



Please follow the posting instructions as suggested. In the meantime, it may be worthwhile running MemTest86 for at least 8 passes (will require two runs of 4 passes) - Test RAM with PassMark MemTest86
 
Thank you both for your reply!

I have tried a stress test on the ram and the diagnostic of windows without get an issue.

I’ll try MemTest86 and let you know!
Do you need the also the dump file that ask deejay? With your bsod program?

I’ll try in this evening thank you!
Fabio
 
Hi,
i attach what i extract with SysnativeBSODCollection.

Unfortunatly seems to block itself in waiting system info I don't know why.

Hope what it saves on documents can help you .

Right now the pc still working good for 9/10 hour without any issue or BSOD.

I have prepared the USB drive with memtest i'll test it in these days.

Cheers
Fabio
 

Attachments

Some of the files can take some time to be exported, with the newer version under development, if a file takes too long to export then it will be skipped.

The previous dump file(s) appear to have been deleted?

There is a couple of programs which I would recommend that you remove:
  • Driver Booster 7
  • AVG Zen
Driver Booster 7 and similar programs should not be used to update drivers, they're usually wrong or outdated. AVG Zen is no longer supported and AVG has caused BSOD problems in the past.
 
Hi all,

sorry for the delay but I had a tough week...

Yesterday they said me that the computer gone in BSOD again but seems to not be recorded on the log/ Event Viewer.

I tried to take another Dump from your program but still stay in Waiting System Info for at least 1 hour.

I attach to the post even the memtest report that said me that the RAM doesn't have any issue.


Thanks for your patience
Fabio
 

Attachments

HI BlueRobot, i don' t find AVG Zen on the Computer and i tried even AVG Remover , same output.
Right now i've enabled the clean boot with only few services in autostart.

I'll right back if i met same BSOD in this week.

Thank you for your support.

Fabio
 
Okay, a shortcut must have been left behind. Please continue to use the system as you normally would and let us know it goes.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top