Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Correct but incorrect. It is a file associated with your graphics card but it is not the driver. Driver files are a different extention, atikmdag.sys is a system file.
Correct that the steam UI uses acceleration.
I agree, check for an update for your graphics card and update if there is one.
If there is a firmware update that is the update you need. Get any update that's available.
If updating your graphics stuff doesn't do it turn the new UI off:
- Right click on the steam icon you use to launch steam and select Properties
- In the ShortCut tab will be a Target field, at the end of the text in the target field after the quotes type a space and then:
Click Apply, and Ok to close the properties window then see if it will run.
If it runs turn off the GPU acceleration option in Steam > Settings > Interface
Hopefully this works. If it doesn't it might mean your video card may be on it's way out.
BSOD is hardware failure.
Computers don't usually splat to the death screen because they can't run something, they just don't run it.
A driver file makes hareware communicate with the system and is a .inf file
A sys file runs the hardware on the system, while it does "drive" the hardware it's not the driver file that makes the hardware communicate with the system it's a configuration file that contains configuration settings for the hardware to run that works in conjuncion with the driver file. They don't communicate with the system (bios) like a driver does they communicate with Windows, the operating system program.
A DLL file is a Direct Library Link file that contains data that tells a program where other files and commands are for that program to run. A dll is not a driver file. They do, sometimes, and they do sometimes contain driver information, but it's rare.
Correct, a DRV is also a driver file.
True is though that without the INF file, the binary is pretty much useless. But the INF is darn useless without the binary as well. Even more useless actually as modifying INF files is a task tech-savy end users can do, there's enough public documentation for that. Writing your own is just one step above INF hacking (which I did in the past). But writing an own driver binary, well, good luck. Writing low-level code is way more complex, than writing some text metadata and that's assuming you have knowledge of the piece of hardware in question.
And quote frankly, when I ask Windows the driver info and Windows gives me a SYS file, then it's the driver. Period. Microsoft know their driver architecture better than you do so if you and Microsoft disagree, Microsoft is right.
Point is, the AMD driver is at fault. That the SYS file is a part of the file suite that make up the driver is pretty darn useful in diagnostics but all in all, updating the AMD driver would be the first thing to try.
there is no latest update for my driver, and i did your command it didn't work either. it looks like my hardware has met its limits. but anyway thanks for replaying
might fix that issue.
small correction. bsod is in 99% a driver failure, even when the hardware is defective. when the hardware is the definitive reason, a bsod will not happen, the crap will just turn off.
My graphic card is an ATI Radeaon HD7870. If I launch Stream, after 5~10 secondes, I get a BSOD.
I tried to unistall and re-install Steam : very bad idea ! Steam on fresh installation will launch on system startup.
The solution has been to close Steam until BSOD came up. After that, I disable my GC with the tool devices manager. When my GC is disable, I can launch Steam and changed the option to stop the infinite loop of BSOD.
I hope, that the Team Steam will Quickly fix the problem.
Read a BSOD screen next time you see one or look up some screen shots or videos. It is a hardware failure. Usually due to overheating or improper connection to the board. Drivers rarely ever fail.
You expliciity said that BSODs are indefinitely caused by hard-ware failure or rather BSOD is the equivalent of hard-ware failure.
That is absolutely incorrect.
And yes, BSODs are MAINLY due to driver issues.
The issue was addressed already in a previous client update & some users fixed it on their own.
As per a previous thread...
https://steamcommunity.com/discussions/forum/1/3145094199306071946/
I never said it's not possible it's a driver error. My statements ARE correct!
The part that stabbed you in the back...
That ^^ is incorrect.
BSODs aren't hard-ware failure.
The correction...
https://steamcommunity.com/discussions/forum/1/3145094199293607121/?tscn=1540764172#c3145094199297206483
Still, not EXCLUDING hard-ware failure.
They run hardware!!
So what is the issue? Hardware!
i got this error my notebook spec is same with you. my Ram is 8Gb i just plays dota 2 here