Excessive boot times >2 mins Windows 10 + Apricorn Velocity DUOx2 PCIe

Page 1 of 2 12 LastLast

  1. Posts : 633
    Win 10 Pro x64 1607 (Build 14393.953)
       #1

    Excessive boot times >2 mins Windows 10 + Apricorn Velocity DUOx2 PCIe


    Hi,

    I have issues when booting my EFI Windows 10 Pro x64 - AU 1607 - 14393.321 SSD on a Mac Pro 5.1 w Apricorn Velocity DUO x2

    Last boot time was 1:58 min while:
    - Fast Startup checked
    - Downloaded 'latest' 2006 (?) AHCI drivers for the Marvell 9230 controller chip on my Velocity DUO x2 - two SSD PCIe extension card:

    Excessive boot times >2 mins Windows 10 + Apricorn Velocity DUOx2 PCIe-marvell-9230-driver-ahci.jpg

    Excessive boot times >2 mins Windows 10 + Apricorn Velocity DUOx2 PCIe-samsung-magincian.jpg

    Excessive boot times >2 mins Windows 10 + Apricorn Velocity DUOx2 PCIe-iastorev.jpg

    Excessive boot times >2 mins Windows 10 + Apricorn Velocity DUOx2 PCIe-storeahci.jpg

    Excessive boot times >2 mins Windows 10 + Apricorn Velocity DUOx2 PCIe-startoverride.jpg

    NOTE I have a PC GTX-680-FTW-4GB flashed with Mac EFI rom. All 4 output ports are performing a it should be.

    Thanks in advance for any directions or solutions to address my absurd boot times of > ~2 min.

    Cheers
    Last edited by M4v3r1ck; 14 Oct 2016 at 05:28.
      My Computer


  2. Posts : 633
    Win 10 Pro x64 1607 (Build 14393.953)
    Thread Starter
       #2

    Did some googling on slow boot and was directed to and found a hardware error in Reliability Monitor:

    Problem signature
    Problem Event Name: LiveKernelEvent
    Code: 117
    Parameter 1: ffffd4825c50c010
    Parameter 2: fffff80219c9f0cc
    Parameter 3: 0
    Parameter 4: 16f8
    Versie besturingssysteem: 10_0_14393
    Servicepack: 0_0
    Product: 256_1
    Versie van besturingssysteem: 10.0.14393.2.0.0.256.48
    Landinstelling-id: 1043

    Cheers
      My Computer


  3. Posts : 579
    Windows 10
       #3

    Hi,
    Try rebuilding the Performance Counters:
    - Go to Windows>Performance>WinSAT folder and delete all XML files.
    - Open an elevated Command Prompt and type:
    Lodctr /r
    winsat formal -clean
    reboot and see.
    If this did not help:
    - Try Troubleshooter : Control Panel>Troubleshooting>View All> Search and Indexing + Windows Store Apps
    Reboot and see
    Further:
    - run WSReset
    If that does not help, you might want to uninstall all Store Apps except Store App itself. See here : Apps - Uninstall in Windows 10 - Windows 10 Forums
    Re-run WSreset
    If that does help, you have to look for errors in Event Viewer
    Last but not least, probably a "In-Place Upgrade" will be your best option to go.
      My Computer


  4. Posts : 633
    Win 10 Pro x64 1607 (Build 14393.953)
    Thread Starter
       #4

    Hi Aldalwar,

    Thanks for your prompt reply, appreciated. I'm confused here a bit. Searching google for Problem Event Name: LiveKernelEventCode: 117 I get many links to a hardware (video) issue rather than software. Would you mind explaining me a bit more why you suggested your tweaks, just for me to interpretate correctly for me to teach some really new troubleshooting solutions. TIA

    Cheers
      My Computer


  5. Posts : 579
    Windows 10
       #5

    Yes, Graphic Drives can cause problems , not the Drivers itself but the Install Routines.
    It is easy to uninstall them and reinstall and see.
    This things I told above are "Basic" procedures, they are not doing any Arm to you PC, at the worst Scenario the PC stays as it was.
    Although, the procedures can have a very big impact in performance.
    I recommend you to beginn with "LODCTR /R" and "WINSAT".
    To do that, open FIle Explorer, browser to c:\windows\performance\winsat and delete all XML files that are present in that Directory.
    Next, click right on Start and open "Command Prompt (Admin)
    Next on the window that was opened type : Lodctr /r press Enter.
    If there is a message saying it was "...Sucessful.." then proceed next, otherwise repeat the Lodctr /r
    Next, on the same window type: Winsat formal -clean and press enter. It will take some minutes. After WIndows has finished and the Prompt is back, restart PC.
      My Computer


  6. Posts : 633
    Win 10 Pro x64 1607 (Build 14393.953)
    Thread Starter
       #6

    Hi Adalwar,

    Thanks for your time explaning this to me a bit more.!

    These were the steps I performed:

    1. deleted all XML files C:\Windows\Performance\WinSAT\DataStore

    2. Command Line

    Code:
    Microsoft Windows [Version 10.0.14393](c) 2016 Microsoft Corporation. All rights reserved.
    
    C:\Windows\system32>Lodctr /r
    Error: Unable to rebuild performance counter setting from system backup store, error code is 2
    
    C:\Windows\system32>Lodctr /r
    Info: Successfully rebuilt performance counter setting from system backup store
    
    3. C:\Windows\system32>Winsat formal -clean
    Windows System Assessment Tool
    > Running the Formal Assessment
    > Running: Feature Enumeration ''
    > Run Time 00:00:00.00
    > Running: WinSAT Direct3D Assessment '-aname DWM -time 10 -fbc 10 -disp off -normalw 1 -alphaw 2 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock'
    > Assessing Desktop Graphics Performance
    > Run Time 00:00:11.23
    > Running: WinSAT Direct3D Assessment '-aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)'
    > Assessing DirectX Batch Performance
    > Run Time 00:00:00.42
    > Running: WinSAT Direct3D Assessment '-aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)'
    > Assessing DirectX Alpha blend Performance
    > Run Time 00:00:00.39
    > Running: WinSAT Direct3D Assessment '-aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3'
    > Assessing DirectX Texture load Performance
    > Run Time 00:00:00.41
    > Running: WinSAT Direct3D Assessment '-aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3'
    > Assessing DirectX ALU Performance
    > Run Time 00:00:00.41
    > Running: WinSAT Direct3D Assessment '-dx10  -aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)'
    > Run Time 00:00:00.01
    > Running: WinSAT Direct3D Assessment '-dx10  -aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)'
    > Run Time 00:00:00.00
    > Running: WinSAT Direct3D Assessment '-dx10  -aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3'
    > Run Time 00:00:00.00
    > Running: WinSAT Direct3D Assessment '-dx10  -aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3'
    > Run Time 00:00:00.00
    > Running: WinSAT Direct3D Assessment '-dx10  -aname GeomF4 -time 7 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 150;200;241 -batchcnt C(50);C(200);C(300) -objs C(12);C(26);C(45) -noalpha -geomf4shader -texpobj C(0) -rendertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1'
    > Run Time 00:00:00.00
    > Running: WinSAT Direct3D Assessment '-dx10  -aname GeomV8 -time 7 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 75;100;120 -batchcnt C(25);C(100);C(150) -objs C(8);C(17);C(29) -noalpha -geomv8shader -texpobj C(0) -rendertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1'
    > Run Time 00:00:00.00
    > Running: WinSAT Direct3D Assessment '-dx10  -aname CBuffer -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 75 -batchcnt C(25) -objs C(8) -rendertotex 6 -rtdelta 3 -texpobj C(1) -cbuffershader -cbufa 2 -cbuff 5 -cbufp 6'
    > Run Time 00:00:00.00
    > Running: Media Foundation Playback Assessment '-input C:\Windows\Performance\WinSAT\winsat.wmv -nopmp'
    > Run Time 00:00:01.95
    > Running: Extended Media Assessment '-input C:\Windows\Performance\WinSAT\Clip_1080_5sec_VC1_15mbps.wmv -video offscreen -audio mute -prevent3pc -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog'
    > Run Time 00:00:07.11
    > Running: Extended Media Assessment '-input C:\Windows\Performance\WinSAT\Clip_1080_5sec_10mbps_h264.mp4 -video offscreen -audio mute -prevent3pc -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog'
    > Run Time 00:00:07.39
    > Running: Extended Media Assessment '-input C:\Windows\Performance\WinSAT\Clip_480_5sec_6mbps_h264.mp4 -video offscreen -audio mute -prevent3pc -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype int2fps'
    > Run Time 00:00:07.06
    > Running: Media Decode/Encode Assessment '-input C:\Windows\Performance\WinSAT\winsatencode.wmv -encode C:\Windows\Performance\WinSAT\winsat.prx'
    > Run Time 00:00:02.44
    > MOOBE Run Time 00:00:39.91
    > Running: CPU Assessment '-encryption -up'
    > Run Time 00:00:03.08
    > Running: CPU Assessment '-compression -up'
    > Run Time 00:00:10.05
    > Running: CPU Assessment '-encryption2 -up'
    > Run Time 00:00:03.08
    > Running: CPU Assessment '-compression2 -up'
    > Run Time 00:00:10.08
    > Running: CPU Assessment '-encryption'
    > Run Time 00:00:10.67
    > Running: CPU Assessment '-compression'
    > Run Time 00:00:10.73
    > Running: CPU Assessment '-encryption2'
    > Run Time 00:00:10.64
    > Running: CPU Assessment '-compression2'
    > Run Time 00:00:10.67
    > Running: System memory performance assessment ''
    > Run Time 00:00:06.03
    > Running: Storage Assessment '-seq -read -n 3'
    > Run Time 00:00:07.00
    > Running: Storage Assessment '-ran -read -n 3'
    > Run Time 00:00:00.50
    > Running: Storage Assessment '-ran -read -n 0'
    > Run Time 00:00:04.03
    > Running: Storage Assessment '-ran -read -n 1'
    > Run Time 00:00:04.22
    > Running: Storage Assessment '-ran -read -n 2'
    > Run Time 00:00:05.41
    > Running: Storage Assessment '-ran -read -n 4'
    > Run Time 00:00:11.94
    > Running: Storage Assessment '-ran -read -n 5'
    > Run Time 00:00:11.78
    > Running: Storage Assessment '-ran -read -n 6'
    > Run Time 00:00:14.20
    > Running: Storage Assessment '-ran -read -n 7'
    > Run Time 00:00:13.56
    > Run Time 00:00:00.00
    > CPU LZW Compression                          1563.78 MB/s
    > CPU AES256 Encryption                        8112.50 MB/s
    > CPU Vista Compression                        4235.03 MB/s
    > CPU SHA1 Hash                                6270.74 MB/s
    > Uniproc CPU LZW Compression                  101.48 MB/s
    > Uniproc CPU AES256 Encryption                363.14 MB/s
    > Uniproc CPU Vista Compression                247.98 MB/s
    > Uniproc CPU SHA1 Hash                        343.68 MB/s
    > Memory Performance                           14072.10 MB/s
    > Direct3D Batch Performance                   42.00 F/s
    > Direct3D Alpha Blend Performance             42.00 F/s
    > Direct3D ALU Performance                     42.00 F/s
    > Direct3D Texture Load Performance            42.00 F/s
    > Direct3D Batch Performance                   42.00 F/s
    > Direct3D Alpha Blend Performance             42.00 F/s
    > Direct3D ALU Performance                     42.00 F/s
    > Direct3D Texture Load Performance            42.00 F/s
    > Direct3D Geometry Performance                42.00 F/s
    > Direct3D Geometry Performance                42.00 F/s
    > Direct3D Constant Buffer Performance         42.00 F/s
    > Video Memory Throughput                      42446.60 MB/s
    > Dshow Video Encode Time                      0.76913 s
    > Media Foundation Decode Time                 0.08994 s
    > Disk  Sequential 64.0 Read                   527.04 MB/s          8.1
    > Disk  Random 16.0 Read                       277.65 MB/s          8.0
    > Total Run Time 00:03:16.05
    
    
    C:\Windows\system32>

    3. Rebooted, boot time 110 sec, still having the Windows hardware error:
    > Problem Event Name: LiveKernel Event
    > Code: 117


    4. Try Troubleshooter: Control Panel>Troubleshooting>View All> Search and Indexing

    See output in Search and Indexing.pdf (329.5 KB)

    5.
    Try Troubleshooter: Control Panel>Troubleshooting>View All> Windows Store Apps

    See output in Windows Store Apps.pdf (332.0 KB)

    6. Reboot

    7.
    WSReset

    Code:
    C:\Windows\system32>WSReset
    
    C:\Windows\system32>

    8. Reboot = 110 sec

    9. Uninstall all Store Apps except Store App itself:

    Code:
    PS C:\Windows\system32> Get-AppXPackage | where-object {$_.name –notlike “*store*”} | Remove-AppxPackage

    10. Reboot = 110 sec

    11. Rerun (elevated CLI) WSReset

    Code:
    C:\Windows\system32>WSReset
    
    C:\Windows\system32>

    12. Boot = ?

    --> Work in Progress !

    Cheers
    Excessive boot times >2 mins Windows 10 + Apricorn Velocity DUOx2 PCIe Attached Files
    Last edited by M4v3r1ck; 14 Oct 2016 at 16:13.
      My Computer


  7. Posts : 579
    Windows 10
       #7

    Well, I suggest you to uninstall and re-install Sound Drivers and Graphic Drivers.
    Also, look in Event Viewer for errors, specially
    - Event ID 121 for Drivers failing to Install
    - Event ID 1016 for Permissions errors.
    This Events could slow down very much the Booting, specially ID 1016.

    Another Option is to go directly for an "In-Place Upgrade". That will re-install Windows, letting your Files, Documents, Programs and everything else intact.
    That would be a good option, before you lose a huge time trying to fix things.
    Have a look in this tutorial how to Repair Windows :
    Repair Install Windows 10 with an In-place Upgrade - Windows 10 Forums[2]=Installation%20and%20Setup

    EDIT : For Testing purposes, to see if is a Software that is causing that long Boot time, try a "Clean Boot".
    Here how to:
    Right Click on Start > Run and type there MSCONFIG, press enter.
    In the window that will pop-up , check "Diagnostic Startup", press apply. Now see if boot is much quicker.
    Another possibility, in the same MSCONFIG windows is to go to "Services" Tab, check "Hide all Microsft services" and the "Disable all", after press "Apply", reboot and see. Do not forget to put this settings back to its original settings.
    Another thing you could try is disabling all "Startup" Software. Press Ctrl+Alt+Del > Task Manager >Start-up and disable all items there. Reboot and see. After testing, do not forget to restore this settings.
    Last edited by Adalwar; 15 Oct 2016 at 04:50.
      My Computer


  8. Posts : 633
    Win 10 Pro x64 1607 (Build 14393.953)
    Thread Starter
       #8

    Good morning Adalwar,

    Thanks so much for sticking around and spending time and effort helping me fixing this issue, appreciated!

    Later today I'll perform your suggested tweaks and will report back like my last post.

    Cheers
      My Computer


  9. Posts : 633
    Win 10 Pro x64 1607 (Build 14393.953)
    Thread Starter
       #9

    Sound Drivers and Graphic Drivers!!!!


    Adalwar said:
    Well, I suggest you to uninstall and re-install Sound Drivers and Graphic Drivers.
    Also, look in Event Viewer for errors, specially
    - Event ID 121 for Drivers failing to Install
    - Event ID 1016 for Permissions errors.
    This Events could slow down very much the Booting, specially ID 1016.
    Checked for the ID# you recommended. No messages (non off all that could be selected) for any error of these ID's.

    Another Option is to go directly for an "In-Place Upgrade". That will re-install Windows, letting your Files, Documents, Programs and everything else intact.
    That would be a good option, before you lose a huge time trying to fix things.
    Have a look in this tutorial how to Repair Windows :
    Repair Install Windows 10 with an In-place Upgrade - Windows 10 Forums[2]=Installation%20and%20Setup

    EDIT : For Testing purposes, to see if is a Software that is causing that long Boot time, try a "Clean Boot".
    Here how to:
    Right Click on Start > Run and type there MSCONFIG, press enter.
    In the window that will pop-up , check "Diagnostic Startup", press apply. Now see if boot is much quicker.
    Another possibility, in the same MSCONFIG windows is to go to "Services" Tab, check "Hide all Microsft services" and the "Disable all", after press "Apply", reboot and see. Do not forget to put this settings back to its original settings.
    Another thing you could try is disabling all "Startup" Software. Press Ctrl+Alt+Del > Task Manager >Start-up and disable all items there. Reboot and see. After testing, do not forget to restore this settings.
    I halted on these recommendations, because searching the web some more about the ID 117 error, being the graphics hard- and or software. Your first suggestion was all it took...

    I suggest you to uninstall and re-install Sound Drivers and Graphic Drivers
    Before doing the "In-Place Upgrade" I again performed the NVdia (Graphic- + HDMI Sound drivers) uninstall, but now with the Display Driver Uninstaller (DDU) V17.0.2.1.

    !!! Windows boot time = 15 sec

    Re-installed the NVidia driver (373.06) package WITHOUT HDMI and Geforce Experiense.

    ??? Windows boot time = 165 sec

    So obviously, although I uninstalled the NVidia driver package with "Uninstall Program" in Windows option and now gave the DDU Uninstaller a shot, the NVidia drivers are not playing well with my EFI Windows 10 and GTX-680 flashed with EFI. Wow, strange that just video drivers can slow down a boot sequence that mu, the difference is ~150 sec...

    Well, I think this troubleshoot has come to an end. Unless you would recommend me to trial-and-error something els.

    Many thanks for your help!!!

    Cheers
      My Computer


  10. Posts : 579
    Windows 10
       #10

    I am happy to have helped you.
    Cheers.

    EDIT: I was not sure of what DDU was, so I was googling to see what it is.
    The Best way to uninstall a Software is surely with its Uninstall program. But if someone really want to "kill" all Software the path is to go to Device Driver, and uninstall it from there, checking the box "Delete Software for Device...".
      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 03:45.
Find Us




Windows 10 Forums