Question PC has various BSODS constantly

[serughujlo]

So like the title says, my PC has various BSOD's all the time. I have reinstalled windows multiple times. I have tried fixing drivers and everything. Every time I reinstall windows and run sfc /scannow it always returns at least one corrupted file. Once it was a bthmodem.sys file and another time it was some other file. Regardless, there is always some corruption on every fresh install of windows. I am at my wits end. It is a PC built by me and only a year old with top of the top of the line hardware (5900x, 4090, 32gb ram). I reinstalled windows 11 today and am just stuck in a bootloop now with INACCESSIBLE_BOOT_DEVICE. I am running memtest86 right now so will update with that but just wondering if anyone else can suggest what to do. Also, when my computer was running and I gamed, my system had less performance than that of similar or the same system by a factor of 10-15% consistently.

I will list out the BSODs that I have encountered from memory:

IRQL_NOT_LESS_OR_EQUAL
NTFS_FILE_SYSTEM
PAGE_FAULT_IN_NONPAGED_AREA
IRQL_UNEXPECTED_VALUE
WHEA_UNCORRECTABLE_ERROR
WHEA_INTERNAL_ERROR
MEMORY_MANAGEMENT
UNEXPECTED_KERNEL_MODE_TRAP


Full System Specs:

Motherboard: Asus Strix X570-F
CPU: Ryzen 9 5900X
Ram: HyperX 32GB 3600MHz DDR4
GPU: Gigabyte Gaming OC 4090 24GB
PSU: Corsair RM850X
SSD: Kingston 240gb (boot drive)
NVME 1: 1TB Samsung 980 Pro Gen 4
NVME 2: 2TB Kingston Gen 4
HDD: Western Digital 1TB WD10EZEX 7200rpm

 

[Roland Of Gilead]

So like the title says, my PC has various BSOD's all the time. I have reinstalled windows multiple times. I have tried fixing drivers and everything. Every time I reinstall windows and run sfc /scannow it always returns at least one corrupted file. Once it was a bthmodem.sys file and another time it was some other file. Regardless, there is always some corruption on every fresh install of windows. I am at my wits end. It is a PC built by me and only a year old with top of the top of the line hardware (5900x, 4090, 32gb ram). I reinstalled windows 11 today and am just stuck in a bootloop now with INACCESSIBLE_BOOT_DEVICE. I am running memtest86 right now so will update with that but just wondering if anyone else can suggest what to do.

I will list out the BSODs that I have encountered from memory:

IRQL_NOT_LESS_OR_EQUAL
NTFS_FILE_SYSTEM
PAGE_FAULT_IN_NONPAGED_AREA
IRQL_UNEXPECTED_VALUE
WHEA_UNCORRECTABLE_ERROR
WHEA_INTERNAL_ERROR
MEMORY_MANAGEMENT
UNEXPECTED_KERNEL_MODE_TRAP

Hey there,

List your full PC specs, including motherboard and PSU and storage specially.

First guess, is whatever drive you're using for the install is damaged/dead or dying.

 

[serughujlo]

Hey there,

List your full PC specs, including motherboard and PSU and storage specially.

First guess, is whatever drive you're using for the install is damaged/dead or dying.

I have updated my post with detailed specs. Also I am starting to suspect that the Kingston 240gb ssd is the root cause of all this. I will reinstall windows with an ISO onto my 1tb Samsung drive when I reimage to fix this bootloop.

 

[Roland Of Gilead]

Have you only used the Kingston SSD for install? Or have you tried the other drives?

Cna you test with Crystaldiskmark/info to look for the drive health?

 

[serughujlo]

Have you only used the Kingston SSD for install? Or have you tried the other drives?

Cna you test with Crystaldiskmark/info to look for the drive health?

I have only tried the kingston SSD for install which is stupid to say but I didn't expect such a simple component to be broken so new but who knows? Maybe it is broken. I can't even get into windows right now because I reinstalled windows recently and it booted into windows once, I went to restart and the computer gave a bsod of INACCESSIBLE_BOOT_DEVICE and has been in a boot loop since. I made a bootable memtest86 and am running that and will reinstall windows 11 from a usb afterwards into a different storage device.

 

[Roland Of Gilead]

I have only tried the kingston SSD for install which is stupid to say but I didn't expect such a simple component to be broken so new but who knows? Maybe it is broken. I can't even get into windows right now because I reinstalled windows recently and it booted into windows once, I went to restart and the computer gave a bsod of INACCESSIBLE_BOOT_DEVICE and has been in a boot loop since. I made a bootable memtest86 and am running that and will reinstall windows 11 from a usb afterwards into a different storage device.

Ah, that's a pity. Yeah, sometimes, but not often a new device can fail. Typically failure rates are pretty low. Given it's new, I'd RMA it, and get it out of the way. If one of your other drives doesn't have anything on it that you could use that as the boot drive for the time being. Or, make a back up of your OS drive, and when you get a replacement but the restore the back up.

Naturally though, I think you want a quicker solution. By trying another drive, you know for sure it's the 240gb is the problem.

 

[serughujlo]

Ah, that's a pity. Yeah, sometimes, but not often a new device can fail. Typically failure rates are pretty low. Given it's new, I'd RMA it, and get it out of the way. If one of your other drives doesn't have anything on it that you could use that as the boot drive for the time being. Or, make a back up of your OS drive, and when you get a replacement but the restore the back up.

Naturally though, I think you want a quicker solution. By trying another drive, you know for sure it's the 240gb is the problem.

I will do all this when I get the chance to which will be a fair few hours from now. I will update afterwards but in the meanwhile I guess all I can really ask is; can a failing SSD really explain all the issues and bad performance in games?

 

[Roland Of Gilead]

Very possible and maybe likely. Testing with another drive, will help you narrow it down.

In game loading time, yes, a bad SSD would cause issues.

 

[serughujlo]

Very possible and maybe likely. Testing with another drive, will help you narrow it down.

In game loading time, yes, a bad SSD would cause issues.

Wow. Just wow. I finally got windows 10 installed with much difficulty and installed crystaldiskinfo. BRO ITS HEALTH IS 39% NO WONDER UGHHH. I'm genuinely swearing off kingston drives forever now onwards.

Now I still have a problem. So I had an install of windows 11 which I mentioned I reimaged yesterday and it got stuck in a boot loop with that INACCESSIBLE_BOOT_DEVICE error. Now I have installed windows 10 in my 1TB 980 Pro Samsung Drive. However, if I disconnect my kingston SSD the bios doesn't recognise the Samsung 1TB nvme as a bootable windows drive. To boot into windows 10 on this samsung drive I have to first boot up, go into a selection screen from the kingston drive to boot into either windows 10 or 11 and only then does it boot to the samsung drive. What do I do now? How do I get the samsung drive to boot? It doesn't show up in the bios as a bootable option at all, only the kingston ssd does.

 

[Roland Of Gilead]

Wow. Just wow. I finally got windows 10 installed with much difficulty and installed crystaldiskinfo. BRO ITS HEALTH IS 39% NO WONDER UGHHH. I'm genuinely swearing off kingston drives forever now onwards.

Okay, that makes sense, and backs up that it's this specific driver causing the issue.

Now I have installed windows 10 in my 1TB 980 Pro Samsung Drive. However, if I disconnect my kingston SSD the bios doesn't recognise the Samsung 1TB nvme as a bootable windows drive. To boot into windows 10 on this samsung drive I have to first boot up, go into a selection screen from the kingston drive to boot into either windows 10 or 11 and only then does it boot to the samsung drive. What do I do now? How do I get the samsung drive to boot? It doesn't show up in the bios as a bootable option at all, only the kingston ssd does.

Ah, yes. My apologies, I should have made it more clear. When you left the Kinston in (with OS on it), and then installed the OS on the 980, the MBR (master boot record) will then remain on the Kinsgton. So the bios looks for this device to boot first. Ideally you should have disconnected all the other drives, do the install on the 980 again, as this sets the MBR on the 980. Once done, then you reconnect the other drives, and you can then access/format them as needed.