Page 3 of 8 FirstFirst 12345 ... LastLast
  1.    29 Feb 2016 #21
    Join Date : Aug 2015
    Penn's Woods
    Posts : 1,275
    Windows 10 Home

    Not an issue with your hardware - only the manner in which you attempted to use it, the firmware, and the software.
      My ComputerSystem Spec
  2.    01 Mar 2016 #22
    Join Date : Feb 2016
    Posts : 111
    Windows 10 Pro
    Thread Starter

    Last question i will be very greatful for response.
    Also i know that UEFI firmware can emulate BIOS functionality (CSM/Legacy) and work with MBR disks just fine.

    So why it happened when i change boot from UEFI USB to SDD?

    Somebody said to me:""If you switch boot devices, try to keep them in the same family. If you use NON UEFI CD/HDD/SSD/USB on everything, don't switch any of them to UEFI or strange things may happen (and if you use UEFI don't switch to BIOS (aka Legacy).

    I wouldn't worry about it, just try to avoid the trigger (switching your boot order around from USB to HDD). Or at least, if you know it's
    going to happen, you know how to fix it! <grin>."



    Maybe because i switch then?


    My bios settings are on default and my disk was formatted in MBR partition. CSM was ENABLED.
    Last edited by xxx123; 01 Mar 2016 at 11:30.
      My ComputerSystem Spec
  3.    01 Mar 2016 #23
    Join Date : Aug 2015
    Penn's Woods
    Posts : 1,275
    Windows 10 Home

    Quote Originally Posted by xxx123 View Post
    Last question i will be very greatful for response.
    Also i know that UEFI firmware can emulate BIOS functionality (CSM/Legacy) and work with MBR disks just fine.

    So why it happened when i change boot from UEFI USB to SDD?


    Somebody said to me:""If you switch boot devices, try to keep them in the same family. If you use NON UEFI CD/HDD/SSD/USB on everything, don't switch any of them to UEFI or strange things may happen (and if you use UEFI don't switch to BIOS (aka Legacy).

    I wouldn't worry about it, just try to avoid the trigger (switching your boot order around from USB to HDD). Or at least, if you know it's
    going to happen, you know how to fix it! <grin>."



    Maybe because i switch then?


    My bios settings are on default and my disk was formatted in MBR partition. CSM was ENABLED.
    Look at your screenshot in post # 12 - it shows the USB as a UEFI bootable device, the Samsung NOT (no "UEFI" in front of it).

    Exactly: because you were configured on BOOT screen for UEFI boot and switch to a first boot device that was NOT suitable for UEFI boot (MBR Samsung disk) and Windows was left on its own after boot failure and found an alternative means to boot. Definition of Insanity: doing the same thing over and over again and expecting the outcome to change. If you made no change in BIOS to switch to Legacy Boot, you would continually have the failure to boot 1st time and Windows finding a way to boot itself (2nd boot).

    I would say that the advice you got to make up your mind over sticking entirely with Legacy Boot (use MBR) or else sticking entirely with UEFI (use GPT) was good advice [see my "2)" in my post # 17]. I would opt for sticking with UEFI/GPT going forward and only revert to Legacy Boot in special circumstances that may occur on rare occasions.
      My ComputerSystem Spec
  4.    01 Mar 2016 #24
    Join Date : Feb 2016
    Posts : 111
    Windows 10 Pro
    Thread Starter

    Yes but why system working fine and booting properly once ,just before i change "UEFI USB KINGSTON" to "P1 SSD SAMSUNG EVO 250 GB". Before i do that system booting properly even if i had primary P1 SSD SAMSUNG EVO 250 GB.

    Problem with Automatic Repair started after i
    change in my UEFI boot priority from :"UEFI USB KINGSTON" to "P1 SSD SAMSUNG EVO 250 GB". Any idea?:] This is my last question and sorry for problem .
      My ComputerSystem Spec
  5.    01 Mar 2016 #25
    Join Date : Aug 2015
    Penn's Woods
    Posts : 1,275
    Windows 10 Home

    Quote Originally Posted by xxx123 View Post
    Yes but why system working fine and booting properly once ,just before i change "UEFI USB KINGSTON" to "P1 SSD SAMSUNG EVO 250 GB". Before i do that system booting properly even if i had primary P1 SSD SAMSUNG EVO 250 GB.

    Problem with Automatic Repair started after i
    change in my UEFI boot priority from :"UEFI USB KINGSTON" to "P1 SSD SAMSUNG EVO 250 GB". Any idea?:] This is my last question and sorry for problem .
    That would be hard to answer with certainty. We would have to know:

    1) Are you sure it actually booted from the Samsung (as MBR) ? Was the Kingston drive bootable and can you be sure it didn't boot from that?

    2) Is it possible you actually had the BIOS configured for Legacy boot at the time and it booted from the Samsung (as MBR)? You said it was switched to BIOS defaults at some time - was it possibly configured for Legacy boot and you reset defaults and had booting UEFI for all the other attempts?

    Unless you reproduce that precise behavior and then give all the particulars on settings and devices actually present for boot, it seems like it would be useless to speculate at this point. I understand your burning curiosity at on that one question but, unless you have way more time on your hands than I do or another TenForums member can explain things in a way I'm unable to, I would just move on and enjoy what now sounds like is a properly configured and operating UEFI/GPT system.
      My ComputerSystem Spec
  6.    01 Mar 2016 #26
    Join Date : Feb 2016
    Posts : 111
    Windows 10 Pro
    Thread Starter

    Previously at first time i formatted disk to MBR ( because disk was formatted without warning about GPT ) partition during install Windows 10 by bootable usb ( iN UEFI boot was: UEFI KINGSTON USB ). Then i had in UEFI options: P1 Samsung Evo 250 GB and UEFI KINGSTON USB. Windows 10 working fine till someday i run memtest86 from bootable usb ( boot was the same :UEFI KINGSTON USB ). After finished memtest i decide to boot windows 10 and then i switch from UEFI KINGSTON USB to P1 Samsung Evo 250 GB and after this Automatic repair started. And then on Automatic repair cant repair your pc screen i choose restart and windows 10 boot at second time properly . Every boot of Windows 10 i had Automatic repair. So i dont know if it was Partition/bios issue ?

    ps:
    I never change anything in bios ( i dont touch CSM,Legacy,Uefi options all is on default )


    I am actually after second format ( this time, i dont know why during installation of Windows 10, Windows give me warning to convert to GPT in UEFI systems so i do this ) and i am booting Windows 10 by SSD Samsung 250 Boot Manager in UEFI, and have no problems, all is fine.
    And i was use the same Usb boot option in UEFI "UEFI KINGSTON USB" to install Windows 10 after this second format.
    But i like to know if that problem was hardware or software/bios related?

    Samsung Evo 250 GB BOOT MANAGER option in UEFI was added after installing Windows 10 on GPT format. ( after this second format )
    So i have 2 options now in UEFI : Samsung Evo 250 GB and Samsung Evo 250 GB Boot Manager.
      My ComputerSystem Spec
  7.    01 Mar 2016 #27
    Join Date : Aug 2015
    Penn's Woods
    Posts : 1,275
    Windows 10 Home

    Quote Originally Posted by xxx123 View Post
    ..So i dont know if it was Partition/bios issue ?...
    Hard to say - one or the other, both, or neither. I will say the trail has gotten a bit cold on this though.
      My ComputerSystem Spec
  8.    01 Mar 2016 #28
    Join Date : Aug 2015
    Maine
    Posts : 39,990
    Windows10Pro 64Bit

    Quote Originally Posted by Word Man View Post
    Hard to say - one or the other, both, or neither. I will say the trail has gotten a bit cold on this though.
    You my good friend have the patience of Jobe!!!! Whew....
      My ComputersSystem Spec
  9.    02 Mar 2016 #29
    Join Date : Feb 2016
    Posts : 111
    Windows 10 Pro
    Thread Starter

    Also i know that UEFI firmware can emulate BIOS functionality (CSM/Legacy) and work with MBR disks just fine. So i cant understand why i get Automatic Repair during first boot, even when i change from UEFI USB KINGSTON to P1: Samsung Evo 250 GB ( like on screen on 2 page ).
    So if UEFI can emulate BIOS functionality why then it get corrupted to Automatic Repair?

    Still, my system works fine ( boot was: P1: Samsung Evo 250 GB ), till i change again from UEFI USB KINGSTON to P1 Samsung Evo 250 GB. So it can be a random occur?
      My ComputerSystem Spec
  10.    02 Mar 2016 #30
    Join Date : Aug 2015
    Penn's Woods
    Posts : 1,275
    Windows 10 Home

    Quote Originally Posted by xxx123 View Post
    ...So if UEFI can emulate BIOS functionality why then it get corrupted to Automatic Repair? ...
    Because you have to actively change the options in your BIOS to boot Legacy instead of UEFI - it doesn't switch itself automatically. It doesn't know in advance whether you are expecting it to boot from an MBR or a UEFI partitioned device. Repeated attempt to boot MBR device while BIOS is configured for UEFI boot = frustration.
      My ComputerSystem Spec

 
Page 3 of 8 FirstFirst 12345 ... LastLast


Similar Threads
Thread Forum
Solved iaStorA.sys BSOD + antivirus conflict?
After the major build (1511) update I've been experiencing recurring BSOD of the kind IRQL_NOT_LESS_OR_EQUAL. I run WhoCrashed that says it's a driver problem (iaStorA.sys). I followed the instructions of a previous post here on the forum...
BSOD Crashes and Debugging
Solved Can't install Office 2007 due to conflict with Groove
I tried to install my Office 2007 on Windows 10. But I get a message saying "Setup has detected an earlier version of Groove on your system ... uninstall your current version of Groove". Groove is not in the Programs section of Control Panel and...
Software and Apps
BSOD pci.sys driver or Handbrake conflict
Good Evening, This PC is about 10 months old, and this BSOD seems to only have started since I upgraded from W7 to W10 in September. The issue is relatively simple really. I get BSOD's when running Handbrake and Vuze. Now I have not noticed it...
BSOD Crashes and Debugging
Network Conflict with the installation of Windows 10.
Since I've downloaded Windows 10 my Ethernet (wired), connection has been absolutely useless. I'm 100% positive it's not the cable itself, and I've tried lots of things to resolve it. Nothing seems to work. So for the time being I've been using...
Network and Sharing
IPv4 IP address conflict since upgrade to Win10
Upgraded an old win7 32-bit Dell Dimension 9200 to Win10 Pro on Friday 31st July. I intended to donate it to a school library in Kenya but shipping / customs costs high so now hoping to sell it to raise funds for the same charity. On Friday 7th...
Network and Sharing
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 19:18.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums