Windows 10 won't boot - fresh install

Page 12 of 13 FirstFirst ... 210111213 LastLast

  1. Posts : 219
    Win 10 Pro 64-bit
    Thread Starter
       #111

    Thanks for the tip Ed. I downloaded Speccy, which enabled me to fill in the motherboard info, but I can't see anything in there about the PSU.

    Any ideas? Thanks again.
      My Computer


  2. Posts : 39,964
    windows 10 professional version 1607 build 14393.969 64 bit
       #112
      My Computer


  3. Posts : 219
    Win 10 Pro 64-bit
    Thread Starter
       #113

    zbook said:
    The option that EdTittel just suggested is: Speccy - System Information - Free Download
    Yes, that's the one I used. As I said, I can't see any mention of PSU.
      My Computer


  4. Posts : 219
    Win 10 Pro 64-bit
    Thread Starter
       #114

    Right, just ran WhoCrashed, and here is the result of the analysis...
    Windows 10 won't boot - fresh install-whocrashed.png

    I've also attached a zip from the log collector.

    Thanks
    Windows 10 won't boot - fresh install Attached Files
      My Computer


  5. Posts : 39,964
    windows 10 professional version 1607 build 14393.969 64 bit
       #115

    Please uninstall Eset and turn on Windows defender:
    Uninstall ESET manually using the ESET uninstaller toolESET Knowledgebase


    Open Ccleaner > windows tab > scroll down to system and advanced > post an image into the thread using one drive or drop box share link.

    In the left lower corner search type system > open system control panel > on the left pane click advanced system settings > under startup and recovery click settings > post an image into the thread using a one drive or drop box share link.

    In the left lower corner search type system > open system control panel > on the left pane click advanced system settings > under performance click settings > on the performance options window click the advanced tab > under virtual memory click change > post an image into the thread of the virtual memory window

    This was displayed as a problem device:
    Code:
    Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64    ROOT\NET\0000    This device is disabled.
    Open device manager > click view > show hidden devices > look for a cisco entry > post an image into the thread as a one drive or drop box share link.






    Code:
    Event[17266]:  Log Name: System  Source: Microsoft-Windows-WHEA-Logger  Date: 2018-01-14T14:48:47.718  Event ID: 2  Task: N/A  Level: Warning  Opcode: Info  Keyword: WHEA Error Event Logs  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: Daisy  Description: A corrected hardware error has occurred. A record describing the condition is contained in the data section of this event.Event[17267]:  Log Name: System  Source: Microsoft-Windows-WHEA-Logger  Date: 2018-01-14T14:49:47.708  Event ID: 2  Task: N/A  Level: Warning  Opcode: Info  Keyword: WHEA Error Event Logs  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: Daisy  Description: A corrected hardware error has occurred. A record describing the condition is contained in the data section of this event.
    Code:
    Event[801]:  Log Name: Microsoft-Windows-Kernel-WHEA/Errors  Source: Microsoft-Windows-Kernel-WHEA  Date: 2018-01-11T23:07:48.687  Event ID: 20  Task: N/A  Level: Information  Opcode: Info  Keyword: WHEA Error Events  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Daisy  Description: WHEA EventEvent[802]:  Log Name: Microsoft-Windows-Kernel-WHEA/Errors  Source: Microsoft-Windows-Kernel-WHEA  Date: 2018-01-14T14:48:46.709  Event ID: 20  Task: N/A  Level: Information  Opcode: Info  Keyword: WHEA Error Events  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Daisy  Description: WHEA EventEvent[803]:  Log Name: Microsoft-Windows-Kernel-WHEA/Errors  Source: Microsoft-Windows-Kernel-WHEA  Date: 2018-01-14T14:49:46.708  Event ID: 20  Task: N/A  Level: Information  Opcode: Info  Keyword: WHEA Error Events  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Daisy  Description: WHEA Event

    Code:
    Event[17456]:  Log Name: System  Source: Service Control Manager  Date: 2018-01-15T22:16:14.825  Event ID: 7024  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Daisy  Description: The Remote Access Connection Manager service terminated with the following service-specific error: {Virtual Memory Minimum Too Low} Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied. For more information, see Help.

    Code:
    Event[17450]:  Log Name: System  Source: Disk  Date: 2018-01-15T22:16:08.549  Event ID: 158  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Daisy  Description: Disk 3 has the same disk identifiers as one or more disks connected to the system. Go to Microsoft's support website (http://support.microsoft.com) and search for KB2983588 to resolve the issue.
    Code:
    Event[17455]:  Log Name: System  Source: RasMan  Date: 2018-01-15T22:16:14.825  Event ID: 20030  Task: N/A  Level: Error  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Daisy  Description: Remote Access Connection Manager failed to start because it could not load one or more communication DLLs. Ensure that your communication hardware is installed and then restart the Remote Access Connection Manager service. If the problem persists, contact the system administrator. There was an unknown error.
    Code:
    Event[17028]:  Log Name: System  Source: Microsoft-Windows-WHEA-Logger  Date: 2018-01-11T23:07:49.703  Event ID: 47  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: Daisy  Description: A corrected hardware error has occurred.Component: MemoryError Source: Corrected Machine CheckThe details view of this entry contains further information.
    Code:
    Event[17400]:  Log Name: System  Source: UASPStor  Date: 2018-01-15T18:33:56.892  Event ID: 129  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Daisy  Description: Reset to device, \Device\RaidPort2, was issued.Event[17401]:  Log Name: System  Source: UASPStor  Date: 2018-01-15T18:34:00.892  Event ID: 129  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Daisy  Description: Reset to device, \Device\RaidPort2, was issued.Event[17402]:  Log Name: System  Source: UASPStor  Date: 2018-01-15T18:34:04.893  Event ID: 129  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Daisy  Description: Reset to device, \Device\RaidPort2, was issued.
      My Computer


  6. Posts : 219
    Win 10 Pro 64-bit
    Thread Starter
       #116

    Hello, sorry I haven't replied, been down with the flu. I'll try and get this done later and post the results.

    Just out of interest, please can you explain to me where you are going with this? I'm interested to know how you're looking at the problem. As I mentioned before, the two issues I see are the sporadic black screen when booting, and the sporadic issue with the Start menu not working. Once the machine is booted correctly, everything seems to be fine. Just interested to know how your investigations are directed towards those.

    Thanks again.

    P.S. The Cisco utility was only installed about an hour before I took that last log collection, so won't have been the cause of anything I saw beforehand.
      My Computer


  7. Posts : 39,964
    windows 10 professional version 1607 build 14393.969 64 bit
       #117

    See post #96 steps #5 and #10.
    When testing for WHEA hardware errors we need to systematically check CPU, GPU, RAM and drive.
    The pending tests are CPU and GPU.
      My Computer


  8. Posts : 219
    Win 10 Pro 64-bit
    Thread Starter
       #118

    I asked you about running those tests, as I was a little nervous, given that my system seemed to be running hot before I started. Please can you comment.

    When I use SpeedFan, the GPUs always show hot, and the Cores often do. Right now they are all showing hot...

    Windows 10 won't boot - fresh install-speedfan.png

    Is it wise to run such tests?
      My Computer


  9. Posts : 39,964
    windows 10 professional version 1607 build 14393.969 64 bit
       #119

    The tests are interactive.
    The aim is to find out what is causing the hardware errors in the event viewer.
    Then decisions can be made.
    Each test has criteria to look for to abort testing
      My Computer


  10. Posts : 219
    Win 10 Pro 64-bit
    Thread Starter
       #120

    You didn't answer my question.

    From the Prime95 web site...

    Warning

    While running Prime95 your CPU will become incredibly hot, it is imperative that you keep a constant watch of your CPU temperature with a system monitoring utility such as Speccy, Speedfan or HWMonitor. If your CPU temperature does reach dangerous levels stop the Prime95 stress test to prevent inflicting damage on your CPU.


    Given that my CPUs are showing hot before I even start the test, is it wise to run the test at all? I don't know what they consider "dangerous levels" but given that I have flames, I am dubious about heating the CPUs even more.

    Actually, I'm a little concerned that they are so hot anyway, as I'm not particularly stressing the machine. Any idea why they would be so hot?

    Comments?
      My Computer


 

  Related Discussions
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 12:50.
Find Us




Windows 10 Forums