It could be a ram module starting to get bad. Make a bootable usb with memtest and do "a bit" of cycles to test
Alternative would be to remove the ram, install just one in slot 1, and see if it installs. If yes, you could redo the test with the other modules until finding the one causing the bsod
Thanks for the suggestion Mazzinia, I did just that and the memory is fine. I have actually tried 3 different sticks of RAM and the issue persists.
It does seem like it would be a RAM issue but I've used sticks from a known working machine as well as two brand-new modules I got from NewEgg and the MOBO is brand new, literally had to take it out of Manufacturer mode. Its all just so baffling...
At this point the only thing that hasnt been replaced in this system is the CPU so by order of elimination, it must be an issue with the CPU... which would explain getting this error with the original build and carrying over even on a new MOBO, new RAM and new SSD. I don't have any extra CPUs laying around so this computer is going to be parted out, I'm not going to spend any more time on it.
Thanks for all your suggestions, I guess I needed to hear someone else say it could be a CPU issue, I couldnt bring myself to admit it, haha!
mazzinia_
6 Professor
•
1.5K Posts
0
March 4th, 2022 09:00
It could be a ram module starting to get bad. Make a bootable usb with memtest and do "a bit" of cycles to test
Alternative would be to remove the ram, install just one in slot 1, and see if it installs. If yes, you could redo the test with the other modules until finding the one causing the bsod
TechManDave
3 Posts
0
March 4th, 2022 13:00
Thanks for the suggestion Mazzinia, I did just that and the memory is fine. I have actually tried 3 different sticks of RAM and the issue persists.
It does seem like it would be a RAM issue but I've used sticks from a known working machine as well as two brand-new modules I got from NewEgg and the MOBO is brand new, literally had to take it out of Manufacturer mode. Its all just so baffling...
mazzinia_
6 Professor
•
1.5K Posts
0
March 5th, 2022 07:00
Do you have any spare videocard, to try swapping just in case ?
And it could be a defected mb, with issues with one ram slot .... or it could have one (or more) pin of the cpu socket slightly bent
TechManDave
3 Posts
0
March 5th, 2022 10:00
At this point the only thing that hasnt been replaced in this system is the CPU so by order of elimination, it must be an issue with the CPU... which would explain getting this error with the original build and carrying over even on a new MOBO, new RAM and new SSD. I don't have any extra CPUs laying around so this computer is going to be parted out, I'm not going to spend any more time on it.
Thanks for all your suggestions, I guess I needed to hear someone else say it could be a CPU issue, I couldnt bring myself to admit it, haha!