BSOD I need to boot to dos (not safe mode dos that causes BSOD)

Ok so I accidentally decided to set my max memory in windows msconfig to 0. Anyhow I know how to fix it (if I could get to dos), but I can’t get to dos since the only option is safe mode dos which loads the boot file and says 0 memory = BSOD.

I don’t have a dvd drive. So my only choice is usb (I can’t believe it’s so hard to get a computer to load to msdos. I mean come on I used to boot to dos from my 5 1/4 floppy before OS existed. ) anyhow, my 2other computers in the house are laptops that run windows 10.

I have a windows 10 retail dvd that I’m guessing would get me to dos prompt but again no dvd drive.

Is their a way to make a windows 7 repair usb without access to windows 7? If not what is the easiest way I can get this computer to boot to dos?

After getting to dos all I need to do is type: bcdedit /deletevalue identifier truncatememory so I can use my computer again

Welcome to the forum true MS-DOS is no use as it won't read NTFS disks there are lots of free boot disk/USB/floppy on boot disk.com

Hi

then from a command prompt
You can always open a command prompt during install by pressing Shift+F10

bcdedit/deletevalue {default} truncatememory


Roy

Thanks for all the replies guys. I will try some stuff and get back to you. I’m wondering if Ctrl + f10 will work while in windows repair. That’s the only thing that loads. Then it says it fixed something ad gonna retry loading windows in an infinite loop of course since it won’t fix max memory. I’m seriously floored at my stupidity (I was just thinking it was a box to say use max memory). But I’m even more floored that windows let’s you set max memory to anything less then what it would need to boot! I mean come in, a warning screen atleast? Lol

Ok odd. I didn’t get an option yesterday for command prompt while in advanced options in the repair windows screen but today when I booted up it searched for problems as usual and then said problem can’t be fixed and one of the reasons listed was corrupt registry. I sure hope that didn’t happen for real during the reboots or it trying to repair itself. Anyhow now command prompt is an option in their and works. So here’s to praying.... lol

Ok so I rand /bcdedit and it showed what I expected:

Truncatememory = 0x10000000

So I typed /bcdedit deletevalue 0x10000000 truncatememory

It said the identifier was incorrect.

So I did what Roy(touchwood) said above: bcdedit/deletevalue {default} truncatememory

It said successful, I checked /bcdedit and the truncatememory field was completely gone. So I closed msdos window, clicked restart computer and it booted right up no issues, in fact it booted way faster then normal lol.

Thanks for the help everyone!