BSOD - Error DRIVER_IRQL_NOT_LESS_OR_EQUAL
After rebooting my computer yesterday morning I got the Blue Screen of Death. I had rebooted after updating my iTunes to iTunes 10 (not sure if this has anything to do with it but i've heard similar stories on other forums). I tried restoring my system to a previous date but after rebooting got the blue screen again. I searched online and found a few suggestions. I have run the disk check and there are no problems, i also ran a memory check and that is fine too. From reading other forums it looks like i have a problem with some drivers. At the moment i can only run my system in safe mode. I tried uninstalling iTunes but i cannot do this in safe mode. I've located the dump files that were created yesterday but have absolutely no clue what to do with them. A lot of solutions i've read involve involve reinstalling windows from a disc. As i bought my laptop from Dell i have no discs as software comes pre-installed on their machines. Has anyone had a similar problem and have any solutions that may help?
February 21st, 2011 1:33pm

Hi there, Upload the dump files to Skydrive and post us the link.Microsoft MVP - Windows Expert (IT Pro)
Free Windows Admin Tool Kit Click here and download it now
February 21st, 2011 4:57pm

Try the Clean Boot diagnostic procedure . Jerry
February 22nd, 2011 4:41pm

Hi, Check this thread for information using BlueScreenView, MyEventViewer and other methods to troubleshoot BlueScreens - top 3 replies (+1 other). http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/c675b7b8-795f-474d-a1c4-6b77b3fcd990 We can analyze the minidumps if you make them available from the SkyDrive or other file sharing sites. Zip or upload the contents of C:\Windows\minidump Use SkyDrive to upload collected files http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65 ------------------------------------------------------------------------- Also do this so you can see the likely bluescreens. Windows Vista automatically restarts if your PC encounters an error that causes it to crash. (also Windows 7) http://www.winvistatips.com/disable-automatic-restart-t84.html =========================================================== Check with these utilities to see if any information can be gathered : This is an excellent tool for posting Blue Screen Error Information BlueScreenView - Free - scans all your minidump files created during 'blue screen of death' crashes, and displays the information about all crashes in one table. http://www.nirsoft.net/utils/blue_screen_view.html ------------- MyEventViewer can be checked at the time of the BlueScreen (BSOD) to within a second or so of the time of the BSOD to provide more information as to possible cause - see TIP. MyEventViewer - Free - a simple alternative to the standard event viewer of Windows. TIP - Options - Advanced Filter allows you to see a time frame instead of the whole file - set it to a bit before and after the time of the BSOD. http://www.nirsoft.net/utils/my_event_viewer.html ------------ AppCrashView - Free - a small utility for Windows Vista and Windows 7 that displays the details of all application crashes occurred in your system. The crashes information is extracted from the .wer files created by the Windows Error Reporting (WER) component of the operating system every time that a crash is occurred. AppCrashView also allows you to easily save the crashes list to text/csv/html/xml file. http://www.nirsoft.net/utils/app_crash_view.html Hope this helps.Rob Brown - Microsoft MVP - Windows Expert - Consumer : Bicycle - Mark Twain said it right.
Free Windows Admin Tool Kit Click here and download it now
February 22nd, 2011 11:59pm

You may boot in Clean Boot Mode as BSOD can be caused by programs that are running in kernel mode. Perform a clean startup to determine whether background programs are interfering with your game or program If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files, rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver is the root cause. Another way is enable muni-dump and use Windbg. Please refer: How to read the small memory dump files that Windows creates for debugging You may paste the result in your next post for analyzing.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
February 23rd, 2011 2:49am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics