Then went into add/remove default programs and removed IE 8. I Uninstalled IE 11 from the updates, which rolled it back to IE 8. That is the one Steam error that QL might be able to do something about by not checking on it during gameplay, so hopefully if they can't actually solve it completely if they're already using the changed auth system rust/cs moved to, then I hope they can do that for the next update, and as some of the problems reported have been a real pain I'm very much hoping any update won't be much longer as it's already been a month and a half. This system had IE 11 on it, It just stopped opening and logging these event id 1000 errors. Rust had problems with it too subsequently I've seen. It was a huge problem in CS at one point apparently but Valve changed the authentication system and that solved it for most. this is pretty common atm for some reason, but some people still seem to just never get it. SOme one in the server said there was a message that said "STEAM COULDN'T Authenticate." So damn sick of it. I am just about ready to abort the game and go over to UT. Originally posted by ^6☼ Deathrow ☼:You are right. Makes no sense.Īnd which settings do you mean, qzconfig?įaulting application start time: 0x01d133995d7be9ed Report Id: 8fe425e5-9875-11e5-992b-082f8c5031b1Ĭ:\Program Files (x86)\Steam\steamapps\common\Quake Live\quakelive_steam.exeĪnd this is after Win 7 pro reinstall and a new Graphics card(Asus GTX 970. Faulting application name: quakelive_steam.exe, version: 0.1.0.739, time stamp: 0x5642185aįaulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000įaulting application start time: 0x01d12c7acdaa3d7cįaulting application path: C:\Program Files (x86)\Steam\steamapps\common\Quake Live\quakelive_steam.exe
0 kommentar(er)
