F5F Stay Refreshed Software Operating Systems Windows memory management BSOD after configuring dual-boot with Linux

Windows memory management BSOD after configuring dual-boot with Linux

Windows memory management BSOD after configuring dual-boot with Linux

A
AwesomeBamboo
Member
51
12-08-2016, 01:25 AM
#1
I set up a dual-boot environment with Linux and Windows 10, using Elementary OS 5.1. After allocating space, I faced issues where I couldn’t switch back to Windows after a short period. The system would briefly display the Windows logo before crashing with a memory management error. Even when booting from USB or in Safe Mode, it failed to start properly. RAM tests didn’t reveal problems, and Linux continued functioning normally. I’m unsure if hardware issues like damaged RAM are the cause, but I’m hoping there’s a way to restore my Windows installation.
A
AwesomeBamboo
12-08-2016, 01:25 AM #1

I set up a dual-boot environment with Linux and Windows 10, using Elementary OS 5.1. After allocating space, I faced issues where I couldn’t switch back to Windows after a short period. The system would briefly display the Windows logo before crashing with a memory management error. Even when booting from USB or in Safe Mode, it failed to start properly. RAM tests didn’t reveal problems, and Linux continued functioning normally. I’m unsure if hardware issues like damaged RAM are the cause, but I’m hoping there’s a way to restore my Windows installation.

O
OnesieLover
Member
60
12-08-2016, 05:22 AM
#2
Did you check if GRUB included memtest and run it?
O
OnesieLover
12-08-2016, 05:22 AM #2

Did you check if GRUB included memtest and run it?

P
PowergirlA
Member
229
12-08-2016, 08:10 AM
#3
No, I didn't... I didn't realize it existed, so I went through GRUB to check for something similar but couldn't locate it. I'm going to try again... It seems I might have been mistaken.
P
PowergirlA
12-08-2016, 08:10 AM #3

No, I didn't... I didn't realize it existed, so I went through GRUB to check for something similar but couldn't locate it. I'm going to try again... It seems I might have been mistaken.

Z
zubz786
Member
62
12-08-2016, 10:04 AM
#4
Nope, can't find it... There isn't a command for it, but i guess i can just boot in to Linux and do a memtest either way...
Z
zubz786
12-08-2016, 10:04 AM #4

Nope, can't find it... There isn't a command for it, but i guess i can just boot in to Linux and do a memtest either way...

S
Shareizard
Junior Member
2
12-14-2016, 12:09 PM
#5
Yes, your system has a grub menu ready to choose between Linux or Windows, and it also includes a MemTestEntry tool.
S
Shareizard
12-14-2016, 12:09 PM #5

Yes, your system has a grub menu ready to choose between Linux or Windows, and it also includes a MemTestEntry tool.

C
Cadariou
Posting Freak
835
12-14-2016, 02:00 PM
#6
I've just installed it, that's all I meant by "I can't just boot into Linux and run a memtest either way." Right now I'm doing the test.
C
Cadariou
12-14-2016, 02:00 PM #6

I've just installed it, that's all I meant by "I can't just boot into Linux and run a memtest either way." Right now I'm doing the test.

T
TomBarty
Member
175
12-15-2016, 06:58 PM
#7
Performed several mem tests repeatedly, yet each time reported clean results while Windows fails to start and displays the warning.
T
TomBarty
12-15-2016, 06:58 PM #7

Performed several mem tests repeatedly, yet each time reported clean results while Windows fails to start and displays the warning.

B
Broflash
Senior Member
740
12-29-2016, 04:29 AM
#8
Just checked—no replies yet. Removed the old partition and created a fresh one. Restarted the setup process, and everything ran smoothly this time. Probably fixed the issue, though it still puzzled me about the crash during installation. The problem seems to be a corrupted partition, but why did that affect the installer too?
B
Broflash
12-29-2016, 04:29 AM #8

Just checked—no replies yet. Removed the old partition and created a fresh one. Restarted the setup process, and everything ran smoothly this time. Probably fixed the issue, though it still puzzled me about the crash during installation. The problem seems to be a corrupted partition, but why did that affect the installer too?