Lea nuestra declaración de privacidad en línea: Marca de tiempo del módulo con errores:Đ0000000 Nombre del módulo con errores: StackHash_0a9e Marca de tiempo de la aplicación:ĕ672d823 Nombre de la aplicación: quakelive_steam.exe I did what little I could with n00kie to try and work out anything that could be changed on the client to mitigate the issue but I don't think anything helped, there's one guy going round saying that upgrading to win10 solved it for him though if you wanted to take a stab in the dark yourself, at least the upgrade is still free at the moment. The one person who posted a full minidump for a crash revealed it to come from steamclient.dll which id have no access to source code for or even symbols so they can't debug it even if they COULD replicate the crash themselves, that's entirely in Valve's hands. Id : There is no evidence of any pin in any of our copies, no one is being stabbed, even passing over it with magnets is showing no sign of any pin.
So to quote QWIH kinda: is this bug known id? And will this be fixed in a new update shortly?įor the most part it's a case of, (abysmal analogy time!) :Ĭustomer : I have a copy of your gigantic haystack (of code), mine is bugged as there is this pin in it that keeps stabbing me, this is your fault, fix it, but you can't look at my haystack, you have to find the pin in your own copy, fix it, and then send the fix to me. I also tried to uninstall steam with quake live and install everything fresh again, but even that did not help. Only updated the video card driver when my first crash appeared approximately 2 days ago. No new programs have been installed or any new system changes. I never had this problem with the standalone version of quake live, but now with Steam all of a sudden i'm experiencing weird crashes.Īdditional Information 2:Đa9e372d3b4ad19135b953a78882e789Īdditional Information 4:Đa9e372d3b4ad19135b953a78882e789Īnd shortly after while trying to play again (45min after the first error)īeen playing on steam since the official 27 oktober release, but this error just started to happen like 2 days ago.
0 kommentar(er)
