Windows 10: Could someone evaluate this memory dump for me? Trying to install 20H2 and keep getting BSOD.

Microsoft R Windows Debugger Version 10.0.21349.1004 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [\\isilonbc\Tech\DUMP FILES\TERXAM11\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: Windows 10 Kernel Version 19041 MP 4 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff807`1de00000 PsLoadedModuleList = 0xfffff8

:)

 

Evaluate a Dump File from Device Verifier

Hi,

I have copied and zipped a dump file from Device Verifier after struggling with several stop codes (BSOD). Can someone here look at this file and evaluate for me?

 

Frequent Memory Dumps

Thank you for your response.

I have uninstalled cccleANER as suggested.

I have turned off real time scanning on McAfee Total Protection.

A couple of questions:

1. How can I check that I am not getting Memory dump files anymore? - they were detected by cccleANER
2. How can I check that I'm not getting interference between Malwarebytes and McAfee? - i.e. I need to know what level of RAM?
   

Thank you for your assistance

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.