• Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Pending OP Response Have a possible hardware issue with my computer

What different things have I told you? I told you that the AMD Radeon Settings app that had the recommended and optional drivers isn't showing me those anymore and I don't know how to get it to show me the information that was shown to me previously. I've asked you multiple times what I did wrong and you keep posting the same reply which I thought I followed. And when I ask what I did wrong you just post the reply again. Obviously I'm not getting what I did wrong and posting the same thing back to me isn't helping me understand.

So was trying to update through the device manager the wrong move or what? What have I been doing wrong that is causing this conversation to go around in circles?
 
It was asked that once you had directly installed the Recommended driver from AMD that should it resolve the dll issue that you create a new system restore point and then post back, when you post back you told us "I installed the new driver and the OpenCL.dll error is no longer appearing" which is when you should have created the new restore point and then post back so we could get on with the testing, unfortunately though for some reason you manually searched for and installed an additional driver which could actually be causing you problems, had you not installed the additional driver it would have been one less possible cause of any issue/s that you are having.

All we are trying to achieve here is for you to have stable Vega video drivers so that you can try to replicate the freezing problem when the add on GPU is not in use, you need to be present to do this so that you can keep a watch on things and the other proviso is that the testing needs to be done when not connected to the internet which helps to rule that in or out as the cause.
 
Okay, so I only installed one driver. I said that I couldn't get it through the AMD Radeon settings from where I got the info for the recommended and optional drivers, so I went through the device manager. It was after that that when I restarted my computer the OpenCL error didn't appear. Is that where we got misunderstood or did I unknowingly install an additional driver?
 
Okay, so I only installed one driver. I said that I couldn't get it through the AMD Radeon settings from where I got the info for the recommended and optional drivers, so I went through the device manager. It was after that that when I restarted my computer the OpenCL error didn't appear.
That is where the confusion has arose, your original post suggested that you had downloaded the recommended driver from AMD and then after the dll error had gone away you went through Device Manager and downloaded and installed another driver, by the by now and as long as you are no longer getting the dll error it means that you should have stable Vega video drivers installed and good to go with the testing, the idea is to see what happens if you push the computer and Vega graphics when not online gaming.

Use the free versions at the following two links.

Stress test your iGPU with Furmark

Check your FPS with Valley
 
I got the furmark test done which I will screenshot the results of, and I tried to get the Valley benchmark to test, but I can't start the program. I'm getting an error code that says, "The code execution cannot proceed because MSVCP100.dll was not found. Reinstalling the program may fix this problem." I tried reinstalling already but that didn't work.
 

Attachments

  • Screenshot (6).png
    Screenshot (6).png
    37.2 KB · Views: 4
No worries as it was more important to see how the onboard video handled the stress test of Furmark, next two tests are;

Refit your add on GPU, restart the computer, keep the computer disconnected from the internet so Windows can`t download anything, test the GPU with Furmark and first of all without installing any drivers, see how that goes, if it goes ok move onto the next test.

Download the latest drivers for your GPU from here install the drivers, still disconnected from the internet, try testing the GPU with Furmark and the latest drivers and see how that goes.
 
Correct, network drivers like GPU drivers can be a pain in the proverbial and by not being connected to the internet in any way you are effectively taking the network drivers out of the equation, some folk go as far as to turn off the router or disconnect the Ethernet cable when troubleshooting driver issues, entirely up to yourself whether or not you choose to do so.
 
With attaching my add-on GPU without being connected to the internet it won't play any of the preset test options on Furmark. And my screen's resolution is tiny, I can probably fit 30 shortcuts on the desktop screen.
 
No problems with that as all that it means is that Windows does not have any generic drivers for your add on GPU.

Continue with what was suggested by downloading the latest drivers for your GPU from the link that was previously attached, disconnect from the internet, install the GPU drivers, test with Furmark then post back with an update for us.
 
I think Nvidia automatically installed something that turned my GPU back to "normal" but it was as I was getting the info for the site you sent me to download the drivers. Now there's some Nvidia Software Agreement it wants me to accept. From my speccy, it says I have the driver version 26.21.14.3200 and the driver from the EVGA website is version 441.66. Will I need to DDU clean that Nvidia software again to get to where I was before it installed by itself? I just don't want to something slightly different that it completely ruins the process.
 
Thanks for checking back (y)

Best way to proceed would be to test with the 26.21.14.3200 drivers that have already been installed and see how things go, if all ok, stick with those drivers, any problems, use DDU and then try the drivers from EVGA.
 
Cool. I ran a Furmark test and it made it through. The frame rate was 10 times better than the Radeon Vega and it didn't crash. I was still only able to do the 1080 resolution test, but it still made it. Also, just to give as vivid detail as possible, after that driver had installed by itself, I wasn't able to open the start menu by pressing the button or hitting the windows key. ctrl - alt - del didn't work either, so I restarted it to see if that would help. It did, but it ended up freezing on me about three minutes after the restart during a YouTube video.
 
after that driver had installed by itself,
Which driver?

I wasn't able to open the start menu by pressing the button or hitting the windows key. ctrl - alt - del didn't work either, so I restarted it to see if that would help. It did, but it ended up freezing on me about three minutes after the restart during a YouTube video.
Sorry but I am done here as you are still not doing as was asked, nothing that we were doing would have had any bearing on Windows in any way but by being connected to the internet while testing Windows is able to install updates that by the looks of things has stuffed the whole thing up again :(

Continue with what was suggested by downloading the latest drivers for your GPU from the link that was previously attached, disconnect from the internet, install the GPU drivers, test with Furmark then post back with an update for us.
 
It was that driver you told me to test instead of installing the one from the EVGA website that I told you about in reply 71.

Am I going to need to DDU that 3200 driver so I can install the one from the website? I thought the thing we were trying to avoid was what happened when the 3200 driver was installed by itself, so since that already happened, I thought it wasn't going to be a problem still being on the internet. I'm sorry for assuming.