Ghost recon crashess with bsod
This is a discussion about Ghost recon crashess with bsod in the Windows Games category; 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
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
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 in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Responses to this topic
I am running XP pro and having no probs at all with ghost recon. Could be a driver issue. ??
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.
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.
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.
Now that would make sense....
The SBLive drivers have never quite been up to par in W2K/XP.
The SBLive drivers have never quite been up to par in W2K/XP.
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.
You've fixed it, but that would be a driver issue most likely. The BSOD usually lists the culprit file, providing there is one.
