Windows 10: BSOD on Startup after clean shutdown

Discus and support BSOD on Startup after clean shutdown in Windows 10 BSOD Crashes and Debugging to solve the problem; My Windows 10 system sometimes crashed on startup, after loading progress. The monitor would show blank white screen, or sometimes the blue screen... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by RTH, Sep 9, 2017.

  1. RTH
    RTH Win User

    BSOD on Startup after clean shutdown


    My Windows 10 system sometimes crashed on startup, after loading progress. The monitor would show blank white screen, or sometimes the blue screen (sometimes with corrupted display).
    This does not happen so often, but I'd like to know the cause. The daily operation of the computer itself is normal and barely had any crashes.

    I've attached my diagnostic report in this thread.

    Thank you.

    :)
     
  2. Amorie Win User

    DRIVER_VERIFIED_DETECTED_VIOLATION and other BSOD errors on Windows 10.

    I understand that a clean boot isnt the source of the bsod, I have now done 3 fresh installs. Also turning off fast startup I doubt will fix the issue. Since it doesnt affect restart. Whether I restart or completly shutdown i have a high chance of BSOD.
    Ive gone days without out a BSOD if i never shutdown or restart my computer. the moment I do shortly after I BSOD.

    Thanks for the response, ill try it out the fast startup change.
     
    Amorie, Sep 9, 2017
    #2
  3. Windows startup is very slow after updated windows

    My PC is windows 10 Home Language. After updated windows my PC is too slow working when Startup and shutdown. I have cleaned all Temp files and "Windows.old" folder. Now my PC is very slow to startup and shutdown.
     
    Nishikanta Wangkhem, Sep 9, 2017
    #3
  4. philc43 Win User

    BSOD on Startup after clean shutdown

    There was one crash mini-dump file created today with a 0x116 stop code (VIDEO_TDR_FAILURE). It's not a true crash, in the sense that the bluescreen was initiated only because of a long delay between the video driver and video hardware rather than any processing error.

    Looking back through the eventlogs the only thing I can spot is that this error happened to coincide with a "Windows failed fast startup with error status 0xC0000001". This has happened twice.

    You could try turning off Fast Startup to see if it makes a difference and prevents these startup crashes, however, if it's fairly infrequent it may not be something you are too bothered by. Turning off Fast startup will cause your boot times to increase a little so that would be the only downside.

    Turn On or Off Fast Startup in Windows 10
     
    philc43, Sep 9, 2017
    #4
  5. Spectrum Win User
    Hi RTH,

    As Philc43 mentioned, this is due to your GPU driver not responding (for over 2 seconds) after a reset has been issued to it. This is generally due to a graphics driver misbehaving or the GPU failing.

    One of the first things you should do is update to the latest NVIDIA driver for your 1060.

    If you have overclocked your GPU, please return all settings to default so we can rule out that as an issue.

    Also monitor your GPU temperatures, ensuring that your GPU is not overheating. This can be done using the Nvidia driver's control panel, or something like HWMonitor

    Reading this bottom to top, we can see that the kernel attempted to send a reset to the GPU, but nvlddmkm.sys (the NVIDIA graphics driver) did not respond in time.

    Code: 0: kd> !dpx Start memory scan : 0xffffe781ddec79d8 ($csp) End memory scan : 0xffffe781ddec8000 (Kernel Stack Base) rsp : 0xffffe781ddec79d8 : 0xfffff801e048a238 : dxgkrnl!TdrBugcheckOnTimeout+0xec 0xffffe781ddec79d8 : 0xfffff801e048a238 : dxgkrnl!TdrBugcheckOnTimeout+0xec *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys 0xffffe781ddec7a18 : 0xfffff801e046d0df : dxgkrnl!ADAPTER_RENDER::Reset+0x153 0xffffe781ddec7a48 : 0xfffff801e046a27f : dxgkrnl!DXGADAPTER::Reset+0x307 0xffffe781ddec7a70 : 0xfffff8004522e100 : nt!ExNode0 0xffffe781ddec7a98 : 0xfffff801e0489a25 : dxgkrnl!TdrResetFromTimeout+0x15 *** WARNING: Unable to verify timestamp for epfwwfp.sys *** ERROR: Module load completed but symbols could not be loaded for epfwwfp.sys 0xffffe781ddec7ab8 : 0xfffff8004522e100 : nt!ExNode0 0xffffe781ddec7ac8 : 0xfffff801e0489b67 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27 0xffffe781ddec7ad8 : 0xfffff8004522e280 : nt!ExNode0+0x180 0xffffe781ddec7ae8 : 0xfffff801de018b40 : NTFS!NtfsFspClose 0xffffe781ddec7af0 : 0xfffff8004522e280 : nt!ExNode0+0x180 0xffffe781ddec7af8 : 0xfffff80044edf419 : nt!ExpWorkerThread+0xe9 0xffffe781ddec7b08 : 0xfffff801e0489b40 : dxgkrnl!TdrResetFromTimeoutWorkItem 0xffffe781ddec7b78 : 0xfffff8004522e280 : nt!ExNode0+0x180 0xffffe781ddec7b80 : 0xfffff80044edf330 : nt!ExpWorkerThread 0xffffe781ddec7b88 : 0xfffff80044f2f7c5 : nt!PspSystemThreadStartup+0x41 0xffffe781ddec7bd8 : 0xfffff80044fcdd36 : nt!KiStartSystemThread+0x16 0xffffe781ddec7bf0 : 0xfffff80044f2f784 : nt!PspSystemThreadStartup[/quote]
     
    Spectrum, Sep 9, 2017
    #5
  6. zbook New Member
    In the code that Spectrum posted there was a 2nd misbehaving driver.

    Please uninstall ESET software.
    Uninstall and reinstall your ESET home productESET Knowledgebase


    Please turn on Windows defender.

    There were multiple corruption entries in the event log.
    The last one was in May.
    What troubleshooting was done for the drive corruption noted in the event viewer?
    There were paging operation problems.
    There were drive hardware problems reported in the event log.

    Open administrative command prompt and type or copy and paste:

    1) sfc /scannow
    2) dism /online /cleanup-image /restorehealth

    3) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    4) chkdsk /x /f /r
    This may take many hours so plan to run overnight.

    5) post the chkdsk results using the information in this link:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials

    6) Run HDTune:
    HD Tune website

    to check the health,
    scan for errors, no quick scan but full scan
    run a benchmark.


    It may take some time, but please take the time you need to perform it properly.
    When above is done please make screenshots of the following
    the health,
    the error scan,
    the benchmark incl. following
    transfer rate,
    access time,
    burst rate,
    cpu usage.
    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials




    epfwwfp.sys ESET Personal Firewall Driver Support: ESET Knowledgebase
    Downloads: Downloads for Home

    Code: epfwwfp epfwwfp c:\windows\system32\drivers\epfwwfp.sys Kernel Driver Yes System Running OK Ignore No Yes[/quote] Code: 10/09/2017 10.08 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 116 P2: ffffa505fe97d280 P3: fffff801e35a08cc P4: ffffffffc000009a P5: 4 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\091017-7453-01.dmp \\?\C:\Windows\Temp\WER-9343-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_116_d719b2331e75468b1326239556fdbfc7a7675e4_00000000_cab_0c058279 Analysis symbol: Rechecking for solution: 0 Report Id: 8d89665c-226a-44d9-85cf-ed3955dd8919 Report Status: 2048 Hashed bucket:10/09/2017 10.07 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 116 P2: ffffa505fe97d280 P3: fffff801e35a08cc P4: ffffffffc000009a P5: 4 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\091017-7453-01.dmp \\?\C:\Windows\Temp\WER-9343-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_116_d719b2331e75468b1326239556fdbfc7a7675e4_00000000_0390395f Analysis symbol: Rechecking for solution: 0 Report Id: 8d89665c-226a-44d9-85cf-ed3955dd8919 Report Status: 4 Hashed bucket: 23/08/2017 14.23 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 116 P2: ffffcc81d7b98250 P3: fffff803186b08cc P4: ffffffffc000009a P5: 4 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\082317-7375-01.dmp \\?\C:\Windows\Temp\WER-9234-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_116_fcadc336db85e55085cfeb30905188e5bb5f6e53_00000000_cab_1cd470bb Analysis symbol: Rechecking for solution: 0 Report Id: a9a9d0d8-4a15-485d-9b47-97269f409cda Report Status: 2048 Hashed bucket: 23/08/2017 14.22 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 116 P2: ffffcc81d7b98250 P3: fffff803186b08cc P4: ffffffffc000009a P5: 4 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\082317-7375-01.dmp \\?\C:\Windows\Temp\WER-9234-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_116_fcadc336db85e55085cfeb30905188e5bb5f6e53_00000000_037c47b7 Analysis symbol: Rechecking for solution: 0 Report Id: a9a9d0d8-4a15-485d-9b47-97269f409cda Report Status: 4 Hashed bucket:[/quote] Code: Event[1057]: Log Name: System Source: Ntfs Date: 2017-02-13T00:55:55.384 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: AFANSYAH-PC Description: A corruption was discovered in the file system structure on volume ??.[/quote] Code: Event[1057]: Log Name: System Source: Ntfs Date: 2017-02-13T00:55:55.384 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: AFANSYAH-PC Description: A corruption was discovered in the file system structure on volume ??. The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x9000000000009. The name of the file is "<unable to determine file name>".[/quote] Code: Event[1066]: Log Name: System Source: Ntfs Date: 2017-02-13T01:12:49.394 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: AFANSYAH-PC Description: A corruption was discovered in the file system structure on volume ??.[/quote] Code: Event[41435]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-05-18T21:00:43.221 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: AFANSYAH-PC Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume11. (A device which does not exist was specified.)[/quote] Code: Event[41436]: Log Name: System Source: disk Date: 2017-05-18T21:00:43.221 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR16 during a paging operation.[/quote] Code: Event[45595]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45596]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45597]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45598]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45599]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45600]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45601]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45602]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45603]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45604]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45605]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45606]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45607]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45608]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45609]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45610]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45611]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45612]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45613]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45614]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45615]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation. Event[45616]: Log Name: System Source: disk Date: 2017-08-07T20:51:49.096 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: An error was detected on device \Device\Harddisk2\DR4 during a paging operation.[/quote] Code: Event[45594]: Log Name: System Source: Microsoft-Windows-NDIS Date: 2017-08-07T20:51:48.261 Event ID: 10317 Task: PnP Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: AFANSYAH-PC Description: Miniport Microsoft Hosted Network Virtual Adapter, {0B25B9C7-22D1-478F-BA20-DEA8D4C01876}, had event Fatal error: The miniport has failed a power transition to operational power[/quote] Code: Event[3617]: Log Name: System Source: disk Date: 2017-03-09T21:35:37.573 Event ID: 154 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: The IO operation at logical block address 0x5808a33 for Disk 0 (PDO name: \Device\00000032) failed due to a hardware error.[/quote] Code: Event[21795]: Log Name: System Source: disk Date: 2017-03-09T21:40:25.218 Event ID: 154 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: AFANSYAH-PC Description: The IO operation at logical block address 0xf4d5d09 for Disk 0 (PDO name: \Device\00000032) failed due to a hardware error.[/quote]
     
    zbook, Sep 10, 2017
    #6
  7. RTH
    RTH Win User
    @philc43

    @Spectrum
    Thank you, I don't like to think that my GPU is failing... I hope not because it's only a few months old lol. I never overclocked things either. Can it be checked that I used two GPU drivers on my system (Intel and NVIDIA) because I have two monitor ( the main monitor is connected to my GPU and a 2nd monitor is on my motherboard)? I have to install Intel driver because it wouldn't display correct resolution on my 2nd monitor.

    @zbook Thank you for a thorough explanation, I have HDD Sentinel installed and all of them reported 'Excellent' health on my installed hard drives. Those error messages could be coming from my External USB HDD. Although I'll do your steps just to make sure.
    Regarding the misbehaving drivers I might will have to do clean reset after all this.
     
  8. Spectrum Win User

    BSOD on Startup after clean shutdown

    Are you not planning on updating your nvidia driver? That is likely the issue.
     
    Spectrum, Sep 10, 2017
    #8
  9. RTH
    RTH Win User
    I just updated my Nvidia driver a few weeks ago so that maybe not the issue.
     
  10. Spectrum Win User
    The crash dumps show otherwise, you are getting a video driver reset error which is causing the blue screen.
     
    Spectrum, Sep 10, 2017
    #10
  11. philc43 Win User
    If it was a driver issue it would be happening all the time, I had observed that it was only happening when the system was starting up with a failed fast startup process. My theory was that there might be a connection and so I wanted to rule this out.

    I had noticed that the graphics driver was already updated which is why I did not suggest that route.
     
    philc43, Apr 5, 2018
    #11
Thema:

BSOD on Startup after clean shutdown

Loading...
  1. BSOD on Startup after clean shutdown - Similar Threads - BSOD Startup clean

  2. Freezing & shutdown of application after startup

    in Windows 10 Gaming
    Freezing & shutdown of application after startup: I have a HP Probook, within 5 mins of startup, screen freezes and then whatever program I have open crushes. Only does it once just after startup then runs beautifully until I shutdown. I've done a reset and seemed to be working fine until I installed some of my favorite...
  3. Freezing & shutdown of application after startup

    in Windows 10 Software and Apps
    Freezing & shutdown of application after startup: I have a HP Probook, within 5 mins of startup, screen freezes and then whatever program I have open crushes. Only does it once just after startup then runs beautifully until I shutdown. I've done a reset and seemed to be working fine until I installed some of my favorite...
  4. Freezing & shutdown of application after startup

    in Windows 10 Customization
    Freezing & shutdown of application after startup: I have a HP Probook, within 5 mins of startup, screen freezes and then whatever program I have open crushes. Only does it once just after startup then runs beautifully until I shutdown. I've done a reset and seemed to be working fine until I installed some of my favorite...
  5. BSOD at shutdown with fast startup feature enabled

    in Windows 10 BSOD Crashes and Debugging
    BSOD at shutdown with fast startup feature enabled: I have an Intel NUC which is having BSOD only at shutdown, with Windows 10. I have narrowed it down to the fast startup feature. If disable it shutdows properly, without BSOD. If it is enabled, it display BSOD just before shutdown. I have latest BIOS and latest drivers. Can...
  6. BSOD on Windows 10 during startup or shutdown

    in Windows 10 BSOD Crashes and Debugging
    BSOD on Windows 10 during startup or shutdown: Greetings, we prepared a brand new Dell Precision 7540 Specification here: We added a 16GB crucial certified DDR, that is recognised by Win. We use a compatible usb-c docking station to have 2 more monitors connected, usb keyboard, mouse and the ethernet. The docking is...
  7. BSOD after startup

    in Windows 10 Ask Insider
    BSOD after startup: So I was messing with msconfig and ended up setting my maximum ram to 250. This caused BSOD right after startup each time. Booting into safe mode didnt work. Resetting the system also didnt work. Is there any possible way to reset the msconfig settings? Prefer not to loose...
  8. Shutdown and startup

    in Windows 10 Performance & Maintenance
    Shutdown and startup: Hello . My windows 10 pc suddenly has been taking ages to shut off. I press shutdown and it takes 30 seconds for the shutdown screen to show. This randomly started 1 day. I reset the pc, keeping only my games and some documents and it,s still the same. It also takes longer to...
  9. Laptop shutdown after startup

    in Windows 10 Performance & Maintenance
    Laptop shutdown after startup: So my hp laptop shutdowns after turning it on. I can get it to fully load once in a while but the majority of the time it simply goes to a black screen after startup and powers off. Any suggestions?...
  10. Computer Hangs at Startup After Shutdown

    in Windows 10 Support
    Computer Hangs at Startup After Shutdown: My system "hangs" after I Shut Down and then start back up. It doesn't occur when I Restart the system. * It "Hangs " when it gets to the black screen with the blue Windows logo in the center. I've waited a half an hour and remained hung. The "round working dots (for lack...