The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
This is getting rediculous[Computer problem]
Khavall
British ColumbiaRegistered User regular
British ColumbiaRegistered User regular
Hey there, some of you may remember me from such thread topics as "My computer crashes when trying to play HL2Ep1, HL2 Ep2, or TF2" and the later "It still won't run those and after getting to testchamber 19 in portal now it crashes on that game too"
Well that problem wasn't ever resolved, and I started playing on another computer for those. But now a new problem arose.
This computer stopped running old-school HL2, which I have beaten before on this computer, and I got to ravenholm this time before it suddenly started having an engine error of "Internal Driver error: Direct3d()" or something like that(It flashed the message before BSODing with some shit about a memory error and ati3duag.dll messing up like it did with the other games. Now here's where it starts getting fun.
Steps I've already taken to try to resolve this matter:
Uninstalled and Reinstalled/updated all Drivers.
Updated DirectX
Ran the DirectX diagnostic tool and everything checked out
Ran the MS memory checker and everything checked out
Reseated my memory
Virus scan + spyware scan both came up clean
So here is a game that has worked for a year.
Now it doesn't.
Everything tells me the computer is working fine, and other games work fine, but any source game and BSOD.
Ideas?
Now, I am on the lower end of the spectrum, I'm playing on a laptop with an ATI Mobile 200M, so I took TF2 and the episodes not running on this machine as ok.
But they all run perfectly on my other system with an old Geforce 4200(I'm building a new computer this summer, so I won't be 5 years in the past for long!) and HL2 original I know has worked on this system, which is when it starts getting frustrating. 2 gigs of ram as well, if that matters.
Well that problem wasn't ever resolved, and I started playing on another computer for those. But now a new problem arose.
This computer stopped running old-school HL2, which I have beaten before on this computer, and I got to ravenholm this time before it suddenly started having an engine error of "Internal Driver error: Direct3d()" or something like that(It flashed the message before BSODing with some shit about a memory error and ati3duag.dll messing up like it did with the other games. Now here's where it starts getting fun.
Steps I've already taken to try to resolve this matter:
Uninstalled and Reinstalled/updated all Drivers.
Updated DirectX
Ran the DirectX diagnostic tool and everything checked out
Ran the MS memory checker and everything checked out
Reseated my memory
Virus scan + spyware scan both came up clean
So here is a game that has worked for a year.
Now it doesn't.
Everything tells me the computer is working fine, and other games work fine, but any source game and BSOD.
Ideas?
Now, I am on the lower end of the spectrum, I'm playing on a laptop with an ATI Mobile 200M, so I took TF2 and the episodes not running on this machine as ok.
But they all run perfectly on my other system with an old Geforce 4200(I'm building a new computer this summer, so I won't be 5 years in the past for long!) and HL2 original I know has worked on this system, which is when it starts getting frustrating. 2 gigs of ram as well, if that matters.
Khavall on
0
Posts
Well those errors have meaning ya know, what was it? Might have too much crap going on in the background that you didn't before and don't know about. I swear mcafee pisses me off so much, I'm too lazy to actually adjust it to not pull this shit but if it's scanning when I'm trying to play a game, it's crapville
I'm fairly sure I just got the same error I was getting before... so
STOP: 0x0000008E (0x00000005, 0xE7B006B6, 0xA7FCF8EC, 0x00000000)
Which is a memory error. Which I would've posted except that I've checked the memory, switched the memory between slots, and reseated the memory, and it has no errors and it's securely in the memory slots.
Debug tool gets me:
The error before the BSOD I can't say what it was, because I only saw it flash up quickly before disappearing before the BSOD, and I don't want to crash my compy the 8 times it would take for me to read and write down the whole error
Oh, also I cut down all non-MS services and programs on startup except for Punkbuster and Steam, and I just had turned the computer on, so I doubt it was a background program.
Not sure if that means anything horrible, or if that's the problem, and it tells me to run a diagnostic to fix the problem. Which totally doesn't fix the problem.
Ok, I fixed the NET counters, so I'll see if the game works now.
I upgraded the RAM a year ago, reseated it, switched nodes, and checked it for errors.
New error though:
when it closed, the BSOD was:
Which tells me Windows SP1 is having problems with my display adaptor, but I'm running SP2. So not much help.
Or it tells me there's a memory problem, which the diagnostic tool says is not true, or there's a problem with my VCard drivers, which I totally uninstalled and reinstalled and made sure were upgraded. Now, I am running catalyst and I remember seeing something about something something catalyst. Are they like, bad drivers or am I just making up stuff so that my problem makes sense?
Hopefully I can string it along for another semester if I don't stress it out too much, because I should have funds by then to build a gaming tower, and then I plan on totally wiping the laptop and turning it into a portable studio.
Well, thanks. Stupid computer.
Check out my band, click the banner.
IF that doesn't help I'm shooting the damn thing.
Crackle
Pop