Please update the progress with posts #96 and #102.
(please perform these steps when the problematic drive is installed in the second bay of the working computer)
When the drive is in the problematic computer please perform a startup repair > indicate if it creates a srttrail.txt
Last edited by zbook; 28 Feb 2021 at 03:52.
@Tekkie Boy: Dropbox - SYSTEM - Simplify your life
- - - Updated - - -
@zbook: I will, I have already I think...
@RingTailCoon: DUDE IT'S LIKE, MOOOST COMPLICATED, TOOOOOOOTALY NONE TUBULAR... sorry I just had a Bill & Ted moment... yea it's an on going thing...
- - - Updated - - -
@zbook:
DiskParInfo.log
You did not have to upload the file. Just post the output as below:
Code:Disk 0 : HDD. It has 3 partition(s). Model: Hitachi HDT721010SLA360 Disk 1 : SSD. It has 2 partition(s). Model: KINGSTON SH103S3480G The script has found the above 2 storage device(s) in total. ======================================================================= Microsoft DiskPart version 10.0.19041.610 Copyright (C) Microsoft Corporation. On computer: DESKTOP-M751J4G Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- Disk 0 Online 931 GB 974 MB Disk 1 Online 447 GB 1024 KB Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 C WinXBoot NTFS Partition 372 GB Healthy System Volume 1 F Arkhive NTFS Partition 397 GB Healthy Volume 2 G Old Boot NTFS Partition 160 GB Healthy Volume 3 N MAGICTHIGHS NTFS Partition 446 GB Healthy Volume 4 E RESERVED FAT32 Partition 451 MB Healthy Disk 0 is now the selected disk. Hitachi HDT721010SLA360 Disk ID: 0016D381 Type : SATA Status : Online Path : 0 Target : 0 LUN ID : 0 Location Path : PCIROOT(0)#PCI(1F02)#ATA(C00T00L00) Current Read-only State : No Read-only : No Boot Disk : Yes Pagefile Disk : Yes Hibernation File Disk : No Crashdump Disk : Yes Clustered Disk : No Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 C WinXBoot NTFS Partition 372 GB Healthy System Volume 1 F Arkhive NTFS Partition 397 GB Healthy Volume 2 G Old Boot NTFS Partition 160 GB Healthy Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Primary 372 GB 1024 KB Partition 2 Primary 397 GB 372 GB Partition 3 Primary 160 GB 769 GB Partition 1 is now the selected partition. Partition 1 Type : 07 Hidden: No Active: Yes Offset in Bytes: 1048576 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 0 C WinXBoot NTFS Partition 372 GB Healthy System Partition 2 is now the selected partition. Partition 2 Type : 07 Hidden: No Active: No Offset in Bytes: 400086269952 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 1 F Arkhive NTFS Partition 397 GB Healthy Partition 3 is now the selected partition. Partition 3 Type : 07 Hidden: No Active: No Offset in Bytes: 826500812800 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 2 G Old Boot NTFS Partition 160 GB Healthy Disk 1 is now the selected disk. KINGSTON SH103S3480G Disk ID: 000163B6 Type : SATA Status : Online Path : 2 Target : 0 LUN ID : 0 Location Path : PCIROOT(0)#PCI(1F02)#ATA(C02T00L00) Current Read-only State : No Read-only : No Boot Disk : No Pagefile Disk : No Hibernation File Disk : No Crashdump Disk : No Clustered Disk : No Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 3 N MAGICTHIGHS NTFS Partition 446 GB Healthy Volume 4 E RESERVED FAT32 Partition 451 MB Healthy Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Primary 446 GB 31 KB Partition 2 Primary 451 MB 446 GB Partition 1 is now the selected partition. Partition 1 Type : 07 Hidden: No Active: Yes Offset in Bytes: 32256 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 3 N MAGICTHIGHS NTFS Partition 446 GB Healthy Partition 2 is now the selected partition. Partition 2 Type : 0C Hidden: No Active: No Offset in Bytes: 479628099584 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 4 E RESERVED FAT32 Partition 451 MB Healthy =============================================================================== Windows Recovery Environment (Windows RE) and system reset configuration Information: Windows RE status: Enabled Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE Boot Configuration Data (BCD) identifier: ff2b4823-5fd8-11eb-b354-00252249db21 Recovery image location: Recovery image index: 0 Custom image location: Custom image index: 0 REAGENTC.EXE: Operation Successful. =============================================================================== Windows Boot Manager -------------------- identifier {bootmgr} device partition=C: description Windows Boot Manager locale en-GB inherit {globalsettings} default {current} resumeobject {ff2b4821-5fd8-11eb-b354-00252249db21} displayorder {current} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {current} device partition=C: path \Windows\system32\winload.exe description Windows 10 locale en-GB inherit {bootloadersettings} recoverysequence {ff2b4823-5fd8-11eb-b354-00252249db21} displaymessageoverride Recovery recoveryenabled Yes allowedinmemorysettings 0x15000075 osdevice partition=C: systemroot \Windows resumeobject {ff2b4821-5fd8-11eb-b354-00252249db21} nx OptIn bootmenupolicy Standard Windows Boot Loader ------------------- identifier {ff2b4823-5fd8-11eb-b354-00252249db21} device ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{ff2b4824-5fd8-11eb-b354-00252249db21} path \windows\system32\winload.exe description Windows Recovery Environment locale en-gb inherit {bootloadersettings} displaymessage Recovery osdevice ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{ff2b4824-5fd8-11eb-b354-00252249db21} systemroot \windows nx OptIn bootmenupolicy Standard winpe Yes Resume from Hibernate --------------------- identifier {ff2b4821-5fd8-11eb-b354-00252249db21} device partition=C: path \Windows\system32\winresume.exe description Windows Resume Application locale en-GB inherit {resumeloadersettings} recoverysequence {ff2b4823-5fd8-11eb-b354-00252249db21} recoveryenabled Yes allowedinmemorysettings 0x15000075 filedevice partition=C: filepath \hiberfil.sys bootmenupolicy Standard debugoptionenabled No Windows Memory Tester --------------------- identifier {memdiag} device partition=C: path \boot\memtest.exe description Windows Memory Diagnostic locale en-GB inherit {globalsettings} badmemoryaccess Yes EMS Settings ------------ identifier {emssettings} bootems No Debugger Settings ----------------- identifier {dbgsettings} debugtype Local RAM Defects ----------- identifier {badmemory} Global Settings --------------- identifier {globalsettings} inherit {dbgsettings} {emssettings} {badmemory} Boot Loader Settings -------------------- identifier {bootloadersettings} inherit {globalsettings} {hypervisorsettings} Hypervisor Settings ------------------- identifier {hypervisorsettings} hypervisordebugtype Serial hypervisordebugport 1 hypervisorbaudrate 115200 Resume Loader Settings ---------------------- identifier {resumeloadersettings} inherit {globalsettings} Device options -------------- identifier {ff2b4824-5fd8-11eb-b354-00252249db21} description Windows Recovery ramdisksdidevice partition=C: ramdisksdipath \Recovery\WindowsRE\boot.sdi
Thanks.
At this point I can tell you that you don't need to do anything anymore.
Your uploaded System Hive is corrupted.
Usually it has a size of about 10 MB.
And then it gets bigger over time.
Your uploaded file only has about 2 MB and important entries are missing and some of them are damaged.
Reinstall the hard drive in your desktop PC, back up your important data from the hard drive.
Then put the hard drive back into the original PC and perform a clean installation.
Sorry for the bad news
Is there any way I can force an inplace upgrade...
Yea, I noticed that. I'm going to try an transplant a system hive that is error free into the damaged registery on the faulty Windows instsallation, if I can get it to boot, maybe it can be repaired or inplace installed... I know its a long shot, but a clean install is a huge problem for me... don't worry I'll back up the original hive first... here we go!
- - - Updated - - -
OMG! It's trying to boot!!! I got this BSOD but, if I we can just get it to repair!! I'm on to something here I know it!!
- - - Updated - - -
Any thoughts...
I am not aware of any way to implant a new System Hive.
Sorry
Quote
