please help!
i just joined this forum today and i've been browsing for a while, trying to get help and see if i can solve this by myself, but i have no idea what most of you are talking about.

i keep randomly getting a blue screen that says:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

it will show up in the middle of me using the computer, sometimes when i'm downloading something or other times when i'm playing a game (i've tried to play the sims 2 three times and i get this message each time about two minutes into running the game). then my computer restarts and my computer tells me it has just recovered from a serious error. the error code is:

BCCode : 100000d1 BCP1 : E2a430b4 BCP2: 000000FF BCP3 : 00000000 BCP4 : FF84F1BF OSVer : 5_1_2600 SP : 2_0 Product_1

then it says the files that were included in the error log are:

C:\DOCUME~1\Owner\LOCALS~1\Temp\\WERb09f.dir00\Mini041306-03.dmp
C:\DOCUME~1\Owner\LOCALS~1\Temp\\WERb09f.dir00\systdata.xml

i have windows xp, i don't know what else i need to tell you about the computer, i don't really know what kind of processor or anything. but if anyone knows why i'm getting this message or how i might fix it, i'd really really appreciate it.

**EDIT

i reposted this in the proper forum now. sorry bout that.

Dani AI

Generated

Brief troubleshooting roadmap for DRIVER_IRQL_NOT_LESS_OR_EQUAL (report from ). Crashes that appear during downloads and when running a game suggest the fault is most likely a kernel-mode driver (network, graphics, or a filesystem/filter driver) or underlying hardware/disk corruption. Earlier suggestions from (memory/virtual memory), (driver focus) and (BIOS update) are good first ideas; the next step is to identify the specific module named in the minidump before doing broad changes.

Analyze the minidump to find the culprit. For a quick glance use BlueScreenView; for a definitive look use WinDbg (Debugging Tools for Windows). Typical WinDbg commands to set symbols and analyze a dump are:

.sympath SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
.reload
!analyze -v

Look for the line "Probably caused by" or a referenced .sys filename in the stack. If a third-party .sys is shown, check its vendor and file date (match it to recent installs/updates). If the kernel (ntoskrnl) is listed, follow the stack to the first non-Microsoft driver.

Isolate drivers and capture system state. Do a clean boot (disable non-Microsoft services/startup) and test stability. Prioritize video, network, storage controller and security/antivirus filter drivers for update or rollback. Useful snapshots to attach when asking for help are a driver list and system report:

driverquery /v > C:\drivers.txt
msinfo32 /report C:\sysinfo.txt

Hardware and other checks: run CHKDSK /r and a S.M.A.R.T. HDD test, verify PSU and component temperatures, reseat memory/PCI cards, and test RAM with memtest86 as suggested by . BIOS updates helped in some cases (). When seeking further diagnosis include the minidump or the !analyze -v output, the suspect .sys name, exact Windows/SP level and recent driver/hardware changes. Caution: Driver Verifier is a powerful tool but will deliberately cause BSODs when it finds bad drivers—have a recovery plan before enabling it.

Recommended Answers

All 8 Replies

This problem can be caused by a damaged pagefile or bad sector that the pagefile is mapped to or faulty RAM module. Try removing the pagefile, rebooting and then creating a new one. Also, have your memory tested, either with your vendors tools or with something like memtestx86.

This code usually indicates that the system tried to access pageable memory and could not or an error returned when it attempted to do so. I have had at least one case where a faulty RAM module was causing this and other stop codes.

thank you sooo much for your help, i'll definitely try those.
well, first i'll test my memory, because i don't know what a pagefile is.

but thank you for responding, i really appreciate it.

Pagefile is the system's swap space. Windows uses a swap file to swap pages of memory to disk. It does this when physical memory is low and for pages that have not been referenced for a certain amount of time. To remove it, open Control Panel > System then click on Advanced tab then the Settings button under Performance Options then click the Advanced tab. Under the Virtual Memory section click the Change button and then find and click in the No Paging file button then click Set. Click OK to dismiss all windows ignoring any warnings. Reboot and then repeat the steps to re-create a pagefile that is 1.5 times your installed physical memory. Make sure the minimum and maximums match i.e. if you create a pagefile of 1024, put 1024 in both boxes. If you have a second hard drive, create the pagefile on that drive.

i removed/replaced the pagefile, but that didn't work. i'm now going to try to test my memory, although i'm doubtful i'll know what to do with the information. i made it 1.5x the suggested size for a pagefile is, but could the problem be that i still didn't make the new pagefile big enough? i wasn't sure if it should be 1.5x the entire memory capacity of the computer, or just the suggested size, or the size of the virtual memory, or what. but i don't think that should matter, because the reason i redid it was incase there was an error in it, right?
either way, thank you for your time.

A pagefile is not absolutely necessary although some applications may not work correctly if it can't page anything. I think Java is one of them. So whatever you put in is fine and usually 1.5 times the physical is norm. It used to be physical memory + 12 in the NT 4/2000 days.

Regardless whether the memory test come through, you should also look into making sure you have the latest drivers for all your hardware and also make sure Windows is updated.

I had similar problems on my home computer with random reboots as well.....a bios update fixed all the problems......

Being that this is a DRIVER_IRQL and not just a IRQL then I would say that the problem with this is a driver issue. Did you change any drivers/install new hardware recently?

According to Technibble.com, this error means:

Stop 0×000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL - This Windows stop error indicates that the computer tried to access memory using a kernal process which had a IRQL that was too high (as kernal processes can only access IRQLs that it is either equal to or IRQLs that less than it). This is usually caused by incorrect or incompatible drivers.

Hope it helps.

hello guy, can you help me..

i dont know what i can do, but my computer have problem with bluescreen disable bios showing..

this the picture

[img] [/img]

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.