I recently upgraded a Toshiba A300 laptop (2009 model) from Win7 to Win10. I use a 125GB Kingston SSD as primary and a 280GB Hitachi as a secondary internal hard disk, in place of DVD drive, inside a cradle. This is a single OS installation, no dual boot. When I cold boot (from power on) and after the Bios logo, the "MBR Error 1" appears on screen and stops booting. To bypass I do a warm restart (Ctrl+Alt+Del) and the second (warm) boot loads Win 10. Also booting is ok from a Restart. Again error message appears only after a cold boot.
As a teaser I have to mention that, whenever I remove the cradle with the secondary Hitachi hard disk, the error does not appear during cold boot !!!. That is the error message appears only if the second hard disk is installed. This is an annoying situation only and does not affect any other operation, except booting.
BSOD happens only when the computer cold boots from a prolonged inactive state. If the PC is off for several hours and is turned on it occurs. Computer typically blue screens, sometimes it freezes at the bios splash screen where they Windows 10 circular loading icon appears on this Gigabyte. I've seen multiple reasons for the occurrence such as bad pooler caller and irql not less or equal. The BSOD happens once then after the computer functions as normal with no other issues.
Power supply, graphics card, and SSD were both pulled from a previous build with zero issues in that build. New to this build is the motherboard, processor, and RAM.
Ran Memtest86 with no errors for 8 passes but I just realized it was after the initial cold boot BSOD and not going from the inactive state to the test directly. Will be swapping out the RAM at Microcenter today just to eliminate that possibility.
Windows 10 was a clean install but it happened on the previous install, BIOS is flashed to the most recent release.
I got a custom built pc for christmas and it has been getting BSOD's since it was built and they have only been happening on cold boots, and the file that is having problems is ntoskrnl.
I chose to log in use the PIN option. I like typing with the num pad.
At the log on screen Num Lock was always off.
1. Checked the BIOS settings: Ensured that the NumLock status in the BIOS was set to enabled
2. Modified the registry a few times Key: HKEY_USERS.DEFAULTControl PanelKeyboard I set the String Value: InitialKeyboardIndicators to 2 then I tried 80000002 then I tried 2147483650
So I have partial success, where NumLock is enabled after a restart, but it is not enabled after a cold-boot.
Upon attempting to perform a fresh install of my display drivers using DDU, I somehow managed to permanently blue screen Windows 10 (Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED). So every time I try to boot into my OS, I get a constant blue screen of death, resulting in my computer to continuously restart and blue screen.
So now I'm trying to boot into safe mode from a cold boot, is there a way that I can access Advanced Options without requiring to boot into the OS itself?I'd like to create a recovery disk with a flashdrive, but I do not have an alternate computer that runs Windows 10, just a MacBook Pro
Yesterday I removed dual booting Linux and after that my Windows 10 won't boot up. I have tried everything. The cmd commands: bootrec /FixMbr; bootrec /FixBoot; bootrec /RebuildBcd; Bcdboot commands and everything. Then I tried Refreshing PC what says: Drive where Windows is installed is locked. Please unlock it.....
Startup repair just scans for a short period and then says: Couldn't fix the problem. I can't Access normal Recovery options, so I'm using a recovery flash drive. I have tried several Live CDs but none of them won't fix the problem. I can access the UEFI Bios, but idk what to change there. I don't want to fresh install Windows, unless it's the only option, because it contains important data.
I installed Windows 10 earlier but after about 10 minutes of using it my computer restarted itself automatically, and then it showed an error message saying that windows had "ran into a problem" on restart an it quotes the error code "0xc000007b".
I have taken a photo of it which can be seen here: [URL] ....
It then restarts again and gives me a list of options: [URL] ....
I upgraded ok with the update and successfully activated windows 10. I downloaded both 32bit and 64bit to usb using media creation tool as I wanted to clean install Windows 10 64bit on my 64bit compatible machine although am currently running 32bit windows 7 as that's what I had to hand when I built the PC. If I attempt to boot 32bit from usb it returns the error winload.efi missing. If I attempt to boot the 64bit version it just returns to windows boot manager.
Frustrated, I opted for the "reset this PC" function in settings instead as an alternative to the clean install and the reset failed, hung, then returned to the screen "what would you like to do". Once I selected "turn off PC" and it restarted and automatically continued the reset only to fail a second time. This time I choose to "return to windows 10" but it just hung. I had to rollback to windows 7 with repair dvd.
With windows 7 now installed again, I still cannot boot from either the 32 or 64 bit option in windows boot manager when I select to boot from the USB.It either returns to the boot manager or returns the winload.efi missing error.I have tried changing settings in bios to disable secure boot and fast boot but it makes no difference. I've read the Andre da Costa (sp?) wiki steps along with countless other how-to-clean-install windows 10 guides.
Inserted my new SSD to a SATA3 port and, next to my HDD 1TB, and went for a clean install right away. The system installed without problems (wiht the old HDD still attached), then i booted up the system (was a bit weird, because two versions were showing, however i formatted the old windows partition) and installed my programs. I saw that a 110 MB of data were still sitting on my old partition where the Windows 10 was earlier. Tried to delete those files but could not. However I shut down my pc and wanted to boot up again. Then it showed me a screen with "select proper boot device or restart computer". I went to BIOS to see if my SSD was set to primary boot device, but it was. But when i manaully select the boot device, my SSD, after starting up the computer, it boots into Windows and is running normally.
Can it be that there is no boot partition on my SSD and it wants to use the boot files from the HDD?? I also tried to unplug the HDD and boot up, but the same massage was showing up. But when i select the boot device manually it works.
I have a dual boot system in the following configuration:
HDD-0 = Win7 OS, HDD-1 = Win7 OS, WinXP OS. I have successfully booted into each of these operating systems - and the Win7 OS on HDD-1 is an exact clone of the primary OS on HDD-0.
I just upgraded the Win7 OS on HDD-0 to Windows 10 using the "Get Windows 10" process. I now get the new blue Boot Manger screen with all three OS's listed and I can successfully boot into Windows 10 and Windows XP. But I cannot boot into the Win7 OS on HDD-1 (which I could before the Windows 10 upgrade). How the upgrade even knew about the other copy of Windows 7, since it was not active and lives on another HDD is beyond me.
One strange thing - if I do a cold startup (power on) I get the new Boot Manger screen. But if I do a Restart from Windows 10, I get the old, black & white boot manger screen - and it does list all three OS's correctly, too.
The error message I get when trying to open (boot) the Windows 7 OS is: "LogonUI.exc - Entry point not found. RtlReleasePath could not be located in the ntdll.dll" And, like others, I now get the black screen with "Windows 7, Build 7601 This copy of Windows is not genuine (but it was yesterday before the Windows 10 upgrade on the other HDD).
And like others, I can start the Crtl+Alt+Del to get the screen with users, Task Manger, etc. And, I can run all my applications by manually starting them in a New Task and browsing to the exe file - like Firefox.exe or Word.exe So, it looks like Windows 7 started and may be running. I just can't get into it.
I think both issues, the LogOn and the "Not Genuine" are both related to the Entry Point no located in the ntdll.dll.
At this point I really don't want to reload Windows 7 since it appears to be running and all the apps can be run manually.
All this happened after the upgrade of the other Win7 on HDD-0.
Still trying to update to windows 10. Have updated windows 7 w/sp1 and have checked that my computer is ready for update 10. Everything goes great until final shut-down and restart.Then I get black screen with Blue Flag and locks up, will not go any further. After 5 hours of waiting tried turning off and it restarted and gave this error message: Instalation failed in the safe OS phase with error during Boot. 0xC1900101-0x20017
I have installed a clean windows 10 installation, and i keep having these different BSOD every time my computer is making a cold start = i shut the pc down in the evening and in the morning BSOD starts the day.. the computer restarts, and it works all day long, resetting and turn off and quick turn on again no BSOD.
Whenever I shut down my computer, I always have this problem. The Windows 10 insignia and the loading circle beneath will appear, then the screen will fade to black, and then my monitor says it can't detect my computer. I then have to unplug my computer from the outlet because I can't shut it down by pressing the power button. When I start it up again afterwards, it will start perfectly fine. And whenever I try to change the boot configurations, it automatically resets itself to the previous version.
When performing a cold start, the windows logo appears but nothing happens. If I reboot (Hold in the start button) and wait a few seconds, then repress the start button, Windows-10 loads. Why is this?
In my desktop I have two hard disks ( disk 0 and disk 1 ) . Disk 1 is a clone of disk 0 created by Macrium Reflect Disk 0 : ( C: ) windows 10 pro , upgrade from windows 7 , ( E: ) windows 8.1 pro , ( G: ) Storage partition Disk 1 : clone of disk 0
problem description : I see in msconfig / boot a wrong listing
windows 10 ( C:WINDOWS) : Current OS ; Default OS
windows 8.1 pro ( H:WINDOWS ) instead of ( E:WINDOWS )
Nevertheless the dual booting works fine as well as the shift between the disks via BIOS.
The question is , could I fix the situation using the EasyBCD of Neosmart Technologies to edit the bootloader ?
I see can change drive letter H: to E: and save the change , am I right or wrong ? or any other way ....
My laptop has dual boot - Windows 7 and Windows 10. My Win7 environment is my main working environment with lots of programs installed and important files. I installed the Win10 environment just to play around with 10 during the technical preview. Now, I would like to disable the 10 environment and upgrade the 7 to 10. Am I able to do this, or have I already "used up" my one upgrade on this computer's Windows license?
I notice that in Windows 7 I have not received the icon in the notification area that invites me to upgrade to 10. This makes me think I might have used up my chance to upgrade.
My end goal is to have a single Windows 10 environment. Note that the reason I want to upgrade my 7 environment to 10 is because I don't want to have to re-install all of my programs and files into the current 10 environment.
As I get ready to do a clean install of 10074 I am curious about the need to disable secure boot and fast boot options. If I do disable secure boot do I need to enable legacy boot?I have had limited success with previous installs to a 2nd hard drive and the problems that arose always seem related to dual booting.
In one instance I did a clean install of 10061 and had left secure boot enabled. In order to get dual boot working I had to disable secure boot, and upon rebooting I needed to change it back to secure. I then made Win 8.1 the default boot and then Win 10 would never boot from the menu, it would just take me back to the boot menu and I could boot into Win 8.1.
I'm making a image for installation of windows 10. I make a USB flash drive with WINPE. and once the device starts into WINPE, it will automatically start to install windows 10 by calling "dism /apply-image". Normally i just shutdown the computer after installation, but now i want to reboot the device and boot into the windows i just installed. But i can't, because if i reboot the device, it will boot into WINPE again and start another turn of installation of windows. How could i temporary boot into my windows 10?
After several weeks of testing I'm ready to go full on Windows 10 and want to get rid of Windows 7 but I have some partitioning issues I want to clean up. I currently have Windows 7 on drive 0 (360 GB) and Windows 10 on drive 1 (500 GB). Both are SATA drives and RAID is enabled in the bios but not active.
What I think I'd like to do is simply swap the drives physically so that Drive 0 has my current Windows 10 install on it and make it primary boot active etc. The drive with Windows 7 on it would become drive 1 and I would delete the Windows 7 partition and re-partition it with a clean empty partition just for extra space.
Second question, any advantage to using this drive configuration in a RAID setup?
I have a legacy 64 bit dual core desktop (ASUS mobo). I have several Sata hard drives in it with the 4th partition of my 1 Terabyte drive containing my Windows 10 Professional boot OS. After converting another similar legacy machine to a NAS device I took the old Windows 10 32 bit OS drive from it and tried booting the ASUS machine with it. Needless to say, the OS didn't like it and reverted to Windows 10 Pro Insider Preview edition (build 11082).
When I tried to restore the boot drive to the original one for this machine the master boot was missing.
I had just formatted another partition on the same drive that had contained a Windows7 installation that had failed. This partition may have contained the master boot record. So I booted to a command prompt from a USB drive and successfully ran the following commands:
bootrec /RebuildBcdbootrec /fixMbr bootrec /fixboot bootsect /nt60 SYSbootsect /nt60 all
After that the BIOS just says "An operating system wasn't found. Try disconnecting any drives that don't contain an operating system" This disk and OS are on the original machine it used to run on. As I understand it, Windows 10 tries to record it's key to somewhere in the BIOS. But the BIOS on these old machines don't provide such a facility. I don't understand what Windows 10 OS does with the key in this instance. If it was recorded in the BIOS then I'd presume that the other Windows 10 drive I attempted to use would have found it and used it. Or perhaps not, since it didn't like the new environment.
what I'm looking for is a way to get my original Windows 10 to boot again on the same machine it had always work on before, from the 4th partition of the 1 terabyte drive I'm using.
I have a custom intel/nvidia mini-itx build with win 10 that has been consistently BSOD on cold startup with various error codes. Its a really annoying problem. No drivers have been identified by who crashed.
The system is completely stable once I am able to log in to windows, even through intense gaming and maxed heaven benchmarks. Nothing is overclocked and all drivers/BIOS are up to date. I have tried disabling Intel smart connect in BIOS at suggestion of another BSOD thread here but did not solve. I have clean installed win 10 from tech bench multiple times to try and fix the problem. Windows SFC finds no integrity violations.
I wasn't sure which forum to put this into. I created a backup image on a usb hard drive. I wanted to be able to restore it using a usb recovery thumb drive. I used the create usb recovery tool and created the recovery flash drive. When I try to boot from the flash drive I get an error saying that the boot configuration data is missing or contains errors. I can boot up the laptop using the current windows install so it isn't referring to the hard drive. I have tried several usb drives and get the same message on each. Here is a screenshot of the message.
