Hello,
Since 5 or 6 months my old MSI laptop (based on MS-16J51 board, I don't have the machine with me atm, i'll update the exact number when I'll get home) started randomly loosing the nvme drive.
At first I thought it was a bios issue, changed the bios battery that was a bit low, but did not solve the issue.
It used to happen like once every 2 or 3 weeks, but now it became more frequent and can happen several time in the same day if you restart the computer.
It looses the nvme at power-up (will boot to bios and report no nvme drive but still sees to SATA drive) but never when it's running.
The workaround is to unplugg the power, remove the main battery and bios battery and it will properly detect the nvme on power-up.
Sometime powerring down, removing power and waiting several hours also "fixes" the issue.
The reset switch does not help.
Of course first thought was the nvme drive. I swapped the nvme (960 evo replaced with 970 evo) but this did not help and the original nvme did not show any errors and works perfectly fine in another machine.
So this weekend I dowloaded the schematics and found that the 3.3V on the nvme port (+3VRUN) was not present when the nvme was not detected. but the main 3.3V voltage is present. So I thought about PQ42, but it looks fine.
I'm thinking maybe the wlan card could play some role as the +3VRUN is shared with it. Haven't tried yet removing the card.
Otherwise the RUND that comes from PQ16 could be pulled low for some reasons ? RUN_ON is generated by U35, I believe it's determined by some voltage condition, but since all voltage seems ok (and the computer startup and enter bios) I would assume it's not one of the main voltage rails.
My understanding is that RUN_ON is generated based on other voltage rails and if for some reason one of the rail does not turn-on within the proper timing, RUN_ON is not activated and stays low. But then I would expect the POWER_FAIL signal to be triggered as well.
I haven't finished investigating, but if anyone already run into this issue, that would help.
Since 5 or 6 months my old MSI laptop (based on MS-16J51 board, I don't have the machine with me atm, i'll update the exact number when I'll get home) started randomly loosing the nvme drive.
At first I thought it was a bios issue, changed the bios battery that was a bit low, but did not solve the issue.
It used to happen like once every 2 or 3 weeks, but now it became more frequent and can happen several time in the same day if you restart the computer.
It looses the nvme at power-up (will boot to bios and report no nvme drive but still sees to SATA drive) but never when it's running.
The workaround is to unplugg the power, remove the main battery and bios battery and it will properly detect the nvme on power-up.
Sometime powerring down, removing power and waiting several hours also "fixes" the issue.
The reset switch does not help.
Of course first thought was the nvme drive. I swapped the nvme (960 evo replaced with 970 evo) but this did not help and the original nvme did not show any errors and works perfectly fine in another machine.
So this weekend I dowloaded the schematics and found that the 3.3V on the nvme port (+3VRUN) was not present when the nvme was not detected. but the main 3.3V voltage is present. So I thought about PQ42, but it looks fine.
I'm thinking maybe the wlan card could play some role as the +3VRUN is shared with it. Haven't tried yet removing the card.
Otherwise the RUND that comes from PQ16 could be pulled low for some reasons ? RUN_ON is generated by U35, I believe it's determined by some voltage condition, but since all voltage seems ok (and the computer startup and enter bios) I would assume it's not one of the main voltage rails.
My understanding is that RUN_ON is generated based on other voltage rails and if for some reason one of the rail does not turn-on within the proper timing, RUN_ON is not activated and stays low. But then I would expect the POWER_FAIL signal to be triggered as well.
I haven't finished investigating, but if anyone already run into this issue, that would help.
Comment