First, go to Windows Update and update your computer...especially the relevant 'Optional' and 'Recommended' updates. These will include the .netframeworks and C++ upgrades. This must be done before trying to install AMD graphics drivers.
I have a very similar (read same) issue. Will post more information once I can boot into my machine!
- Dell Optiplex XE (2010) (obviously not a hardcore gamer, just need a PC to practice my flying on and, until yesterday, this rig has worked flawlessly with new Q9300 and Radeon 7950)
- Intel Q9300
- 8 GB DDR3 RAM
- Sapphire Radeon HD 7950 (single monitor, LG 49" 4K TV, HDMI-out)
Hadn't started my machine in 3 weeks (as of yesterday, 4/20/2016) and hadn't connected to the internet since then, either. BUT, I do have auto updates turned on. Fired up Flight Simulator X and started a 2 hour flight. 1 hour in, screen turned blue and white checkered and audio went to terrible droning sound. Rebooted machine. Showed the windows logo on black backdrop "starting Windows" then goes to black screen and no sound. Went into Safe Mode, deleted driver, deleted everything AMD/ATI, reinstalled drivers from disk (15.x) and it worked for about 15 minutes. Went into Crimson Settings and clicked "update". As soon as the update (16.x) installed, it rebooted and did the black screen thing again. This time, uninstalled everything using IObit Uninstaller and wiped out all the ATI/AMD/Raptr/Vulkan folders in Programs Files. Reinstalled from disk. This time, it would not boot again. As soon as I delete all AMD drivers, I can boot into Windows 7 just fine (not Safe Mode, but regular boot), but no AMD software/settings.
Contacted Sapphire support and they said they believe my GPU is bad. However:
- I have had this GPU since Christmas.
- It works perfectly fine in Safe Mode.
- After reinstalling drivers 1st time, it worked wonderfully.
- I can see BIOS splash and "Starting Windows" black screen with logo, so this doesn't sound like bad GPU to me...
ANY guidance would be so appreciated! Yes, my GPU is under warranty, but I don't think replacing will solve this issue.