Ghost recon crashess with bsod

After playing ghost recon for half an hour it crashes with a BSOD IRQ_LESS_OR_NOT_EQUAL anyone else experiencing this problem? My system: p3 800eb abit be6-2 512 MB RAM elsa geforce 3 ti200 hercules fortissimo 2 maxtor hd 30GB

Windows Games 5469 This topic was started by ,


data/avatar/default/avatar33.webp

269 Posts
Location -
Joined 2001-02-06
After playing ghost recon for half an hour it crashes with a BSOD "IRQ_LESS_OR_NOT_EQUAL
anyone else experiencing this problem?
 
My system:
 
p3 800eb
abit be6-2
512 MB RAM
elsa geforce 3 ti200
hercules fortissimo 2
maxtor hd 30GB

Participate on our website and join the conversation

You have already an account on our website? Use the link below to login.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic


data/avatar/default/avatar26.webp

24 Posts
Location -
Joined 2001-10-06
I am running XP pro and having no probs at all with ghost recon. Could be a driver issue. ??

data/avatar/default/avatar28.webp

47 Posts
Location -
Joined 2001-11-30
An IRQ_LESS_OR_NOT_EQUAL BSOD would almost certainly be a driver issue, although which driver is causing it is the question...
 
Does the fortissimo 2 have XP drivers now? Could also be video drivers also. Also, make sure the video card isnt sharing IRQs...
 
Sorry, this sounds like the standard shpeel, but those are pretty much the causes of this paticular BSOD.
 
Hope it helped.

data/avatar/default/avatar33.webp

269 Posts
Location -
Joined 2001-02-06
OP
it seems it is an EAX issue, i read that on the ghost recon forums. When i disable EAX in the game itself it works fine.

data/avatar/default/avatar28.webp

47 Posts
Location -
Joined 2001-11-30
Now that would make sense....
 
The SBLive drivers have never quite been up to par in W2K/XP.

data/avatar/default/avatar40.webp

3087 Posts
Location -
Joined 2001-01-21
Plus, the IRQ sharing would be there in XP/2k because of ACPI, and that is usually NOT the problem.
 
You've fixed it, but that would be a driver issue most likely. The BSOD usually lists the culprit file, providing there is one.