Q: I sometimes [a lot of the time] get BSOD on my computer and it gets quite annoying. When it happens a message comes up saying: DRIVER_IRQL_NOT_LESS_OR_EQUAL Can someone tell me why this happens and a possible solution? I award best answers. I think it may be because I have two Wireless internet driveers, the windows one and the one that came with the wiFi adapter [I have a USB that connects to the wireless internet]. Could that be it? Im actually pretty sure it is my interenet driver because the BSOD ALWAYS happens when im streaming a lot of cvideo, downloading a torrent or using my webcam. There were 3 in my Device Manager. The Sitecom adapter Something called "family Ethernet" and 1394 network card i disabled all but the sitecom wirelss one.
A: I Found This Thread Particularly Good At Dealing With General BSODs You Do Not Necessarily Need To Reformat And Reinstall. Should You Go This Route, However, The First Thing You Should Install Is A BIOS Update, If Any, Then The Chip Set For Your CPU Then Mother Board, Video, Sound And Any Other Devices Such As Network Adapter, Gaming Console(s) etc. edit: Lost's Answer Is Very Good But, It Might Be A Direct Memory Access Error. Another Way Of Putting This Is Some Device (Driver) Is Trying To Incorrectly Use Memory Already Allocated To The Kernel For Example. edit2: OK, Now You Need To Check Those Device Drivers Through Device Manager By Expanding The Categories And Talking Properties Of Each, Then Check Under The Resources Tab. Conflicts Will Show There And May Be Resolvable Through Device Manager. You Should Know There Are "Hidden" Devices Which May Also Cause Conflicts. Add To The List Of Environment Variables For Your User The Following: DEVMGR_SHOW_NONPRESENT_DEVICES Set The Value To1 Restart Device Manager And Click On Show Hidden Devices. Be Warned, Do Not Randomly Disable Or Stop Any Of These As They Are Hidden For Good Reason. You Can Also Try msinfo32 And Look At The Hardware Resources And Memory Categories. Any Conflicts Should Appear There Also, From There You Can Track Down The Culprit In Device Manager. Good Luck