Jump to content

WinXP BSOD...grrr...


Recommended Posts

Well I've looked and looked and I can't find a solution to this, so I thought I would try running it up the flagpole here...


Okay, short version, I just bought a new computer about a month ago (Dell 8500), and now when I play Neverwinter Nights I get crashed to a blue screen periodically with the following error message: "DRIVER_IRQL_NOT_LESS_OR_EQUAL".


Some (hopefully relevant) specs on the PC:


P4 2.6gig

WinXP Home edition OS

ATI Radeon 9800 (not Pro) video card

768 MB RAM

BIOS version A01


I have downloaded the latest versions of both NWN and the expansion pack (SoU), and I have downloaded the latest ATI drivers for the 9800 video card. I have no USB devices at all connected to the machine, and while I did add 512MB RAM, the problem predates that installation. I have tried stopping all anti-virus software before launching (per a suggestion I read somewhere) and that didn't help.


The problem appears at random intervals, and happened both before and after I installed the expansion pack. Sometimes I can play for three hours without crashing, and sometimes it crashes 3 times in 10 minutes. It can be while opening a door, engaging a monster, or just while walking down a hallway. My old computer (700mhz Celeron, 32MB PCI graphics card) ran the game flawlessly, albeit with lower graphical settings.


I realize this is a heck of a long shot, but does anyone have any idea what I can try next? Update the BIOS, maybe? I can't tell you how frustrating this is. :(

Link to comment
Share on other sites



A search of the Microsoft Knowledgebase brings up many possibilities for this BSOD message. Most of them appear to be related to CD or HD problems.


Try a Google search for that exact error message. I found lots of potential suggestions for it.

Link to comment
Share on other sites


The Stop 0xD1 message indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error.


Interpreting the Message

This Stop message has four parameters:


Memory referenced.

IRQL at time of reference.

Type of access (0x00000000 = read operation, 0x00000001 = write operation).

Address that referenced memory.

Resolving the Problem

For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.


Stop 0xD1 messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.

For more information about Stop 0xD1 messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x000000D1, and 0xD1.


updated and comaptiable drivers are very important when running XP. Check your hardware with the HCL http://www.microsoft.com/hcl If you hardware is not on the list it does not mean it won't work it just means it hasn't been tested by Microsoft and they won't Guarantee it to be compatible. If it not on the list check the manufacturer's website fo an up to date XP driver, if they don't have one you may be out of luck. This goes for motherboards and the bios too.

Link to comment
Share on other sites

Thanks, Camp. I did see that page referenced in a few places, but to my non-techy mind it translated loosely to: "Make sure you're using updated drivers for everything." I did update my video drivers, and I checked the windows update site for any other driver updates, so I think I am current. It was suggested to me that I check specifically for DirectX updates, so I'm going to do that, and punching the error msg directly into Google is a good idea as well...thanks! :)

Link to comment
Share on other sites

  • 2 weeks later...

Well just for the sake of closure, and on the extremely unlikely chance that someone in the future will happen upon this thread and wonder how I fixed the problem, I ended up downloading new DirectX drivers and disabling hyperthreading in my BIOS. One of those two actions fixed my issue. So now I am Neverwintering away to my heart's content. Huzzah! Calloo, callay!


The end.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...