BSOD MEMORY_MANAGEMENT once or twice a week

Good evening,

My name is David, I hope you're all fine.

Since I've built my new computer back in November I've been having BSOD in Windows with the error MEMORY_MANAGEMENT.

This error happens once or twice a week. It happens while doing desktop work, it never happened while playing games.

I've been trying a lot of things, and of course, CPU Tests, Memory Tests (Windows Memory Diagnostic), SSD Tests, disconnect and connect again all y devices and all seems fine.

Could you help me in some way? I'm desperate, I don't know what else to try...

Here you'll find all the data and minidumps as instructed:

GRENYESPC-(2020-03-29_21-20-31).zip - Google Drive

Thank you very much in advance.

The logs were in a foreign language and could not be scanned.

Please change the default language to English and upload a new V2:

https://www.tenforums.com/tutorials/...dows-10-a.html
Change Display Language in Windows 10

Thank you zbook!

Here a new V2 in English GRENYESPC-(2020-03-30_00-08-35).zip - Google Drive

For all steps / tests please post images into the thread:

Take Screenshot in Windows 10

How to Upload and Post Screenshots and Files at Ten Forums

Indicate whether Windows driver verifier had recently been used.



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

13) Make sure that there is no over clocking while troubleshooting.

14) To ensure that there are no improper bios settings please reset the bios

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computer’s CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow
3 Easy Ways to Clear CMOS (Reset BIOS)
How to Clear CMOS (AKA Reset BIOS Settings)

15) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

16) 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.

17) Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
Disk Management - How to Post a Screenshot of


18) 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


19) 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

20) These tests / steps can be performed overnight:
a) Memtest86
b) HD Tune full error scan
c) Sea Tools for Windows long generic test

Hello zbook,

While I was waiting for response I've tried Memtest86. Four passes and in the 2nd pass started the errors, while Windows Memory Diagnostic always shows no errors.

I've stopped at 3rd pass with error count 222 and tried to disable XMP from BIOS, just to try something while waiting.

After 4 passes Memtest86 ended with error count 0. No errors. So maybe this could be the culprit?

I'll wait for your response before doing all the points you told me just in case you want to change them.

Thank you again very much for all your help and time.

Please complete the steps in the earlier post to tune up the computer.

The computer stability / instability can be monitored during the next few days.
Then repeat RAM testing.
Please post images and text reports into the thread.

Ok, I'll do. With Xmp enabled or disabled? Thanks again

Please disable xmp.

Hi, points 1 to 12:

Code:

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

C:\Users\david>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.

C:\Users\david>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.752

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\Users\david>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.752

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Users\david>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.

C:\Users\david>chkdsk /scan
The type of the file system is NTFS.

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

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

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

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

 878454783 KB total disk space.
 475193420 KB in 609978 files.
    340828 KB in 107143 indexes.
         0 KB in bad sectors.
   1293259 KB in use by the system.
     65536 KB occupied by the log file.
 401627276 KB available on disk.

      4096 bytes in each allocation unit.
 219613695 total allocation units on disk.
 100406819 allocation units available on disk.

C:\Users\david>wmic recoveros set autoreboot = false
Updating property(s) of '\\GRENYESPC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.

C:\Users\david>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\GRENYESPC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.

C:\Users\david>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\Users\david>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\Users\david>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier              {badmemory}
badmemorylist           0x7ff78c

C:\Users\david>

Windows had found bad memory addresses and blocked them.