Windows Forum

Ask something
Discussion Locked

PC Blowup

0 helpful
10 replies

by jmonroe

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

HELP!!!
What is causing this problem and how do I fix it? Using Win 2000 Pro on a peer to peer network with a Dell Demension 700R. The reoccuring problem is: occassionally my screen goes black and displays this message: stop: 0x000000D1 (0xE4434040,0x000000FF,0x0000001,0xBE9C10F0) Driver_IRQL_not_less_or_Equal and I have to manually reboot. Most commonly occurs when transfering files FROM this PC TO a network peer PC, but can happen when doing other normal tasks like running Word 2000. Then when I reboot, I always see the message: \systemroot
system32\drivers\ausbd.sys not found. I'm not sure the 2 messages are related, but would like to solve both if possible. Thank you!

10 replies

by jmonroe

Hello,
Thank you for a prompt response. Unfortunately, Q269279 is a solution if firewall Black Ice is used. I don't use that program. Tried to search Knowledgebase for an appropriate solution to error message: stop: 0x000000D1 (0xE4434040,0x000000FF,0x0000001,0xBE9C10F0) Driver_IRQL_not_less_or_Equal. I was not successful, but perhaps you have better capabilities.

I also downloaded and installed new drivers for my Creative Labs Web Cam Go ES and Iomega Jazz drive, both which are USB devices. Also checked Device Manager, USB controllers and there were no problems. I do think that the "\systemroot
system32\drivers\ausbd.sys not found" error at boot up is probably related, but cannot identify to what, or where that driver belongs. I hope you do!!
Thank you

by talli

The error message u quote is usually associated with a bad or missing driver.People tend to associate IRQL with IRQ and IRQ conflicts (and u might very well have one if some driver doesn't support IRQ sharing ,check the Device Manager), but it actually means that an attempt was made to touch the pageable memory at a process internal request level (IRQL) too high, which is, like I said, usually caused by buggy drivers.So,try to eliminate the culprit by uninstalling your devices, one by one, and wait to see if the situation is any better.Or, try to remember what system changes u have performed prior to this error appearing.The driver file name obviously is USB related, so those r the devices to start with.Search your system for this file, ifit's missing-look for it's latest version on the Web, if it's there-try updating/replacing it.

by jmonroe

You needed to read my original request. Your response was not helpful. Of course I need the file ausbd.sys. Where do I go to find it????

by jmonroe

You needed to read my original request. Your response was not helpful. Of course I need the file ausbd.sys. Where do I go to find it????

by jmonroe

You needed to read my original request. Your response was not helpful. Of course I need the file ausbd.sys. Where do I go to find it????

by isys

It seems that ausbd.sys is a USB 2.0 driver. Do you have USB 2.0 hardware? Is the file present? If not and you are doing USB type operations (USB network atapter, maybe?), it could be the source of your problem. The file is available here:

http://web.singnet.com.sg/~autoken/

if you want to copy it.

by jmonroe

Finally you have provided the correct solution!!! Thanks for the url. I used the ausbd.sys file by copying it into the
system32\driver folder. That seemed to clear my problem with the error message at reboot and I tested transfering files over the peer-to-peer network and didn't have a blowup. So far, it's working. Thank you very much.

This discussion is closed to new replies.