Drive issue, or is it new GPU? Flummoxed

NickTheBiz

NickTheBiz

NickTheBiz

Associate
Joined
29 Apr 2015
Posts
313
Hey guys, apologies for the sounding board post.

My 3060 died recently and while it's going through the returns process, I've got a 3060Ti. Had it a month and had a few problems. Initially I had some BSOD but after upgrading to the latest Nvidia drivers, it seemed fine.

A week or so after the majority of the time I turn the PC on, it says it can't find a boot device and needs to reboot. Both my drives are listed in the bios without issues and thus eventually after a few reboots, power cycles, it will boot up. Thereafter, generally no problems other than an occasional BSOD, which feels quite simply like the hard drive as simply become unavailable/stopped working.

I've checked all connections, reseated things ok. When operational, I've stress tested the machine, ran the Samsung drive check... all with no issues, hence I'm torn on what to do next. Wait for the 3060 replacement, go back to that card and see if that's fine and put it down to some sort of 3060Ti conflict with the mobo/drive? Or is the Samsung drive just intermittently faulty?

Any advice/thoughts most appreciated and welcome.




Kit:
Ryzen 5 - 3600
ASUS - ROG STRIX B450-F GAMING AM4 Motherboard
Kingston HyperX Fury 16GB (2x8GB) DDR4 PC4-25600C16 3200MHz Dual Channel Kit (HX432C16FB3K2/16)
Lian-Li O11 Mini Midi-Tower Case - White
NZXT Kraken x63 280
Corsair SF600
Zotac RTX 3060Ti
Samsung 980-Pro vNAND 500GB (OS)
P2 M.2 2280 Crucial 2TB Drive (Data)
 
NickTheBiz said:
Hey guys, apologies for the sounding board post.

My 3060 died recently and while it's going through the returns process, I've got a 3060Ti. Had it a month and had a few problems. Initially I had some BSOD but after upgrading to the latest Nvidia drivers, it seemed fine.

A week or so after the majority of the time I turn the PC on, it says it can't find a boot device and needs to reboot. Both my drives are listed in the bios without issues and thus eventually after a few reboots, power cycles, it will boot up. Thereafter, generally no problems other than an occasional BSOD, which feels quite simply like the hard drive as simply become unavailable/stopped working.

I've checked all connections, reseated things ok. When operational, I've stress tested the machine, ran the Samsung drive check... all with no issues, hence I'm torn on what to do next. Wait for the 3060 replacement, go back to that card and see if that's fine and put it down to some sort of 3060Ti conflict with the mobo/drive? Or is the Samsung drive just intermittently faulty?

Any advice/thoughts most appreciated and welcome.




Kit:
Ryzen 5 - 3600
ASUS - ROG STRIX B450-F GAMING AM4 Motherboard
Kingston HyperX Fury 16GB (2x8GB) DDR4 PC4-25600C16 3200MHz Dual Channel Kit (HX432C16FB3K2/16)
Lian-Li O11 Mini Midi-Tower Case - White
NZXT Kraken x63 280
Corsair SF600
Zotac RTX 3060Ti
Samsung 980-Pro vNAND 500GB (OS)
P2 M.2 2280 Crucial 2TB Drive (Data)
Click to expand...

I had a very similar experience a week ago after just rebooting my machine and no hardware changes. I'm starting to think something has changed with the Windows bootloader in a recent update. Maybe I'm just reading into things with a sample size of 2 - but this could also be a software issue.
 
3060Ti might use a little more power than the 3060 - could the PSU be marginal?

Cold boots will be slightly more intensive power wise than warm reboots, as components get "inrush current"
 
Armageus said:
3060Ti might use a little more power than the 3060 - could the PSU be marginal?

Cold boots will be slightly more intensive power wise than warm reboots, as components get "inrush current"
Click to expand...

Cheers, I had thought of that, but discounted it as I didn't think the symptoms were typical of low power. Do you think they are then?
 
NickTheBiz said:
Cheers, I had thought of that, but discounted it as I didn't think the symptoms were typical of low power. Do you think they are then?
Click to expand...

Probably not as low power issues would normally be under load rather than at boot.

It's possible the PSU is failing, or the rails are not stabilising quickly enough at cold boot though (although again you would have expected it to do the same with the old card)

If you've got another PSU handy, it'd be worth a try to rule out.
 
Is Reliability history showing anything?

Could also move GPU to different slot to change variables.
As problem seems to have started after GPU dying, who knows if it did something to slot.
And definitely reseat DIMMs if you haven't done that.
Just in case you nudged one slightly while changing GPU.

Could also swap M.2 slots.
 
EsaT said:
Is Reliability history showing anything?

Could also move GPU to different slot to change variables.
As problem seems to have started after GPU dying, who knows if it did something to slot.
And definitely reseat DIMMs if you haven't done that.
Just in case you nudged one slightly while changing GPU.

Could also swap M.2 slots.
Click to expand...

Some good ideas, cheers. What's the 'reliability history' though?
 
Well it sounds similar to event kernel 41 issue.

Hence asking about event viewer.

A similar issue on my lads PC was resolved by turning off fast boot and hibernation.


Of course this may be completely unrelated but Is free to try.
 
Very frustrating. Other than the suggestions mentioned above, have you tried running CCleaner. I'm just thinking is there something causing conflict for it to be intermittent. Doubtful but always worth a shot I suppose.
 
sastusbulbas said:
Well it sounds similar to event kernel 41 issue.

Hence asking about event viewer.

A similar issue on my lads PC was resolved by turning off fast boot and hibernation.


Of course this may be completely unrelated but Is free to try.
Click to expand...

I too had/have a weird similar issue and also disabled fast boot on the off chance. Initially i had issues booting from sleep so thought it was the ram.

Unsure if this was the issue as haven't had enough boot ups to rule it out, was only last week i disabled fast boot.
 
It is always a good idea to check the reason for BSODs especially if they are happening without the PC being stressed, especially when non-business software is being run. For example the occasional BSOD can occur due to memory issues with games and sometimes that's just the nature of the beast. Assuming that you are running Windows, make sure the OS is configured to produce a memory dump and then use a Microsoft tool called WinDbg, which is not too hard to use in its basic form and can provide useful information about why the BSOD occurred. If the cause is hardware then it is likely to be genuine.

If a boot device cannot be found at POST then it's either a BIOS issue or a HW issue. Normally I'd say that a BIOS issue can only be a configuration issue, and as advised if fast boot is enabled, try disabling it. However after it happened to me I know that a BIOS can be corrupted (flash memory does have this risk) and may need to be flashed. If the BIOS is out of date then this would be a good time to update it to the latest. But since you are managing to boot into the OS by simply power cycling then check the HW. Even just unplugging and re-plugging SATA cables or reseating NVMe cards could cure a poor connection problem. Next time it boots into OS do a full test of the drive.
 
You must log in or register to reply here.
Back
Top Bottom