BSOD Error code: 0x000000D1, driver_irql_not_less_or_equal

Arc said:

conhaqu3, what Paul suggest you is right, McAfee was one of your problrm. See it:

Code:

fffff880`035bcd98  fffff880`01d20080Unable to load image \SystemRoot\system32\drivers\mfewfpk.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mfewfpk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfewfpk.sys
 mfewfpk+0x7080

Description here: Driver Reference Table - mfewfpk.sys

But, it is not only McAfee, but also another problematic antivirus which two were installed at the same time. McAfee is removed now, but Avast is still contributing to your crashes.

Code:

fffff880`035bd268  fffff880`046792abUnable to load image \SystemRoot\System32\Drivers\aswFW.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswFW.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswFW.SYS

Description here: Driver Reference Table - aswFW.SYS

Code:

fffff880`035bd4d8  fffff880`0469a06aUnable to load image \SystemRoot\System32\Drivers\aswTdi.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswTdi.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
 aswTdi+0x106a

Description here: Driver Reference Table - aswTdi.SYS

Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

The Atheros NIC (AR8151) driver is very old.

Code:

start             end                 module name
fffff880`0a934000 fffff880`0a950000   L1C62x64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\L1C62x64.sys
    Image name: L1C62x64.sys
    Timestamp:        Mon Sep 19 13:12:11 2011 (4E76F253)
    CheckSum:         0001D371
    ImageSize:        0001C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from ATHEROS Network drivers for Windows.

Intel(R) Wireless WiFi Link 5000 Series Adapter Driver is also very old.

Code:

fffff880`0a03d000 fffff880`0a8c3000   NETwNs64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\NETwNs64.sys
    Image name: NETwNs64.sys
    Timestamp:        Thu Aug 04 05:58:26 2011 (4E39E7AA)
    CheckSum:         0083C028
    ImageSize:        00886000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Intel Download Center

Let us know the results.

Arc,

Thanks for the clean and well-detailed response.

I removed McAfee using mcafee removal tool and successfully removed Daemon tools lite as well.

I am currently still using Avast just to see if I will get another BSOD.

As far as the updates of the drivers that you mentioned are concerned, the Atheros link only shows a driver dated of 2010 so there's no point in installing. The Intel Wireless Wi-Fi link, I click on "Automatically check computer for updates" but it appears some kind of message saying that the firewall is blocking. Nonetheless, I don't think it is a problem of the drivers as my ASUS PC is just 4 Months-old.

I will know try to search for updates in Windows Updates and use uTorrent to see if windows crashes again (I forgot to mention in the description that I got 2 BSOD, separately, while searching for updates and while using uTorrent).

By the way, any chance the "C" disk had enlarged it size because of the BSOD? Yesterday, I had like 4 trewout the day and the disk passed from 138 GB free space available to 124 GB...and I didn't even installed any new software or anything else....

Please fill me in on this last subject.

Many thanks,
conhaqu3

Well, 2 days have passed and no signs of any annoying BSOD :)

I think it may had to do with a conflict between the two anti-viruses.

Nevertheless, I will wait until it has passed a week to fully close this thread.

Thanks to all who dedicated time to help me solve this problem.

Rgrds,
conhaqu3

SkyDrive link is broken Noel.

"This item is no longer available"

NoelDP said:

Sorry - technical hitch (I accidentally deleted the entire folder, which broke the link)

Noel's SkyDrive

Just did as you asked and when finishing typing the command "XCOPY <drive>:\conaa <drive>:\windows\winsxs /y /i /s /v /h" I got this message: "The system cannot find the file system"

I did the procedure again and double-check the command spelling and still got the same message.