Closed GoogleCodeExporter closed 9 years ago
On second thought I think I know what the issue might be, but I don't think it
is a major factor.
Maybe around 3 or 5 weeks ago I was playing a different game through Steam(Halo
was not installed at this time). I alt-tabbed when I had died and was going to
unpause a Youtube video (which I was watching before the game actually
started). Two seconds after doing so Windows BSOD'd. When logging back into
Windows, every game on my Steam list that I had installed would crash on load
or display weird effects. Source engine based games in particular would crash
on load saying "Invalid Access to memory location" (involving DEP if I remember
correctly) An example of a game displaying weird effects would be Sonic
Generations. While the game worked fine, there was no UI, I couldn't see it at
all.
Sometimes these games were fixable by validating steam cache, but there were
some cases where validating cache, deleting the gcf file associated with the
game, and reinstalling steam did not fix it. It was basically a random chance
of being fixed or not. Some crashes of hl2.exe reported the fault module of
"StackHash_db93" but this seems to change every other time a crash happens.
What I am thinking could possibly be the problem is that because of the BSOD,
certain pieces of my DirectX install/Windows/RAM could have gotten corrupt, but
one thing that has me think otherwise is that the games, when actually fixed,
work as intended with no crashes to speak of. No glitches of any kind. And as I
said before, Halo PC and Halo Custom Edition work just fine without the DLL in
it. Perhaps the d3d9.dll (which if I remember what you said Kornman a long ass
time ago) the DLL is basically a fake that Halo loads thinking it's DirectX but
instead is OpenSauce) uses something from DirectX/Windows that is corrupt, and
is not letting it run because of that.
Original comment by codebr...@codebrainshideout.net
on 24 Jun 2012 at 2:27
Going to assume this is fixed by revision 830474666259 as we don't use d3d9.dll
anymore. Let us know if this still happens after the next official release.
Original comment by TheFieryScythe@gmail.com
on 5 Oct 2012 at 11:45
Original issue reported on code.google.com by
codebr...@codebrainshideout.net
on 24 Jun 2012 at 1:39