[SOLVED] BSOD

[mark010203]

I'm having issues my laptop lately. There are times it just goes to BSOD like twice or thrice a day. Even though I'm just using it for browsing and windows word i still get a random BSOD sometimes it's kind a frustrating. Any help to why this is would be greatly appreciated.

I already runned windows memory diagnostic and scanned my laptopno problems came up. My laptops drives is up to date.



Here's my dumpfile i hope this helps. Thank you.



Microsoft (R) Windows Debugger Version 10.0.19041.685 X86

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\Minidump\022521-11953-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 19041 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0xfffff8062e200000 PsLoadedModuleList = 0xfffff8062ee2a390

Debug session time: Thu Feb 25 23:15:09.940 2021 (UTC + 8:00)

System Uptime: 1 days 5:58:02.245

Loading Kernel Symbols

..



Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.

Run !sym noisy before .reload to track down problems loading symbols.



.............................................................

................................................................

................................................................

..............................

Loading User Symbols

Loading unloaded module list

.........................................

For analysis of this file, run !analyze -v

4: kd> !analyze -v

***

* *

* Bugcheck Analysis *

* *

***



STORE_DATA_STRUCTURE_CORRUPTION (1c7)

The store component detected a corruption in its data structures.

Arguments:

Arg1: 0000000000000000, A chunk heap buffer's hash doesn't match.

Arg2: ffff940f22a55000, Chunk heap buffer whose hash didn't match.

Arg3: 00000000c1c3b4de, Expected buffer hash.

Arg4: 000000000004cb90, Page frame number of the corrupted page.



Debugging Details:

------------------





KEY_VALUES_STRING: 1



Key : Analysis.CPU.Sec

Value: 3



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on MSI



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.Sec

Value: 3



Key : Analysis.Memory.CommitPeak.Mb

Value: 80



Key : Analysis.System

Value: CreateObject





DUMP_FILE_ATTRIBUTES: 0x8

Kernel Generated Triage Dump



BUGCHECK_CODE: 1c7



BUGCHECK_P1: 0



BUGCHECK_P2: ffff940f22a55000



BUGCHECK_P3: c1c3b4de



BUGCHECK_P4: 4cb90



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXNTFS: 1 (!blackboxntfs)





BLACKBOXPNP: 1 (!blackboxpnp)





BLACKBOXWINLOGON: 1



CUSTOMER_CRASH_COUNT: 1



PROCESS_NAME: MemCompression



STACK_TEXT:

ffffed0fc9d17838 fffff8062e628138 : 00000000000001c7 0000000000000000 ffff940f22a55000 00000000c1c3b4de : nt!KeBugCheckEx

ffffed0fc9d17840 fffff8062e43fd15 : 5cfb05c9deca342b 000000000004cb90 0000000000000650 ffffed0fc9d17969 : nt!SmHpBufferProtectEx+0x1e8414

ffffed0fc9d178a0 fffff8062e43f348 : 00000000ffffffff ffff878a9155531a ffff940f266917f8 00000000204d88b6 : nt!SmHpChunkUnprotect+0x2d

ffffed0fc9d178d0 fffff8062e4c518c : 0000000000000000 0000000000000000 ffffed0fc9d17969 0000000000000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRecordUnprotect+0x1c

ffffed0fc9d17900 fffff8062e43eda2 : ffffed0f00000000 ffff940f3cb6ba10 0000000000000000 fffff8062e43ec93 : nt!ST_STORE<SM_TRAITS>::StDmPageRemove+0x130

ffffed0fc9d179d0 fffff8062e43e2ce : ffff940f141e2000 ffffed0fc9d17a98 0000000000000001 ffff940f135b1080 : nt!ST_STORE<SM_TRAITS>::StWorkItemProcess+0xc2

ffffed0fc9d17a20 fffff8062e522391 : 0000000000000000 ffff940f00000000 0000000000000000 0000000000000000 : nt!SMKM_STORE<SM_TRAITS>::SmStWorker+0x12a

ffffed0fc9d17ae0 fffff8062e517e25 : ffff940f141e2000 fffff8062e522380 ffffed0fc9c7f2a8 000fa4efbd9bbfff : nt!SMKM_STORE<SM_TRAITS>::SmStWorkerThread+0x11

ffffed0fc9d17b10 fffff8062e5fd0d8 : ffffc901c784a180 ffff940f135b1080 fffff8062e517dd0 0000000000000000 : nt!PspSystemThreadStartup+0x55

ffffed0fc9d17b60 0000000000000000 : ffffed0fc9d18000 ffffed0fc9d11000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28





SYMBOL_NAME: nt!SmHpBufferProtectEx+1e8414



MODULE_NAME: nt



IMAGE_NAME: ntkrnlmp.exe



IMAGE_VERSION: 10.0.19041.804



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 1e8414



FAILURE_BUCKET_ID: 0x1C7_0_nt!SmHpBufferProtectEx



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {677f42d4-ea31-d924-1621-3373689c0a0a}



Followup: MachineOwner

 

[Fix_that_Glitch]

Try doing a clean boot to see if it stops, to see if it is a background program causing a problem. Then if it doesn't crash, you can refer to
How to determine what is causing the problem after you do a clean boot to check which program is causing the issue.