Problems with Games

[EneilShade]

Well, I posted here a while ago with problems running Bad Company 2. These problems, I assure you, did not stem from any sort of weak system. Just check out my computer's specs. I was having a very strange problem -- every little while, the game would just seize up on me and about a minute later, it would un-seize. I could then continue playing the game as though nothing happened (except I would be disconnected from the server by the time I came back). It usually happened about 10 minutes after I started playing, as in actually entering a server and spawning. The problem seems to be linked to how much load my system is under because the game never locks in the menu. I also did not immediately come to this forum to ask your help -- I have spent MONTHS trying to debug this problem. I will now (for your possible problem solving pleasure) post all that I have found:
-It is most likely not the graphics card. I had a GTS 250 before my 6870 that had the same problem.

-It is most likely not the RAM. I ran two full goes of Memtest86+ on it.

-I am assuming it is not load on the CPU that causes a seize -- things like Blender that take 100% of all six cores lead to no issues.

-The problems look to be directly linked to DirectX (still unsure of this point), because games like Killing Floor which run using graphics libraries other than DirectX do not crash.

-It is not my dual-monitor configuration. I have tested running just one monitor on each monitor.

-My sound system is involved in the crashing process. I noted that when I disabled my digital outs, the game took longer to crash. I then took this to an extreme and disabled ALL of my sound devices. No luck -- still crashed.

-It is not overheating. My hand can attest to this fact.

-I am assuming (again) that it is not the PSU because games like Killing Floor -- which still tax my system -- do not crash. I would think that a faulty PSU would cause a crash correlating to system load regardless of the graphics library you use.

-The only thing that is truly circumstantial is this: I am betting it is not the MoBo because, again, other games that do not use DirectX do not have this problem.

-I have tried a re-install of DirectX -- Windows won't let me. It says I have a newer or equivalent version installed.

-My computer only crashes when gaming, and seemingly only with games that use DirectX.

-The seizing happens the same way with all games, same time until seize, same time until un-seize.

-The BIOS is also unlikely to be the suspect -- I recently re-flashed to the newest version.

-I have tried multiple versions of my graphics drivers and uninstalled and reinstalled them repeatedly.

Funny thing is, when you read the above, I eliminate EVERY part of my computer as a suspect, meaning it must be gremlins, right? That is what I am coming to the conclusion of unless any of you have any other ideas.

Thanks so much in advance for helping one fellow so horridly stuck as I,
EneilShade

 

[Jazzel]

the problem was windows update: number KB917422

Uninstalling that windows update should fix the problem. If that aint the case you might have corrupted windows.. might want to do recovery or go back to the settings(few months ago) when it was working.

 

[EneilShade]

I would attempt that solution, were it not for the fact that KB917422 does not show up on my installed updates list.

Also: it is most likely not Windows. I had this problem when my old hard drive failed. I had to do a clean install of Windows, and it is still happening.

Edit: I have discovered more. It only happens when DirectX is drawing on a 3D surface.

Edit to Edit: Nope. It has started to happen to all sorts of things. It is getting worse.

 

[EneilShade]

Okay, more info. The crash rate is in no way tied to system load. I turned all the settings down on BFBC2, and it still crashed well within its normal crash profile. This makes me think even more that it is a software and not hardware problem. I have tired multiple times (even with restarts) to re-install DriectX on my computer, to no avail. It would seem that nothing can fix this problem.

I REALLY need your help!