Log in

No account? Create an account

Previous Page | Next Page

EDIT: Downloaded a new graphics card driver, and so far it's working.. *knocks on wood* here's hoping that was the only issue. :/

Alright, as usual, my disclaimer that I'm Really Not Good with computer-type stuff when it comes down to anything beyond, like, typing and playing on them. So this may seem like a stupid question, etc etc., but I hope y'all will help anyhow and not mock. :/

Anyhow, here's the situation. Last night I was playing some Sims 2, and suddenly my screen started flickering, getting way too bright, flickering some more, that sort of thing. I ended up having to shut down, and I shut down the computer and monitor for the night, figuring that it was probably this monitor dying on me now, since for some reason I just can't seem to keep my monitors running for very extremely long.

So today, I boot up my computer, and everything's hunky-dory so far while checking my email and such, browsing the interwebs, etc. But when I try to boot up Sims 2 again, I get the following message:

Failed to find any DirectX 9.0c compatible graphics adapters in this system! Please make sure you have a DirectX 9.0c compatible graphics adapter and have installed the latest drivers provided by the manufacturer. The application will now terminate.

So... I'm assuming this means that some hardware somewhere has gone kaput? Would that be my video card? Or... is it something else? Maybe a bad driver? Anyone who can suggest possible (or probable) problems and solutions? Please?


Nov. 9th, 2008 05:13 pm (UTC)
Didn't reinstall DirectX, although I did check it with ... er.. whatever it is you run in the "run" command to check directx, and it said it was okay, no files missing.

I *did* install a nice fresh driver for my ATI card, and it's now letting me play, so I'm *hoping* that the only issue was my old driver suddenly deciding to go wonky for some reason? Computers, they baffle me.

Nov. 10th, 2008 02:03 pm (UTC)
A bad driver could cause exactly this problem, and fixing the driver has fixed the problem, so I suspect the driver was the whole problem.

If it happens again, start worrying. Until then, it's fixed.