Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

fixlist for FRST64 please? can't boot...ugh... [Closed]


  • This topic is locked This topic is locked

#1
skoolpsyk

skoolpsyk

    New Member

  • Member
  • Pip
  • 6 posts

 I really don't know what this all means, but it sure doesn't look good. Can someone make a fixlist from this? 

I haven't been able to boot, even in safemode. 

 

thanks!!!!

 

Scan result of Farbar Recovery Scan Tool (FRST.txt) (x64) Version: 12-09-2014
Ran by SYSTEM on MININT-3NRIMSA on 17-09-2014 14:58:47
Running from G:\
Platform: WIN_7 (X64) OS Language: English (United States)
Boot Mode: Recovery
Attention: Could not load system hive.
Attention: System hive is missing.
 
Tutorial for Farbar Recovery Scan Tool: http://www.geekstogo...very-scan-tool/
 
==================== Registry (Whitelisted) ==================
 
(If an entry is included in the fixlist, the registry item will be restored to default or removed. The file will not be moved.)
 
ATTENTION: Software hive is missing.
 
==================== Services (Whitelisted) =================
 
(If an entry is included in the fixlist, the service will be removed from the registry. The file will not be moved unless listed separately.)
 
 
==================== Drivers (Whitelisted) ====================
 
(If an entry is included in the fixlist, the service will be removed from the registry. The file will not be moved unless listed separately.)
 
 
========================== Drivers MD5 =======================
 
 
==================== NetSvcs (Whitelisted) ===================
 
(If an item is included in the fixlist, it will be removed from the registry. Any associated file could be listed separately to be moved.)
 
 
==================== One Month Created Files and Folders ========
 
(If an entry is included in the fixlist, the file\folder will be moved.)
 
 
==================== One Month Modified Files and Folders =======
 
(If an entry is included in the fixlist, the file\folder will be moved.)
 
 
==================== Known DLLs (Whitelisted) ================
 
 
==================== Bamital & volsnap Check =================
 
(There is no automatic fix for files that do not pass verification.)
 
C:\Windows\System32\winlogon.exe IS MISSING <==== ATTENTION!.
C:\Windows\System32\wininit.exe IS MISSING <==== ATTENTION!.
C:\Windows\SysWOW64\wininit.exe IS MISSING <==== ATTENTION!.
C:\Windows\explorer.exe IS MISSING <==== ATTENTION!.
C:\Windows\SysWOW64\explorer.exe IS MISSING <==== ATTENTION!.
C:\Windows\System32\svchost.exe IS MISSING <==== ATTENTION!.
C:\Windows\SysWOW64\svchost.exe IS MISSING <==== ATTENTION!.
C:\Windows\System32\services.exe IS MISSING <==== ATTENTION!.
C:\Windows\System32\User32.dll IS MISSING <==== ATTENTION!.
C:\Windows\SysWOW64\User32.dll IS MISSING <==== ATTENTION!.
C:\Windows\System32\userinit.exe IS MISSING <==== ATTENTION!.
C:\Windows\SysWOW64\userinit.exe IS MISSING <==== ATTENTION!.
C:\Windows\System32\rpcss.dll IS MISSING <==== ATTENTION!.
C:\Windows\System32\Drivers\volsnap.sys IS MISSING <==== ATTENTION!.
C:\Windows\system32\codeintegrity\Bootcat.cache IS MISSING <==== ATTENTION!.
C:\Windows\System32\winsrv.dll IS MISSING <==== ATTENTION!.
 
==================== Restore Points  =========================
 
 
==================== BCD ================================
The boot configuration data store could not be opened.
The requested system device cannot be found.
 
 
==================== Memory info =========================== 
 
Percentage of memory in use: 10%
Total physical RAM: 6135.12 MB
Available physical RAM: 5517.11 MB
Total Pagefile: 6133.27 MB
Available Pagefile: 5500.84 MB
Total Virtual: 8192 MB
Available Virtual: 8191.9 MB
 
==================== Drives ================================
 
Drive d: (BACKUP ) (Fixed) (Total:931.51 GB) (Free:325.43 GB) NTFS
Drive g: () (Removable) (Total:15.01 GB) (Free:15.01 GB) FAT32
Drive x: (Boot) (Fixed) (Total:0.03 GB) (Free:0.03 GB) NTFS
 
==================== MBR & Partition Table ==================
 
========================================================
Disk: 1 (MBR Code: Windows 7 or 8) (Size: 931.5 GB) (Disk ID: A5A25410)
Partition 1: (Not Active) - (Size=931.5 GB) - (Type=07 NTFS)
 
========================================================
Disk: 2 (MBR Code: Windows XP) (Size: 15 GB) (Disk ID: C3072E18)
Partition 1: (Not Active) - (Size=15 GB) - (Type=0C)
 
==================== End Of Log ============================

  • 0

Advertisements


#2
Ztruker

Ztruker

    Member 5k

  • Technician
  • 7,087 posts
If the system won't boot, how are you running FRST?
  • 0

#3
skoolpsyk

skoolpsyk

    New Member

  • Topic Starter
  • Member
  • Pip
  • 6 posts

using the repair disc I use the command prompt to execute it off a flash drive...


  • 0

#4
Ztruker

Ztruker

    Member 5k

  • Technician
  • 7,087 posts
Are there any parameters needed for it to run this way?
Reason I ask is the FRST seems to not be able to find the registry hive so the out put to me is highly suspect.
  • 0

#5
Naathim

Naathim

    GeekU Minion

  • Expert
  • 4,568 posts
Hi.
 
Your system is heavily damaged and I don't know if it will be possible to bring it back without reformat/reinstall.

Reboot your machine, enter the Recovery Environment and access the Command Prompt again.

Instead of running FRST, type in the following command:
chkdsk c: /r
and press Enter.
(If your system drive wasn't C: but another one, adjust that in the command)

Upon completion please try to generate another one FRST report.
  • 0

#6
skoolpsyk

skoolpsyk

    New Member

  • Topic Starter
  • Member
  • Pip
  • 6 posts

chkdsk wouldn't run for the longest time then all of a sudden it did; but then finally it did!  but then it would not run sfc /scannow because it said a repair was pending a reboot but of course it won't reboot...

I ran listparts64 after chkdsk /r and the results are below.  I think I'm screwed, but if I pulled the drive and put it in a docking station connected to a laptop would I at least be able to get my files (I have most of them backed up, but haven't backed up in a while...)?    

 

ListParts by Farbar Version: 31-07-2014
Ran by SYSTEM (administrator) on 17-09-2014 at 22:06:11
Windows 7 (X64)
Running From: G:\
Language: English (United States)
************************************************************
 
========================= Memory info ====================== 
 
Percentage of memory in use: 10%
Total physical RAM: 6135.12 MB
Available physical RAM: 5512.44 MB
Total Pagefile: 6133.27 MB
Available Pagefile: 5491.08 MB
Total Virtual: 8192 MB
Available Virtual: 8191.92 MB
 
======================= Partitions =========================
 
1 Drive c: (System Reserved) (Fixed) (Total:0.1 GB) (Free:0.07 GB) NTFS ==>[Drive with boot components (obtained from BCD)]
2 Drive d: (BACKUP ) (Fixed) (Total:931.51 GB) (Free:325.43 GB) NTFS
4 Drive f: (Repair disc Windows 7 64-bit) (CDROM) (Total:0.16 GB) (Free:0 GB) UDF
5 Drive g: () (Removable) (Total:15.01 GB) (Free:15 GB) FAT32
6 Drive x: (Boot) (Fixed) (Total:0.03 GB) (Free:0.03 GB) NTFS
 
  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online         1397 GB      0 B         
  Disk 1    Online          931 GB      0 B         
  Disk 2    Online           15 GB      0 B         
 
Partitions of Disk 0:
===============
 
Disk ID: A5A25414
 
  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Primary            100 MB  1024 KB
  Partition 2    Primary           1397 GB   101 MB
 
======================================================================================================
 
Disk: 0
Partition 1
Type  : 07
Hidden: No
Active: Yes
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 1     C   System Rese  NTFS   Partition    100 MB  Healthy            
 
======================================================================================================
 
Disk: 0
Partition 2
Type  : 07
Hidden: No
Active: No
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 2     E                RAW    Partition   1397 GB  Healthy            
 
======================================================================================================
 
Partitions of Disk 1:
===============
 
Disk ID: A5A25410
 
  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Primary            931 GB  1024 KB
 
======================================================================================================
 
Disk: 1
Partition 1
Type  : 07
Hidden: No
Active: No
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 3     D   BACKUP       NTFS   Partition    931 GB  Healthy            
 
======================================================================================================
 
Partitions of Disk 2:
===============
 
Disk ID: C3072E18
 
  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Primary             15 GB    56 KB
 
======================================================================================================
 
Disk: 2
Partition 1
Type  : 0C
Hidden: No
Active: No
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 4     G                FAT32  Removable     15 GB  Healthy            
 
======================================================================================================
============================== MBR Partition Table ==================
 
==============================
Partitions of Disk 0:
===============
Disk ID: A5A25414
Partition 1: (Active) - (Size=100 MB) - (Type=07 NTFS)
Partition 2: (Not Active) - (Size=1397 GB) - (Type=07 NTFS)
 
==============================
Partitions of Disk 1:
===============
Disk ID: A5A25410
Partition 1: (Not Active) - (Size=932 GB) - (Type=07 NTFS)
 
==============================
Partitions of Disk 2:
===============
Disk ID: C3072E18
Partition 1: (Not Active) - (Size=15 GB) - (Type=0C)
 
 
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=C:
path                    \bootmgr
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {default}
resumeobject            {ebbe1cfc-f9c0-11de-80df-8f5407fc8639}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30
 
Windows Boot Loader
-------------------
identifier              {default}
device                  partition=E:
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {ebbe1cfe-f9c0-11de-80df-8f5407fc8639}
recoveryenabled         Yes
osdevice                partition=E:
systemroot              \Windows
resumeobject            {ebbe1cfc-f9c0-11de-80df-8f5407fc8639}
nx                      OptIn
 
Windows Boot Loader
-------------------
identifier              {ebbe1cfe-f9c0-11de-80df-8f5407fc8639}
device                  ramdisk=[E:]\Recovery\ebbe1cfe-f9c0-11de-80df-8f5407fc8639\Winre.wim,{ebbe1cff-f9c0-11de-80df-8f5407fc8639}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[E:]\Recovery\ebbe1cfe-f9c0-11de-80df-8f5407fc8639\Winre.wim,{ebbe1cff-f9c0-11de-80df-8f5407fc8639}
systemroot              \windows
nx                      OptIn
winpe                   Yes
 
Resume from Hibernate
---------------------
identifier              {ebbe1cfc-f9c0-11de-80df-8f5407fc8639}
device                  partition=E:
path                    \Windows\system32\winresume.exe
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
filedevice              partition=E:
filepath                \hiberfil.sys
debugoptionenabled      No
 
Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=C:
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}
badmemoryaccess         Yes
 
EMS Settings
------------
identifier              {emssettings}
bootems                 Yes
 
Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200
 
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              {ebbe1cff-f9c0-11de-80df-8f5407fc8639}
description             Ramdisk Options
ramdisksdidevice        partition=E:
ramdisksdipath          \Recovery\ebbe1cfe-f9c0-11de-80df-8f5407fc8639\boot.sdi
 
 
****** End Of Log ****** 

  • 0

#7
Naathim

Naathim

    GeekU Minion

  • Expert
  • 4,568 posts
Hi.

Please post me a fresh FRST report instead of ListParts.

Did you ran sfc /scannow on your own? If so, please refrain from self-fixes while I am leading you.
  • 0

#8
skoolpsyk

skoolpsyk

    New Member

  • Topic Starter
  • Member
  • Pip
  • 6 posts

I wasn't able to run frst64 again because it was getting hung up on listing partitions...but I kept trying and it just worked now for some reason!

 

 

Scan result of Farbar Recovery Scan Tool (FRST.txt) (x64) Version: 12-09-2014
Ran by SYSTEM on MININT-4I82F5I on 18-09-2014 07:44:20
Running from e:\
Platform: WIN_7 (X64) OS Language: English (United States)
Boot Mode: Recovery
Attention: Could not load system hive.
Attention: System hive is missing.
 
Tutorial for Farbar Recovery Scan Tool: http://www.geekstogo...very-scan-tool/
 
==================== Registry (Whitelisted) ==================
 
(If an entry is included in the fixlist, the registry item will be restored to default or removed. The file will not be moved.)
 
ATTENTION: Software hive is missing.
 
==================== Services (Whitelisted) =================
 
(If an entry is included in the fixlist, the service will be removed from the registry. The file will not be moved unless listed separately.)
 
 
==================== Drivers (Whitelisted) ====================
 
(If an entry is included in the fixlist, the service will be removed from the registry. The file will not be moved unless listed separately.)
 
 
========================== Drivers MD5 =======================
 
 
==================== NetSvcs (Whitelisted) ===================
 
(If an item is included in the fixlist, it will be removed from the registry. Any associated file could be listed separately to be moved.)
 
 
==================== One Month Created Files and Folders ========
 
(If an entry is included in the fixlist, the file\folder will be moved.)
 
 
==================== One Month Modified Files and Folders =======
 
(If an entry is included in the fixlist, the file\folder will be moved.)
 
 
==================== Known DLLs (Whitelisted) ================
 
 
==================== Bamital & volsnap Check =================
 
(There is no automatic fix for files that do not pass verification.)
 
C:\Windows\System32\winlogon.exe IS MISSING <==== ATTENTION!.
C:\Windows\System32\wininit.exe IS MISSING <==== ATTENTION!.
C:\Windows\SysWOW64\wininit.exe IS MISSING <==== ATTENTION!.
C:\Windows\explorer.exe IS MISSING <==== ATTENTION!.
C:\Windows\SysWOW64\explorer.exe IS MISSING <==== ATTENTION!.
C:\Windows\System32\svchost.exe IS MISSING <==== ATTENTION!.
C:\Windows\SysWOW64\svchost.exe IS MISSING <==== ATTENTION!.
C:\Windows\System32\services.exe IS MISSING <==== ATTENTION!.
C:\Windows\System32\User32.dll IS MISSING <==== ATTENTION!.
C:\Windows\SysWOW64\User32.dll IS MISSING <==== ATTENTION!.
C:\Windows\System32\userinit.exe IS MISSING <==== ATTENTION!.
C:\Windows\SysWOW64\userinit.exe IS MISSING <==== ATTENTION!.
C:\Windows\System32\rpcss.dll IS MISSING <==== ATTENTION!.
C:\Windows\System32\Drivers\volsnap.sys IS MISSING <==== ATTENTION!.
C:\Windows\system32\codeintegrity\Bootcat.cache IS MISSING <==== ATTENTION!.
C:\Windows\System32\winsrv.dll IS MISSING <==== ATTENTION!.
 
==================== Restore Points  =========================
 
 
==================== BCD ================================
 
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=Y:
path                    \bootmgr
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {default}
resumeobject            {ebbe1cfc-f9c0-11de-80df-8f5407fc8639}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30
 
Windows Boot Loader
-------------------
identifier              {default}
device                  partition=F:
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {ebbe1cfe-f9c0-11de-80df-8f5407fc8639}
recoveryenabled         Yes
osdevice                partition=F:
systemroot              \Windows
resumeobject            {ebbe1cfc-f9c0-11de-80df-8f5407fc8639}
nx                      OptIn
 
Windows Boot Loader
-------------------
identifier              {ebbe1cfe-f9c0-11de-80df-8f5407fc8639}
device                  ramdisk=[F:]\Recovery\ebbe1cfe-f9c0-11de-80df-8f5407fc8639\Winre.wim,{ebbe1cff-f9c0-11de-80df-8f5407fc8639}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[F:]\Recovery\ebbe1cfe-f9c0-11de-80df-8f5407fc8639\Winre.wim,{ebbe1cff-f9c0-11de-80df-8f5407fc8639}
systemroot              \windows
nx                      OptIn
winpe                   Yes
 
Resume from Hibernate
---------------------
identifier              {ebbe1cfc-f9c0-11de-80df-8f5407fc8639}
device                  partition=F:
path                    \Windows\system32\winresume.exe
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
filedevice              partition=F:
filepath                \hiberfil.sys
debugoptionenabled      No
 
Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=Y:
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}
badmemoryaccess         Yes
 
EMS Settings
------------
identifier              {emssettings}
bootems                 Yes
 
Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200
 
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              {ebbe1cff-f9c0-11de-80df-8f5407fc8639}
description             Ramdisk Options
ramdisksdidevice        partition=F:
ramdisksdipath          \Recovery\ebbe1cfe-f9c0-11de-80df-8f5407fc8639\boot.sdi
 
 
==================== Memory info =========================== 
 
Percentage of memory in use: 10%
Total physical RAM: 6135.12 MB
Available physical RAM: 5494.89 MB
Total Pagefile: 6133.27 MB
Available Pagefile: 5485.38 MB
Total Virtual: 8192 MB
Available Virtual: 8191.9 MB
 
==================== Drives ================================
 
Drive d: (BACKUP ) (Fixed) (Total:931.51 GB) (Free:325.43 GB) NTFS
Drive e: () (Removable) (Total:15.01 GB) (Free:15 GB) FAT32
Drive g: (Repair disc Windows 7 64-bit) (CDROM) (Total:0.16 GB) (Free:0 GB) UDF
Drive x: (Boot) (Fixed) (Total:0.03 GB) (Free:0.03 GB) NTFS
Drive y: (System Reserved) (Fixed) (Total:0.1 GB) (Free:0.07 GB) NTFS ==>[System with boot components (obtained from reading drive)]
 
==================== MBR & Partition Table ==================
 
========================================================
Disk: 0 (MBR Code: Windows 7 or 8) (Size: 1397.3 GB) (Disk ID: A5A25414)
Partition 1: (Active) - (Size=100 MB) - (Type=07 NTFS)
Partition 2: (Not Active) - (Size=1397.2 GB) - (Type=07 NTFS)
 
========================================================
Disk: 1 (MBR Code: Windows 7 or 8) (Size: 931.5 GB) (Disk ID: A5A25410)
Partition 1: (Not Active) - (Size=931.5 GB) - (Type=07 NTFS)
 
========================================================
Disk: 2 (MBR Code: Windows XP) (Size: 15 GB) (Disk ID: C3072E18)
Partition 1: (Not Active) - (Size=15 GB) - (Type=0C)
 
==================== End Of Log ============================

  • 0

#9
Naathim

Naathim

    GeekU Minion

  • Expert
  • 4,568 posts
Ok, let's give this one a whirl.

Reboot your machine, enter the Recovery Environment and access the Command Prompt again.

Instead of running FRST, type in the following command:
chkdsk c: /x
and press Enter.
(If your system drive wasn't C: but another one, adjust that in the command)

Upon completion please try to generate another one FRST report.
  • 0

#10
Naathim

Naathim

    GeekU Minion

  • Expert
  • 4,568 posts
Just FYI:

Your thread has been moved to another section of the forum. We don't want to have threads with malware-related tools (FRST is one of them) in open forums, where anyone can post a reply.
  • 0

#11
skoolpsyk

skoolpsyk

    New Member

  • Topic Starter
  • Member
  • Pip
  • 6 posts

Ok, let's give this one a whirl.

Reboot your machine, enter the Recovery Environment and access the Command Prompt again.

Instead of running FRST, type in the following command:

chkdsk c: /x
and press Enter.
(If your system drive wasn't C: but another one, adjust that in the command)

Upon completion please try to generate another one FRST report.

 

 

tried chkdsk c: /x    it just says:

 

Cannot open volume for direct access


  • 0

#12
Naathim

Naathim

    GeekU Minion

  • Expert
  • 4,568 posts

Bad news I am afraid. FRST gets stuck because the OS partition has become RAW. It's the file system that Windows cannot recognize - that is why we are not able to do anything, we can't even access that partition. Seems like the malfunction destroyed the partition...


  • 0

#13
Naathim

Naathim

    GeekU Minion

  • Expert
  • 4,568 posts

Receiving help here:

http://www.smartestc...se/#entry270209

 

Topic closed.


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP