BSOD Boot Loop... Save Me From Troubleshooting Hell

[Wilk]

Hello Everyone, 

 

I am new to the forum and joined so that I could turn to you, fine people of the internet, in helping me solve my BSOD. I will start by saying I read the pinned threads in this section, but I believe my situation makes it so that I cannot create a dump file.

 

I am experiencing consistent blue screen crashing with the stop code IRQL NOT LESS OR EQUAL when booting up my PC. The PC posts and briefly shows "preparing automatic recovery" before then showing the BSOD. This was a new PC I built myself last month with all new parts aside from the GPU. The PC worked for almost 2 weeks before I received the BSOD while using it and now I receive the BSOD every time on boot.

 

Parts List: https://pcpartpicker.com/list/stHhwz

 

Hear are the steps I have tried, I kept this brief, but I can provide more information if required.

• Booting to windows 10 from a USB drive. This results in the exact same BSOD crash as a normal boot, ruling out any driver related issues I would think?
• Ran Memtest86 overnight, 10 passes zero errors. 
• RMA'ed my GPU, also tried another known working GPU in the system. Same Issue
• Replaced motherboard, went from a MSI B550 board to the Asus one listed, this now gives me a q-code readout, but still the same BSOD on boot. Asus Q-code is B1. Mobo was updated to latest BIOS available.
• Tried removing my ssd entirely and booting to USB as well as booting to USB with a HDD installed instead. Same BSOD issue.

 

If anyone has any ideas I would love to hear them, obviously I have cleared CMOS, but there were no overclocks present at the time of the initial crash. I also have a short video of the process but the file size is too big to post.

 

Thanks

 

 

[AndrewTheFrenchMan]

Hi Wilk,

 

I'm sorry you gotta deal with this, here are some thoughts that came to mind and hopefully it will help, it sounds like the OS is trying to access an illegal memory address at startup or something similar, you could try this:
 

- Make sure the memory is well seated (maybe re-seat it) bu you probably already did this.

- Maybe try the system with different memory sticks, maybe 3200 mHz instead of 3600 mHz.

- Make sure you have all 16GB showing up in the BIOS (probably did this already too).

- Check the pins on your CPU and try it with another CPU to see if that is the issue.

- Maybe try a different OS, like Ubuntu, it's very easy to install and uninstall and you can check to see if that was the issue.

 

I'm not an expert so I could be completely wrong, but from what you described and already have done, this is what I would recommend.

 

[Wilk]

16 minutes ago, AndrewTheFrenchMan said:

Hi Wilk,

 

I'm sorry you gotta deal with this, here are some thoughts that came to mind and hopefully it will help, it sounds like the OS is trying to access an illegal memory address at startup or something similar, you could try this:
 

- Make sure the memory is well seated (maybe re-seat it) bu you probably already did this.

- Maybe try the system with different memory sticks, maybe 3200 mHz instead of 3600 mHz.

- Make sure you have all 16GB showing up in the BIOS (probably did this already too).

- Check the pins on your CPU and try it with another CPU to see if that is the issue.

- Maybe try a different OS, like Ubuntu, it's very easy to install and uninstall and you can check to see if that was the issue.

 

I'm not an expert so I could be completely wrong, but from what you described and already have done, this is what I would recommend.

 

Thanks for the suggestions, I have checked that the memory is reseated and shown in the BIOS. 

 

Unfortunately I do not have any additional memory or a CPU to try, I am trying to avoid waiting on another RMA that may or may not solve my issue, but it could certainly come to that. 

 

I will look into installing Ubuntu, Linux is outside of my experience, but at least it is something I can try before sending out my CPU. 

[AndrewTheFrenchMan]

5 minutes ago, Wilk said:

Thanks for the suggestions, I have checked that the memory is reseated and shown in the BIOS. 

 

Unfortunately I do not have any additional memory or a CPU to try, I am trying to avoid waiting on another RMA that may or may not solve my issue, but it could certainly come to that. 

 

I will look into installing Ubuntu, Linux is outside of my experience, but at least it is something I can try before sending out my CPU. 

OK, Ubuntu is very easy to install, it's just like windows but that was kind of a last resort thing, i do not have very high confidence that it will solve your issue, but I have seen random crap solve my issues in the past