I did some trouble shooting/testing today. 
 
Re-seated GPU
Re-seated PCIe extension cable
Removed PCIe extension cable
Mounted GPU into second PCIe motherboard slot
Swapped out Display Port cables
Changed monitors using HDMI cable/monitor
Re-seated memory modules
 
I have reset CMOS as well
 
Still process is, Power On > Good POST > Start reading drives > Screen goes blank and POST code display shows CPU temp as if system booted. Press RESET and system will reboot as normal and pass any and all stress tests I can throw at it. Click Restart and system with restart as normal and run great. This is only happening on a power-on boot.
 
NOTE: I am starting to get ghosting shadows in games, Chrome and other applications. I just noticed this today for the first time.
 
Any ideas?
Roger

Thank you bcavnaugh.
That makes sense. I will see if the warranty is still good.
Appreciate your time Sir
Roger

Sajin
Is your bios current?

Yessir, v1.03. I check for updates often. Being a new board and all.

That's a good question Sajin. I received the board and test benched it. It came with 1.01. Once system was built and OS installed I updated to 1.03. The system ran for over a month until this last week when this issue started. Should I install 1.02 or even revert to 1.01?
 
The odd thing is that it does not hang on any Q Codes at all. It passes POST, the screen goes blank at the same time the drive LED goes nuts, then the POST codes go right to reporting CPU temp. It acts like the system booted but the display is blank. Seems like a GPU issue but yet the GPU is very strong in stress tests and gaming once in Windows. Seems that maybe the PSU is not sending enough initial power to the GPU, just enough for display during POST or while in BIOS. I tried several DP ports on GPU as well as another monitor via the HDMI port.
 
By the way I mentioned an issue with Ghosting Shadows in an earlier post above. I fixed that. During testing I was checking if the monitor had settings for inputs and I had inadvertently changed the OD to Extreme. It's on normal now and working properly again. 
 
Roger

Yes, I'd defintely try out the older bios version. Uninstalling the nvme driver temporarily shouldn't be a problem.

I looked up post code 97 and saw where one guy said that it could be GPU initilization.   The M.2 shares sata ports 4/5   Anything there?   Try uninstalling your video cards, use onboard video and keep both M.2 in place and see if it happens.  That would rule out gpu or M.2 drive. 
 
"M.2 Key-M (80mm, Top) – x4 o M.2 Enable/Disable is set within the BIOS o This M.2 Key-M slot shares lanes with SATA ports 4/5. Installing an M.2 device will disable SATA ports 4/5."
 
I don't have that board but on the dark version, you can disable PCIe lane with a toggle switch if you have a loop.   You can always leave your cards on the loop and just pull them away from the slots.   My loop would support two cards like that temporarily.   Whenever I get post costs, I start yanking things one by one until I get a clean boot.  Then put things back in one by one to see what variable it is.   That also included nonessential things plugged into the USB ports.  

Sorry Roger, didnt realize about the onboard video. Hope things are ok

On another note, I have 3200 cl14 as well. Any luck getting overclocks on them?

Delirious
Sorry Roger, didnt realize about the onboard video. Hope things are ok

On another note, I have 3200 cl14 as well. Any luck getting overclocks on them?

Hello Delirious,
Yes, all is running very well again, thank you. 
 
I ran my 3200 CL14 @ 3333 CL14 with stock voltage for several weeks. The other day I went to 3400 maintaining CL14 but had to bump voltage to 1.40. So far so good. I don't know how much difference it really makes but hey, if it will run it.... "RUN IT" 
 
By the way, if I may be so bold, I would like to share a slideshow of my build. I'm a concrete mixer truck driver with a bit of computer enthusiasm on the side. This is my first real "custom" build. I'm quite happy with it and look forward to building another.
https://youtu.be/6S9fLBHw1Mo
 
Cheers
Roger

So did you succeed in solving your issue ?

Now it works fine? Can u tell how to solve

WB_FlashOver

ForTheWin
So did you succeed in solving your issue ?

Yes Sir. It was the Samsung NVMe driver v3.0. I uninstalled it and things worked great. Days after v3.1 came out and I tried that. It worked without troubles, however the speeds and system response times were not as good as the stock Windows NVMe driver. I am now running the Windows driver with satisfaction.
 
Thanks for checking on me.
Roger

happy to hear this !!