BSOD when closing UT2004
  1 / 4    
This seems to be a problem related to AMD and Nvidia. Every driver after 61.77 crashes my system with a BSOD stating...

IRQL_NOT_LESS_OR_ EQUAL bla bla bla

I'm also aware of the work arounds with DEP thing or running the game under OpenGL but I shouldn't have to since it works fine with driver 61.77 (the previous official if I recall correctly). Could Nvidia fix this bug please. It's real and I can point to other threads around the WEB dealing with the same problem.
Besides that I have no other issues...

EDIT:
Here's my specs
Athlon64
Asus K8N-E DX
Gainward 6800GT
WinXP Home SP2
This seems to be a problem related to AMD and Nvidia. Every driver after 61.77 crashes my system with a BSOD stating...



IRQL_NOT_LESS_OR_ EQUAL bla bla bla



I'm also aware of the work arounds with DEP thing or running the game under OpenGL but I shouldn't have to since it works fine with driver 61.77 (the previous official if I recall correctly). Could Nvidia fix this bug please. It's real and I can point to other threads around the WEB dealing with the same problem.

Besides that I have no other issues...



EDIT:

Here's my specs

Athlon64

Asus K8N-E DX

Gainward 6800GT

WinXP Home SP2

#1
Posted 11/25/2004 08:18 PM   
This bug is so werid I have an amd64 3200+ and a 6800 gt - I play ut2k4 roughly daily and I've never had this problem-and I go through tons of drivers. Maybe its an amd driver thing? Most people seem to be using the current amd drivers-im using the 1.1.0.0 from jan. 03....very stable...and ive never had this problem.
This bug is so werid I have an amd64 3200+ and a 6800 gt - I play ut2k4 roughly daily and I've never had this problem-and I go through tons of drivers. Maybe its an amd driver thing? Most people seem to be using the current amd drivers-im using the 1.1.0.0 from jan. 03....very stable...and ive never had this problem.

AMD64 3200+ ll 1024MB DDR 400 ll Evga 6800 GT @ stock ll WD 160 GB HD w/ 8MB Cache ll 430 Watt True Antec PSU ll

#2
Posted 11/25/2004 08:33 PM   
[quote name='solofly' date='Nov 25 2004, 04:18 PM']This seems to be a problem related to AMD and Nvidia. Every driver after 61.77 crashes my system with a BSOD stating...

IRQL_NOT_LESS_OR_ EQUAL bla bla bla

I'm also aware of the work arounds with DEP thing or running the game under OpenGL but I shouldn't have to since it works fine with drivers 61.77 (the previous official if I recall correctly). Could Nvidia fix this bug please. It's real and I can point to other threads around the WEB dealing with the same problem.
Besides that I have no other issues...

EDIT:
Here's my specs
Athlon64
Asus K8N-E DX
Gainward 6800GT
WinXP Home SP2
[right][post="813"]<{POST_SNAPBACK}>[/post][/right][/quote]

Have you tried re-applying the latest official patch for the game? Maybe that would help.
[quote name='solofly' date='Nov 25 2004, 04:18 PM']This seems to be a problem related to AMD and Nvidia. Every driver after 61.77 crashes my system with a BSOD stating...



IRQL_NOT_LESS_OR_ EQUAL bla bla bla



I'm also aware of the work arounds with DEP thing or running the game under OpenGL but I shouldn't have to since it works fine with drivers 61.77 (the previous official if I recall correctly). Could Nvidia fix this bug please. It's real and I can point to other threads around the WEB dealing with the same problem.

Besides that I have no other issues...



EDIT:

Here's my specs

Athlon64

Asus K8N-E DX

Gainward 6800GT

WinXP Home SP2

[post="813"]<{POST_SNAPBACK}>[/post]




Have you tried re-applying the latest official patch for the game? Maybe that would help.

#3
Posted 11/25/2004 08:35 PM   
Some little bell rings in my head sound similar to 'nx-bit'...
Some little bell rings in my head sound similar to 'nx-bit'...

#4
Posted 11/25/2004 09:16 PM   
[quote name='ArChAnGeLv7' date='Nov 25 2004, 01:33 PM']This bug is so werid I have an amd64 3200+ and a 6800 gt - I play ut2k4 roughly daily and I've never had this problem-and I go through tons of drivers. Maybe its an amd driver thing? Most people seem to be using the current amd drivers-im using the 1.1.0.0 from jan. 03....very stable...and ive never had this problem.
[right][post="821"]<{POST_SNAPBACK}>[/post][/right][/quote]

I run my rigs at stock so there is no reason for crashes. I really don't know who's at fault here but I do know driver 61.77 doesn't crash OS when I exit UT2004 and drver 67.02 does, for example. (nothing else changes) Like I said before, 61.77 is the last driver that works flawlessly.

Here's a thread to start with...

[url="http://forums.guru3d.com/showthread.php?threadid=114435&perpage=10&pagenumber=1"]http://forums.guru3d.com/showthread.php?th...10&pagenumber=1[/url]
[quote name='ArChAnGeLv7' date='Nov 25 2004, 01:33 PM']This bug is so werid I have an amd64 3200+ and a 6800 gt - I play ut2k4 roughly daily and I've never had this problem-and I go through tons of drivers. Maybe its an amd driver thing? Most people seem to be using the current amd drivers-im using the 1.1.0.0 from jan. 03....very stable...and ive never had this problem.

[post="821"]<{POST_SNAPBACK}>[/post]




I run my rigs at stock so there is no reason for crashes. I really don't know who's at fault here but I do know driver 61.77 doesn't crash OS when I exit UT2004 and drver 67.02 does, for example. (nothing else changes) Like I said before, 61.77 is the last driver that works flawlessly.



Here's a thread to start with...



http://forums.guru3d.com/showthread.php?th...10&pagenumber=1

#5
Posted 11/25/2004 09:54 PM   
Here's another...

[url="http://www.nvnews.net/vbulletin/showthread.php?t=37255"]http://www.nvnews.net/vbulletin/showthread.php?t=37255[/url]

#6
Posted 11/25/2004 10:09 PM   
[url="http://www.nvnews.net/vbulletin/showthread.php?t=36541&highlight=UT2004"]http://www.nvnews.net/vbulletin/showthread...ighlight=UT2004[/url]

#7
Posted 11/25/2004 10:20 PM   
Bump.
Bump.

#8
Posted 12/01/2004 11:05 PM   
I can attest to having the exact same problem. Every driver after the 61.77s has caused me problems, which leads me to believe this is an NVIDIA problem rather than an AMD problem (proof positive of this would be if someone with an Intel setup is having the same issue).

Specs:

A64 3500+
ASUS A8V Deluxe
eVGA 6800 GT
XP SP2
I can attest to having the exact same problem. Every driver after the 61.77s has caused me problems, which leads me to believe this is an NVIDIA problem rather than an AMD problem (proof positive of this would be if someone with an Intel setup is having the same issue).



Specs:



A64 3500+

ASUS A8V Deluxe

eVGA 6800 GT

XP SP2

#9
Posted 12/05/2004 06:48 AM   
Here´s the solution for the problem. The problem is on PC´s with the following specs:

-Win XP home/pro with SERVICE PACK 2
-AMD Athlon 64 CPU
-GeForce 6800 Series
-nVidia ForceWare Driver later than 61.77

The "troublemaker" is the "nx-bit" feature which is a part of the Athlon64 CPU. It is enabled in XP with SP2, the function is called No-Execution. It seems that ForceWare driver later than 61.77 have great problems with this feature.

For me, games like Ut2k4, Far Cry, Ski Alpin 2005, Flatout are always crashing when using a ForceWare later than 61.77.

The solution is, edit your boot.ini and edit the /NoExecute to AlwaysOff

(disable write protection before saving boot.ini /yes.gif' class='bbc_emoticon' alt=':yes:' /> )

/NoExecute=AlwaysOff

NOW, nx-bit feature is OFF and you´ll see, all crashing problems and BSOD´s are gone.

If you think about, that nx-bit is a (great) feature to defend your system against bad code, how bad is the code of the "new" ForceWare Drivers?

So, nVidia, FIX IT, FIX IT, FIX IT!!! :magic:
Here´s the solution for the problem. The problem is on PC´s with the following specs:



-Win XP home/pro with SERVICE PACK 2

-AMD Athlon 64 CPU

-GeForce 6800 Series

-nVidia ForceWare Driver later than 61.77



The "troublemaker" is the "nx-bit" feature which is a part of the Athlon64 CPU. It is enabled in XP with SP2, the function is called No-Execution. It seems that ForceWare driver later than 61.77 have great problems with this feature.



For me, games like Ut2k4, Far Cry, Ski Alpin 2005, Flatout are always crashing when using a ForceWare later than 61.77.



The solution is, edit your boot.ini and edit the /NoExecute to AlwaysOff



(disable write protection before saving boot.ini /yes.gif' class='bbc_emoticon' alt=':yes:' /> )



/NoExecute=AlwaysOff



NOW, nx-bit feature is OFF and you´ll see, all crashing problems and BSOD´s are gone.



If you think about, that nx-bit is a (great) feature to defend your system against bad code, how bad is the code of the "new" ForceWare Drivers?



So, nVidia, FIX IT, FIX IT, FIX IT!!! :magic:

#10
Posted 12/05/2004 02:51 PM   
[url="http://www.nvnews.net/vbulletin/showthread.php?t=41917"]http://www.nvnews.net/vbulletin/showthread.php?t=41917[/url]

#11
Posted 12/07/2004 03:45 AM   
Is this a personal solution, or a generalized resolution to issues already known with DEP and A64 CPUs? I don't think this is the solution to the issue, but a general overall recommend to those with SP2 installed on A64 based boxes.
Is this a personal solution, or a generalized resolution to issues already known with DEP and A64 CPUs? I don't think this is the solution to the issue, but a general overall recommend to those with SP2 installed on A64 based boxes.

#12
Posted 12/07/2004 07:01 AM   
I have exactly the same issue as yall.

61.77 work perfectly. All subsequent drivers crash my comp to a blue screen as I exit UT2004.

AMD 3500
Asus A8V
Corsair C2 2X512 @ 2-3-3-6
BFG 6800GT
Antec 430w

Nvidia: PLEASE FIX THIS ISSUE!!!
I have exactly the same issue as yall.



61.77 work perfectly. All subsequent drivers crash my comp to a blue screen as I exit UT2004.



AMD 3500

Asus A8V

Corsair C2 2X512 @ 2-3-3-6

BFG 6800GT

Antec 430w



Nvidia: PLEASE FIX THIS ISSUE!!!

#13
Posted 12/12/2004 09:59 AM   
sounds like its when the gpu speeds switch from 3d into 2d that causes this problem...
sounds like its when the gpu speeds switch from 3d into 2d that causes this problem...

#14
Posted 12/12/2004 10:35 AM   
This problem only occurs on systems with XP SP2. Go back to SP1 and you won't have this problem.
This problem only occurs on systems with XP SP2. Go back to SP1 and you won't have this problem.

#15
Posted 12/12/2004 10:41 AM   
  1 / 4    
Scroll To Top