[Tommy_F]

Hello everybody!

I recently got a couple of BSOD's with the 0x000000D1 error, irq_not_less_or_equal.

I ran the debugging app that microsoft offers and it found out that the wanarp.sys is to blame for the error. But this information was already displayed on the blue screen...

I checked, and the service corresponding to that file is disabled. At this moment, I ran out of ideas...

My memory dump was set for kernel dump, but now I set it to minidump, so I can attach some minidump files after the next BSOD. Because it will happen.

I have an Intel Celeron 2.66GHz CPU, 1GB ram, a WD 160 GB hdd, a seagate 20GB hdd, and I run XP sp2.

Any help will be very appreciated. Thanks in advance.

[kniht]

Go here and download "autoruns" (freeware): http://www.microsoft.com/technet/sys.../AutoRuns.mspx

Run the .exe and see if the driver for wanarp.sys is being loaded at boot even if the service is disabled.

You'll be surprised how many items are loaded upon boot.

Here's the scoop on the BSOD:

Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL

The Stop 0xD1 messages 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.

Possible Resolutions:

• 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.

[Tommy_F]

I downloaded the "autoruns", ran the program, did a search for wanarp.sys, and there it is, it was found in the drivers section, so it is loaded up even if it is not used.

Should I delete that entry?

And yes, you were right, I was amazed by the number of items that are loaded on boot. I bet I don't even use 30% or more of those...

[ozrom1e]

And yes, you were right, I was amazed by the number of items that are loaded on boot. I bet I don't even use 30% or more of those...

Be careful do not just start stopping any of those because you may not use them but your computer does and neds some or all of them.

No do not just delete the entry what does the fix say that you to do that you were running?

Here is the info on wanarp.sys

http://www.file.net/process/wanarp.sys.html

[kniht]

In autoruns go to "Options" and select "Hide Microsoft Entries" (if not already selected), then go to File and select "Refresh". This will keep you from disabling an MS entry needed for proper running of your system.

If wanarp.sys is disabled, there is no reason to have it's driver load at boot, go ahead and uncheck it. If you enable wanarp.sys sometime in the future, you can always go back into autoruns and recheck to load the driver at boot.

Seems to me, if the bsod is pointing to wanarp.sys and the service is disabled, and Stop 0xD1 pertains to faulty drivers, then unchecking the wanarp.sys driver so it doesn't load into your system should take care of your BSOD problem.

But, then again, that's the common sense approach and we're dealing with computers here!

[Tommy_F]

Well, I unchecked the box, rebooted, the box is still unchecked. I hope this solves my problem.

Thanks very much for the assistance! I now have this new tool (autoruns) and some more knowledge and hopefully next time I will be able to handle the issue myself!

Again, I appreciate the help.

I will wait for a couple of days to see if any more BSOD's occur, if not, I am marking the thread solved.

[Tommy_F]

Oh damn....after a couple of days BSOD free it reappeared... The same exact problem. I have the wanarp.sys unchecked in autoruns but it still gives me the BSOD. I deleted the entry in autoruns, but my internet connection won't work without it. Lucky me I did a registry backup before deleting the entry...and I was able to restore it. So my internet connection seems to be using wanarp.sys, although not loaded? I don't understand. I think I will run a memtest86...

[Tommy_F]

I booted from the Ultimate Boot CD and ran Memtest86 v3.3 for 1 pass and it showed no error, I ran the Windows Memory diagnostics for 1 pass, no error there either. I am running out of options here...

Can a mod pls mark this thread unsolved again? :S

[Tommy_F]

Any ideas anyone?

[peterdiva]

Post some of the minidump files. Zip up 5 or 6 of the most recent. Is that 2x512MB sticks of RAM or 1x1GB?

[Tommy_F]

Unfortunately i only have 1 minidump file...I run CCleaner regularly and that seems to have deleted them. I attached that single one.

[peterdiva]

That crash was caused by memory corruption with 7 errors. This is usually a sign of a RAM problem. You need to run Memtest for 7 passes. As Memtest isn't perfect, if the RAM passes post your RAM setup.

Teefer.sys is also in the mix, but I'll need to see some more dumps to see if it's consistent. From what I can find out this belongs to Sygate Firewall. You can try uninstalling it for problem isolation.

BugCheck 100000D1, {40, 2, 1, f6c18150}
Probably caused by : memory_corruption

CHKIMG_EXTENSION: !chkimg -lo 50 -d !wanarp
f6c183fd-f6c18403 7 bytes - wanarp!WanpSendPackets+f5
[ ff 75 14 50 ff 50 54:e8 9e 2b 95 00 90 90 ]
7 errors : !wanarp (f6c183fd-f6c18403)

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

[Tommy_F]

Thanks. I can't really uninstall sygate, I don't trust any other free f/w...
I will let memtest run overnight...

I also get some cannot read/write memory errors from windows media player after it runs for a while. I really hope nothing is wrong with my RAM. The are expensive...