• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Stop Errors in Windows 2000

D

DJediMaster

Senior member
Hi, does someone know what this stop error means and what might be the cause? It only occurs sometimes when i try and run a 3D application.

stop: 0x000000D1
driver_irql_not_less_or_equal

Thanks.
 

Do you have service pack 1? Also might be an IRQ conflict. Is your nic card and video adapter on the same IRQ?
 
I have sp1 installed but I just re-installed it anyways. I thought win2k supports irq sharing. I have like 4 or so devices on irq 11.
 
Ok, do this: Go into the bios and where it says "Plug and Play OS installed:" change it to "yes." This way, windows 200 can configure the IRQ's itself a little beter. If that still does not work, then moving cards to differnt PCI slots might help.
 
I just recieved another stop error

stop: 0x000000d1, 0xFF959400, 0x00000002, 0x00000000, 0xEDB1F127
*address EDB1F127 base at EDB1B000, datestamp 3920C578 - emu10k1f.sys

I think the problem is related to my sound blaster live value card. I tried moving my pci cards to different slots. I hope that helps things out.
 
Allright. I found a way to recreate the stop errors. I run a 3D appplication i quit it and then logoff and logon again as the same user. I proceed to run the same application..it will then give me the stop error. The error is not the one i posted above about the sblive but:

0x000000D1
driver_irql_not_less_or_equal

It happens with games such as deus ex, unreal tournament and mechwarrior4 but not with other titles. Is this only happening to me?
 
Here's what i got:
cpu: athlon t-bird 750@750
mobo: a7V rev 1.01
ram: 256 pc133
vid card: 3D Blaster TNT2 Ultra
sound card: sblive value
nic1: D-Link DFE-530TX
nic2: 3Com EtherLink XL PCI TPO NIC (3C900B-TPO)
 
I had this issue or something like it with an Athlon system. Swap the processor or memory and see if it goes away. I had a perfectly good operating machine until I swapped out the processor. I had gotten an error issue similar to yours. Put the original processor in and all was fine.... I took the the unit that "caused" the issue into my distibutor and had it tested. It pulled the same stop error issue on him in 98 and 2000 in a different machine. Bad processor.... New out of the box. If you find another solution to this let us know...
 
This is happening to me too, my rig is in my signature, you will see that it isn't an athlon problem. I believe it is the soundcard on an ACPI system. You can fix this, but I forgot how, and the computer will no longer shut down automatically. I also don't think you can go back to an ACPI system if you change it.
 
its a driver issue. loks like a sound blaster issue to me. ive fixed it by uninstalling the hardware and using win2k reference drivers. damn soundblasters.

loosbrew
 
The STOP: 0xD1 error is a generic error and until the file that causes it is identified, you will have a hard time determining its cause.

From your posts it looks like it is probably your soundcard and / or its drivers.
Try moving the card to another slot. Make sure the slot is not shared.
Reserver IRQ 5 for it in the BIOS.
Completely uninstall your drivers and reinstall again.

Every time I have fought with this error it has turned out to be a hardware/driver issue. Once the SCSI cable was loose. Another time a SCSI card was loose!. Yet another time, we had to swap out the processor. Only once did it turn out to be software related, and then some hardware monitoring agent was messing up the drive controller drivers.
What I would do is start pulling out all non-essential cards and see if the error goes away.
If not, try pulling out all memory DIMMs and then putting them in one by one to see if it is bad memory. If that doesn't work, try replacing the board and/or the processor.
If however by pulling out the cards the error goes away, you can start putting in cards one by one till you identify which one is the culprit.

In your case, you mention that it happens only after playing 3D games. Try setting your card to AGP2X, try disabling fast writes and sidebanding. Try not selecting hardware acceleration for the sound.

Just some pointers.

Good Luck.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top