DRIVER_IRQL_NOT_LESS_OR_EQUAL afd.sys

[n0p3]

Hello,

Since 3 Days, i`ve more and more BSOD crashes.
I don´t know, what the problem could be. i hadn´t changed anything.
I´ve done a
- Memtest - all clear.
- a sfc scan - there were problems, which couldn´t repair.
- reinstall my graficcard.

but no results
Please help me.
i have no just to reinstall windows

 

[Arc]

Click on button below ....

​

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[n0p3]

here is the zip - thanks for ur help

 

[Arc]

Uninstall Wise Care 365 and consider the money spent on it was a bad investment. That will be a wise decision.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus and teh touchpad driver SynTPEnh.
5. Apply > OK
6. Accept then restart.

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.

Let us know for any further BSOD after doing these.
___________________________________________

BugCheck 50, {fffffa80115d8bf0, 1, fffff880035dffb7, 0}

*** WARNING: Unable to verify timestamp for WiseTDIFw64.sys
*** ERROR: Module load completed but symbols could not be loaded for WiseTDIFw64.sys

Could not read faulting driver name
[COLOR=Red]Probably caused by : WiseTDIFw64.sys[/COLOR] ( WiseTDIFw64+5fb7 )

Followup: MachineOwner
---------

 

[n0p3]

Thanks, for the answer.
i have closed all startup programms, except antivir and syntpenh.
than ive downloaded sptd - this program writes, that ive no sptd.
But do u know, what program makes the bsod?

 

[n0p3]

no positive results.
2 crashes, after clean the start up and deinstallation wise care - it seems, that this program makes the bsod -
Not funny.
in the attachment u´ll find the last both crashes.

 

[Arc]

But do u know, what program makes the bsod?

Read the first line of post #4. If I did not know, I would not have posted in your thread.

Uninstall Wise Care 365 and consider the money spent on it was a bad investment. That will be a wise decision.

BugCheck 50, {fffffa80115d8bf0, 1, fffff880035dffb7, 0}

*** WARNING: Unable to verify timestamp for WiseTDIFw64.sys
*** ERROR: Module load completed but symbols could not be loaded for WiseTDIFw64.sys

Could not read faulting driver name
[COLOR=Red][B]Probably caused by : WiseTDIFw64.sys [/B][/COLOR]( WiseTDIFw64+5fb7 )

Followup: MachineOwner
---------

I see that the failing module is still present in your system.

wisetdifw    WiseTDIFw    \??\[COLOR=Red][B]c:\windows\wisetdifw64.sys [/B][/COLOR]   Kerneltreiber    [B][COLOR=Red]Ja [/COLOR][/B]   System    Wird ausgeführt    OK    Normal    Nein    Ja

If you are sure that you have uninstalled Uninstall Wise Care 365 as suggested (your posts gives a hint that you were not ready to accept it initially) then go to C:Windows and delete these two items there ....

• wisehdinfo WiseHDInfo \??\c:\windows\wisehdinfo64.dll
• wisetdifw WiseTDIFw \??\c:\windows\wisetdifw64.sys

Let us know for any further BSOD.

 

[n0p3]

of course, i ve deinstalled wise care.
The both files i´ve deleted.
same Problem - BSOD -
i post the last dmp

 

[Arc]

[COLOR=Red]BugCheck C5[/COLOR], {fffff8000000010b, 2, 0, fffff800031f84b1}

Probably caused by : Npfs.SYS ( Npfs!NpRemoveDataQueueEntry+a5 )

Followup: MachineOwner
---------

Npfs is a system native driver and it is not the actual crashing module (with a little exception). But basically a 0xC5 is a driver related issue.

In a deeper search it reveals a failing module.

fffff880`0a588458  fffff880`04f917f7Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys[/COLOR]
 atikmdag+0xab7f7

    Image name: atikmdag.sys
[COLOR=Red]    Timestamp:        Fri Mar 20 08:25:48 2015[/COLOR] (550B8C34)

Another example of bad computing. Dont use a BETA display driver. BETAs are for testing, not for daily use.

Uninstall the installed display driver using DDU. Then install the CCC 14.4 WHQL only.

Let us know for any further BSOD after doing it.

But please keep it in mind that a pure snake oil like Wise Care 365 can corrupt the windows install beyond repair. If correcting the display driver did not help and another failing module jumps up, then we have to take some deeper steps.

 

[n0p3]

i knew, i didn´t have installed wise care. that was my fault. i am sorry. thanks for ur support. now it seems better, since the laptop restarted. maybe the last step was the right step. if came a bsod, ill write it on.

 

[Arc]

Yes, do it. I will be bit of anxious to know how it runs.