Question BSOD : CRITICAL PROCESS DIED, UNEXPECTED_STORE_EXCEPTION while gaming.

Oct 29, 2020
16
0
10
0
Ive been having this problem since a months now, Im receiving those bsod codes everytime, Critical_Process_Dies while gaming and unexpected store exception randomly, Ive tired
Dism tools
Sfc /Scannow but it said it couldnt continue
I tried chkdsk and it says corrupted system or something like that, and it says it cant display anymore.
I reinstalled windows 3 times but still getting this

But at last reinstall, i didnt update any, I didnt got one but after i played gta san andreas, I got Critical process died. I hope someone help me. Thank you.
 

Colif

Win 10 Master
Moderator
I tried chkdsk and it says corrupted system or something like that, and it says it cant display anymore.
can you get us a screenshot so we have exact error. upload to an image sharing website and show link here.

If you get critical process died on 3 different installs it might be a problem with the drive.

What drives do you have in pc? if you can tell me who makes them I can find tests for them.


did you run dism after SFC as normally if it can't fix anything, you run dism and then re run sfc

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents

upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem
 

Colif

Win 10 Master
Moderator
im going to delete your replies in the other thread as they don't relate to it.

here is a quote of your last post

I tried windbg preview, it automatically detected DMP file from Windows\Memory.DMP
and this is what it says

Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
**
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**
Unable to read PsLoadedModuleList
**
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**
KdDebuggerData.KernBase < SystemRangeStart
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x0000000000000000 PsLoadedModuleList = 0xfffff80649e48150
Debug session time: Thu Oct 29 23:27:46.324 2020 (UTC + 8:00)
System Uptime: 0 days 0:13:54.048
**
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**
Unable to read PsLoadedModuleList
**
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**
KdDebuggerData.KernBase < SystemRangeStart
Loading Kernel Symbols
Unable to read PsLoadedModuleList
GetContextState failed, 0xD0000147
CS descriptor lookup failed
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
For analysis of this file, run !analyze -v
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counter
fffff806`49bc14e0 ?? ???
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
that dmp isn't much help. its corrupted, maybe a clue to look at drives.
 
Oct 29, 2020
16
0
10
0
if you are not sure of what drives you have, you can look in device manager under Disk drives, it should tell you there.
i got KERNEL_DATA_INPAGE_ERROR, this stopcode rarely happen. This is what i found on mini dump file



Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\103020-23515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


* Path validation summary **
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff80023a00000 PsLoadedModuleList = 0xfffff80023e48150
Debug session time: Fri Oct 30 02:15:43.415 2020 (UTC + 8:00)
System Uptime: 0 days 2:32:25.137
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
nt!KeBugCheckEx:
fffff80023bc14e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff6801eef4450=000000000000007a
5: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: ffff8f05e6d520e0, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2874

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-BI74IFM

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 3004

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

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 7a

BUGCHECK_P1: 20

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: ffff8f05e6d520e0

BUGCHECK_P4: 0

ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff6801eef4448 fffff80023c15485 : 000000000000007a 0000000000000020 ffffffffc000000e ffff8f05e6d520e0 : nt!KeBugCheckEx
fffff6801eef4450 fffff80023b323fb : 0000000000000000 00000000c000000e 0000000000000000 0000000000100000 : nt!MiWriteComplete+0x18ffb5
fffff6801eef4500 fffff80023a3e26d : ffff8f05e6d36080 ffff8f05ee87b088 0000000000000000 0000000000000000 : nt!IopCompletePageWrite+0x4b
fffff6801eef4530 fffff80023a48c32 : 0000000000000000 0000000000000000 ffff8f0500000000 0000000000000000 : nt!KiDeliverApc+0x19d
fffff6801eef45f0 fffff80023aa555d : ffffd0011d29e180 ffff8f0500000191 ffffd0011d29e101 0000000000000000 : nt!KiExitDispatcher+0x282
fffff6801eef4650 fffff80023a4848f : fffff6801eef4700 ffff8f05ee87b010 ffff8f05e507f801 ffff8f0500000001 : nt!KeInsertQueueApc+0x14d
fffff6801eef46f0 fffff80023a476a7 : 0000000000000000 ffff8f05e1f2b801 ffff8f05e50f3010 ffff8f05e51d8180 : nt!IopfCompleteRequest+0xdcf
fffff6801eef4800 fffff80026a932ec : ffff8f05e1f17a40 fffff6801eef4959 ffff8f05e1f178f0 0000000000000000 : nt!IofCompleteRequest+0x17
fffff6801eef4830 fffff80023a31f79 : fffff6801eef4959 fffff80027631d78 ffff8f05ee87b010 ffff8f05e6d36080 : volmgr!VmReadWrite+0x22dc
fffff6801eef4870 fffff800276239f0 : ffff8f05e51d8180 fffff6801eef4959 ffff8f05ee87b010 fffff6801eef48f0 : nt!IofCallDriver+0x59
fffff6801eef48b0 fffff8002762305c : 0000020100000000 0010000000000000 0038000000000000 ffff8f05e51d8180 : fvevol!FveFilterRundownReadWrite+0x920
fffff6801eef49c0 fffff80023a31f79 : 0065006c0067006f 006400700055005c 005c006500740061 00650069006c0043 : fvevol!FveFilterRundownWrite+0x4c
fffff6801eef4a60 fffff800277e3ca3 : 0000000000000000 ffff8f05e1e2da20 0000000000000100 0000000000000000 : nt!IofCallDriver+0x59
fffff6801eef4aa0 fffff800277e4f2d : 0000000000000002 fffff6801eef4be0 0000000000000000 00844cb800855100 : iorate!IoRateIssueAndRecordIo+0x7f
fffff6801eef4ae0 fffff800277e5120 : 0000000000000000 00000000000a6045 0000000000000000 0000000000000000 : iorate!IoRateProcessIrpWrapper+0x19d
fffff6801eef4c20 fffff80023a31f79 : ffffe970c6fe8325 0000000000000000 ffff8f05e50a7a40 ffff8f05ee87b010 : iorate!IoRateDispatchReadWrite+0x80
fffff6801eef4c60 fffff800277612d5 : 0000000000000000 0000000000006021 fffff6801eef4d19 0000000000000100 : nt!IofCallDriver+0x59
fffff6801eef4ca0 fffff80027761099 : 000000430083b498 ffffffffffffffff 0000000000000000 ffff8f05e50a7a40 : rdyboost!SmdProcessReadWrite+0x1f5
fffff6801eef4d80 fffff80023a31f79 : 0000000333abc000 ffff8f05e51da190 ffff8f05e51da1a8 0008e89f11c91ceb : rdyboost!SmdDispatchReadWrite+0x89
fffff6801eef4db0 fffff800276e1033 : ffff8f05e50994e0 fffff800276f4340 000004d200000000 fffff8002773ac04 : nt!IofCallDriver+0x59
fffff6801eef4df0 fffff80023a31f79 : ffff8f05e51da190 fffff8002770e294 0000000000000000 ffff8f05ee87b368 : volume!VolumePassThrough+0x23
fffff6801eef4e20 fffff800276f127d : 0000000333abc000 ffff8f05e51da190 ffff8f05e51da1a8 0000000000000000 : nt!IofCallDriver+0x59
fffff6801eef4e60 fffff800276f1143 : 0000000000000000 0086914800000000 fffff6801c461300 0800bc6a80bce79c : volsnap!VolsnapWriteFilter+0x11d
fffff6801eef4ee0 fffff80023a31f79 : 0000000000000000 0000000000000001 0000000000000000 0000000000000000 : volsnap!VolSnapWrite+0x13
fffff6801eef4f10 fffff80026d4327c : 0000000000000000 0000000000000000 0000000000000000 0000004300000000 : nt!IofCallDriver+0x59
fffff6801eef4f50 fffff80023bc4dae : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : Ntfs!NtfsStorageDriverCallout+0x1c
fffff6801eef4f80 fffff80023bc4d6c : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KxSwitchKernelStackCallout+0x2e
fffff6801c4612a0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSwitchKernelStackContinue


SYMBOL_NAME: volmgr!VmReadWrite+22dc

MODULE_NAME: volmgr

IMAGE_NAME: volmgr.sys

IMAGE_VERSION: 10.0.18362.592

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 22dc

FAILURE_BUCKET_ID: 0x7a_c000000e_volmgr!VmReadWrite

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {926fffaa-ca3b-a1ec-ad21-fa8bab592dfc}

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

5: kd> !blackboxbsd
Stream size mismatch (expected = 192, read = 168)
 

Colif

Win 10 Master
Moderator
volmgr.sys - volume manager

error spells it out
DISK_HARDWARE_ERROR: There was error with disk hardware

The requested page of kernel data could not be read in. Typically caused by a bad block in the paging file or disk controller error.
paging file on your C drive, who makes the boot drive in pc? most makers have hardware testing software
 
Reactions: UshierBantilan

ASK THE COMMUNITY

TRENDING THREADS