Cannot launch Windows installation due to blue screen error.
Cannot launch Windows installation due to blue screen error.
Attempting to set up Windows 11 Pro with the specified hardware is challenging. The system shows persistent boot issues, frequent blue screens after a few minutes, and recurring errors during Windows installation scans. I've reset the BIOS, disabled XMP/auto overclock, used only one RAM stick (and both), and tried memory testing. The drive appears functional but the OS fails to initialize properly. Any suggestions would be greatly appreciated. Also, the update process gets stuck even after clearing cache.
Oops, I missed that in the first message. The latest bios are available on MSI's website.
Is the 980 Pro still available? Did it come into stock around launch and comes from a different configuration? The 980 Pros released with updates if I recall correctly had a problematic firmware that affected drives. A fix was issued months later, so a brand new unit should include the patch unless it's older models. Are you using a brand-new Windows installer on a verified USB drive, or is it outdated? Or could there be an issue with the installer itself or your SSD needing a firmware update or replacement?
I’d confirm the firmware is current for your 980 Pro, run CrystalDiskInfo and CrystalDiskMark to verify performance, and test with a cheap flash drive plus a fresh Windows 11 installer. Just to be certain. Also, ensure the drive is connected via a motherboard USB port instead of your case’s USB ports if you’ve used the latter before.
Apologies for the delayed response. I've successfully fixed Windows without bluescreens, but one reset has come back. The status_access_violation error still appears in all major browsers, forcing me to reload and restart whatever I was doing. I’m unsure whether to create a new thread for this issue. Also, the bluescreen problem is gone—I no longer need to buy a new drive. Now I have a 990 Pro that’s running perfectly without any issues. I’ll share updates on the 980 Pro once I run several tests on it.
Enable XMP in BIOS, then turn it off and check if the problem resolves. A friend experienced this issue because his memory had XMP enabled, which caused problems. He found his motherboard kit wasn’t listed in the QVL, so he returned it for one that was available. This seems to be a software-related problem, though since it affects multiple browsers, hardware might be involved.