Bsod 000000a irq


  1. Posts : 1
    64
       #1

    Bsod 000000a irq


    Just started happening more frequently the past couple weeks. System is about 6 months old. I'm assuming it has to do with a device driver, but don't recall any significant changes during that time frame.
    Today I just went through the device manager to verify nothing showed as an error, then ran windows updates to update the logitech software. Finally ran lenovo update to update the network drivers.

    I've attached the dump/logs
      My Computer


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

    Welcome to Seven Forums.

       Note
    Do not start the trial version of MalwareBytes


    Update this driver:
    e1c62x64.sys Tue Dec 21 15:30:56 2010 (4D1073D0)
    Intel(R) 82579V Gigabit Network Connection driver
    Driver Reference Table - e1c62x64.sys


    • System File Checker
      • The SFC /SCANNOW Command - System File Checker scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible. If you have modified your system files as in theming explorer/system files, running sfc /scannow will revert the system files to it's default state.
    • Run Disk Check in Windows 7
      • Run this on your Hard Drive(s). This will show you how to run Check Disk or chkdsk in Windows 7 to check a selected hard disk for file system errors and bad sectors on it. With both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log


    • Test and Diagnose RAM issues with MEMTEST86+
      • Pay close attention to Part 3 of the tutorial "If you have errors". Take the test for at least 7-10 passes. It may take up to 22 passes to find problems.
        • Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. RAM - Test with Memtest86+

    Bugcheck Summary:
    Code:
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Tue Nov 19 23:25:10.551 2013 (UTC + 6:00)
    System Uptime: 0 days 2:25:28.678
    BugCheck A, {8, 2, 0, fffff8000301676c}
    *** WARNING: Unable to verify timestamp for e1c62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
    Probably caused by : e1c62x64.sys ( e1c62x64+23ed7 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Tue Nov 19 20:58:40.729 2013 (UTC + 6:00)
    System Uptime: 0 days 18:32:23.334
    BugCheck A, {0, 2, 1, fffff8000306db42}
    *** WARNING: Unable to verify timestamp for e1c62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
    Probably caused by : e1c62x64.sys ( e1c62x64+23ed7 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Tue Nov 19 02:24:48.376 2013 (UTC + 6:00)
    System Uptime: 0 days 1:00:19.714
    BugCheck D1, {68, 2, 1, fffff88005a95f60}
    *** WARNING: Unable to verify timestamp for e1c62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
    Probably caused by : e1c62x64.sys ( e1c62x64+23f60 )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Tue Nov 19 01:23:28.849 2013 (UTC + 6:00)
    System Uptime: 0 days 0:12:47.589
    BugCheck D1, {68, 2, 1, fffff88004695f60}
    *** WARNING: Unable to verify timestamp for e1c62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
    Probably caused by : e1c62x64.sys ( e1c62x64+23f60 )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Tue Nov 19 01:09:39.510 2013 (UTC + 6:00)
    System Uptime: 2 days 23:16:34.285
    BugCheck D1, {90, 2, 1, fffff8800475bfd3}
    *** WARNING: Unable to verify timestamp for e1c62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
    Probably caused by : e1c62x64.sys ( e1c62x64+23fd3 )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  dwm.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Sat Nov 16 01:51:59.430 2013 (UTC + 6:00)
    System Uptime: 0 days 0:29:48.888
    BugCheck D1, {68, 2, 1, fffff88003160f60}
    *** WARNING: Unable to verify timestamp for e1c62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
    Probably caused by : e1c62x64.sys ( e1c62x64+23f60 )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Sat Nov 16 00:32:20.382 2013 (UTC + 6:00)
    System Uptime: 1 days 20:30:58.586
    BugCheck D1, {90, 2, 1, fffff88005a2ffd3}
    *** WARNING: Unable to verify timestamp for e1c62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
    Probably caused by : e1c62x64.sys ( e1c62x64+23fd3 )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  SearchIndexer.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Wed Nov 13 21:04:34.767 2013 (UTC + 6:00)
    System Uptime: 0 days 0:01:39.704
    BugCheck D1, {68, 2, 1, fffff88005223f60}
    *** WARNING: Unable to verify timestamp for e1c62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
    Probably caused by : e1c62x64.sys ( e1c62x64+23f60 )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  Skype.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Wed Nov 13 21:02:10.944 2013 (UTC + 6:00)
    System Uptime: 0 days 0:05:18.674
    BugCheck A, {8, 2, 0, fffff800035ee76c}
    *** WARNING: Unable to verify timestamp for e1c62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
    Probably caused by : e1c62x64.sys ( e1c62x64+23ed7 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      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 21:25.
Find Us