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
well as in any issue being reported, we cant always wonder if and when people will start posting thread complaints, but this may either be certain configurations with a small portion of people or just the beginning of when more complaints start being posted.
who knows, but im sure i have seen maybe a few so far, havent bothered to look at them or ask to see if computer specs were the same or said computers had anything in common.
could also be compatibility was degraded for w/e hardware with all the new updates.
but like i said, steam triggered the BSOD.
it happened during a game update from steam, it showed a kernel driver, after it happened and i knew where and when it would happen, i avoided that situation so it wouldnt happen again (simply didnt allow game updates on steam), then awhile after steam updated the client and i was able to download again with no issues.
i literally did nothing to my computer, didnt mess with said kernel driver, just avoided downloading updates from steam games.
only thing i actually did was use "bluescreen viewer" to read the BSOD info and research it online.
so in that case steam again triggered the BSOD and after they did an update to the client, the BSOD never happened again.
just food for thought.
i very rarely ever look at reddit... i use steam forums as that is the likely place most will post their complaints, ask questions, ect..
as i said, the software triggers the BSOD then its at fault, no questions asked.
if said software never triggered the BSOD, the person could have gone years or the life of the computer and not seen said BSOD, even if the driver was "faulty".
I first experienced this when the new UI was released and the client attempted to update. I uninstalled the client and reinstalled it. I was able to use the client but all of the games needed to be reinstalled since they were all removed when I uninstalled the client. I did not want to undertake that project at the time so now a few weeks later when I launch the client, it attempts to update again and again is triggering a BSOD with WHEA_Uncorrectable_Error stop code.
I can run games from other launchers without an issue, it only occurs during the Steam client update.
you still trying to claim it being a computer issue?
you were already told it was a steam issue.... if steam triggers the BSOD then steam is at fault.
you dont get it clearly...
he literally told you his computer has no issues while steam isnt running, so that means every other program on his computer doesnt cause an issue... ie computer has no issues.
steam comes along and causes an issue... ie steam is at fault, not the computer.
your going to have to accept the facts.
if steam is the only thing that triggers the BSOD, then it is a steam issue.
steam is obviously doing something that the hardware/driver or w/e cant handle.
doesnt matter, its common sense.
the OP hasnt commented on this thread since nov 15th, highly doubt he will be commenting any time soon.
Thank you for your help!
I come back here everytime that steam crashes, so around ones a week.
- Let me ask this, how come steam works fine for 1 week after reinstalling it, if it is hardware or driver related? shouldn't it then just crash everytime I try to run it?
- And I have a dual screen setup, so when it crashes one screen freezes and the other just goes black, so I cant remember what the blue screen said when I only used one monitor.
- And I did the scan you asked about (SFC /SCANNOW) no errors
- And I have now done a memory scan, no problem there.
- And I to have a ASUS ROG Motherboard, So I guess I can look into setting it back to default.
But THIS DID NOT HAPPEN BEFORE THE NEW STEAM UPDATE, I have never had troubles like this with steam before.
I will let you all know if down clocking my pc helps. Thanks for all the suggestions.
I had two fatal crashes with reboot playing Hitman 2 a month ago, all of them in the same spot. So i avoided that spot and keep playing. I also played with a lot of other games without problem (GTA, Borderlands 2 and some other).
Then, a week after, Hitman 2 crashed again, and this time my system did not boot again. Dead.
After testing my rig one component at time, i found what was the issue : my videocard died. Probably it was already falling, and stressing it with a heavy game killed it.
So yes, it can be an hardware component that is failing and crashes the driver, and maybe Steam is stressing it too much. This include : Your PSU, CPU, GPU and RAM.
Can take a photo of the BSOD with your phone and post it here ? Usually there is an hint about the driver who crashed.
Steam library shouldn't stress any hardware components, but it do. There are many reports of innatural resource usage by Steam.
But of course can just be a coincidence.