BSOD 1E, 0D, different everytime

Page 3 of 3 FirstFirst 123

  1. Posts : 23
    Windows 7
    Thread Starter
       #21

    Ok as soon as i get back to the job i will let u know
      My Computer


  2. Posts : 23
    Windows 7
    Thread Starter
       #22

    After leaving the laptop playing 4 hours of youtube videos it seem to be ok so will let you know if this comes back to us, and will post the next one if it does.
      My Computer


  3. Posts : 23
    Windows 7
    Thread Starter
       #23

    Another BSOD for you guys,
      My Computer


  4. Posts : 23
    Windows 7
    Thread Starter
       #24

    yellowstone said:
    After leaving the laptop playing 4 hours of youtube videos it seem to be ok so will let you know if this comes back to us, and will post the next one if it does.
    In good news i can say that this laptop didn't return back to us so thanks for the help on that just got another one above this post
      My Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #25

    Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, 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 enabling DV.

       Tip



    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


  6. Posts : 23
    Windows 7
    Thread Starter
       #26

    Arc said:
    Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, 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 enabling DV.

       Tip



    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    Let us know the results, with the subsequent crash dumps, if any.
    Thanks that worked and we fixed that one.
      My Computer


  7. Posts : 23
    Windows 7
    Thread Starter
       #27

    Now we have a new one.

    We have check the HDD, done a external chkdsk and local chkdsk,

    We have already done a 24 hour memtest and changed the memory.

    Here is the BSOD:
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #28

    The last crash is caused by McAfee Host Intrusion Detection Link Driver.
    Code:
    fffff880`06b27298  fffff880`015bdfdcUnable to load image \SystemRoot\system32\drivers\mfehidk.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for mfehidk.sys
    *** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
     mfehidk+0x42fdc
    Description here: Driver Reference Table - mfehidk.sys

    Uninstall McAfee Using McAfee Removal Tool. 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.

    Let us know the results.
      My Computer


  9. Posts : 23
    Windows 7
    Thread Starter
       #29

    Hi Arc,

    I know it been a long time, that did fix the computer many thanks,

    I was wondering if you could help with another one that has had my team confused,

    We have just built a brand new system:
    CPU: AMD FX 6300
    RAM: 4GB
    SSD: 120GB
    HDD: 1TB
    Motherboard: Asus M5A78L-M LE

    Once installing Windows 7 to the system it will get to the completing installation then after around 5 mins of sitting there it will then BSOD with a 0x00000101,

    We are so confused as why this would do this on brand new stock,

    We had a dead identical system built at the same time and that one is running fine.

    Could you please help us with our investigation.

    Many thanks

    Yellowstone
      My Computer


  10. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #30

    As it is a different PC, and a different issue, start another thread for it. And, put the details in your system specs for that PC.
    See your system specs and fill it up here.
      My Computer


 
Page 3 of 3 FirstFirst 123

  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:27.
Find Us