PDA

View Full Version : UT 2004 BSOD On Exit


Blue078
10-24-04, 09:04 PM
PNY 68GT
MSI K8N NEO2/3500+/ 2x512mb Crucial Ballistix/Audigy2

I'am getting BSOD, then reboot when I exit ut2004 ?? Everything else is just fine. Happens with VC OCed and also at stock

Tried the official NV drivers, then 65.73..then 66.81. Also tried a fresh XP install on a spair HDD with nothing but XPSP1 and UT2004...same BSOD on exit. Tried with UT 2004 unpatched, and patched.

This doesnt happen if I use my old FX 5950, it's only one game, and this card.


Any ideas!!!

Thanks

bkswaney
10-24-04, 09:17 PM
It seems this is a AMD problem.
I'm sure someone can help u out. :)
I've seen a lot of post on this error.
Try doing a search on the forums.

circuitbreaker8
10-24-04, 09:46 PM
It seems this is a AMD problem.
I'm sure someone can help u out. :)
I've seen a lot of post on this error.
Try doing a search on the forums.


Wow, do you diss AMD in every thread you go to?

Anyways, I got this on my intel system a lot, and i found out it was due to the ram voltage.

bkswaney
10-24-04, 11:00 PM
Wow, do you diss AMD in every thread you go to?

Anyways, I got this on my intel system a lot, and i found out it was due to the ram voltage.


Not hardly.
As a matter of fact I'm building a 64 now. :)
I only stated I "have" seen a lot of post on this.
I just noticed most all seem to be AMD rigs.
I love AMD. :)

Unreal426
10-25-04, 12:11 AM
This happened to me as well on my K8N-E + 3400+ in windows XP

I'm interested to see how this is fixed as well.

saturnotaku
10-25-04, 05:31 AM
We have a search function here for a reason. (http://www.nvnews.net/vbulletin/showthread.php?t=36541&highlight=UT2004)

Decimator
10-25-04, 07:50 AM
I was getting that for a while (BSOD on closing down UT2K4) so started closing it down "gently" Forfeit>back>Exit UT2004>Yes rather than Exit Game, then I got a better PSU and replaced a stick of RAM that was going bad and that fixed it.

Blue078
10-25-04, 08:25 AM
If it were PSU, or ram then why doesnt this happen in the same rig, but with the 5950 installed ???

And it's hard to belive that a 3 month old 500w Zippy/Emacs PSU isnt enough.

But none the less I'll stick some other memory in and rule that one out.

Blue078
10-25-04, 08:33 AM
We have a search function here for a reason. (http://www.nvnews.net/vbulletin/showthread.php?t=36541&highlight=UT2004)

Thank You.
I've seen that, if you had taken time to fully read my first post, you would have noticed It even happens with SP1, which is all I use, being their are still a lot of bugs with SP2 :)

And again if it were an XP or the rest of my system problem, would you be so kinda as to explain why this doesnt happen with the same drivers and my FX 5950 ultra ??

Blue078
10-25-04, 08:36 AM
I was getting that for a while (BSOD on closing down UT2K4) so started closing it down "gently" Forfeit>back>Exit UT2004>Yes rather than Exit Game, then I got a better PSU and replaced a stick of RAM that was going bad and that fixed it.

Humm.. :) Your way of exiting does work.

It's just bugging the _ _ _ _ out of me, to know what part of the 68GT is couseing this bug.

Decimator
10-25-04, 10:58 AM
If it were PSU, or ram then why doesnt this happen in the same rig, but with the 5950 installed ???

And it's hard to belive that a 3 month old 500w Zippy/Emacs PSU isnt enough.

But none the less I'll stick some other memory in and rule that one out.

6800's are pretty well known for their higher power requirements, you could also make sure that there isn't anything else connected to the connector you've got going to the 12v plug on the 6800, it probably has to do with the fact that shutting down the game powers down the hard drive and the 6800 at the same time (and prolly the CD-ROM too), which could put a spike on your 12V rail and cause the crash. Another way to test for RAM problems would be to use something like Windows Memory Diagnostic or Memtest86+ and let it run for half an hour or so:

http://oca.microsoft.com/en/windiag.asp#appendix