Single BSOD, similar circumstances to an older thread, driver help?


  1. Posts : 281
    Win7 Professional 64
       #1

    Single BSOD, similar circumstances to an older thread, driver help?


    First, if I'm posting in the wrong forum - and I admit I haven't followed the instructions for posting in this forum - I apologize. I'd not be posting here except for a single BSOD error I got last night.

    Circumstances are a bit similar to Not BSOD, I was informed to move this thread here, though. EVENT ID 56

    In my case, I was doing something very very "benign" and "low-stress" - saving a Word document - and my screen went black, and then I had a BSOD, possibly the first one I've seen on my machine, although I have had occasional stoppages related to the power supply or a bad CPU.

    I'm typing this from work so don't have access to the exact wording, but after restarting my computer, I checked the event log and there was an error "Intel Management Engine Interface driver has failed to perform handshake with the firmware" with Event ID 3. This error had never appeared before (I filtered the event log).

    Computer functioned normally the next three hours before I did my normal before-bed restart, it restarted normally, I logged in normally this morning, and used the computer for about 30 minutes with no problem. But I checked the event log and that same "Intel Management Engine Interface driver has failed to perform handshake with the firmware" error today, so it's appeared twice, evidently as the computer starts, the last two times I've started.

    Reading the Not BSOD, I was informed to move this thread here, though. EVENT ID 56 thread I ran a "clean" sfc /scannow check, then did a disk check (with "automatically fix" and "scan for/attempt recovery" boxes checked and left for work. My daughter told me an hour later that the computer had moved to the normal login screen.

    I've not yet run the memtest86+ suggested in the referenced thread.

    "Netting it all out" with the above as background, here are my concerns:

    • I have a yellow triangle caution icon in the Intel Management Engine Interface driver in device manager, as the above-referenced thread mentions - how do I make this go away?
    • The "Intel Management Engine Interface driver has failed to perform handshake with the firmware" never occurred with my computer until yesterday and has now occurred both times I've started my computer. How do I solve this?
    • (Broader and more generally) How common is it for a computer to "just have" a random BSOD? I have seen just about every computer I've used have these. Just some scary-looking BSOD, that never ever repeats again.
      My Computer

  2.    #2

    Sorry about the late reply, sometimes we miss threads.

    A normal functioning computer should never have BSODs.
    Put it this way, a bugcheck means Windows has found a critical fault where it cannot continue functioning otherwise data can be damaged.

    As for the Intel Management issues I recommend you create a restore point first to avoid further issues arising if you accidentally install the wrong thing (Or I suggest the wrong thing by mistake), so it's better to be safe than sorry.

       Warning

    Before changing drivers, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point Manually before altering drivers.


    Now that a restore point has been made I suggets you go here and update your Intel Management Engine Interface driver.

    https://downloadcenter.intel.com/Sea...agement+engine

    Can you also please upload the dump files that should have been created by the bugcheck.
    They're located in either two places, it depends on your configuration.
    C:/Windows/minidump or
    C:/Windows/memory.dmp

    If it's located in minidump then copy it to the desktop and then right click it and zip it up, upload that in your next reply.
    If it's located in Windows as memory.dmp then copy it to the desktop and then right click it and zip it up, now you will need to upload it to something like OneDrive as it's too large to upload directly to Seven Forums.
    Post the link of the site you uploaded it to here.
      My Computer


  3. Posts : 281
    Win7 Professional 64
    Thread Starter
       #3

    Thanks for the reply, and I have attached the minidump file, zipped, here.

    When I returned home from work tonight and logged into the computer, the event viewer showed no further errors (and for specificity, the error I got twice as described in the original post was Event ID 3, with event detail shown below), and all my Device Manager devices were normal, none with the yellow caution triangle.

    - System

    - Provider


    [ Name] HECIx64


    - EventID 3


    [ Qualifiers] 49159



    Level 2


    Task 0


    Keywords 0x80000000000000

    - TimeCreated


    [ SystemTime] 2014-05-02T02:20:10.181224100Z



    EventRecordID 312668


    Channel System


    Computer XXXWIN7


    Security
    - EventData






    000000000100000000000000030007C0000000000000000000000000000000000000000000000000
    Binary data:

    In Words
    0000: 00000000 00000001 00000000 C0070003
    0008: 00000000 00000000 00000000 00000000
    0010: 00000000 00000000

    In Bytes
    0000: 00 00 00 00 01 00 00 00 ........
    0008: 00 00 00 00 03 00 07 C0 .......À
    0010: 00 00 00 00 00 00 00 00 ........
    0018: 00 00 00 00 00 00 00 00 ........
    0020: 00 00 00 00 00 00 00 00 ........
    So maybe, I hope, everything is all set now.

    In addition to the attached minidump, and the above event log information, I pasted my full chkdsk from this morning below. The only (to me) abnormal-looking part is this:

    CHKDSK is verifying security descriptors (stage 3 of 5)...
    181504 file SDs/SIDs processed. Cleaning up 781 unused index entries from index $SII of file 0x9.
    Cleaning up 781 unused index entries from index $SDH of file 0x9.
    Cleaning up 781 unused security descriptors.
    Security descriptor verification completed.
    So from all this information - minidump, event detail, and chkdsk results, what insight can someone offer me?

    Full chkdsk below:

    Checking file system on C:
    The type of the file system is NTFS.

    A disk check has been scheduled.
    Windows will now check the disk.

    CHKDSK is verifying files (stage 1 of 5)...
    181504 file records processed. File verification completed.
    1515 large file records processed. 0 bad file records processed. 2 EA records processed. 89 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
    250936 index entries processed. Index verification completed.
    0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
    181504 file SDs/SIDs processed. Cleaning up 781 unused index entries from index $SII of file 0x9.
    Cleaning up 781 unused index entries from index $SDH of file 0x9.
    Cleaning up 781 unused security descriptors.
    Security descriptor verification completed.
    34717 data files processed. CHKDSK is verifying Usn Journal...
    37258400 USN bytes processed. Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
    181488 files processed. File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    4195719 free clusters processed. Free space verification is complete.
    Windows has checked the file system and found no problems.

    78046207 KB total disk space.
    60879008 KB in 138199 files.
    95436 KB in 34718 indexes.
    0 KB in bad sectors.
    288887 KB in use by the system.
    65536 KB occupied by the log file.
    16782876 KB available on disk.

    4096 bytes in each allocation unit.
    19511551 total allocation units on disk.
    4195719 allocation units available on disk.

    Internal Info:
    00 c5 02 00 80 a3 02 00 8e f3 04 00 00 00 00 00 ................
    3b 03 00 00 59 00 00 00 00 00 00 00 00 00 00 00 ;...Y...........
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

    Windows has finished checking your disk.
    Please wait while your computer restarts.
      My Computer

  4.    #4

    Can you try running SeaTools and see if it finds anything, I suggest the Long Generic Test.


    Run SeaTools to see if your HDD or SSD is failing

    Post back the results.

    Code:
    BugCheck 24, {1904fb, fffff88003192b58, fffff880031923b0, fffff880012a9ee4}
    
    Probably caused by : Ntfs.sys ( Ntfs!TxfSetupTransactionContextFromCcb+34 )
      My Computer


  5. Posts : 281
    Win7 Professional 64
    Thread Starter
       #5

    Although the fact that this occurred at all bothers me, I'm marking this as solved.

    After I did the sfc /scannow and chkdsk more than 72 hours ago, the computer has performed normally, the error events that had started to show in my event viewer no longer happened, and the devices, all devices, show as fine in device manager. I've continued to monitor the event viewer in that time, and no events have happened that are of concern. There have never been events associated with any of my HDDs.

    So I'm running fine, and I hope the good behavior of the past 72 hours persists for a long time.
      My Computer

  6.    #6

    That's good news :)
    Any more issues let me know.
      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 04:41.
Find Us