No Proper Bootup On Cold Start Up - Can't Detect Computer
Aug 7, 2015
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.
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 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.
I just upgraded to Windows 10 from Windows 7. My wife and I use the same computer at home and each have a user account.
On Windows 7, when the computer started, the first screen we would see is both user accounts and select the appropriate one. Windows 10 (as many of you already know) seems to go directly to the user account that was on at shutdown. Is there any setting I could make to offer the choice of both user accounts each time on boot up?
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?
Sometime over the last month or so, every time fire-up my laptop, the start menu is open. I can click anywhere outside it and it will close, and does behave normally. It's more annoying than trouble. I don't consider myself a noob, but this is perplexing as I cannot find a setting to start up the OS without the start menu being open. Maybe a reg hack?
My assumption is MS did this in some recent update trying to introduce me to their new way of thinking. I only think this as after I upgraded to 10, I deleted all the tiles in the start menu that I didn't want. One day about a month ago, more came back. I figured it was MS trying to sell me on tiles, yet again.
yesterday I opened Windows 7 iso file in my Windows 10 operating system, and pressed 'Install now', I immediatly cancel the operation, and a new partition showed up next to C: drive, I knew nothing about system partition yesterday and I though Windows 7 installation reserved it, so I erased the 2 folders that had inside (EFI and Boot). But the partition still existed, so I restarted the PC and now shows: "Reboot and select proper boot device" (Windows 10 no longer boots).
I tried to fix it with Windows 10 USB iso's troubleshoot and everything failed, so I tried using the Command prompt tool but couldn't do much with it.
I try and go into the bios to change the order of the boot devices but my keyboard start to turn on with flashing leds like normal then just turns off.
So I installed Windows 10 via media creation tool on my newly built desktop PC but its stating my windows key is from what I'm assuming the laptop I made it from ( GF's laptop). I bought a key for windows 10 but I can't get to any screen that allows me to type it in. When I go to System> Activate I get a notification sound like a window popped up and needs me to click something but I can't see anything nor is a window present. From there the whole settings window freezes up and forces me to end it. Is there any way to remedy this without reinstalling all my programs?
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.
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.
When turning on my computer today, I had to face a BSOD with the error name being "System Thread Exception not Handled", which prevented me from launching Windows 10 in either way. So I rebooted my computer on my Linux Mint partition in order to look on the internet the solution to this error. I then created a USB bootable with Windows 10, so I can access to the troubleshoot kits. However, when I launched my computer again on my USB key, I found myself in front of a black screen with words saying "Reboot and select proper boot device".
Things get quite weird from now, because when I try to boot from my SSD where Windows 10 is installed, I no more have the previous BSOD, but always and always this black screen with the same message. I do not know how to do now in order to access to Windows 10 again.
Unfortunately, being unable to access to Windows 10, I can't give you a DM Log Collector.
Downloaded Windows 10 and started installing it. The install got to around 20% and now I'm stuck on a black screen with "Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key". I have gone into BIOS and changed boot order around but it doesn't seem to make any difference.
I am getting that error at splash screen after failed dual boot install of Debian. It was on the same drive, but I do not have another PC to get a boot repair or any other tool. I could go to a friend as last resort. Tried setting bios, still doesn't work.
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
My custom-built pc all of a sudden won't boot in to windows. i get the error message "reboot and select proper boot device or insert boot media in selected boot device and press a key", and i have made sure that my hdd is my first boot option. i want to reinstall windows now because that seems like the only way out, but i cant because i have no recovery usb or disc. what can i do to boot to this harddrive, that my bios detects just fine.
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 have a strange anomaly with my HP Pavilion dv7-1245dx Entertainment Notebook that had Windows 8.1installed. When I started bootup, it got so far and froze up. I had to do a hard shutdown. On the second try, the laptop starts, but takes an inordinately long time to get to the lock screen.
I thought that when I installed my 240 GB SSD drive and installed Windows 10 that the anomaly would be gone, but it's still happening.
If I shut down, I have to go through the two bootup tries again.
I recently updated my HP to Windows 10. During setup after I logged in, I got the BSOD. I thought there was nothing wrong until I logged in and found out that I didn't have Start Menu access. About 10 seconds later, the BSOD came up again. Now every time I log in, about 10 to 30 seconds after login, I get the BSOD.
During boot up I get a black screen for about 1 min then the login for my account. I notice a lot of hard drive activity during the black screen. I'm using amd-catalyst-15.10beta-64bit-win10-win8.1-win7-oct12.exe (latest one).
Win 10 works fine except for the black screen. I've had this black screen since day one but it seems to be longer. I have tried AMD 15.7.1 driver.
I don't have an on board graphics.
I'm almost thinking of grabbing another hard drive and do a clean install and see if that fixes it.
I've had this issue for a while and haven't really bothered to do anything about it till now. Since I upgrade to Win10 some months ago, I've noticed that every time I start or reboot my PC my internet connection dissappears after the first 5-10 seconds and then returns some ~60 seconds later. The loss of connectivity is not displayed in the Network sys_tray nor will Chrome/Edge tell me I do not have a connection. What happens instead is that the browser tabs take a very long time to load until they all suddenly load at once. Services like steam connect on start up, but then I go into offline mode as soon as I "lose the connection".
I'm not using WiFi and have not changed any hardware since upgrading to Win10. My suspicion is that I'm able to receive packages, but my outgoing packages are being, somehow, blocked. I am using zonealarm but have also tried with it uninstalled.
I woke up this morning and turned on my laptop from sleep mode and it went straight to my desktop not to a screen to ask to input my password like usually. Is this normal or some mix up?
I just upgraded to Windows 10 from 8.1 with MAJOR hassles (BSOD, black screens, freezes, unresponsiveness, etc), so I decided to do a clean install. But during the install, it hanged at the black screen after "getting devices ready." I did a cold boot and got a black screen. The display didn't get a signal since the monitor light stays yellow instead of turning green.
I disconnected the power cord and held the power button down for a few seconds (some discharge static electricity method I found on the web), and reconnected the power cord, and it boot up fine into the Windows setup menu and set up everything fine. After downloading some programs and stuff, I turned off my PC off and booted it up, and I get this same black screen issue. Weird thing is, if I do the same method of holding the power button down and stuff, it boots up fine to the login menu and desktop.
What I've read or something, I should remove the CMOS battery or something, or upgrade the BIOS, etc.
For two years I have had three hard drives installed. One small one went bad and at bootup I would get that information with "Press F1 to resume" which I would do and then windows would load. I upgraded to windows 10 from 7 three weeks ago, same message, and no problem, as it would still go right into windows. Last week I noticed windows update had a list of important updates. I believe I also had an nvideo GeForce driver update which I am sure I did first without problems.
When I did the windows updates and had to restart, I noticed I had a slightly different look but it still took me to the same press F1 to resume. However, the result was it went to a totally black screen with a tiny band of the new windows blue across the top and in the middle of the screen it said WAIT, not in windows type but in the same script when you first begin booting computer. It just remained there and there was no activity taking place, no blinking red light or solid red light like my computer always does.
After at least 20 minutes of no activity I rebooted with the same result. Repeating the F1 kept giving the same result, and further reboots and then the F1 caused the computer to reboot maybe 2 out of 5 tries instead of directly going to the black screen. At one point I quickly saw something where I believe it askd to press tab or possibly delete and then gave an option to press F1 or F2. I am not sure which I pressed but it did go into windows and everything was fine for the rest of the day. I let my computer on but at some point overnight it had rebooted and back to the press F1 to resume which results in back to the black screen WAIT and this is where I am at again (I am using a different computer to send this).
