Question BSOD during Windows 11 Setup ?

Dec 18, 2023
10
0
10
What am I missing?

I have a Corsair Vengeance I7400 Gaming PC that is throwing various BSOD during Windows 11 installation process.

I have a new SSD, two new sticks of DDR5 RAM, and a brand new spare RTX 3050 in an attempt to build the machine around whatever hardware issue was occurring.

But unless it’s a driver, it’s got to be the motherboard based on having the same behavior with all these new components. It almost always crashes after the first windows 11 reboot when installing on USB drive onto blank drive.
 
What is the motherboard model?

What is the current motherboard BIOS version?

What is the exact model of each of the memory kits and did ALL of the memory in each kit come together in one package or are there multiple DIMMs that were purchased separately that you are trying to use together, even if they are the same part number?

Which DIMM slots, exactly, are you populating? Have you tried with only a single DIMM in the A2 slot?

Have you pulled the CPU to make absolutely certain there is not even ONE even marginally bent or deviated pin on the motherboard?

Do you have any issues at all if you are not trying to install Windows? In the BIOS?

It might also be a good idea to create a bootable Linux distro on another machine and try booting that to see if it's actually a hardware issue.
 
  • Like
Reactions: Roland Of Gilead
What is the motherboard model?

What is the current motherboard BIOS version?

What is the exact model of each of the memory kits and did ALL of the memory in each kit come together in one package or are there multiple DIMMs that were purchased separately that you are trying to use together, even if they are the same part number?

Which DIMM slots, exactly, are you populating? Have you tried with only a single DIMM in the A2 slot?

Have you pulled the CPU to make absolutely certain there is not even ONE even marginally bent or deviated pin on the motherboard?

Do you have any issues at all if you are not trying to install Windows? In the BIOS?

It might also be a good idea to create a bootable Linux distro on another machine and try booting that to see if it's actually a hardware issue.
What is the motherboard model?

What is the current motherboard BIOS version?

What is the exact model of each of the memory kits and did ALL of the memory in each kit come together in one package or are there multiple DIMMs that were purchased separately that you are trying to use together, even if they are the same part number?

Which DIMM slots, exactly, are you populating? Have you tried with only a single DIMM in the A2 slot?

Have you pulled the CPU to make absolutely certain there is not even ONE even marginally bent or deviated pin on the motherboard?

Do you have any issues at all if you are not trying to install Windows? In the BIOS?

It might also be a good idea to create a bootable Linux distro on another machine and try booting that to see if it's actually a hardware issue.
MSI B760-VC WI-FI (MS-7D98)

I updated the BIOS earlier today to the most recent version (E7D98IMS.B60)

I haven’t touched the CPU, ever. Would pins get bent without ever being unlatched?

None of the BIOS component tests have revealed any failures or issues of any kind.

Good idea with the Linux install test. I will try that.
 
What is the motherboard model?

What is the current motherboard BIOS version?

What is the exact model of each of the memory kits and did ALL of the memory in each kit come together in one package or are there multiple DIMMs that were purchased separately that you are trying to use together, even if they are the same part number?

Which DIMM slots, exactly, are you populating? Have you tried with only a single DIMM in the A2 slot?

Have you pulled the CPU to make absolutely certain there is not even ONE even marginally bent or deviated pin on the motherboard?

Do you have any issues at all if you are not trying to install Windows? In the BIOS?

It might also be a good idea to create a bootable Linux distro on another machine and try booting that to see if it's actually a hardware issue.
Image1
During the Ubuntu install, things appear to get stuck around here (see image)
 
You shouldn't need to "install" Ubuntu. It should run from the flash drive you put it on so long as you create a bootable distro.
When booting, it gives me a few options
Ubuntu
Ubuntu (graphics safe mode or something similar)
Other options
Etc
Etc


The machine goes through a “checking disks” exercise, where it is stuck for a couple minutes on 33% checking ./pool/restricted/n/Nvidia-kernel-source-525_525.85.05-0ubtuntu0.20.04.1_amd64.deb

A couple times I had errors.

Once, it got to a screen where it said:

“Try Ubuntu” OR “Install Ubuntu”

I chose install because that made the most sense at the time. The install froze in the middle.

I will click “Try” next time and see what happens.
 
This time I clicked “Try Ubuntu”.

The system immediately froze where I saw my mouse pointer but the neither the mouse or keyboard was responding to num lock or mouse movement.
 
So, aside from the motherboard, which we know, what are the rest of the specifications?

CPU, exact power supply model, memory kit model, storage devices, etc.?

How old is this system and is it still under warranty, or that ship has sailed?

Was it working properly for a long period of time and then suddenly began not working properly, or has it never worked properly?
 
So, aside from the motherboard, which we know, what are the rest of the specifications?

CPU, exact power supply model, memory kit model, storage devices, etc.?

How old is this system and is it still under warranty, or that ship has sailed?

Was it working properly for a long period of time and then suddenly began not working properly, or has it never worked properly?
This is a Corsair Vengeance PC.

Unfortunately, this has taken a life of its own. I could send it to them but they said I’d be out of a machine for 2-4 weeks which I couldn’t handle (at the time)

It worked fine for a while but started to exhibit a behavior where it would bluescreen and would need reinstalling windows or would keep bluescreening regularly. The errors indicated it may have been the video card, which I replaced, and it worked fine for around 10 days. But I think that was a red herring and sheer luck. I obtained additional RAM and another SSD to avoid sending it in. Along with my additional video card I figured I could isolate the issue and as long as it wasn’t the motherboard, I could avoid sending it in.

I’ve made a mess of the SSDs because eventually the BSOD was occurring in the midst of Windows installs. But the machine freezes now while running Ubuntu and no SSDs even in it.

But it’s hard to tell what isn’t functioning because of my stupidity/ignorance, and what’s not functioning because it’s broken.

For instance, I can get Ubuntu to run (but freeze) on the preloaded RAM, while the new RAM sticks seem to throw Ubuntu errors.

I was hoping to find someone to help me isolate the issue but I bet I have more than one at this point.

Old RAM is Vengeance DDR5 5600MT/s
New RAM is Vengeance DDR5 6000MT/s

Old GPU is Nvidia 3070
New GPU is Nvidia 3050 (I realize it’s inferior but just trying to isolate the problem.)

Old SSD MP1000
New SSD WD Black 500GB

I can’t make sense of the Ubuntu errors because they are different so frequently.

Power supply is Corsair RM750e
 
This is a Corsair Vengeance PC.

Unfortunately, this has taken a life of its own. I could send it to them but they said I’d be out of a machine for 2-4 weeks which I couldn’t handle (at the time)

It worked fine for a while but started to exhibit a behavior where it would bluescreen and would need reinstalling windows or would keep bluescreening regularly. The errors indicated it may have been the video card, which I replaced, and it worked fine for around 10 days. But I think that was a red herring and sheer luck. I obtained additional RAM and another SSD to avoid sending it in. Along with my additional video card I figured I could isolate the issue and as long as it wasn’t the motherboard, I could avoid sending it in.

I’ve made a mess of the SSDs because eventually the BSOD was occurring in the midst of Windows installs. But the machine freezes now while running Ubuntu and no SSDs even in it.

But it’s hard to tell what isn’t functioning because of my stupidity/ignorance, and what’s not functioning because it’s broken.

For instance, I can get Ubuntu to run (but freeze) on the preloaded RAM, while the new RAM sticks seem to throw Ubuntu errors.

I was hoping to find someone to help me isolate the issue but I bet I have more than one at this point.

Old RAM is Vengeance DDR5 5600MT/s
New RAM is Vengeance DDR5 6000MT/s

Old GPU is Nvidia 3070
New GPU is Nvidia 3050 (I realize it’s inferior but just trying to isolate the problem.)

Old SSD MP1000
New SSD WD Black 500GB

I can’t make sense of the Ubuntu errors because they are different so frequently.

Power supply is Corsair RM750e
Here’s the other thing. One one stick of RAM with no SSD, I am able to get Ubuntu running, but only when I add the “nomodeset” flag in the parameters each time I boot. I’m going to let it run in this mode and gather any system errors (which I think is highly likely).

Without the “nomodeset” flag, it freezes on the Ubuntu splash screen.
 
This is a Corsair Vengeance PC.

Unfortunately, this has taken a life of its own. I could send it to them but they said I’d be out of a machine for 2-4 weeks which I couldn’t handle (at the time)

And it has ALREADY not been working worth a crap, for how long?

The point being, stop it. Send it back. Get it RIGHT. There is NO reason YOU should have to deal with this on a system that is under warranty unless YOU DID SOMETHING that caused it. If not, then quit quibbling and send it back. Let them fix the problem that likely has nothing to do with you in the first place. Back up anything important as far as specific files for your installed programs that you've invested time in, and your game files, if any. Then figure out another way to get by for the two weeks. Use your phone or another machine if need be. There is NO reason for you to be dealing with this if it's a hardware problem or something related to the software installations THEY did.

If you know that it is YOU, or something YOU did, then we can just disregard this, maybe, still might be worth doing, and move on. But honestly, if you can get them to make it right it would be foolish to not do so.
 
Last edited: