Bex 9. okt. 2017 kl. 6.04
OpenGL-program.exe has stopped working
Hi!

For couple of weeks now I've had this issue every time when starting Steam.
"Opengl-program.exe has stopped working"

I haven't changed anything or installed anything new.
I can't find any tips on google.

Any way to troubleshoot this issue?


Win8, AMD A8-4500M, AMD Radeon HD 7600M.
< >
Viser 7690 av 113 kommentarer
Bad 💀 Motha 13. okt. 2017 kl. 20.21 
Opprinnelig skrevet av Will^T:
Opprinnelig skrevet av Bad_Motha:

Yea, as things update, you need to continue updating your other stuff too, like OS and Drivers.
It's all relevant.

You can see what the fault is in your post, fix that yourself, it's Visual C++ Runtime 2015

thanks man appreciate it just installed and now a different problem

Fault Module Name: api-ms-win-crt-runtime-l1-1-0.d

Problem Event Name: APPCRASH
Application Name: gldriverquery.exe
Application Version: 0.0.0.0
Application Timestamp: 59bc6c77
Fault Module Name: api-ms-win-crt-runtime-l1-1-0.d
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791a783

And that error pertains to:
https://stackoverflow.com/questions/33265663/api-ms-win-crt-runtime-l1-1-0-dll-is-missing-when-opening-microsoft-office-file
Will^T 13. okt. 2017 kl. 23.16 
Opprinnelig skrevet av Bad_Motha:
Opprinnelig skrevet av Will^T:

thanks man appreciate it just installed and now a different problem

Fault Module Name: api-ms-win-crt-runtime-l1-1-0.d

Problem Event Name: APPCRASH
Application Name: gldriverquery.exe
Application Version: 0.0.0.0
Application Timestamp: 59bc6c77
Fault Module Name: api-ms-win-crt-runtime-l1-1-0.d
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791a783

And that error pertains to:
https://stackoverflow.com/questions/33265663/api-ms-win-crt-runtime-l1-1-0-dll-is-missing-when-opening-microsoft-office-file

thanks for the help bad_motha but canf figure it out how to fix this api but steam still loads so ill just keep playing till then
staviq 13. okt. 2017 kl. 23.33 
Opprinnelig skrevet av Will^T:
after the new client update now this is the problem does steam even test the updates before releasing? iam using vista by the way steam still loads but its annoying to keep this problem popping up everytime i load steam

gldriverquery.exe has stopped working

exact error

Problem signature:
Problem Event Name: APPCRASH
Application Name: gldriverquery.exe
Application Version: 0.0.0.0
Application Timestamp: 59bc6c77
Fault Module Name: VCRUNTIME140.dll
Fault Module Version: 6.0.6001.18000

Same thing happening to me, first it was "opengl-program" then steam updated and now it's "gldriverquery", all within hours.

Are they really pushing test updates live ? WTF ?
A smile 14. okt. 2017 kl. 0.35 
I am very sorry, they will only say this kind of words, this question I also met, their server is the Chinese bully, you may not know what is the bully, if you have Chinese friends, can ask him. I hope to have a good time with your friends!
internaut 14. okt. 2017 kl. 0.41 
Well, I am confident it IS the updates. I just closed a game and Steam had another update. Upon completion of update, Steam reloaded, the old gl error has been replaced with a new gl error = "gldriverquery.exe has stopped".

Blaming existing drivers/hardware/OS when the update can't marry up with them the way they are and expecting clients to run out and buy a new OS, or new comp with a new OS, and new video cards are nothing short of draconian expectations.
This amounts to 2 updates, and 2 different gl errors immediately after an update. That's not client hardware or OS nor a coincidence. That's the update bar raised too high. If we need to upgrade to 7, 8, or 10, just to continue using the games we already bought, why were we not told before that Steam would turn it's back on us? No! I don't think Steam operates this way.

I read the update log and in it somewhere, it mentioned (paraphrasing) fixes were based on error reports and tickets. Gone are the days of beta testors. It sems all dev everywhere toss out their wares and wait for feedback, fix and send again...
Sist redigert av internaut; 14. okt. 2017 kl. 0.51
abacusHex 14. okt. 2017 kl. 12.13 
This fix for the problem (specifically, the "gldriverquery.exe has stopped" error) worked for me.

Go to C:\Program Files (x86)\Steam\bin
Right click on gldriverquery.exe
Click the Compatibility tab
Under Settings, check "Run this program as an administrator" (yes, even if you are already an admin)

Also- If you have other people using Steam under a different login on your system, do this under the "Change settings for all users" button instead

Click OK, restart Steam... hopefully you won't see the message again.

My system is a new install of Steam on new hardware, so I can't say anything about what might have changed to cause it. I was getting the error from the first install and launch.

Sist redigert av abacusHex; 14. okt. 2017 kl. 12.15
The Giving One 14. okt. 2017 kl. 12.15 
Opprinnelig skrevet av bmilner:
My system is a new install of Steam on new hardware, so I can't say anything about what might have changed to cause it. I was getting the error from the first install and launch.
Could be that your Steam is installed under UAC for Windows, in program files. I usually suggest to never install Steam there, as well as others in the community, but that is just my opinion as it may help to prevent such issues.

I always install Steam in a folder all by itself, totally outside UAC control.
abacusHex 14. okt. 2017 kl. 12.18 
Opprinnelig skrevet av The Giving One:
Could be that your Steam is installed under UAC for Windows, in program files. I usually suggest to never install Steam there, as well as others in the community, but that is just my opinion as it may help to prevent such issues.

I always install Steam in a folder all by itself, totally outside UAC control.
That sounds plausible. Would explain why allowing gldriverquery.exe to run as an admin fixes it, essentially bypassing UAC. I did install in the default location.
Sist redigert av abacusHex; 14. okt. 2017 kl. 12.18
The Giving One 14. okt. 2017 kl. 12.27 
Opprinnelig skrevet av bmilner:
That sounds plausible. Would explain why allowing gldriverquery.exe to run as an admin fixes it, essentially bypassing UAC. I did install in the default location.
It's easy to move Steam, if you want to try that in the future. For now, if this issue is resolved, maybe just consider it for later if anything else comes up. Thanks.

Moving a Steam Installation and Games

https://support.steampowered.com/kb_article.php?ref=7418-YUBN-8129
abacusHex 14. okt. 2017 kl. 12.29 
Opprinnelig skrevet av The Giving One:
Opprinnelig skrevet av bmilner:
That sounds plausible. Would explain why allowing gldriverquery.exe to run as an admin fixes it, essentially bypassing UAC. I did install in the default location.
It's easy to move Steam, if you want to try that in the future. For now, if this issue is resolved, maybe just consider it for later if anything else comes up. Thanks.

Moving a Steam Installation and Games

https://support.steampowered.com/kb_article.php?ref=7418-YUBN-8129
Thanks, may undo the file change I made, and try that just to see.
internaut 14. okt. 2017 kl. 19.10 
Opprinnelig skrevet av Bad_Motha:
Opprinnelig skrevet av yori-boy:
I am using "windows vista" but after booting OS

Remove Steam from your OS Startup and reboot.


Then go to Steam folder, delete everything EXCEPT for the following...
.....

Remove Steam "from [your] startup" then delete it???? I don't get it. Do you mean the msconfig startup, All programs > Steam.....) of just the shortcut?

Thanks. Sorry to seem blank, but ;)

The Giving One 15. okt. 2017 kl. 2.03 
@internaut

Yes, I am almost positive that the helpful Bad_Motha means removing/disabling Steam from your startup tab in msconfig. Steam has a setting for that also in the settings menu, to make Steam auto launch on boot.

Totally disable all that, so you have to launch Steam manually. It's usually best to do that anyway, regardless of any issues that may be present.
Sist redigert av The Giving One; 15. okt. 2017 kl. 2.04
Seven7 15. okt. 2017 kl. 2.37 
users with gldriver errors will update nVidia Game ready drivers - new version fix problem
this co-incedence: M$, nVidia release bugged updates at same time with new version Steam client
Sist redigert av Seven7; 15. okt. 2017 kl. 3.26
445782448 15. okt. 2017 kl. 2.39 
1
Bex 15. okt. 2017 kl. 2.40 
Opprinnelig skrevet av The Giving One:
@internaut

Yes, I am almost positive that the helpful Bad_Motha means removing/disabling Steam from your startup tab in msconfig. Steam has a setting for that also in the settings menu, to make Steam auto launch on boot.

Totally disable all that, so you have to launch Steam manually. It's usually best to do that anyway, regardless of any issues that may be present.

This doesn't take care of the original problem. I've never had Steam launch on startup. Error appears every time I launch Steam manually.

Disabling Steam from launching at startup still is a good idea. There's a lot of other useless stuff launching too, everyone should take a careful look at all of them and disable all but the necessary ones.

Re-locating Steam might be a solution to some errors.
< >
Viser 7690 av 113 kommentarer
Per side: 1530 50

Dato lagt ut: 9. okt. 2017 kl. 6.04
Innlegg: 113