• 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.

Weirdest thing ever

ManCannon

2[H]4U
Joined
Aug 9, 2004
Messages
2,451
I've been playing around with my new computer today, mostly playing UT2004, and I've ran into a very weird problem twice. When I minimize UT2004 with alt esc I can get back to the desktop just fine, but when I click on UT2004 and try to maximize it a weird blue screen with a bunch of characters flashes for a second, a loud sound thump comes out of my speakers and my computer restarts. I haven't encountered any other problems besides this. Anyone have any ideas as to what the heck is going on?
 
It sounds like your computer is blue screening on restore of that game but I'm not sure why. Get the latest updates for sure and then do the following:

Control Panel->System->Advanced Tab->Startup and Recovery settings button-> uncheck the automatically restart option. Now when your computer blue screens you can see what file is causing the problem and that could point us in the right direction to fix it.
 
Well I just got a GPF when I exited UT2004 and it restarted again then too. I'm gonna switch the automatic rebooting off now so I can see what the blue screen says. Thanks for the tip, I'll let you know what it says next time it happens.
 
Alright here's what it said.

It had a little blurb at the top then it said:

"IRQL_NOT_LESS_OR_EQUAL"

After that it said if this is the first time this has happened, restart your computer, if this has happened more than once, you may have improperly installed hardware or software. Hmmm, I have no idea what I could have installed incorrectly. Any ideas?

EDIT: This just keeps getting weirder. Now when I enter UT2004, my mouse and keyboard dont work to click through the "Nvidia: The way it's mean to be played" animation. If I sit through the whole thing I can work the menu, then when I select a game, my keyboard and mouse dont work again. WTF?!
 
Does the blue screen give any kind of file that is causing the problem, like a dll or something? If UT2004 is the only app this is happening with then I would say your game is borked and you should uninstall, delete the game directory, then reinstall. If other things are having problems then it could be related to your memory or drivers.
 
So far it's just UT2004. I have tried uninstalling and reinstalling, maybe I'll try that again. I'll be using the comp a lot more tomorrow, so maybe I'll be able to get some more info. I used it all day today and it seems to be just related to UT. Everytime I exit the game or try to maximize the game I get a blue screen now. I played HL2 for a while too and had no problems.
 
Last I heard IRQ not less or equal as a RAM problemo.
 
Have you Memtested your system? That can show you if it is a RAM issue, which at the moment it sounds like. Apart from that, you might want to reinstall the game as suggested. Check that all your devices are fine, you have the right drivers etc. Sometimes a driver problem can cause that issues.
 
What drivers might I have forgotten? I installed al the drivers that came with my motherboard, chipset drivers, audio drivers, network drivers, usb drivers. As well as the latest videocard drivers and my soundcard's drivers.

I planned to get memtest tomorrow to test that out. Anyway thanks for the suggestions guys.
 
sounds like an irq conflict between your sound card and your video card that neither of them likes one single bit. since the sound card can yell louder it apparently does, hence, "THUMP!"
 
starhawk said:
sounds like an irq conflict between your sound card and your video card that neither of them likes one single bit. since the sound card can yell louder it apparently does, hence, "THUMP!"
I like the way you put that ;)
 
:D humor defuses a situation easily... my only problem is that i tend to use too much of it.

and that most of my puns are baaaaaad.
 
I'm not sure if that's it. The computer seems to make a thump if I restart it or shut it down anyway. Plus I used this sound card and this video card with same drivers for a week on my old computer with no problems at all. Hopefully I can figure out what's going on today. If anything else happens I'll keep you guys informed, here's hoping I can get this issue solved.
 
what are your system specs? on my laptop it will randomly reset after that boot screen if i happen to use Coolmon. although i couldn't imagine ut2004 having problems with the chipset / cpu.
 
AMD 64 3200+ 754
DFI Lanparty UT nForce3 250Gb
GeForce 6800 NU
1 GB PDP PC3200 2225 RAM
80 GB SATA
Audigy ES Soundcard
Lite-On CDRW/DVDROM
 
Alright, well I've been playing around a little more and here's what I've found. I have two games installed on the system so far, HL2 and UT2004. So far UT2004 is the only thing that's been able to bring up the bluescreen and it does it often. I've been able to make it bluescreen too. All I have to do is minimize the game, and leave it minimized for a bit, then try to maximize it, and boom, BSoD. Now if I do the same thing in HL2, keeping it minimized for a while then maximizing it, nothing happens. It just comes back and plays just like it did before.

I don't know what's wrong, but it seems like UT2004 isn't meshing well with my new system. Sucks though, because UT2004 is the game I play most often :(.
 
hmmm... from what i understand, main difference between the 2 games is directx.

apparently, hl2 is all opengl- no directx whatsoever. not sure of the differences, or even wtf opengl is, but it certainly works.

ut2k4 is going to go with the somewhat easier and more widespread use of directx. directx 9.0 i believe.

i have no idea how (if) this could be related to the problems... but i thought it would be good to throw it out there.
 
Really? I thought HL2 was a DirectX game like UT2004. I thought the only recent game that used OpenGL was Doom 3. Hmmm, well I'm installing Far Cry now to see how that fares.
 
:rolleyes: figures i'd get them confused...

truth to tell, i'm not even sure what opengl is or how it works.
 
Yeah I tried that a few times already, no difference.I've tried it patched with no cd and no patch with cd, and both times same problems. Installed Far Cry and it had no problems, same as HL2. Pretty ironic though. My old computer ran UT2004 alright, but I wanted to build a new computer specifically for games and when I do, the only game that doesn't work is my favorite game :(.
 
OK, it just happened again, and this time in another game. Just installed Vampire the Masquerade: Bloodlines, and after 20 or so minutes I got the BSoD. I must have been blind before because I noticed the .dll this time. Here's exactly what it said:

"nv4_disp.dll - Adress BFA110D3 base at BF9D3000, Date Stamp 00000000"

So that's my display driver right? I have the latest driver's from nvidia. And the card seems to be functioning beautifully. HL2 runs like butter at 1600x1200.
 
Mem address conflict? What's that? I assume it has to do with my RAM right? But I got no errors in memtest86. What should I do?
 
means that 2 progs are trying to access the same area of ram. memtest probably woudn't catch it (don't know much about memtest, never used it) because there isn't a problem with the ram itself. it's simply that 2 programs are set to use the same area in memory.

you can fix this very easily in device manager, although it is a little long to do.
 
Well I don't care how long it takes, I'll do it. If it's too much trouble to type out, do you perhaps know a site that could explain it to me?
 
starhawk said:
means that 2 progs are trying to access the same area of ram. memtest probably woudn't catch it (don't know much about memtest, never used it) because there isn't a problem with the ram itself. it's simply that 2 programs are set to use the same area in memory.

you can fix this very easily in device manager, although it is a little long to do.

I will be surprised if you can fix this using device manager. Please post what info you have, I would be interested in reading it. In my opinion you should uninstall the Nvidia display drivers, use driver cleaner to wipe them out completely, then reinstall with the latest version. If that does not fix the issue then you may want to try an older version of the drivers and see what happens.
 
simple... enter device manager, write down all the i/o mem addresses for every device (look under the "resource" tab) and find the two that conflict. figure out where there's an empty space that can be used, and switch one of them to that empty space.
 
Also, I don't know if this makes any difference, but I just crashed with UT2004 again and I noticed there was no reference to that .dll (why I didn't see it before). It just said "STOP" and then a bunch of letters and numbers.
 
its a RAM problem, sounds likea bad stick.

I had the same problem, put in a new 512 of Mushkin and it fixed the problem

my old ram was some no-name brand i got at a computer show, ha i've learned my lesson :)
 
133 said:
its a RAM problem, sounds likea bad stick.

I had the same problem, put in a new 512 of Mushkin and it fixed the problem

my old ram was some no-name brand i got at a computer show, ha i've learned my lesson :)

that's what i'm thinking... but what the comp spits out will tell us for sure.
 
I don't have my printer hooked up. Don't have any ink for it anyway. Wait, you can print blue screens?

Oh well, I'll just copy it down. Do you want all the numbers after "STOP" or is there something else I should be on the lookout for? I guess I'll have to RMA the RAM :(.

EDIT: About the RAM though, I did notice that it's timings were 2325 instead of 2225 in memtest86 if that means anything. I just assumed that was because I hadn't tweaked it yet though.
 
shot in the dark but have you tried lossening your mem timings? cuz i had some kingston mem that didnt even run at stock stable, i have a feeling its the ram. in my ocing travels i pushed my ram to far and got both the IRQ conflict crap and the stop 0x0blah blah blah BSODs and going back to a less intense setting fixed the problem. also might wanna try putting just one stick at a time in. also try running prime 95 if that fails its def the ram settings or the ram it self. Prime stresses the mem much more like its stresses in games and crap so it will probly tell ya.
good luck
 
I ran prime95 for 15 mins with no errors, but I'm going to run it a lot longer a little later. At the moment though I have more information.

I just got a BSoD with UT2004 again. But this time, when I went to play the game I got a message that my cd key was invalid and I'd have to reinstall my game. I got this same message once before after it happened to. I don't know if that means anything, but I figured I'd keep everyone who's trying to help me informed.
 
ManCannon said:
I don't have my printer hooked up. Don't have any ink for it anyway. Wait, you can print blue screens?

i imagine that [PrtSc] would function to either copy the bluescreen into memory or (since it's dos) simply print it out.

Oh well, I'll just copy it down. Do you want all the numbers after "STOP" or is there something else I should be on the lookout for? I guess I'll have to RMA the RAM :(.
all the numbers, letters, EVERYTHING.

EDIT: About the RAM though, I did notice that it's timings were 2325 instead of 2225 in memtest86 if that means anything. I just assumed that was because I hadn't tweaked it yet though.
or quite possibly your computer's ram is messed up.
 
"*** STOP: 0x0000000A (0x9 D086240, 0x00000002, 0x00000000, 0x8051EC1C)

Beginning dump of physical memory
Physical memory dump complete"

And of course there's still the "IRQL_NOT_LESS_OR_EQUAL" at the top.
 
This sounds an awful lot like memory problems. This happened to a friend of mine's laptop. At first it's only some small weird behavior, but it gradually gets worse; the system becomes more unstable, corrupting your files slowly until suddenly the system won't boot. Replacing the memory did the trick.
 
Back
Top