bleep

SOLVED Appreciate the help so far. I tried three different cards in the same system, and on all of them, HDMI worked, but DP did not. Next I tried the three cards in another PC connected to the monitor. Again HDMI worked, DP didn't. This suggested to me that the issue was either the cable, or the monitor. Thankfully I had another DP capable monitor elsewhere in the house, with another DP cable. I tried first swapping the cable, hoping it would be a bad cable (cheaper to replace), but again the problem persisted. So then I swapped for a different monitor, just to confirm, and it worked with the old cable on a new monitor. Fearing for my wallet, I put everything back to the way it was before, just hoping something would work now, and I wouldn't need a new monitor. And to my surprise, it all worked again. Not a clue what was causing the problems, but after I swapped monitors, cables, cards, and computers, something must've been the right combination of things changing to make the old monitor start to behave again. Still no clue why it wouldn't boot to windows without a working DP output, but I'm just going to laugh nervously and pretend like everything is working fine now. Again thanks for the help sorting through the troubleshooting steps!

Gonna try clearing CMOS despite how it turned out last time. Hopefully I can at least get a consistent POST. EDIT: I'm in to Windows over HDMI on my old GPU now. I don't dare try any other configurations for fear I can't get back into Windows. I am going to attempt a clean install of the 2080 Super drivers and hope I get through the process unharmed. Will update when something happens. EDIT2: Ok with the correct drivers and the 2080 Super in, I get no signal when using DisplayPort but I DO get signal when I use HDMI. So, that leaves the question, wtf is making it so I can't use DP? Could it be a bad cable? It was working fine until I updated drivers/cards. Any thoughts anyone has here would be most-helpful.

Ok I've got something, after a lot of rebooting, trying new configurations, I got into Windows with HDMI. I cannot use DisplayPort though, I get no signal from that. But I can at least get into Windows now. Think a clean driver installation could help here? EDIT: Well, after one more reboot, things got worse. Now when it turns on the fans spool up to 100% and stay that way... just like before. No BIOS, no Windows.

I cannot even get into Windows at this point. I wouldn't even have the first clue how to get into safe mode if it's not booting to an OS. Without a screen it's hard to know how far the computer makes it into the boot process. I don't even know if it is POST-ing successfully. My keyboard's num-lock, caps-lock, scroll-lock buttons seem to light the indicator LED's. Is that evidence it is POST-ing successfully?

System Specs: CPU - Ryzen 3900X MoBo - Asus Prime X570 P Memory - G.Skill FlareX 32 GB (2x16 GB) (Part: F4-3200C14D-32GFX) Storage - 500 GB WD Black NVMe Black SSD GPU - EVGA 2080 Super PSU - EVGA SuperNOVA 750 GA (750 Watt, 80+ Gold) OS - Windows 10 Pro The Problem: So today my new graphics card arrived. It's a 2080 Super, and I was upgrading from a 2080 (I only pulled the trigger on this because it was priced lower than my 2080, which was still within the return window). I plugged in the 2080 Super and booted to Windows like normal. GeForce Experience recognized the new GPU and suggested I install new drivers. I went through the normal installation process, opting for a clean install too. I was then prompted to restart my computer, which I did. Except, nothing came up on screen. I thankfully had Windows Remote Desktop set up and was able to control my computer from there. It looked like normal, except GeForce Experience was already open, and it was prompting me to install drivers again (like it had failed to install the first time?). Getting nervous by this point, I opted for the express install this time. After this was over, GeForce Experience did not prompt me to restart, it just said "installation complete". I still had no output, so I tried to reboot my machine once more. Only now, when it powered on, all the fans blasted 100% and wouldn't stop. I waited a few minutes and got nothing on the screen, no BIOS, no Windows. I tried rebooting a couple times, and nothing fixed it. It won't boot to Windows so I can't remote in, and my CPU doesn't have integrated graphics, so I can't bypass the GPU. When I power on my machine, the monitor flashes on for a brief moment and then goes back into standby, displaying nothing. I'm stuck with not a clue what I can try next. I would appreciate any help! What I've Tried: I removed the GPU and re-seated it I tried using a different DisplayPort output on the card I tried swapping back to my old 2080. (I also have a 980 sitting around somewhere that I will try soon too in-case using a different series card will make a difference) I have opened a support ticket with EVGA P.S. - I am hesitant to clear my CMOS because the last time I did, BIOS stopped recognizing my NVMe drive as bootable, I made a post about it here.

FINAL EDIT: Ok so this is my only, and final edit to this post. I got no replies but I am editing it now in the event someone has this problem in the future and finds this resource. To be clear, in the end I was unable to get my OS to boot, HOWEVER, I was able to recover all of my data and start fresh with all my old data on a cleanly formatted machine, without any losses; effectively, I found a workaround, not a solution, to my original problem. I will document the steps needed to do this here. Before anything, read the original post and decide that the problem you face is the same problem I've described here. This procedure WILL wipe your drive, and effectively give you a new OS, though your data will be preserved. Remove all drives except the misbehaving NVMe drive; this is more or less a protective measure, to prevent any unanticipated data loss. Create a Windows To-Go USB thumb drive (NOT a Windows installation media). You can use a USB 2.0 if it's all you have around (it's what I used), but it will be quite sluggish. To create a Windows To-Go USB, there are plenty of tutorials floating about online, but I used the Windows Media Creation Tool to download a Windows .iso and used Rufus to create a boot-able USB with Windows To-Go. Perform your first boot to Windows To-Go on your defunct machine with the NVMe drive inserted. Go through the set up process like normal. You can skip all the online account set up stuff and all the updates; just get to the desktop. Open File Explorer, and verify that you can see your NVMe drive listed when you select "This PC". If you cannot, you may be out of luck, and your SSD may need to be RMA'd, Insert an external hard drive onto which you will back up your files. Copy over anything you want to keep (App Data, Documents, or even your whole user folder). Anything you do not save now will be deleted! Once you're satisfied with you data haul, you will need to create a Windows Installation Media, and again I used the Windows Media Creation Tool. Insert your installation media into your machine with ONLY your NVMe SSD to prevent erroneous formatting of drives. Verify that you are still unable to boot from your NVMe drive, and that the only boot-able option in BIOS is your installation media. Install Windows like you normally would for a new machine, selecting custom install, imputing your product key if you have one, and when it asks you for the drive on which you would like to install Windows, you need to delete the partition of your NVMe SSD (there should only be one partition listed), and reformat this drive. In doing so, you will be able to install Windows cleanly and boot into a fresh, new OS. Don't forget to copy all your files back over from your external storage device. You can also reconnect any additional storage media, such as game drives at this point. And that's it. Although I was unable to ever learn how to solve my problem, or even why it was happening in the first place, I at least was able to come up with a remedy that preserved all of my data, and only cost me about half a day of downtime. Thank you for coming to my TED talk. Initial post follows below. ~ ~ ~ ~ ~ Preface: Hi all! First time poster, so forgive me if I am missing some of the standard operating procedures here. Please let me know if I am in the right place for assistance. I will attempt to be quite diligent in responding and updating this post. System Specs: CPU - Ryzen 3900X MoBo - Asus Prime X570 P Memory - G.Skill FlareX 32 GB (2x16 GB) (Part: F4-3200C14D-32GFX) Storage - 500 GB WD Black NVMe Black SSD GPU - GeForce RTX 2080 Ventus 8G OC PSU - EVGA SuperNOVA 750 GA (750 Watt, 80+ Gold) OS - Windows 10 Pro In Brief: Today after trying and failing to overclock my memory, I was forced to clear my CMOS when I pushed the envelope a bit too far and I couldn't even enter the BIOS (not sure but it might have failed to POST or, more-likely, the RAM timings were too tight to function). Upon re-inserting the battery and reconnecting everything, I was sent straight back into BIOS and my SSD with my OS was not listed as a boot-able option. Everything else looked normal though. After trying a whole host of possible solutions I feel like I've learned a lot about the issue, yet I'm no closer to solving it. Description: Background I recently built a new system, as my old one (the one from which I write you now) was nigh on 5 years old and it was starting to show. I bought everything fresh and new, save my GPU which was purchased refurbished. I opted for an entry level X570 MoBo as I was not interested in any overclocking at the time of construction. It worked great for the last couple of weeks, I was able to work, game, browse, all at the same time without so much as breaking a sweat. All was well until today, when I, ever the optimist, decided to try and push my luck with some mild memory overclocking. I used Ryzen DRAM calculator to find what I believed to be a safe timing enhancement given my memory specs. To the best of my ability I tweaked around in the BIOS until I was sure everything was input correctly, and I saved and rebooted, only to be greeted with... nothing; I left it for about 5 minutes to think about its life decisions (I thought maybe it needed some time to POST the first time memory settings like this were changed, no idea why). Seeing as nothing was happening, I realized I hecked up and decided to opt for my last-resort option of clearing the CMOS, and this my dear readers is where tragedy struck. The Problem After clearing the CMOS, I re-inserted the battery and made sure everything was back in its proper place. I hit the power button and successfully was greeted with the option to enter BIOS, which I did to make sure everything was back to normal. All looked well, my memory was registering as 32 GB and the clock speed and timings were back to the default. Only problem was, I now had no boot-able devices found. I'm getting a little nervous at this point because I was worried I had fried either something on my MoBo or my SSD. Trying not to panic I did all my idiot checks and isolated the problem as best I could. I removed my extra 1 TB drive, and swapped M.2 slots, and still nothing. I verified that the device is registered as an NVMe storage device by the BIOS, and even ran a device self test in the NVMe Configuration page of the BIOS. At this point I decided to do some research and see if other people had this issue. I found a couple of forum posts with some ideas and I tried them but to no avail. I am now stuck with a very expensive paperweight and would like to know if there is anybody out there who can help me out here. What I've Tried A post on Tom's Hardware seemed promising, but did not work, despite my best efforts. The description of the problem seemed similar enough that it was worth a shot. I created a Window's install USB in the event I needed to resort to the nuclear option, but used the install tool to try and view the partition. I found that the installation media was able to recognize the NVMe drive, but it said it wouldn't be able to install windows on that particular partition (I would need to delete/reformat) and gave the following message: This is just a little bit beyond the edge of my understanding, despite my best research efforts, so I don't really understand what this means. However, one helpful piece of insight I gained her was that when I selected the Load driver option in the installation screen, and then selected browse, I was able to view my filesystem, including all my documents and folders. and it had the correct "C:" volume label, which did give me a little hope that my data might be recoverable at least. Next I wanted to see if I could boot to Windows at all on the machine from a separate drive, and if I was going to be able to recover any data from the NVMe drive. So I made a Window's to Go USB and booted to that. And it worked! I was able to view my NVMe filesystem and save the important stuff to another external drive. This verified for me that my filesystem was completely in-tact and the data was recoverable. But despite the OS still being on the drive and functioning more-or-less as any other external drive, I am still unable to get it to boot to windows from the drive. Conclusion: And that's pretty much everything the is to tell about how I ended up in this situation, and where I need some assistance. Sorry for the long post, but I wanted to provide any information that could be relevant. To reiterate, I am unable to boot to my NVMe SSD despite all signs pointing to the drive being configured appropriately. This suggests to me that perhaps the issue is somewhere between the BIOS and the drive, but I don't feel like I know enough to say for certain at this time. Any help that some of you might be able to offer would be greatly appreciated. Also, again, this is my first post so I apologize if some of the minutiae of this forum's etiquette were lost on me, and would appreciate feedback where appropriate. Thank you. ADDING NOTE HERE FOR VISIBILITY: Read the final edit at top of post for my eventual resolution to the problem!