Many thanks, can you please click on the sensor button above and share the section which show the motherboard name?
Yes enough and this show your motherboard do have sufficient power to the system should be alright.hwinfor for motherboard.Is this sufficient information?
![]()
Sorry I may not quite understand your question butI just use the stock fam that came with the AMD 3600 CPU.Yes enough and this show your motherboard do have sufficient power to the system should be alright.
May I check what fan do you plug into the cpu_opt header as this should normally same rpm as the CPU rpm but it run at different speed per your sensor show.
May I know which specify nvme you are using now for the OS?Sorry I may not quite understand your question butI just use the stock fam that came with the AMD 3600 CPU.
Can you have a look at my CrystalDiskMark for my NVME I posted earlier. Is that okay?
Thanks YongKit for your help.
I ran CrystalDiskMark for my NVME. This is the result. The NVME has not crashed when using it before this problem or even currently
![]()
Many thanks for the update.Thanks Yong Kit for your advice.
My OS is in Western Digital Blue WDS100T2B0C SN550 PCIe NVNE M.2 2280 Internal Solid State Drive, Blue, 1TB bought and installed in Dec 2020. It has never given me any problem when in use.
I looked into my casing and tracked where CPU OPT is connected to and if I am not wrong it is connected to the front fan of the casing.
I have check my PSU 12 V and they are securely connected.
In the morning, I connected back my SATA hard disk and also my other SSD. After which when shut down and powering up again, the old problem of having to reboot two or 3 times to detect the windows in the NVME came up again. Did this about 3 times and same thing happened. Once into windows everything runs fine, no crashes, able to detect hard disks, SSD etc.
Then shut down left PC alone and had lunch. After lunch at 2 pm, power up and into windows with ease. 2 times successful. At 5 pm power up and into windows with no problem. Tried 4 times and successful.
check crystaldiskinfo alsoI ran CrystalDiskMark for my NVME. This is the result. The NVME has not crashed when using it before this problem or even currently
![]()