---

@Thomas_ wrote:
I just got this laptop a few months ago. Its a inspiron e1505 with the standard intel "graphics accelarator" graphics card, a 1.83 Ghz Duo Core, and 2 GB of RAM.

Soon after getting it i would get very infrequent BSODs. Now the Blue Screens have become very frequent and seem entirly random. They dont happen at shutdown or while doing anything. Sometimes its when i have been gone a while, sometimes just after startup sometimes while typing an email, just random. I have run a very thorough RAM check (running memtest86 all night) and my hardware seems fine. It must be drivers but I have no clue which ones. I get the following message on the BSOD (not always this, but often... sometimes its "DRIVER_IRQL_NOT_LESS_OR_EQUAL"):

MULTIPLE_IRP_COMPLETE_REQUESTS

***STOP: 0x00000044 (0x89613DC0, 0x00000D62, 0x00000000, 0x00000000)

I'm am at a loss here, any ideas? Have you been able to fix this problem, are other inspiron e1505/e1705's having this problem. I haven't changed my system much. I uninstalled a few things like the dell jukebox and stuff like that, and added a few other programs. But mostly my computer is still pretty bare. This issue didn't seem to start after any particular installation. Help...

-Thomas

---

A Google search of your issue led me to this page in the Microsoft knowledge base:

http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B839619

Don't know if that will solve your problem or not but take a look.

Well, I dont think that could be the issue. I dont believe any version of "Novell Client" is installed on my system. The BSOD happened again just as I was last trying to answer this message. It was again MULTIPLE_IRP_COMPLETE_REQUESTS 0x44 (random, 0xD62, 0x00, 0x00). Im still searching for answers. The page you pointed to is the closest i've found but i dont see how it could be causing the error. Is anyone else with an e1505 or similar having these problems?

Thanks,

-Thomas

Hey Thomas,
I also got a Dell E1505 (Inspiron 6400) and I have the exact same problem. Sometimes, I can work with the laptop for two or three weeks without getting any bluescreen, thinking that the problem is solved, but suddenly... same error message (MULTIPLE_IRP_COMPLETE_REQUESTS), same stop-code (0x00000044), same trouble.

I talked to those support-hotline-guys many times, but they actually didn't have a clue, what to do about it. So they send a technician, who couldn't help me either. I formatted the harddisk, installed windows and the newest drivers, but still the same problem.

I tried to analyse the minidump-file with the MS Debugger tool and found out, that a file called acpi.sys is causing the BSOD. But ACPI.sys is a windows file which is for managing standby and hibernation. You can't just delete this file...!?

Dell told me, that acpi.sys is somehow affected by any of the programs I run. They couldn't tell me which one it is, they just said it's a software problem and they do not and don't have to provide support for problems with the software. I'm pretty sure they just wanted to get rid of me and my annoying questions without knowing what is really going on with my PC.

After spending many, many hours on trying to solve the problem without success, I'm tired of the trial and error method. After having a look at this forum, I recognized that this problem is well known for E1705/E1505-Users and it seems like there's a fundamental malfunction with these models. That's why I will try to return the laptop and get my money back. I'm sure, this is the best solution...

I fixed it. It turned out to be bad toshiba bluetooth drivers. Just uninstall the all the blutooth software dell intstalled and either update it or use windows to manage your bluetooth. I has worked for me. 4 weeks with no BSODs!

-tom

I have a BSOD as well been there for 2 months now

but its got the name FILE_SYSTEM and the stop is 0x00000022

can anyone help me on my type of bsod...

Arkus

Hmmm. Sorry, i really dont know anything about that specific BSOD error. I was able to fix mine by doing lots of searches for the error, and logging it everytime it happened. Try to see if you can identify what happened when it began. Maybe you installed something that interacted badly with your computer. Sorry i cant suggest anything else.

-thomas