Random crashes possible associated with vox

[guncrasher]

I removed my xtreme gamer sound card completely with drivers and havent had a disco since then.  using mobo/usb headset no problems in two days.  and yeah ventrillo rocks 

semp

[bustr]

Few years back I had to use a USB headset for the same problems but I had an earlier SB card in that system. Turns out the eairlier card was going bad so I replaced it with an X-fi card. That was with an earlier motherboard with a single core 3Ghz CPU. This issue with lockups during VOX has been a constant with the game as long as I've been playing over three different PC, 6 video cards and 3 different sound cards since 2002.

Some versions of the game or patches of versions have been solid. Some made pull my hair out or replace/upgrade the vido or sound card. Or just build a bigger badder computer all together. If Skuzzy describes his current game PC in an off hand remark and he's describing a completely new machine from just a few months ago and it's about time for a new game version. I know its time to get a bigger stick to beat the game with at my end........

[Ardy123]

Could TDRs be happening due to inadequate cooling?

I purchased some larger case fans...

Any tools to stress the gfx card?

[Chalenge]

After one month of flying Windows 7 32 bit the number of crashes of AH were 0. After two days of flying Windows 7 64 bit the number of crashes of AH so are 4. I dont believe vox is related at all but I do think networking is. It is possible it is tied to system latency. What I believe I am seeing is AH attempting to execute along some line and the system blocking the process because of a busy resource. In order to really find the source of the problem I suspect it is going to take a monitoring program of some sort which is beyond me. I have removed individual devices and drivers all the way down to the MB (still ongoing) as possible and I still have not discovered the source of the problem.

[bustr]

Read this:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;969028

When it happens use the hot keys and generate your own memory dump. You will then get a Blue Screen with the following message.

*** STOP: 0x000000E2 (0x00000000,0x00000000,0x00000000,0x00000000)
The end-user manually generated the crashdump.

When it is finished, see if Skuzzy might be interested in reading it. Or debug it with Windbg your self.

The article mentions some applets also if you can get to the desktop.