BSOD while browsing

Question

while i'm browsing my PC suddenly BSOD i can't must error code but as i remember is like Sata Corrupt * * *

but before this happen few days ago i experiencing hang on my PC or freezing...

can anyone here help me which is my main problem to my PC ? if its hardware or software..

P.S my storage is NVMe m.2 (WD_Black) and 2nd T-Force and my mobo; PRO Z790-P WIFI DDR4

dump file link:- https://drive.google.com/file/d/1yOqewjnGUIg8GR4oI2uugaMkt8Rw6rNp/view?usp=sharing

Answer 1

If you have already disabled memory compression via the command: Disable-MMAgent -mc, keep an eye on it to see if the blue screen will appear again.

Answer 2

all my storage is good healthy and when i test Memory Diagnostic no error found.. all my driver is latest

Answer 3

No problem here. after disabling Disable-MMAgent -mc what should i do next ?

Answer 4

Good afternoon Good afternoon

Jay Rodney Besario2, how are you? Checking the dump you sent I could see that the cause of your BSOD is memory compression.

Download the QuickMemoryTestOK_x64 tool and test your memory

StartFragmentIn this LOOPS part, put LOOPS: 10 and then click on "start test" and wait for completionEndFragment

StartFragment

obs.: caso no resultado da ferramenta não conste nada de anormal , erro ou falha você pode executar o seguinte comando para desativar a compactação de memória:

Abra o powershell como admin e execute o comando abaixo:

EndFragment

Disable-MMAgent -mc 

***************************************************

* *

* Análise de verificação de bugs

* *

***************************************************

STORE_DATA_STRUCTURE_CORRUPTION (1c7)

O componente de armazenamento detectou uma corrupção em suas estruturas de dados.

Argumentos:

Arg1: 0000000000000001, ocorreu uma exceção sem tratamento no thread de armazenamento e o hash de um buffer de heap de bloco não corresponde, o que provavelmente é a origem da exceção.

Arg2: ffff8807d8920000, buffer de heap de bloco cujo hash não correspondeu.

Arg3: 000000003b2fa533, hash de buffer esperado.

Arg4: 000000020049e3c6, Número do quadro da página corrompida.

PROCESS_NAME: MemCompression

TRAP_FRAME: ffffce040000000f -- (.trap 0xffffce040000000f)

Não é possível ler o quadro de armadilha em ffffce04'0000000f

Redefinindo o escopo padrão

STACK_TEXT:

ffffce04'13f3e488 fffff805'ce78c659 : 00000000'000001c7 00000000'00000001 ffff8807'd8920000 00000000'3b2fa533 : nt! KeBugCheckEx

ffffce04'13f3e490 ff805'cea05718 : 00000002'0049e3c6 ffffce04'13f3e5a0 ffffce04'13f3fb00 ffffce04'13f3e670 : nt! SmHpChunkHeapProtect+0x13d

ffffce04'13f3e4f0 fffff805'ceac803c : ffff8807'c413f000 ffffce04'13f3e5a0 ffffce04'00000001 fffff805'ce8bb94f : nt! SMKM_STORE::SmStUnhandledExceptionFilter+0x50

ffffce04'13f3e540 fffff805'ce901a8c : ffffce04'00000003 ffffce04'13f3f5b8 ffffce04'13f39000 ffffce04'13f40000 : nt!'SMKM_STORE::SmStWorkerThread'::'1'::filt$0+0x1b

ffffce04'13f3e570 fffff805'ceaae68f : ffffce04'13f3f5b8 ffffce04'13f3eb70 0000000000'00000000 000000000'00000000 : nt!_C_specific_handler+0x9c

ffffce04'13f3e5e0 fffff805'ce699072 : 00000000'00000000 fffff805'ce400000 fffff805'ce8bb94f fffff805'ce4fb9e4 : nt! RtlpExecuteHandlerForException+0xf

ffffce04'13f3e610 fffff805'ce7dd501 : ffffce04'13f3f480 ffffce04'13f3f2a0 ffffce04'13f3f480 fffff780'00000708 : nt! RtlDispatchException+0x2d2

ffffce04'13f3ed70 fffff805'ceab9145 : 00000000'00000000 ffff807'dcd77000 ffffce04'0000000f fffff805'ce65f05b : nt! KiDispatchException+0xac1

ffffce04'13f3f480 fffff805'ceab75a1 : 000000000'000000000 000000000'000000000 00000000'0000000c ffff8807'c87560c0 : nt! KiExceptionDispatch+0x145

ffffce04'13f3f660 fffff805'ce791804 : ffff8807'c413f050 00000000'001f831a ffff8807'c413f0e8 ffff8807'c413f050 : nt! KiRaiseAssertion+0x361

ffffce04'13f3f7f0 ffff805'ce7934a1 : ffff8807'c413f050 ffff8807'dcd77d50 ffff8807'c413f050 ffff8807'00000001 : nt! ST_STORE::StDmPageRecordRemove+0x394

ffffce04'13f3f890 fffff805'ce6218e5 : 00000000'00000001 ffff8807'c413f000 ffff8807'db56e090 fffff805'ce621fc2 : nt! ST_STORE::StDmPageRemove+0xa11

ffffce04'13f3f9c0 fffff805'ce62128b : ffff8807'00000000 fffff805'00000000 ffff8807'd13fdd90 000000000'00000000 : nt! ST_STORE::StWorkItemProcess+0x245

ffffce04'13f3fa60 fffff805'ce8bb94f : ffff012b'00000000 ffff8807'00000001 ffffffff'fffdb610 0000000000'00000000 : nt! SMKM_STORE::SmStWorker+0x3bb

ffffce04'13f3fb00 fffff805'ce8a2d1a : ffff8807'c413f000 fffff805'ce8bb920 ffffbe01'55b01180 066fe47f'b19bbdff : nt! SMKM_STORE::SmStWorkerThread+0x2f

ffffce04'13f3fb30 fffff805'ceaa61b4 : ffffbe01'55b01180 ffff8807'c216e3c0 fffff805'ce8a2cc0 00500065'00720061 : nt! PspSystemThreadStartup+0x5a

ffffce04'13f3fb80 000000000'00000000 : ffffce04'13f40000 ffffce04'13f39000 0000000000'000000000 000000000'00000000 : NT! KiStartSystemThread+0x34

Please let me know if the above procedure solved your problem I look forward to hearing from you!

Answer 5

Hi there, Jay! This is Marc and thanks for reaching out. I appreciate you providing those details about your setup and the steps you've already tried. Based on what you've shared, I have a few ideas that should help resolve this issue.

Possible Causes:

> Faulty RAM: Memory corruption is a common cause of this type of error.

> Storage Issues: While your main storage is NVMe, memory management corruption can sometimes be triggered by storage subsystem problems (though this is less likely).

1. Test Your RAM

Run Windows Memory Diagnostic:

> Search for “Windows Memory Diagnostic” in the Start menu and run it.

> Choose to restart and check for problems.

Run MemTest86 for a More Thorough Test:

> Download MemTest86 and create a bootable USB.

> Boot from the USB and let it run for several passes.

2. Check for Storage Issues

> Use CrystalDiskInfo or WD Dashboard to check the health of your NVMe and T-Force drives.

> Update your NVMe/SATA drivers and motherboard BIOS.

3. Check for Driver or Software Issues

> Update all drivers, especially chipset, storage, and network drivers.

> Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to check for corrupted system files.

Additional troubleshooting steps: Try re-seating your RAM, switch ram slots then reboot your system. Test One Stick at a Time: If you have multiple RAM modules, test each one individually to isolate the faulty component.

Your BSOD is caused by memory management corruption, most likely due to faulty RAM or system instability. Start by testing your RAM and updating your drivers and BIOS. If the problem persists, consider hardware replacement or further diagnostics.

Please try these steps and let me know how it goes. If you run into any issues, just reply back with the details.

Best regards,