Author Topic: DxDiag.txt (Read 367 times)

bit · « **on:** October 21, 2005, 12:28:25 PM »

Keep getting CTD, and get the TCP error when I login.

I did remove the USB mic, so lets hope that fixes the CTD.

If im the only one getting the TCP error, its probobly my crazy firewall.

My DxDiag.txt

RTR · « **Reply #1 on:** October 21, 2005, 12:48:59 PM »

bit, run a ping plot. Get it at http://www.pingplotter.com ( I think).

Sounds like you are getting slowed down somewhere between your pooter and HTC. Ping plotter can help you determine where you are losing packets in the route to HTC server.

My experience has been that its not generally a problem with HTC or your computer, but rather, the route the info takes through the web via your ISP.

hope you get it sorted out.

cheers,
RTR

Skuzzy · « **Reply #2 on:** October 21, 2005, 01:34:15 PM »

A firewall can definately cause this. Easy to verify though. Disable the firewall and try the game.

bit · « **Reply #3 on:** October 21, 2005, 01:51:39 PM »

I disabled the firewall, and did not receive the error.

I did get a CTD after unpluging that USB mic.

I fly without firewall, lets hope the CTD ends here

bit · « **Reply #4 on:** October 21, 2005, 01:54:21 PM »

bit · « **Reply #5 on:** October 21, 2005, 04:03:43 PM »

Crashes still, even with no firewall and no USB mic.

In event log I got:
Fault bucket 236780066.

Faulting application aceshigh.exe, version 0.0.0.0, faulting module aceshigh.exe, version 0.0.0.0, fault address 0x000b1ee6.

But I guess that wont help :/

The address(?) 0x000b1ee6 appears mostly, but also have these:

Fault bucket 236752356.

Faulting application aceshigh.exe, version 0.0.0.0, faulting module aceshigh.exe, version 0.0.0.0, fault address 0x0004f351.

Faulting application aceshigh.exe, version 0.0.0.0, faulting module aceshigh.exe, version 0.0.0.0, fault address 0x0004b37f.

Skuzzy · « **Reply #6 on:** October 21, 2005, 04:12:26 PM »

Have you overclocked anything? Also, might be a small things, but I think Creative has a newer driver for the Audigy card.

I hope you did not load the Creative utilites.

bit · « **Reply #7 on:** October 22, 2005, 06:55:41 AM »

No overclock. I thought I had the new SB driver. I down loaded from their site last week.

Maybe I d/l the wrong one :/

Now I have got bluescreens a couple of time, when I copy files from my PC to the gateway PC. So I must have some generall problem with the PC now.

bit · « **Reply #8 on:** October 23, 2005, 02:50:53 PM »

Reinstalled windows and AH. Played for an hour or so and BANG CTD again

Auto updating sound bastard drivers from creative site. Running out of ideas here...

Im not 100% sure, but some how I think the CTD always hapends when im closing in on a bad guy ?

38ruk · « **Reply #9 on:** October 23, 2005, 10:23:48 PM »

Do you have motherboard monitor , or any other utility to mesure how hot the cpu is getting? Could be that the heatsink has some crap in it , or that the thremal past has deteriorated . If you go into the bios you should be able to see the temps at idle , but that doesnt help you at load . Worse come to worse , you could pull the side off it and see how hot the heatsink is . GL 38

bit · « **Reply #10 on:** October 24, 2005, 10:09:43 AM »

I monitor the temps on cpu and video.

I also try with reinstalling AH2.

The CTD is not so that the game dissapeares instaneniously.

First I can see the AH2 fullscreen window. I see a toolbaar. The window is light grey and then black. I can still hear the sound of the game. Then I get a microsoft error report window. When I press cancel or send, then im back at the desktop.

It also seems to hapend alot when im about to land.

Last time I had maybe 3-4 sorties and landed 1 kill. When I had 3 kills, the crash came at final aproach, wheels down and all

Any tests or logs or audits one can turn on ? I am running XP.