I just recently upgraded from an earlier build of Windows 10 to the latest build 11099. That went okay. But the problem was when I decided to extend the system partition (as it had only 3GB free left), after rebooting to extend the partition with MiniTool Partition Wizard (it required me to reboot so it could unlock the partition). That seemed like it went okay too, but after restarting, I would get a BSOD and no boot up at all. It seems like the partition extension has messed up the boot files. I say that because a folder named "$WINDOWS.~BT" has been created in the root directory of the system drive. (Now it's drive G: because I'm on another system in another partition temporarily).
And some other folder as well:
So my question is this. Since I have all these boot files here, could it possibly be that while the partition was being extended, the software I used might have messed up those files, and now my Windows doesn't boot up?
If so, or whatever the reason for that matter, is there anything I can do to take those boot files back to where they belong?
I am currently running windows10 on a HP tablet. I have it in a docking station, which has a second larger screen attached.
Last night set it up, perfect movie playing on external, able to browse ect on tab. Removed it today, re-docked, no display (blank screen) on external. Reset duel settings, making tab the primary screen.
A few months ago, i made a dual boot of Windows 8.1 and Windows 10. Now I was running out of memory on my Windows 10 partition, so I removed Windows 8.1. I was unable to add the free space to the Windows 10 partition because this free space was before the 10-partition.
So I decided to clone W10 to the free space using Easeus disk copy. (Successfull). Now i wanted to boot the clone, remove the old one and add the free space to the cloned W10. But i am unable to boot the clone. I can't chose the partition to boot from. What went wrong? there are 2 identical partitions with W10. How I can solve this without reinstalling everything?
I was messing around with partitions and created a test partition that was unfortunately the same size as my EFI partition. I went to delete my test partition, but deleted the EFI partition by mistake and now my computer won't start.
I am running windows 10 on my desktop and I have it hooked up to a TV to have two displays. I am using an HDMI splitter (2 Port HDMI Video Splitter from StarTech.com) but my Windows 10 is not recognizing the second display. The TV displays the same screen as my monitor but will not allow me to "extend" because not second screen is being recognized. What could be the issue?
I have decided to get ready to remove my pesky 4.88GB Windows 8.1 Partition (partition 5) from my PC because now I have Windows 10 and no longer have the option to go back. I have used a Command in the Elevated Command Prompt to enable the F8 boot menu as a substitute to the manufacturers boot menu (Press Esc.) I know the boot menu by the manufacturer will be removed with the (partition 5) too. I have also found that the WinRE is on a different partition (partition 4), and so my question is... If I delete the manufacturers partition (p 5), will the F8 menu also be gone as well? It seems the F8 menu was put there by windows and not the manufacturer, but is it on partition 5 or is it on the same one as the WinRE partition (p 4)?
I upgraded my Windows 7 to Windows 10. Now I would like to have a multi-boot. If I install Windows 7 on my blank 150 GB partition, will Windows 10's boot sequence recognize it so that I have a working multi-boot?
So I have a 128gb 840 evo ssd as my C drive and then a WD caviar Blue as a mass storage drive . So with windows 10 just coming out and it being free I thought I would duel boot it with windows 7(currently running) and went and cleared out a bunch of old games and programs and ended up the 47 gb free so I would have space to make a partition and have a little room after that. then once I tried to shrink the volume it says the maximum i can shrink it is 129mb. so I tried on my HDD and it worked just fine being able to shrink it 600GB(the remaining storage).
My computer froze during a Windows update, and I had to force a shut down, which really messed up my computer.
My computer was stuck in a boot loop, so I attempted to reinstall windows 10 onto it. At around 3% it crashed again, and since then has been really messed up.
If it tries to boot normally, it no longer gets stuck in a boot loop, but now just instantly crashes to blue screen, saying a required device can't be accessed (error 0xc000000f).
I tried to boot into the windows 10 install disk to try and run chkdsk or attempt other recovery tasks, but it crashes after a few seconds of being on the menu, saying to search for FAT FILE SYSTEM to try and fix the error.
I downloaded gparted onto a USB and ran it. It gave me this error: [URL]
I need to install Linux for school and therefore was partitioning my windows. I created a 60GB and 1GB swap ext3 partitions using easus partition master and now I am getting a blue screen with that code. Note; I haven't tried to install Linux yet.
I used repair in windows usb media which couldn't find anything, then I tried the following:
Recently I was trying to add comments to movie folders so that i can keep a brief description about it when i click on it. It was easy to add comment then i had a bit trouble to get the comment getting displayed in the details pane...after playing with the registry for a while i got that solved as well.
Now I ended up with a problem where the comment being displayed eds with just some 3 or 4 words with the remaining given in dots (...) and I get a full display of it when i hover the mouse over it, which obviously goes way in 5 seconds or so.
So what i need is to find a way to expand what ever that is shown in the details pane so that it shows the entire content in consecutive lines without being restricted to one line (without having to hover a mouse)
You might get a picture of it if you have a small details pane on the right and make it show your processor details when you open thisPC.
Whow, Win 10 seem so easy at the first installation but problems or bizarre things come out one after the others. Now, I can't move a windows unless this one has been reduce. Is it possible to get back this function has I use to do it with previous version?
I created a dual boot system quite some time ago and all was well until.RTM partition was completely up-to-date. I had recently updated to Windows 10 Build 10251 on the Insider partition.I turned the machine off on Sunday January 31, left town, and returned Saturday February 6. All was well with the dual boot when I turned the system off before leaving. When I turned the system on last night, it booted directly into the Insider Partition. There seems to be no option to boot into the RTM partition.
Anyway, a while ago, I was playing with booting installations from a HDD, which worked, but now it seems I'm stuck with the partition I used to store the installation on.
So I have two questions:
1. To delete the H partition, I need to first set the C one to active, correct? 2. Is it even safe to delete the partition since it's a "system" partition?
The H partition is empty as far as general files go, but since it's bootale, it always shows up as a boot option, which is mildly annoying.
I have now a couple of windows 10 laptops (using hdd rather than ssd) where the system shows progress to 12% and then waits forever, maybe 2 hours or so before completing.
What is happening, but with the limited info that Windows 10 shows it is hard to estimate how long it will take. At least with chkdsk before windows 8/10, one had something to go on.
reminds me of Vista and defrag where again Microsoft thought it was an improvement to show less information.
Okay, so the other week i received a new Clevo P650SE laptop. The laptop only had a 500GB 7200RPM HDD with Windows 10 to begin with, so yesterday i added my Samsung 840 EVO SSD. As i wanted this to now be the primary drive, i made another new installation of Windows onto here. After doing this, the system now displayed a boot selection at startup with the choice between the new Windows 10 installation on my SSD or the old one on the HDD.
As i no longer wanted to use the HDD for running Windows, i decided it would be best to delete Windows from this drive. So i booted onto an Ubuntu USB and wiped the entire drive of it's data in GParted, which included three different partitions. This seemed perfectly fine to me at the time, because i had a the new installation from the SSD showing up in the boot manager.
However, when i rebooted the machine and attempted to boot into the new installation on the SSD, it gives me this message:
"The boot configuration data from your PC is missing or contains errors. File: /EFI/Microsoft/Boot/BC Error code: 0xc000000f"
I have tried everything to recover the system but nothing has worked. Startup repair from my Windows USB doesn't do anything, the system reset wouldn't operate because it stated that the partition was locked.
Nothing with the Command Prompt is working, I have done 'bootrec /fixmbr', 'bootrec /fixboot' and 'bootrec /rebuildbcd', but the last command returns the following error:
"The requested system drive cannot be found."
I also did 'bcdboot C:/Windows' but that also refused to work. I assumed the reason for this might be because the drive didn't have a letter, but when i attempted to add a letter is says:
"The specified drive letter is not free to be assigned."
Both drives in my laptop have now been completely wiped and converted to MBR, but even with the two drives empty the original message still appears when booting my Windows USB in UEFI.
I have only had this laptop a couple of weeks and it's already completely messed up. I can boot the Windows USB in Legacy and install Windows as normal, but of course i'm looking to have it back on UEFI as it was before.
Last night I accidentally hit 'hibernate' and as i was in a rush i held the power button. Low and behold i woke up this morning went to put it on and got to the BSOD. I basically get to the login screen, login and then it repeats. Ive had the BSOD before but it just restarted and everything was fine. Now I'm trying to turn the pc on and its stuck in a reboot cycle, doesn't get to the login screen. I've literally tried everything, the PC won't even reset or anything. Genuinely stuck....
I've gotten the BOSD 7 times today. The BOSD said it was because of various things throughout the day, at first it said it was Memory Management, but after that I just started to get annoyed.
Checking back through the event logs, the bugcheck says the errors were: 0x00000050; 0x000000ef ; 0x0000001a; 0x0000000a; 0x00000139; 0x000000c1
If it isn't obvious, I really don't know how to solve this or if the bugcheck errors useful at all. What I do know is that I was just using google chrome when some of the crashes happened. Also during the day, several times I booted up my computer and logged in and then went away for 5 minutes after logging in (without doing anything). When I came back, it was obvious that my computer had restarted.
I am using Dell inspiron laptop (pretty old one) which started acting weirdly. Upon examining, there was a problem with HDD so I had it changed.
As soon as I got new HDD installed and installed Windows 10 on it, computer started acting weird again - slow startups, random freeze etc.- but it was running ok and I was fine with it. But earlier today, it suddenly displayed BSOD and crashed when it was idle. Now to the main and the funny part, it does not boot anymore. To elaborate, blank screen appears after BIOS screen (right when the logo of windows should be displayed) and it remains blank for several more minutes before the logo and spinning dots magically appear, it doesnt disappear thereafter.
I figured, I could run startup repair or some other tool to solve the problem by booting from the DVD of windows 10. Now for this one, the logo appears with the spinning dots which disappears after a while like it should. And after it disappears, blank screen persists thereafter. Dumbfounded, I tried booting from a USB stick of Windows 8 I had which gave the same problem.
I have already tried altering most of the options in BIOS and the diagnostic tool gives and all-ok for all the installed hardware.
I run Win10 under Parallels at MacBook. Few days ago it started to crash about 30 minutes after boot. I don't need to do anything, just wait and it will die. Usually it's REGISTRY_ERROR, but sometimes another error.
sfc shows some errors, but they don't look dangerous.
I've talked to Parallels guys and they claim it's Windows issue, not VM. Checked Win7 VM and works fine.
I am using Dell inspiron laptop (pretty old one) which started acting weirdly. Upon examining, there was a problem with HDD so I had it changed.
As soon as I got new HDD installed and installed Windows 10 on it, computer started acting weird again - slow startups, random freeze etc.- but it was running ok and I was fine with it. But earlier today, it suddenly displayed BSOD and crashed when it was idle. Now to the main and the funny part, it does not boot anymore. To elaborate, blank screen appears after BIOS screen (right when the logo of windows should be displayed) and it remains blank for several more minutes before the logo and spinning dots magically appear, it doesnt disappear thereafter.
I figured, I could run startup repair or some other tool to solve the problem by booting from the DVD of windows 10. Now for this one, the logo appears with the spinning dots which disappears after a while like it should. And after it disappears, blank screen persists thereafter. Dumbfounded, I tried booting from a USB stick of Windows 8 I had which gave the same problem.
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 bsods and game crashes of steam. I putted a new ram because the previous ram kit died (faulty rams causing bsods)and also I have a new graphic card r9 280 (because the previous gtx480 died too). What can I do? Bumps are not specific. I believed that sound driver causing problems and I disabled sound controller from bios and uninstalled the drivers. Unfortunately bsods don't stop. I have checked for drivers , updates, memtest but nothing. I noted that bsods and crashes happen in the first boot. If I have a bsod or I reboot after a game crash then BSODS and crashes stop to happen.
My Windows 10 (64bit) has always had issues with "page fault in nonpaged area" errors, usually when rebooting from sleep. Yesterday, my system crashed again again. Instead of booting up as normal, it crashed again with the same error, rebooted, and crashed again. My computer can no long boot to Windows.
I've searched online and have seen that it could be my RAM, so I tried running one stick at a time and it didn't work. I also tried to use a bootable flash drive (made with Media Creation Tool) to reformat my hard drive / reinstall Windows 10, but I get the same error/crash when I boot from the flash drive.
Here's my system specs:
CPU: Intel I-4790k RAM: G.Skill RIPJAW 2x8GB MOTHERBOARD: Asus Z97-A ATX LGA1150 STORAGE: Samsung 840 EVO 250GB SSD
After upgrading to Windows 10 from Windows 7 within the last week, everything was fine at first. Then this morning Everything on screen froze, and when I did a force restart, the following happened (and continues to happen ad nauseam):
Windows tries to boot as normal, but I get the BSOD saying Unmountable_Boot_Volume
It then restarts, saying it's going to repair the problem, only this time it flashes to a blue screen that says Chose Your Keyboard Layout. At this point I am unable to use either my mouse or keyboard. I've tried wireless, wired, all USB ports. Nothing.
I don't have Windows 7 disc (came pre-loaded from the factory), and I don't have a Windows 10 disc or flash drive. The only other computer I have to work with this is an old laptop running XP. I downloaded the Media Creation Tool, but when I try and run it on my XP laptop it says it's not a valid win32 application, so making a flash drive boot seems out of the question.
