Morpheus2396
New member
- Local time
- 1:55 AM
- Messages
- 5
Hello guys,
I'm new to 7F and I am glad of having joined to community of W7 users
I have a very serious problem since a few days. Let's sum it up:
Before the problem occured, I employed a dual-boot setup (W7 & W10):
- Win7 x64 installed on a SSD (UEFI-Installation, GPT-Partition) (Win7-Installation/Partition is labeled "C:\")
- Win7, Programs and System Files stored on the SSD
- Personal Data, User Files and Games (of W7) stored on the HDD (GPT-Partition labeled "D:\")
- Win10 Pro x64 (15/11) also installed on the HDD (UEFI-Installation, GPT-Partition labeled "C:\" internally)
Background:
- a few days ago, a BSOD (0x0000007F) occurred on Win7 after login - probably a defrag tool called WarpDisk caused it, because it defragmented C:\pagefile.sys despite C:\ being on a SSD!
- after that, the same BSOD occured in Win7 after every login (after successfully booting)
- before the BSOD popped up, I noticed that BOTH Steam & Origin requested me to log in - despite both clients were configured to "stay logged in"!
- Win10 was NOT affected by this problem - everything worked flawless!
My first attempt to fix the problem:
- starting WinRE
- running CHKDSK, SFC /scannow, "System Startup Repair", "Last known working configuration" and "BootRec" - all failed! (CHKDSK % SFC both reported "no problems")
- Uninstalling WarpDisk (manually from W10) and then repeating the same steps was useless, too! The same BSOD always occurred after every login!
- at that point, it dawned on me that maybe not Windows 7 itself, but the EFI-Partition was damaged!
So, my second attempt was:
- deleting the EFI-Partitions (ESP- and MSR- partitions) on the SSD
- recreating them (fresh new ones)
- manually rebuilding the BCD store with BCDEdit in order to repair the Win7 bootloader.
- the first few lines of commands were successfully applied by the system but on a certain point, I got stuck - and it was always the same point, where I hit the dead end:
bcdedit /store BCD /set {default} default {guid}
- whenever I tried to apply this command, an error message occurred:
The requested system device cannot be found.
- I spent the following couple of hours with disstressing attempts to whatever rebuild the BCD store by the "trial-error" scheme, with several attempts.
- however, all attempts failed. I couldn't rebuild the BCD store!
By then, the problem got even more serious:
Now, I couldn't boot ANYMORE because the boot manager got messed up after my unsuccessful attempts with BCDEdit - I couldn't even boot W10 anymore, which worked flawlessly until then.
Fortunately, I could repair the W10 bootloader by creating a new, fresh one:
(I used this walkthrough for this goal - because it's dedicated to UEFI-/GPT-Installations of Windows)
- recreating EFI-Partitions (ESP and MSR) on the HDD
- copying W10 boot files to the ESP-Partition
- repairing EFI boot record
- rebuilding BCD store
(I just don't understand, why the same attempt did't work with W7 - my guess is, the EFI boot files in the Windows folder (C:\Windows\Boot\EFI) themselves are damaged, so copying them to a fresh ESP-Partition will not repair the W7 bootloader)
In the meanwhile, I made a fatal mistake:
- when I once more tried to recreate the ESP- and MSR-Partitions for W7 on the SSD, I accidently selected the wrong partition and hit "ENTER"
- the partition I accidently selected was my W7 partition!
- immediately an error message occurred: (I don't remember how exactly it was, something like this: )
"Could not format partition. The selected partition is too large for the destination filesystem"
- for the first seconds, I was surprised about this message - because I *always* succeeded with this step!
- but then, I realized I accidently selected my W7-Partition (filling up the entire SSD, ~ 120GB in size) and unawaringly tried to apply a FAT32 filesystem on it...
- I entered "list disk" in diskpart and now the filesystem of my W7-Partition wasn't NTFS anymore, but RAW!
- nevertheless, my W7 partition wasn't reformatted (because it was still full 107 out of ~ 120GB, with 12GB of free space) and no data was erased!
- but it didn't have a filesystem either - the partition information (NTFS filesystem and other partition properties) was erased by my accidental mistake, despite the reformat process was aborted immediately...
Now, my first priority is to restore the filesystem of my W7-Partition - so, I can access W7 again. But I don't know how to recover lost partition properties. I say again, the partition *itself* seems to be unchanged - but apparently partition metadata (filesystem and other properties) is reset/lost!
Please help me with this - the initial boot problem is actually not my primary priority...
And keep in mind: This is an UEFI-Installation - so, many commands (e.g. BootRec) and tutorials/walkthroughs might not apply to this problem...
Thx,
M2396
I'm new to 7F and I am glad of having joined to community of W7 users
I have a very serious problem since a few days. Let's sum it up:
Before the problem occured, I employed a dual-boot setup (W7 & W10):
- Win7 x64 installed on a SSD (UEFI-Installation, GPT-Partition) (Win7-Installation/Partition is labeled "C:\")
- Win7, Programs and System Files stored on the SSD
- Personal Data, User Files and Games (of W7) stored on the HDD (GPT-Partition labeled "D:\")
- Win10 Pro x64 (15/11) also installed on the HDD (UEFI-Installation, GPT-Partition labeled "C:\" internally)
Background:
- a few days ago, a BSOD (0x0000007F) occurred on Win7 after login - probably a defrag tool called WarpDisk caused it, because it defragmented C:\pagefile.sys despite C:\ being on a SSD!
- after that, the same BSOD occured in Win7 after every login (after successfully booting)
- before the BSOD popped up, I noticed that BOTH Steam & Origin requested me to log in - despite both clients were configured to "stay logged in"!
- Win10 was NOT affected by this problem - everything worked flawless!
My first attempt to fix the problem:
- starting WinRE
- running CHKDSK, SFC /scannow, "System Startup Repair", "Last known working configuration" and "BootRec" - all failed! (CHKDSK % SFC both reported "no problems")
- Uninstalling WarpDisk (manually from W10) and then repeating the same steps was useless, too! The same BSOD always occurred after every login!
- at that point, it dawned on me that maybe not Windows 7 itself, but the EFI-Partition was damaged!
So, my second attempt was:
- deleting the EFI-Partitions (ESP- and MSR- partitions) on the SSD
- recreating them (fresh new ones)
- manually rebuilding the BCD store with BCDEdit in order to repair the Win7 bootloader.
- the first few lines of commands were successfully applied by the system but on a certain point, I got stuck - and it was always the same point, where I hit the dead end:
bcdedit /store BCD /set {default} default {guid}
- whenever I tried to apply this command, an error message occurred:
The requested system device cannot be found.
- I spent the following couple of hours with disstressing attempts to whatever rebuild the BCD store by the "trial-error" scheme, with several attempts.
- however, all attempts failed. I couldn't rebuild the BCD store!
By then, the problem got even more serious:
Now, I couldn't boot ANYMORE because the boot manager got messed up after my unsuccessful attempts with BCDEdit - I couldn't even boot W10 anymore, which worked flawlessly until then.
Fortunately, I could repair the W10 bootloader by creating a new, fresh one:
(I used this walkthrough for this goal - because it's dedicated to UEFI-/GPT-Installations of Windows)
- recreating EFI-Partitions (ESP and MSR) on the HDD
- copying W10 boot files to the ESP-Partition
- repairing EFI boot record
- rebuilding BCD store
(I just don't understand, why the same attempt did't work with W7 - my guess is, the EFI boot files in the Windows folder (C:\Windows\Boot\EFI) themselves are damaged, so copying them to a fresh ESP-Partition will not repair the W7 bootloader)
In the meanwhile, I made a fatal mistake:
- when I once more tried to recreate the ESP- and MSR-Partitions for W7 on the SSD, I accidently selected the wrong partition and hit "ENTER"
- the partition I accidently selected was my W7 partition!
- immediately an error message occurred: (I don't remember how exactly it was, something like this: )
"Could not format partition. The selected partition is too large for the destination filesystem"
- for the first seconds, I was surprised about this message - because I *always* succeeded with this step!
- but then, I realized I accidently selected my W7-Partition (filling up the entire SSD, ~ 120GB in size) and unawaringly tried to apply a FAT32 filesystem on it...
- I entered "list disk" in diskpart and now the filesystem of my W7-Partition wasn't NTFS anymore, but RAW!
- nevertheless, my W7 partition wasn't reformatted (because it was still full 107 out of ~ 120GB, with 12GB of free space) and no data was erased!
- but it didn't have a filesystem either - the partition information (NTFS filesystem and other partition properties) was erased by my accidental mistake, despite the reformat process was aborted immediately...
Now, my first priority is to restore the filesystem of my W7-Partition - so, I can access W7 again. But I don't know how to recover lost partition properties. I say again, the partition *itself* seems to be unchanged - but apparently partition metadata (filesystem and other properties) is reset/lost!
Please help me with this - the initial boot problem is actually not my primary priority...
And keep in mind: This is an UEFI-Installation - so, many commands (e.g. BootRec) and tutorials/walkthroughs might not apply to this problem...
Thx,
M2396
Last edited:
My Computer
At a glance
Windows 7 Ultimate x64 SP1 (German Version), ...Intel Core i7 4771 (boxed), HT enabled, OCed ...4x 4GB Corsair Vengeance (DDR3-1600, Dual Cha...Nvidia GeForce GTX 770 4GB @ FW359.00 WHQL
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- custom build (self-made)
- OS
- Windows 7 Ultimate x64 SP1 (German Version), UEFI-Installation
- CPU
- Intel Core i7 4771 (boxed), HT enabled, OCed (Turbo-OC)
- Motherboard
- ASUS Z87-K (C2-Stepping) @ BIOS 1402
- Memory
- 4x 4GB Corsair Vengeance (DDR3-1600, Dual Channel, XMP on)
- Graphics Card(s)
- Nvidia GeForce GTX 770 4GB @ FW359.00 WHQL
- Hard Drives
- SSD: Samsung SSD 840 Pro 128GB @ latest FW (Win7 Main Drive)
HDD: Samsung HD501LJ 500GB (Win7 User Files, Win10 Installation)
- Antivirus
- Kaspersky Internet Security 2016
- Browser
- Opera (most preferred), Firefox (universal)
)
