- Aug 20, 2017
- 5
- 0
- 520
Hello to all,
I have been trying to resolve an odd issue with my Windows startups that seems to center around some elusive driver problem. It is my belief that there is some vestigial remnant of Catalyst drivers (story on that below) remaining and that the OS calls upon those drivers at startup, which of course fails because I uninstalled those and installed Crimson over it once I resolved an earlier problem. Since that time, upon starting Windows and getting to the desktop, numerous little cube artifacts will appear throughout the display, the system briefly fails to respond, and then the device driver recovers and all works normally again. However, I have had a devil of a time trying to clean out whatever files or registry entries are causing it - DDU has not resolved it, nor has Driver Fusion or CCleaner. Consequently I try to avoid shutting the computer down when I can, as it is a bit annoying to deal with every boot, and I opt for standby instead. I also edited the registry timer to (mostly) stop bluescreens upon boot from the delayed GPU response.
As for the background story: a few months ago I was having trouble getting my GPU to deliver a signal to my monitor upon reaching Windows boot. That problem was seemingly hardware related as cleaning the PCI-E ports and making sure that the DVI cable was properly connected on both ends resolved that problem. However, during the process of trying to sort it out, I played quite a bit with drivers and got desperate enough to see if the old pre-Crimson drivers would work.
Does anyone know of some program that would be appropriate for removing older drivers? I am concerned that given the age of the drivers I tried to use, the newer versions of the aforementioned file/registry cleanup utilities may have passed over the culprit.
Any other possible solutions are welcome, as well. I would simply prefer to not have to deal with the trouble of reinstalling Windows or other such dramatic steps, as everything else, including the GPU, works fine outside of this problem. Other than attempting to find it manually by checking dates of files in the Windows directory, I have no other good ideas.
Thanks for any and all assistance.
I have been trying to resolve an odd issue with my Windows startups that seems to center around some elusive driver problem. It is my belief that there is some vestigial remnant of Catalyst drivers (story on that below) remaining and that the OS calls upon those drivers at startup, which of course fails because I uninstalled those and installed Crimson over it once I resolved an earlier problem. Since that time, upon starting Windows and getting to the desktop, numerous little cube artifacts will appear throughout the display, the system briefly fails to respond, and then the device driver recovers and all works normally again. However, I have had a devil of a time trying to clean out whatever files or registry entries are causing it - DDU has not resolved it, nor has Driver Fusion or CCleaner. Consequently I try to avoid shutting the computer down when I can, as it is a bit annoying to deal with every boot, and I opt for standby instead. I also edited the registry timer to (mostly) stop bluescreens upon boot from the delayed GPU response.
As for the background story: a few months ago I was having trouble getting my GPU to deliver a signal to my monitor upon reaching Windows boot. That problem was seemingly hardware related as cleaning the PCI-E ports and making sure that the DVI cable was properly connected on both ends resolved that problem. However, during the process of trying to sort it out, I played quite a bit with drivers and got desperate enough to see if the old pre-Crimson drivers would work.
Does anyone know of some program that would be appropriate for removing older drivers? I am concerned that given the age of the drivers I tried to use, the newer versions of the aforementioned file/registry cleanup utilities may have passed over the culprit.
Any other possible solutions are welcome, as well. I would simply prefer to not have to deal with the trouble of reinstalling Windows or other such dramatic steps, as everything else, including the GPU, works fine outside of this problem. Other than attempting to find it manually by checking dates of files in the Windows directory, I have no other good ideas.
Thanks for any and all assistance.
Facebook
Twitter
Instagram