Wellbe

Took NVMe out and everything worked properly. Tried NVMe drive again incase I just hadn't fitted it 100% correctly. This time I was extra sure and the exact same issues started up again (not POSTing every now and then). Will be returning it for a replacement. Thanks for all the help - PC up and running perfectly at the moment.

So, I flashed BIOS/UEFI to latest version (Version 1401 2019/12/11) which worked hurray! (I get so stressed doing it for some reason) And an oddity has occured. The Sabrent 1TB NVMe drive popped up as a recognised drive in the new version of the UEFI which it wasn't in the older version. I booted to windows and was able to format and partition the drive fine BUT when I went to copy something to the drive it gave me an unusual MS DOS error when trying to copy/save files. I wish I took a note of the error but didn't. I thought a restart might help but the UEFI has now stopped seeing the NVMe drive again and it has disappeared from windows. Am I correct in thing that this reinforces the idea that there might be something hinky with the M.2 NVMe? I would just pop it out but it's buried under the CPU cooler and would mean removing it the get it out. Thanks again for any thoughts.

Any other ideas anyone? Turns out sleep overnight didn't work either. When waking in the morning PC comes on but no reaction on monitor.

I checked in the BIOS and can't really see anywhere that explicitly says single/dual channel. Everything looks right though and even XMP1 is working fine. Performance wise everything is excellent. Just this stupid intermittent boot issue. Tested sleep and the machine sleeps and comes out of sleep perfectly. Maybe I'll just never shut down.... lol.

Hey! Thanks for the response! The motherboard light really does shout memory but I've gotten it to post with each stick in single channel (the A2 slot is recomended in the manual for single channel) and both sticks in dual channel (in the recommended slots). Running now in dual channel which CPU-Z confirms. And RAM is definately a dual channel kit. But with any of the setups above the same issue of stalling at post happens for a few boot tries until it works. RMA definately an option but just seems strange and almost memory unrelated apart from the light on the mobo. Thanks for the suggestions.

Hi all, Would really appreciate some help as I'm completely stumped. New build PC - my second one. First was 10 years ago and was a breeze New PC hardware: i7 9700k asus ROG Z390-E MSI 2070 Super Corsair RM750x PSU Corsair 2x8 3200 LPX RAM Noctua DH15 cooler NZXT H710 case Intel 660p 1TB M.2-2280 NVMe Sabrent Rocket 1TB M.2-2280 NVME So, plugged everyhing in, went for first boot and got stuck at orange DRAM led light on motherboard. No post. All switches, fans and lights working fine though. Did the usual troubleshooting with RAM to check slots or sticks and discovered that the machine will post every few boots completely unrelated to where the RAM is. When it posts everything is working perfectly, all RAM is showing. I installed windows and everything windows works great. No issues - typing on the machine now. GPU great, temps are great. If I restart the maching it restarts fine and comes back to windows. However, when I power the PC off and try switch it back on it goes back to the same issue. It gets to DRAM light on motherboard which usually stays lit and no post. Sometimes the DRAM led will go off but the VGA led which should be next doesn't light and the PC just stays like that with no post. Powering off and on will, after a few tries, work perfectly and the lights cycle correctly from CPU to GPU to VGA to BOOT and then machine posts and loads windows fine. It's gotten me really confused. A few notes: I've reseated RAM and GPU with no discernable changes to the problem. I have a pretty old monitor running on HDMI cable which I don't think would make any difference as works perfect on old machine but getting a new monitor tomorrow so will see if displayport connection on new montior might help. Only one of the NVME drives is showing but will troubleshoot that after. Haven't flashed UEFI yet either as waiting to see if monitor fixes it tomorrow. Anyone experience anything similar and can offer some possible solutions?