BSOD- Critical Process died, System_service_exception, Memory_managent

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


Computer Memory | DDR4 DDR RAM Upgrades | Crucial.com

Code:

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

PS C:\Windows\system32> sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\Windows\system32> dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.720

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
PS C:\Windows\system32> dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.720

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\Windows\system32> sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\Windows\system32> chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
  341248 file records processed.
File verification completed.
  5675 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  1644 reparse records processed.
  478200 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.
  1644 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  68477 data files processed.
CHKDSK is verifying Usn Journal...
  37443464 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

  68219903 KB total disk space.
  31947064 KB in 266206 files.
    184160 KB in 68478 indexes.
         0 KB in bad sectors.
    449275 KB in use by the system.
     65536 KB occupied by the log file.
  35639404 KB available on disk.

      4096 bytes in each allocation unit.
  17054975 total allocation units on disk.
   8909851 allocation units available on disk.
PS C:\Windows\system32> D:
PS D:\> chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
  52480 file records processed.
File verification completed.
  27 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  67 reparse records processed.
  60942 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.
  67 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  4231 data files processed.

Windows has scanned the file system and found no problems.
No further action is required.

 419571711 KB total disk space.
 329604580 KB in 47137 files.
     13752 KB in 4233 indexes.
         0 KB in bad sectors.
    131247 KB in use by the system.
     65536 KB occupied by the log file.
  89822132 KB available on disk.

      4096 bytes in each allocation unit.
 104892927 total allocation units on disk.
  22455533 allocation units available on disk.
PS D:\> cd C:\windows\system32
PS C:\windows\system32> wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-C9A3ECB\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.
PS C:\windows\system32> wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-C9A3ECB\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.
PS C:\windows\system32> wmic recoveros get autoreboot
AutoReboot
FALSE

PS C:\windows\system32> wmic recoveros get DebugInfoType
DebugInfoType
7

PS C:\windows\system32> bcdedit /enum {badmemory}
Invalid command line switch: /encodedCommand
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.
PS C:\windows\system32> bcdedit /enum

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {a3412c57-5b50-11ea-88a2-d8e02cd25fa6}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 120

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 10
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {a3412c59-5b50-11ea-88a2-d8e02cd25fa6}
displaymessageoverride  Recovery
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {a3412c57-5b50-11ea-88a2-d8e02cd25fa6}
nx                      OptIn
bootmenupolicy          Standard
PS C:\windows\system32>

There are commands that are specific for administrative command prompt that do not work in PS.

The instructions were to use administrative command prompt.

Please run bcdedit /enum {badmemory} using administrative command prompt.

Sorry, done.

Code:

Microsoft Windows [Version 10.0.18363.720]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier              {badmemory}

C:\Windows\system32>

The commands/results ran look good.

The RAM that is not on the QVL is a confounding factor.

It is best to use motherboard manufactured tested RAM.

But then how was it possible that they ran stable for some time and then it started to bsod? Could they get damaged? I still have warranty on them so I think I could exchange them for different ones.
I will try to get the replacement.

But until then maybe I could try to make them stable by changing some "fancy" parameter or two in bios? :)

Once confounding factors are reduced or removed the testing should become easier.

Testing can still be performed now.
However the tests are not designed to test incompatibility.
So a test pass does not rule out problems.




Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan




Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows |
Seagate
How to use SeaTools for Windows | Seagate Support US



Run Memtest86 version 8.3 (or newer version if available) for four passes.
Repeat the test so that eight passes are performed.

MemTest86 - Official Site of the x86 Memory Testing Tool

Use a camera or smart phone camera to take pictures and post images into the thread.
In case there are any problems uploading images use share links (one drive, drop box, or google drive)

Memtest86 has a feature to produce a text report.
Please post this in addition to the images.

Okay so I downloaded HD Tune, I was using it with my old SSD too I remember. But with this one I can't see any temperature nor the Health bar statistics. And when I do the benchmark it only goes up to 500MB/s, but I am pretty sure this one can go up to 3GB/s. How come I can't see anything about this SSD?
Btw I was downloading and installing a little program while doing a benchmark at the very start, so the speed went down.
Attachment 271287
Attachment 271288

I will do other tests very soon.

- - - Updated - - -

Error scan:
Attachment 271293

- - - Updated - - -

SeaTools long generic scan:
Attachment 271295

Can I trust this temperature? Is this normal for SSD?
Attachment 271296

- - - Updated - - -

MemTest86 aborted test because of too many errors... Didn't even go for the second run for this time:
Attachment 271302
Attachment 271303
Attachment 271304

These were the Bios settings, including Turbo-Boost mode disabled, during all the previous tests:

Attachment 271305
Attachment 271306
Attachment 271307
Attachment 271308

- - - Updated - - -

Missed the MemTest html log:
Attachment 271320

Run HD Sentinel: (free or trial edition)
Hard Disk Sentinel - HDD health and temperature monitoring
Hard Disk Sentinel - HDD health and temperature monitoring
Post images of each of these tabs into the thread:
Overview tab
Temperature
SMART
Disk performance


Run Crystal Disk standard edition:
CrystalDiskInfo – Crystal Dew World
Post an image into the thread.


When replacing RAM:
a) Make sure all modules are on the motherboard QVL
b) Make sure that the SKU are identical
c) To benefit from dual channel capability of the motherboard some motherboard manufacturers require all modules to be paired (even number of modules)

HD Sentinel:
Overview:
Attachment 271323
Temperature:
Attachment 271324
SMART:
Attachment 271325
Disk Performance:
Attachment 271326
Quick Test:
Attachment 271327

CrystalDiskInfo:
Attachment 271328