• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

BSOD on Unreal Engine games!?

Ke0

Weaksauce
Joined
Oct 14, 2004
Messages
118
Ok for some reason on Unreal Engine based games, if I exit the game I blue screen and my PC resets, it doesn't do this for any other game, been playing HL2, Vampire: Bloodlines, some Quake 3, Doom 3 and I can exit them all no problmes, If I exit Unreal or Raven Shield it BSOD on me then my PC rests, I just started doing this, when I first installed UT2K4 it never did this.

Anyone know what's up? I passed memtest86 after running for 12 hours so it's not memory
 
Ke0 said:
Ok for some reason on Unreal Engine based games, if I exit the game I blue screen and my PC resets, it doesn't do this for any other game, been playing HL2, Vampire: Bloodlines, some Quake 3, Doom 3 and I can exit them all no problmes, If I exit Unreal or Raven Shield it BSOD on me then my PC rests, I just started doing this, when I first installed UT2K4 it never did this.

Anyone know what's up? I passed memtest86 after running for 12 hours so it's not memory

I'm having the same issue here as well. Never noticed it doing that until I put the last couple of updates on it (there is a brand new one out that I haven't got yet). The game plays just fine, but when I close out and quit, I get a quick BSOD and then the system resets.

I reformatted a few weeks ago because of this, but when I reloaded UT2004 back up I applied all the updates without testing to see if it still BSOD'ed on exit. I was thinking about doing a complete uninstall, and trying a virgin run to see if it does it again. Strange, whatever is causing it.

Ax
 
I got some questions I'll need to ask you, to help you help yourself.
1. what is you operating system?
2. Do you have an firewall running
3. Did you Try reinstalling directx?
4.Did you Try turning off any thing that auto updates ?
5. what resolution are you running in the games?
 
Crazy tech said:
I got some questions I'll need to ask you, to help you help yourself.
1. what is you operating system?
2. Do you have an firewall running
3. Did you Try reinstalling directx?
4.Did you Try turning off any thing that auto updates ?
5. what resolution are you running in the games?

1. XP
2. Yes
3. Yes
4. Of Course MS is evil ;)
5. 1280x1024
 
Crazy tech said:
I got some questions I'll need to ask you, to help you help yourself.
1. what is you operating system?
2. Do you have an firewall running
3. Did you Try reinstalling directx?
4.Did you Try turning off any thing that auto updates ?
5. what resolution are you running in the games?

Pfft....Yeah, checked all of this when I reformatted my whole system. :D

But like I mentioned earlier, I re-applied all the updates and patches to UT2004 without testing it virgin. It still BSOD's on me.

Ax
 
I was having ut2004 crash because of the fire wall not allowing connection to the online servers to fix this I stared the game in an window so I could see any pop ups saying connection blocked do you want to let blah blah connect clicked yes and save settings . the bods errors I've seen were caused by the that dam nview desktop manager that put its self down in the start menu by the clock after disabling it the bsods went away but I never had it cause restarts though. Also turn off the application controlled on the anti aliasing setting and the anisotropic filtering I set mine to 8 for the first and 4 for the second.
 
A quick search would have revealed that the BSOD is caused by DEP protection. Only way around it currently is by disabling DEP on start up (This of course is for you A64 owners).

I wish they would stickey this question as its asked about twice a month :(
 
Anyone know what's up?
Yes.....

It took me awhile to figure it out and put it all together. I used to play UT2004, RavenShield, etc. for hours with no problems. I played through all of Doom3 and HL2 without a problem, then went back to UT2004 and Raven Shield and started getting BSODs when exiting.....hmmm...thinking what had changed in my system......XP SP2. :) The only thing in my system that changed. It's SP2s DEP, which doesn't play well with Unreal engine-based games on Athlon64s. I disabled DEP and haven't had a single crash since. So if you're

1) getting BSODs at exit of Unreal engine-based games
2) using XP SP2
3) have an Athlon64

definitely try disabling DEP. It worked for me.
 
hmmm just noticed it started when I got Pro SP2 lol, I was so pissed I thought it was my ram and was gonna RMA it earlier today before I wised up and ran Memtest86 and passed easily. How do you disable DEP? I'm not a fan of having to wait 7 seconds for windows to load.
 
lol and I'm geting a64 setup next week that I traded for ,but I got the same error from what i listed on my xp 2700 system too till I did what I listed.
 
Ke0 said:
hmmm just noticed it started when I got Pro SP2 lol, I was so pissed I thought it was my ram and was gonna RMA it earlier today before I wised up and ran Memtest86 and passed easily. How do you disable DEP? I'm not a fan of having to wait 7 seconds for windows to load.

Check in Administrative Tools>Services,if it's in services just disable it.I'm not sure it's there,I haven't reloaded SP2 yet,but it's worth a shot.

Chris
 
Ah that solved the problem, thanks, you know this really should be a stickie, I'm sure this quesion has been asked many times and will be asked many times

edit: It's not a service

have to go to

Run
C:\boot.ini
/NoExecute=xxxxx to /NoExecute=Alwaysoff
 
Ahhh,I'll have to come back to this thread after I reinstall SP2.Thanks.

Chris
 
No Prob, thanks to those who told me it was DEP, and thank google for being google :cool:
 
Ke0 said:
No Prob, thanks to those who told me it was DEP, and thank google for being google :cool:

Ditto that. I tried to disable DEP exclusivly for UT2004 at first, but it still crashed. Once I disabled it altogether, things have been working great. Apprecaite the tips guys.

Ax
 
I was under the impression that DEP was a useful feature to have, so I would suggest turning it on and getting some 71.xx drivers or above. Makes the crashes go away and you can have DEP on. I should know, the same problem was screwing with me when I first built this baby.
 
I dunno exactly what DEP is, but I was getting along without out it in SP1, so I'm not missing it
 
Back
Top