Windows 10: Win 10 RS-4 not compatible with Intel DX58SO motherboard Solved

Page 4 of 25 FirstFirst ... 2345614 ... LastLast
  1.    07 Dec 2017 #31

    johngalt said: View Post
    Just read this. Although it says no .ISO based installs are affected, I wonder if this DOES extend to UUP2ISO created ISOs?

    Insider Preview Build Installs Fail with Error Code 80096004 - Microsoft Community

    Bordi, have you tried an .ISO from the slow ring downloaded directly from Microsoft at all?

    Yes mate, the 17025 DVD is an official ISO release downloaded directly from MS

    https://www.microsoft.com/en-us/soft...?wa=wsignin1.0
      My ComputerSystem Spec

  2. johngalt's Avatar
    Posts : 1,534
    WinX Pro x64 IP current
       07 Dec 2017 #32

    Yeah, I know, just making sure.
      My ComputersSystem Spec

  3. Fafhrd's Avatar
    Posts : 1,928
    Windows 10 x86 14383 Insider Pro and Core 10240
       07 Dec 2017 #33

    Microsoft does not endorse or support UUPtoISO etc., generated ISO clean installs, only those ISO images that MS distributes AFAIK.
      My ComputersSystem Spec

  4. johngalt's Avatar
    Posts : 1,534
    WinX Pro x64 IP current
       07 Dec 2017 #34

    Yes, I know that as well. That is why I was checking to make sure Bordi had tried the official release, to rule out this as a possible factor with his installation issues.

    Bordi, do you have a spare drive, or else can you make a new, small partition and try installing 17025 directly (without first installing 16299) to see if it breaks when doing a clean install?
      My ComputersSystem Spec

  5.    07 Dec 2017 #35

    johngalt said: View Post
    Yes, I know that as well. That is why I was checking to make sure Bordi had tried the official release, to rule out this as a possible factor with his installation issues.

    Bordi, do you have a spare drive, or else can you make a new, small partition and try installing 17025 directly (without first installing 16299) to see if it breaks when doing a clean install?
    I try fresh installing directly with every new release mate, after the normal upgrade fails

    It just doesn’t go past the windows logo each and every time

    Some part of my hardware or BIOS is incompatible with the RS-4s

    bordi said: View Post
    Windows 10 Fall Creators Update (RS3)
    Build 16299.15 10/2/2017 installed perfectly, working perfectly even now

    Windows 10 (RS4)
    Build 16353 8/31/2017* only released to Skip Ahead not tried
    Build 16362 9/13/2017* only released to Skip Ahead not tried
    Build 17004 9/27/2017* only released to Skip Ahead not tried
    Build 17017 10/13/2017 - Failed in SAFE_OS error during BOOT 0xC1900101-0x20017
    Build 17025 10/25/2017 - Failed in SAFE_OS error during BOOT 0xC1900101-0x20017
    Build 17035 11/8/2017 - Failed in SAFE_OS error during BOOT 0xC1900101-0x20017
    Build 17040 11/16/2017 - Failed in SAFE_OS error during BOOT 0xC1900101-0x20017
    Build 17046 11/22/2017 - Failed in SAFE_OS error during BOOT 0xC1900101-0x20017

    I've tried upgrading, fresh install, formatting the hard disc, always the same result.
    Can’t get past the frozen windows logo to the spinning/circling dots
    Last edited by bordi; 07 Dec 2017 at 16:22.
      My ComputerSystem Spec

  6. johngalt's Avatar
    Posts : 1,534
    WinX Pro x64 IP current
       07 Dec 2017 #36

    Indeed so.

    Just had an idea, leu me check something.
      My ComputersSystem Spec

  7. Fafhrd's Avatar
    Posts : 1,928
    Windows 10 x86 14383 Insider Pro and Core 10240
       07 Dec 2017 #37

    Failed in SAFE_OS error during BOOT 0xC1900101-0x20017

    googling this, led to many different causes and solutions, many from fairly long ago.

    going through the \panther\setuperr.log seems a good idea

    one solution involved deleting a CPU check file: Windows\system32\mcupdate_genuineintel.dll

    another required reducing RAM to original specs for the hardware,

    Install errors finally solved with an hour to spare - Forums - CNET

    and

    How to fix error 0xc0000017 when installing Windows 10

    all pointed to memory errors - either real bad memory or falsely reported errors

    these led to removal of badmemory markers in the BCD store to enable installation following the error message you posted.

    and so on

    Probably worth going through some of the solutions with a clear mind tomorrow.
      My ComputersSystem Spec

  8. johngalt's Avatar
    Posts : 1,534
    WinX Pro x64 IP current
       07 Dec 2017 #38

    OK, Your motherboard is pretty analogous to mine, I have an eVGA x58 Classified 3 motherboard, with many of the same features (and pitfalls) as yours.

    My motherboard uses the Marvell chipset for providing the SATA III connectivity onboard, whereas yours provides a Marvell chipset for controlling the 2 eSATA ports you have available. For my setup, even though the Marvell doesn't provide true SATA II speeds (5 Gbps max versus normal 6 Gbps), I still use it for my two primary drives, both of which are SATA III SSDs. The only things I have connected to the regular ICH10R SATA II ports are my storage (mechanical) drives as well as my BluRay burner.

    I'm curious - in your setup, how are your drives connected? Is everything connected to the SATA II ports, or is anything connected to the eSATA ports?

    Also, I'm assuming that you've installed as many of the drivers listed here as you can get installed: Downloads for Intel® Desktop Board DX58SO
      My ComputersSystem Spec

  9. johngalt's Avatar
    Posts : 1,534
    WinX Pro x64 IP current
       07 Dec 2017 #39

    Fafhrd said: View Post
    Failed in SAFE_OS error during BOOT 0xC1900101-0x20017

    googling this, led to many different causes and solutions, many from fairly long ago.

    going through the \panther\setuperr.log seems a good idea

    one solution involved deleting a CPU check file: Windows\system32\mcupdate_genuineintel.dll

    another required reducing RAM to original specs for the hardware,

    Install errors finally solved with an hour to spare - Forums - CNET

    and

    How to fix error 0xc0000017 when installing Windows 10

    all pointed to memory errors - either real bad memory or falsely reported errors

    these led to removal of badmemory markers in the BCD store to enable installation following the error message you posted.

    and so on

    Probably worth going through some of the solutions with a clear mind tomorrow.
    That reminds me of another of the foibles of the eVGA x58 mobos - Though I never personally experienced this, the word in the eVGA forums was that, particularly when installing Windows 8+, you reduce the RAM in your motherboard to a single stick in the main bank (and with your motherboard, that would be bank 0 in channel 0, the closest one to the CPU). Since we both have LGA1366 CPUs, I made full use of my triple channel slots (I have 6 to your 4) and thus have a stick in each of the 0 banks for each channel, but if you were to make use of triple channel, you'd have it in the first and last 2 (from CPU outward) skipping that second slot for true triple channel features. However, almost everyone else posting in the eVGA forums back when Windows 10 first came out kept running into really weird errors, which were (usually) resolved by users dropping down to a single stick of RAM, and this advice was carried over from the first days of the eVGA x58 line being released and folks trying to install Windows 7 on those boards.

    As I said, I never had any issues with my mobo causing me to have to drop the # Memory DIMMs in my computer, that I can recall, and I also have it overclocked in the BIOS, which was another thing that was mentioned to remove when installing, and particularly clean installing Windows 7 / 8 / 10.

    I suspect that the reason I have had few issues is because of my quick incorporation of SSDs in the build. Who knows?
      My ComputersSystem Spec

  10. Berton's Avatar
    Posts : 5,281
    Win10 Home and Pro, Win10 Insider Preview, WinXP Home Premium, Linux Mint
       07 Dec 2017 #40

    I am assuming, and could be wrong, that IP Builds with numbering of 16xxx.xx are for Version 1703 and IP Builds with numbering of 17xxx.xx are for Version 1709. Least ways that's have they have shown on my 2 IP computers now on Version 1709 Build 17046.1000.
      My ComputerSystem Spec


 
Page 4 of 25 FirstFirst ... 2345614 ... LastLast

Related Threads
Read more: Intel: We're ending all legacy BIOS support by 2020 | ZDNet See also: http://www.uefi.org/sites/default/files/resources/Brian_Richardson_Intel_Final.pdf
I spoke to Microsoft after they re-installed latest windows 10. There were some buggy issues after the update, e.g couldnt click windows icon at bottom left corner, black screen with white mouse on loading my account from startup (this happend...
Solved Intel Motherboard Powerup in Drivers and Hardware
Just bought a used Intel DQ57TM motherboard with i5-650 CPU. As I am going away on hols tomorrow, I quickly connected it up to a good power supply plus internal speaker, resting the mobo on an insulated surface. No other connections were made. ...
Intel DX58SO MB & Win 10 in Installation and Upgrade
Has anyone upgraded their Intel DX58SO system to Win 10? If so, are there any issues? Intel hasn't, and likely won't, update the 5 Series drivers for the new OS. The latest available on the Intel Download Center are Win 7 drivers. I'm...
Solved Intel DX58SO compatibility with XEON in PC Custom Builds and Overclocking
I'd like to ask if someone has a XEON running on that mobo. I would like to buy one and would like to make sure that it runs on this mobo. I'm using the latest BIOS, SOX5810J.86.5600 dated 07/29/2013. Thanks for all advice in advance!
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 13:15.
Find Us