Windows 10 Fails Regular Boot, Safe Mode boot OK


  1. Posts : 16
    Windows 10
       #1

    Windows 10 Fails Regular Boot, Safe Mode boot OK


    Hi,

    I have a desktop Windows 10 x64 machine that's been working fine for months/years. It was automatically updated from Win7 last year.

    This morning I replaced the 2x4GB DDR3 memory with 2x8GB DDR3. This seemed to work though for some reason it works at 800MHz instead of the 1600MHz that the memory supports. The BIOS shows mem freq 1600 as expected. But this is the smaller issue. The PC worked booted fine.

    When everything seemed to working as expected, I was still bothered by the slow startup and login times. Now with 16GB I had expected these times to improve.
    I installed Windows SDK performance recording tool and set it to record the boot sequence and restarted the PC.

    Windows failed to boot twice (UNEXPECTED KERNEL MODE TRAP) and went into the auto diagnostic repair mode. Restore just spins until I lose patience. I did manage to boot in safe mode and disable the recording. It did not help.

    Running sfc/scannow "did not find any integrity violations".

    I also managed to uninstall the Windows SDK/Perf Rec (by restarting the MSI service) - to no avail.

    I ran the Windows memory test, but when it's done it reboots, the reboot fails, and I never did see the results.

    I replaced the new RAM with the original ones, but this did not make any difference (BIOS setting are as they were originally).

    I'm totally stumped!!

    Please advise,

    Thanks!!
      My Computer

  2. philc43's Avatar
    Posts : 4,358
    64bit Win 10 Pro ver 1909 Build 18363.535 and W10 Insider Ver 2004 Build 19536
       #2

    Hello adish and welcome to TenForums :)

    The recent crashes are all suggesting the ESET driver eamonm.sys might be a factor.

    Code:
    BugCheck 1000007F, {8, ffff84001fc88b30, ffff840020108000, fffff8019ea3b196}
    
    *** WARNING: Unable to verify timestamp for eamonm.sys
    *** ERROR: Module load completed but symbols could not be loaded for eamonm.sys
    Try uninstalling the ESET remote admin software and see if this helps.
      My Computers


  3. Posts : 16
    Windows 10
    Thread Starter
       #3

    Thanks for the answer - how/where did you find this?
    Is there a tutorial somewhere about how to read those reports?

    Anyway, uninstalling ESET did seem to do the trick and the computer booted properly.

    Strangely enough, reinstalling it again from scratch causes the same BSOD problem.
      My Computer

  4. Ztruker's Avatar
    Posts : 10,251
    Windows 10 Pro X64 1909 18363.815
       #4

    Start here:

    Great tutorials on setting up to read Windows 10 mini dumps.

    How to Install and Configure WinDBG for BSOD Analysis
    WinDBG - The Basics for Debugging Crash Dumps in Windows 10
      My Computers


 

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

Designer Media Ltd
All times are GMT -5. The time now is 15:41.
Find Us




Windows 10 Forums