Trouble With Steam (full support email request to Valve)
Hello. I am currently having an issue downloading the Scout, and the Sniper vs Spy updates. I have tried following all the steps on the “Download stalls at a certain percentage” support topic (https://support.steampowered.com/kb_article.php?ref=6966-IADH-1503), except for the router step requiring me to directly plug my computer into the modem. My computer is on a different level of the house from the router and modem, and is connected via household electrical wiring, so this step is not feasible. Everytime I try to run the game, it says “This game is currently unavailable,” and the problem remains stuck at download starting at 81%; so I have started this troubleshooting process courtesy of this page: https://support.steampowered.com/kb_article.php?ref=4595-WEXN-6831 . I have reached this step, which has now cause an error the support pages don’t seem to have documented. “If renaming the clientregistry.blob file does not resolve the issue, please exit Steam and delete everything under the Steam installation directory except Steam.exe, the ClientRegistryOld.blob, and the /SteamApps folder - this will force Steam to update when you log in.” This is the error window I receive when attempting to relaunch the direct steam.exe executable: “Steam.exe (main exception): Win32 StructuredException at 0043D0BE : Attempt to read from virtual address 0 without appropriate access rights.” I am using an administrative account currently. I have also noticed that every failed attempt creates a new file titled as such: “Valve_2009_6_12T6_11_55C0.mdmp” made at 1:11 AM and “Valve_2009_6_12T6_41_59C0.mdmp” at 1:42 AM. I just now noticed that “Valve_2009_6_12T6_45_4C0.mdmp” was created at 1:45 AM when I did not attempt to relaunch Steam. I have attached these files for your review. Fortunately I have backed up the files step 3 requested me to delete in a seperate folder not located within Steam’s root folder. For your consumption I recommend this be looked into, because I do not believe any troubleshooting steps should cause errors that as of June 12th, 2009 at 1:49 CST, have no currently accessible support topic. Seriously, troubleshooting a troubleshooting step?
6 months ago by cchausman