Game Freezing when using vox ...

[SlapShot]

At times, if I press the button to use squad vox or local vox, the screen freezes for like 5-10 seconds and then will recover.

At other times, I will try vox, the screen will freeze as described before, but when it un-freezes, it tells me that it has reset all my graphic setting to the minimums. I have been running full blown graphic settings for some time now (1024 high res too) and always run 59 FPS.

Last night I had the same problem freezing, but this time I crashed to the desktop when AH released itself. When I came back into the game, the graphic settings were all set to minimum.

Anyone else experiencing this? ... Skuzzy, any ideas?

[FLS]

I get a freeze the first time I push the button, after that it's fine. Same with film.

[Skuzzy]

If the frame rate falls too low for a given period of time, the game will revert back to lower graphic settings.

Freezing with VOX is normally caused by a few things.

1)  System resources too low causing Windows to have to swap out processes to make room for VOX.
2)  Too many dropped packets on the connection back to your computer causing a long delay in establishing a VOX connection.
3)  Too many devices sharing an IRQ (interrupt) with the sound card.
4)  Too many sound devices.


Generally, one, or more, of the above is the culprit.  Send me a DXDIAG output SlapShot and I'll give it a going over.

[SlapShot]

If the frame rate falls too low for a given period of time, the game will revert back to lower graphic settings.

Freezing with VOX is normally caused by a few things.

1)  System resources too low causing Windows to have to swap out processes to make room for VOX.
2)  Too many dropped packets on the connection back to your computer causing a long delay in establishing a VOX connection.
3)  Too many devices sharing an IRQ (interrupt) with the sound card.
4)  Too many sound devices.


Generally, one, or more, of the above is the culprit.  Send me a DXDIAG output SlapShot and I'll give it a going over.

Thanks Skuzzy ... email sent with DxDiag.

[icepac]

I vote #3.

Sadly, it gets harder and harder to control which IRQ's a device will use since the advent of ACPI.

In the past, I had to actually flash my bios with one that allowed me to disable ACPI so I could manually assign IRQs to devices and I'm not sure you can run vista or newer OS's without it enabled.

In Winxp, you had to push f5 during install at the prompt for installing raid drivers (at the beginning of install) and keep hitting f5 when it asks for recovery console....then select "standard computer" unless you happen to have a "C-step" pentium (rare).

This is a pretty extreme measure.

Easier is to disable in the bios whatever things you are not using to free up resources that may be sharing irqs.

If you don't use a parallel port, serial ports, firewire 1394, or ps2 keyboard and mouse......disabling them might help.

Just make sure you remember that you disabled them in the bios should you decide to use them later.