2

I execute sfc /scannow
Windows resource find corrupted file. However, it can not restore it!

Here is CBS.Log

I keep getting unexpected_store_exception

After apply suggested solution
I still get this unexpected store exception error.

The problem still happening.

I tried

  1. I uninstall Avast Anti-Virus
  2. clean install with new Window 10 ISO USB installer
  3. disabled "Fast Startup"
  4. DISM /Online /Cleanup-Image /RestoreHealth
  5. sfc /scannow

But, still does not solved error.

Here is my minidumps. Minidump.zip

If you want more information or log, Just make a comment what you need (b.b)

ibocon
  • 123

1 Answers1

1

The debug data are missing for but while analyzing the dmp file with Windbg I see a memory corruption in volmgrx.sys:

255 errors : !volmgrx (fffff80130c31000-fffff80130c310ff)
fffff80130c31000 *f8 *f4 *f3 *ff *f7 *f2 *f1 *ff *f9 *f4 *f1 *ff *f5 *f3 *f2 *ff ................
fffff80130c31010 *f7 *f2 *f3 *ff *f8 *f4 *f3 *ff *f7 *f4 *f0 *ff *fb *f5 *f0 *ff ................
fffff80130c31020 *f6 *f4 *f4 *ff *fc *f6 *f1 *ff *f6 *f4 *f4 *ff *f8 *f4 *f3 *ff ................
fffff80130c31030 *f6 *f4 *f3 *ff *f6 *f4 *f4 *ff *f6 *f4 *f4 *ff *f6 *f4 *f4 *ff ................
fffff80130c31040 *f6 *f4 *f4 *ff *f6 *f4 *f4 *ff *f6 *f4 *f4 *ff *f6 *f4 *f4 *ff ................
fffff80130c31050 *f6 *f4 *f4 *ff *f8 *f3 *f5 *ff *f8 *f4 *f3 *ff *f9 *f4 *f3 *ff ................
fffff80130c31060 *f9 *f3 *f4 *ff *fa *f6 *f1 *ff *f6 *f4 *f3 *ff *f6 *f5 *f1 *ff ................
fffff80130c31070 *f8 *f3 *f4 *ff *f8 *f3 *f4 *ff *f7 *f5 *f4 *ff *f8 *f4 *f3  ff ................
fffff80130c31080 *fb *f6 *f3 *ff *f8 *f5 *f1 *ff *f8 *f4 *f3 *ff *f7 *f5 *f5 *ff ................
fffff80130c31090 *f6 *f4 *f3 *ff *f8 *f4 *f3 *ff *f9 *f4 *f5 *ff *f8 *f3 *f4 *ff ................
fffff80130c310a0 *f6 *f4 *f4 *ff *f8 *f5 *f1 *ff *f8 *f3 *f2 *ff *f8 *f3 *f4 *ff ................
fffff80130c310b0 *f8 *f4 *f3 *ff *f8 *f3 *f2 *ff *f6 *f5 *f1 *ff *f8 *f3 *f4 *ff ................
fffff80130c310c0 *f5 *f3 *f3 *ff *f7 *f4 *f0 *ff *f8 *f2 *f3 *ff *f7 *f3 *f2 *ff ................
fffff80130c310d0 *f8 *f5 *f0 *ff *f7 *f4 *f0 *ff *f7 *f2 *f3 *ff *f8 *f3 *f2 *ff ................
fffff80130c310e0 *f7 *f3 *f2 *ff *f4 *f2 *f1 *ff *f6 *f4 *f3 *ff *fa *f2 *f2 *ff ................
fffff80130c310f0 *f6 *f3 *ef *ff *f6 *f1 *f2 *ff *f4 *f1 *f3 *ff *f8 *ef *f2 *ff ................

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

MEMORY_CORRUPTOR:  LARGE_256

STACK_COMMAND:  .cxr 0xffffd00026201c30 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE_256

BUCKET_ID:  MEMORY_CORRUPTION_LARGE_256

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE_256

If DISM was succesfull to repair all files, the file may get corrupted in memory. So run memtest86+ and check the Samsung M378B1G73EB0-CK0 RAM module for errors.

magicandre1981
  • 99,606