[SOLVED] There isn't enough memory to create a ramdisk device.

Solitario · Jun 23, 2021

Hello everyone, after doing the Windows memory diagnostic I get the error in the title, I would like to know if a solution is possible. I already tried with the solutions that are on the net, but they do not work for me. I hope you can help me to solve this problem. Thank you very much in advance. Best regards.

axe0 · Jun 23, 2021

Did these problems also occur before you installed Windows 11? Windows 11 has officially not launched, is therefore not ready for customers and can be unstable.

Solitario · Jun 23, 2021

It happened with Windows 10 as well, as I can't start Windows without the xmp profile of the memories enabled.

Solitario · Jun 23, 2021

What I don't know is if it is a problem of Windows or of my ram memories.

axe0 · Jun 23, 2021

From the logs I noticed that one of your drives is having problems, likely just a file system problem that should be fixed with a chkdsk. I don't know which drive though.

Another thing is that the dump files are corrupted, in combination with the first screenshot this makes me believe that your RAM is faulty.

Solitario · Jun 23, 2021

And there is no way to fix this Windows error that I get after the memory check?

axe0 · Jun 23, 2021

The Windows error looks to be some sort of configuration issue with the pagefile, can you verify that the pagefile is managed by Windows?

Solitario · Jun 23, 2021

It was managed by Windows, but I modified it after verifying the ram memories, now it is like this.

axe0 · Jun 23, 2021

Let Windows manage the pagefile.

Did you get the Windows error before changing the pagefile settings?

Solitario · Jun 23, 2021

Yes, I received the error earlier.

Solitario · Jun 23, 2021

I have no memory marked as bad in this log.

Code:

C:\WINDOWS\system32>bcdedit /enum all

Firmware Boot Manager
---------------------
identifier              {fwbootmgr}
displayorder            {f9cd9f7e-d118-11eb-8490-806e6f6e6963}
                        {f9cd9f78-d118-11eb-8490-806e6f6e6963}
                        {f9cd9f79-d118-11eb-8490-806e6f6e6963}
                        {f9cd9f7a-d118-11eb-8490-806e6f6e6963}
                        {f9cd9f7b-d118-11eb-8490-806e6f6e6963}
                        {f9cd9f7c-d118-11eb-8490-806e6f6e6963}
                        {f9cd9f7d-d118-11eb-8490-806e6f6e6963}
timeout                 1

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  unknown
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {018c7c11-ce55-11eb-998a-e934f1de9331}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Firmware Application (101fffff)
-------------------------------
identifier              {f9cd9f78-d118-11eb-8490-806e6f6e6963}
path                    \EFI\BOOT\BOOTX64.EFI
description             UEFI OS

Firmware Application (101fffff)
-------------------------------
identifier              {f9cd9f79-d118-11eb-8490-806e6f6e6963}
description             INTEL SSDSCKKF180H6H

Firmware Application (101fffff)
-------------------------------
identifier              {f9cd9f7a-d118-11eb-8490-806e6f6e6963}
description             ST2000DM006-2DM164

Firmware Application (101fffff)
-------------------------------
identifier              {f9cd9f7b-d118-11eb-8490-806e6f6e6963}
description             Hitachi HUA723020ALA640

Firmware Application (101fffff)
-------------------------------
identifier              {f9cd9f7c-d118-11eb-8490-806e6f6e6963}
description             KINGSTON SUV400S37240G

Firmware Application (101fffff)
-------------------------------
identifier              {f9cd9f7d-d118-11eb-8490-806e6f6e6963}
description             WDC  WDS250G2B0A-00SM50

Firmware Application (101fffff)
-------------------------------
identifier              {f9cd9f7e-d118-11eb-8490-806e6f6e6963}
device                  partition=\Device\HarddiskVolume12
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description             Windows Boot Manager

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 10
locale                  en-US
loadoptions             DENABLE_INTEGRITY_CHECKS
inherit                 {bootloadersettings}
recoverysequence        {288b9b99-ce4d-11eb-846a-8552152950c9}
displaymessageoverride  Recovery
recoveryenabled         Yes
testsigning             No
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {018c7c11-ce55-11eb-998a-e934f1de9331}
nx                      OptIn
bootmenupolicy          Standard

Windows Boot Loader
-------------------
identifier              {288b9b99-ce4d-11eb-846a-8552152950c9}
device                  ramdisk=[\Device\HarddiskVolume11]\Recovery\WindowsRE\Winre.wim,{288b9b9a-ce4d-11eb-846a-8552152950c9}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[\Device\HarddiskVolume11]\Recovery\WindowsRE\Winre.wim,{288b9b9a-ce4d-11eb-846a-8552152950c9}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {2ec3fee7-5983-11eb-9c4a-2cf05d58804e}
device                  ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{2ec3fee8-5983-11eb-9c4a-2cf05d58804e}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  es-MX
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{2ec3fee8-5983-11eb-9c4a-2cf05d58804e}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Resume from Hibernate
---------------------
identifier              {018c7c11-ce55-11eb-998a-e934f1de9331}
device                  partition=C:
path                    \WINDOWS\system32\winresume.efi
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
recoverysequence        {288b9b99-ce4d-11eb-846a-8552152950c9}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
custom:21000026         partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=\Device\HarddiskVolume12
path                    \EFI\Microsoft\Boot\memtest.efi
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}
badmemoryaccess         Yes

EMS Settings
------------
identifier              {emssettings}
bootems                 No

Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Local

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

Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}

Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}

Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}

Device options
--------------
identifier              {288b9b9a-ce4d-11eb-846a-8552152950c9}
description             Windows Recovery
ramdisksdidevice        partition=\Device\HarddiskVolume11
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier              {2ec3fee8-5983-11eb-9c4a-2cf05d58804e}
description             Windows Recovery
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

C:\WINDOWS\system32>

x BlueRobot · Jun 23, 2021

The {badmemory} identifier only has values if the RAM supports ECC, otherwise it will always be empty. I wouldn't rely on it anyway.

There definitely appears to be some issue with your RAM or something similar; Win RE will mount the recovery .wmi file as a RAM disk, hence why it's complaining there isn't enough available RAM when it attempts to boot into the recovery environment.

Have you attempted to boot with one stick?

Solitario · Jun 23, 2021

I will try it now and let you know if I get the same error again.

Solitario · Jun 23, 2021

It is indeed a ram module that fails, I will have to use the warranty. Thank you both very much. Best regards.

Search

Search

[SOLVED] There isn't enough memory to create a ramdisk device.

Solitario

Well-known member

Attachments

axe0

Administrator,
BSOD Academy Instructor,
Security Analyst

Solitario

Well-known member

Solitario

Well-known member

axe0

Administrator,
BSOD Academy Instructor,
Security Analyst

Solitario

Well-known member

axe0

Administrator,
BSOD Academy Instructor,
Security Analyst

Solitario

Well-known member

axe0

Administrator,
BSOD Academy Instructor,
Security Analyst

Solitario

Well-known member

Solitario

Well-known member

x BlueRobot

Administrator

Solitario

Well-known member

Solitario

Well-known member

[SOLVED] There isn't enough memory to create a ramdisk device.

Well-known member

Attachments

Administrator, BSOD Academy Instructor, Security Analyst

Well-known member

Well-known member

Administrator, BSOD Academy Instructor, Security Analyst

Well-known member

Administrator, BSOD Academy Instructor, Security Analyst

Well-known member

Administrator, BSOD Academy Instructor, Security Analyst

Well-known member

Well-known member

Administrator

Well-known member

Well-known member

Administrator,
BSOD Academy Instructor,
Security Analyst

Administrator,
BSOD Academy Instructor,
Security Analyst

Administrator,
BSOD Academy Instructor,
Security Analyst

Administrator,
BSOD Academy Instructor,
Security Analyst