Crashes in Swat4

Associate
Joined
22 Aug 2006
Posts
35
Location
UK
Hi,
I have recently just upgraded my cpu from a Athlon 3200 Venice to a Athlon 4000 Sandiego.
Was very happy and all went well until I noticed that I could not complete a night of swat4 and it would crash at random but only in swat.
Sometimes I would manage a whole game and other times it would be loading into the server and lockup.
When it does crash it is not a normal BSOD but a complete lockup ingame with a high pitch squeel that would kill my ears,from that I would have to do a reset to get it to reboot.
I have checked with the DirecX diagnostic test(which was ok) and done a re-install of DirectX to latest version just in case.
rechecked my sound and gfx card drivers and chipset drivers are up to date
Checked IRQ are all ok and seem to be but if anyone would like to verify as I am not totalt familier other than the gfx and sound are on seperate IRQ and do not share with any other thing.
Checked all my other games and it only crashes on this one.BF2.COD2.Pasific Assault.Farcry.HL2.DOD-Source to name a few.
I have even gone as far as uninstalling my sound card and using onboard to see if that helped but no go.
I would let it go as just swat4 being badly coded but on my 3200 venice it ran just fine and to be honest I love the game too much to just walk away from it.
Any help or suggestions would be very welcome.
Thanks
Stev0
 
SWAT4 has slight stability problems, for me it was kicking back to desktop though.
 
At a wild ghess could it be an incompatability issue between the new cpu and the motherboard and is there any way of confirming this without buying a new one,also is there any way of testing the cpu other than prime95 or is that as good as it gets.
I have run Prime95 and SuperPI and they both come back ok.
The only other thing is that the motherboard has always had temp reading issues that apparently stem back to the bios but doesnt affect all but enought to create a few dozen threads in the msi forums.
when it does rarely get the correct temp it will read 35c idle and 45c full load,but all other times it reads 45c idle and 58-60c full load.
I am quite comfident that it is a bios missread but could this make windows wigout and shut down for safety.
 
If it was a compatibility problem you'd know it in other ways and other games would have issues too. If the CPU was running at 60 under load then it could cause problems but again you'd notice it in other games. Is your CPU detected properly in the POST screen and with CPU-Z?

You have quite an old motherboard there so a BIOS update might help, such as later versions adding support for E4 and E6 revision CPUs.
 
Tetras said:
If it was a compatibility problem you'd know it in other ways and other games would have issues too. If the CPU was running at 60 under load then it could cause problems but again you'd notice it in other games. Is your CPU detected properly in the POST screen and with CPU-Z?

You have quite an old motherboard there so a BIOS update might help, such as later versions adding support for E4 and E6 revision CPUs.

Yes the 4000 is detected properly in post and cpuz and I am using the latest 1.C bios for the motherboard.
I would worry about the temps but I use a zalman copper flower cooler that is not even warm under full load so I am 99% sure it is not a temp issue.
However is it possible that swat4 is executing some kind of code that just is not present in all the other games,just a ghess.
Would it be worth taking a step back and maybe re installing my old 3200 venice to see if it settles out on swat?
 
Swat is buggy for some people who couldnot get pass the logo and got a white/black screen with sound still playing, when i had that i went to swat forums and found out what it was not sure what i did but it worked, it was a while ago, best go to their forums really

Q
 
queamin said:
Swat is buggy for some people who couldnot get pass the logo and got a white/black screen with sound still playing, when i had that i went to swat forums and found out what it was not sure what i did but it worked, it was a while ago, best go to their forums really

Q

Yeah I did try that,I spent a couple of days going through the swat4 forums but most of it was stuff I had already done like my 1st post.
Just annoying how its all gone south since the cpu change.
 
Might be a stupid question but have you tried uninstalling swat 4 and reinstalling it with all the patches?? If I ever have issues with games its usually easier and quicker just to reinstall and see if that helps and atleast them you know its a fresh install with no corrupt files.
 
dale1uk said:
Might be a stupid question but have you tried uninstalling swat 4 and reinstalling it with all the patches?? If I ever have issues with games its usually easier and quicker just to reinstall and see if that helps and atleast them you know its a fresh install with no corrupt files.

Yes I have tried re-installing the whole game from clean,I even went as far as re-installing all of windows as well at one point just to prove to myself it wasnt something i had done wrong.
Unfortunatly neither worked.
 
With all the tests done i can only come to one conclusion that the motherboard is out classed by the new cpu so i am thinking of moving up to nforce4 pci express which is a bit earlier than I planned but anyway.
Would anyone have a good sugestion for a new motherboard to match up with an athlon 4000.
 
Just a thought, does it do it in single player aswell or is it just when your online? My bro has the same motherboard and cpu with a 6800 ultra and all his games including swat 4 work flawlesly. Cant see the motherboard being outclassed by that cpu, if that was the case it would affect more than just swat 4. Have you tried putting the 3200 back in to see if it works then?? Worst case is uninstall everything inc windows, reinstall xp and swat 4 only ( inc all drivers) and see what happens then. May seem like a real pain but you'll have to do the same if you end up changing motherboards.
 
Not 100% sure but will try and find out and post the version. One thing I do know is that he's had that cpu and board for apporx 1 year now and its worked fine from day one so quite possibly is not the latest one. The board has the Live Update so flashing the bios is very simple to do, so maybe worth dropping back a version or so and trying that.
 
Well now I am very very confused because during single player mode it did lock up but I was still able to ctrl alt delete out and view the crash report.

Fault bucket 204982065.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

and also

Faulting application swat4.exe, version 1.1.34688.0, faulting module dsound.dll, version 5.3.2600.2180, fault address 0x00009d40.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Now I am lost.
Anyone come across or understand this one please.
 
I had the exact same problem, would stall with a high pitched scream, and a hard reset was the only way out.

Bought some decent RAM and havn't had a problem since!
 
Axel40 said:
I had the exact same problem, would stall with a high pitched scream, and a hard reset was the only way out.

Bought some decent RAM and havn't had a problem since!

Well Im gald that I am not alone but I dont consider my ocz platinum as suspect so far with it only affecting this one game and not heavier memory hog games like BF2.
I have installed the latest release of directx that was linked,thanks
Just have to give it a go again and see.
 
Yeah just saw your spec in your sig after i posted! Strange alright. I had some crap TwinMos stuff, got some ballistix and the problem went away immediately.

Let us know how you get on..
 
the only thing that crosses my mind is if running 4 sticks of ram is having any issues cos the new cpu also use a different memory controller.
Just a ghess
 
Back
Top Bottom