Frequent BSOD, suspect wdf01000.sys and ntoskrnl.exe


  1. Posts : 17
    Windows 7 32-bit
       #1

    Frequent BSOD, DRIVER_IRQL_NOT_LESS_OR_EQUAL


    I'm running Windows 7 Pro (64-bit) and at various times throughout the day, no matter what I have open, I get the same BSOD error - DRIVER_IRQL_NOT_LESS_OR_EQUAL. DM Log Collector zip file is attached. Any assistance would be most appreciated.
    Last edited by hught78; 21 Apr 2014 at 23:25.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Your BSOD's were caused by Intel Management Engine Interface driver.

    TeeDriverx64.sys Tue Apr 23 23:36:39 2013 (5176C6A7)
    Intel Management Engine Interface driver
    Driver Reference Table - TeeDriverx64.sys

    Please remove it for testing purpose.

    Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-


    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!:-

    hardlock.sys Mon Feb 2 21:34:08 2009 (49871270)
    Hardlock Device Driver by Aladdin KnowledgeSystems
    Driver Reference Table - hardlock.sys

    NTIDrvr.sys Wed Mar 25 09:09:39 2009 (49C9A073)
    NTI CD-ROM Filter Driver by NewTech Infosystems (likely a part of Acer Empowering Technology)
    Driver Reference Table - NTIDrvr.sys

    UBHelper.sys Mon Apr 27 14:48:19 2009 (49F57153)
    NTI CD &DVD-Maker or NTI Backup NOW! or NTI CD-Maker by NewTech Infosystems (usually in Acer Empowering Technology)
    Driver Reference Table - UBHelper.sys

    mwlPSDFilter.sys Tue Jun 2 16:07:30 2009 (4A24F9E2)
    EgisTec Inc. Fingerprint Biometrics
    Driver Reference Table - mwlPSDFilter.sys

    mwlPSDNServ.sys Tue Jun 2 16:07:39 2009 (4A24F9EB)
    EgisTec Inc. Fingerprint Biometrics
    Driver Reference Table - mwlPSDNServ.sys

    mwlPSDVDisk.sys Tue Jun 2 16:15:29 2009 (4A24FBC1)
    EgisTec Inc. Fingerprint Biometrics
    Driver Reference Table - mwlPSDVDisk.sys

    iaStor.sys Sat Oct 3 01:58:50 2009 (4AC65B7A)
    Intel Storage drivers
    Driver Reference Table - iaStor.sys

    aksdf.sys Wed Jul 21 21:59:49 2010 (4C471975)
    Data Filter Driver by Aladdin Knowledge Systems
    Driver Reference Table - aksdf.sys

    aksfridge.sys Fri Sep 24 17:27:55 2010 (4C9C8B3B)
    AksFridge driver (Aladdin security products)
    Driver Reference Table - aksfridge.sys

    To perform a clean install of a driver, follow this tutorial:

    Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

    Scan with Kaspersky TDSSKiller:

    ESET online scanner:

    Run Disk Check on your hard disk for file system errors and bad sectors on it:

    Check for heating issues using Speccy or HWmonitor

    Upload a screen shot: Screenshots and Files - Upload and Post in Seven Forums

    Post a screenshot of your Hard Drive(s) using Crystal Disk Info software:

    Run a Hard Drive test:

    Post back results.

    BSOD BUGCHECK SUMMARY
    Code:
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Tue Apr 22 00:36:24.941 2014 (UTC + 6:00)
    System Uptime: 0 days 0:17:10.189
    BugCheck D1, {10, 2, 0, fffff88000e8c87c}
    Probably caused by : Wdf01000.sys ( Wdf01000!FxIrpQueue::RemoveNextIrpFromQueue+14 )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  UNS.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Mon Apr 21 22:19:36.131 2014 (UTC + 6:00)
    System Uptime: 0 days 0:03:18.054
    BugCheck D1, {10, 2, 0, fffff88000e568c5}
    Probably caused by : Wdf01000.sys ( Wdf01000!FxIrpQueue::RemoveNextIrpFromQueue+5d )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  UNS.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Mon Apr 21 22:15:20.494 2014 (UTC + 6:00)
    System Uptime: 0 days 0:41:39.239
    BugCheck D1, {10, 2, 0, fffff88000ee887c}
    *** WARNING: Unable to verify timestamp for TeeDriverx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for TeeDriverx64.sys
    Probably caused by : TeeDriverx64.sys ( TeeDriverx64+e54d )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  IAStorDataMgrS
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Mon Apr 21 21:32:54.550 2014 (UTC + 6:00)
    System Uptime: 0 days 0:47:49.451
    BugCheck D1, {ffffffffffffffa4, 2, 1, fffff88000e7b73b}
    *** WARNING: Unable to verify timestamp for TeeDriverx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for TeeDriverx64.sys
    Probably caused by : TeeDriverx64.sys ( TeeDriverx64+ea43 )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  Few32.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Mon Apr 21 20:44:12.708 2014 (UTC + 6:00)
    System Uptime: 0 days 0:41:38.260
    BugCheck D1, {30, 2, 0, fffff88000e3d883}
    *** WARNING: Unable to verify timestamp for TeeDriverx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for TeeDriverx64.sys
    Probably caused by : TeeDriverx64.sys ( TeeDriverx64+e54d )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Sat Apr 19 04:23:45.135 2014 (UTC + 6:00)
    System Uptime: 0 days 0:24:55.925
    BugCheck D1, {b8, 2, 0, fffff88000e234fe}
    *** WARNING: Unable to verify timestamp for TeeDriverx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for TeeDriverx64.sys
    Probably caused by : TeeDriverx64.sys ( TeeDriverx64+e7d5 )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Sat Apr 19 03:57:35.836 2014 (UTC + 6:00)
    System Uptime: 0 days 0:10:58.013
    BugCheck D1, {10, 2, 0, fffff88000ee587c}
    *** WARNING: Unable to verify timestamp for TeeDriverx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for TeeDriverx64.sys
    Probably caused by : TeeDriverx64.sys ( TeeDriverx64+e54d )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Sat Apr 19 03:45:25.200 2014 (UTC + 6:00)
    System Uptime: 0 days 0:30:53.000
    BugCheck D1, {10, 2, 0, fffff88000e3087c}
    Probably caused by : Wdf01000.sys ( Wdf01000!FxIrpQueue::RemoveNextIrpFromQueue+14 )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  UNS.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Fri Apr 18 22:20:11.412 2014 (UTC + 6:00)
    System Uptime: 0 days 0:05:09.017
    BugCheck D1, {10, 2, 0, fffff88000eda87c}
    *** WARNING: Unable to verify timestamp for TeeDriverx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for TeeDriverx64.sys
    Probably caused by : TeeDriverx64.sys ( TeeDriverx64+e54d )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Fri Apr 18 22:13:40.351 2014 (UTC + 6:00)
    System Uptime: 0 days 1:41:33.906
    BugCheck D1, {ffffffffffffffa4, 2, 1, fffff88000f4273b}
    *** WARNING: Unable to verify timestamp for TeeDriverx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for TeeDriverx64.sys
    Probably caused by : TeeDriverx64.sys ( TeeDriverx64+e757 )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    
      My Computer


  3. Posts : 17
    Windows 7 32-bit
    Thread Starter
       #3

    Thank you for your help, koolkat77. I had trouble finding any updated drivers, really only finding one for hardlock. All others, including the updated Intel iaStor.sys, proved elusive. This hard drive has moved to a new machine and I no longer have any biometric devices or CD/DVD software. I honestly don't recall every having software related to thmany of these drivers. Most of the drivers could be seen in Device Manager under Hidden->Non-Plug-and-Play, but there was not an option to update. When I chose uninstall they went away but came back upon reboot.

    SFC ran and cleaned some things up I think.
    TDSSKiller found no threats.
    ESET found one Conduit threat and removed it.
    CHKDSK found and repaired many disk errors, it was good to see progress here.
    No heating issues with HWMonitor.
    Hard drive looks fine, this isn't the first one I've tried - this is a cloned disk. CrystalDiskInfo pic is attached.
    Hard drive test came back with everything looking good.

    How do you recommend I address the driver issues?
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    I'd recommend you to Clean Up Factory Bloatware, with a special reference to Point #13
    13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.
    Last edited by koolkat77; 23 Apr 2014 at 05:02.
      My Computer


  5. Posts : 17
    Windows 7 32-bit
    Thread Starter
       #5

    I think I got it figured out thanks to your help. After removing the Intel Management Engine the BSOD's ceased. Thanks again!
      My Computer


  6. Posts : 15,026
    Windows 10 Home 64Bit
       #6

    Glad you got it sorted! :)
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd
All times are GMT -5. The time now is 17:01.
Find Us