Author Topic: Boot problems after power supply failure  (Read 12265 times)

0 Members and 1 Guest are viewing this topic.

REDACTED

  • Guest
Re: Boot problems after power supply failure
« Reply #15 on: September 03, 2014, 05:03:53 PM »
Second part (due to message size limit):

Code: [Select]
==================== One Month Modified Files and Folders =======

(If an entry is included in the fixlist, the file\folder will be moved.)

2014-09-03 16:29 - 2014-09-03 16:29 - 00000000 ____D () C:\FRST
2014-08-28 20:49 - 2014-08-19 15:17 - 00000000 ____D () C:\Program Files (x86)\HEMA Fotoservice
2014-08-28 20:49 - 2013-11-13 18:41 - 00000000 ____D () C:\Users\Patrick\AppData\Roaming\IrfanView
2014-08-28 20:49 - 2013-11-13 18:32 - 00000000 ____D () C:\Windows\System32\Macromed
2014-08-28 20:49 - 2013-11-13 18:30 - 00000000 ____D () C:\Users\Patrick\AppData\Local\Adobe
2014-08-28 20:49 - 2013-11-11 19:16 - 00000000 ____D () C:\ProgramData\NVIDIA
2014-08-28 20:49 - 2013-11-11 18:22 - 00000000 ____D () C:\users\Patrick
2014-08-28 20:49 - 2009-07-14 04:20 - 00000000 ____D () C:\Windows\registration
2014-08-28 20:49 - 2009-07-14 04:20 - 00000000 ____D () C:\Windows\AppCompat
2014-08-28 18:42 - 2014-08-28 18:42 - 00000000 ____D () C:\Windows\System32\config\tijdelijkRB
2014-08-28 17:01 - 2014-08-28 17:00 - 00000000 ____D () C:\Windows\System32\config\mybackup
2014-08-27 16:30 - 2013-12-27 16:04 - 00000000 ____D () C:\Users\Patrick\Documents\Outlook-bestanden
2014-08-27 08:16 - 2013-11-11 18:19 - 01994445 _____ () C:\Windows\WindowsUpdate.log
2014-08-27 08:12 - 2013-11-13 17:29 - 00001054 _____ () C:\Windows\Tasks\GoogleUpdateTaskMachineCore.job
2014-08-27 08:12 - 2009-07-14 06:08 - 00000006 ____H () C:\Windows\Tasks\SA.DAT
2014-08-27 08:12 - 2009-07-14 05:51 - 00178505 _____ () C:\Windows\setupact.log
2014-08-26 22:09 - 2013-11-13 17:29 - 00001058 _____ () C:\Windows\Tasks\GoogleUpdateTaskMachineUA.job
2014-08-26 21:28 - 2013-12-28 21:05 - 00000000 ____D () C:\Users\Patrick\AppData\Roaming\ObviousIdea
2014-08-26 20:32 - 2014-04-18 14:29 - 00000000 ____D () C:\Users\Patrick\AppData\Roaming\FileZilla
2014-08-26 08:38 - 2009-07-14 05:45 - 00022064 ____H () C:\Windows\System32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0
2014-08-26 08:38 - 2009-07-14 05:45 - 00022064 ____H () C:\Windows\System32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0
2014-08-26 08:37 - 2011-04-12 14:00 - 00764394 _____ () C:\Windows\System32\perfh013.dat
2014-08-26 08:37 - 2011-04-12 14:00 - 00160042 _____ () C:\Windows\System32\perfc013.dat
2014-08-26 08:37 - 2009-07-14 06:13 - 01710684 _____ () C:\Windows\System32\PerfStringBackup.INI
2014-08-26 08:31 - 2009-07-14 05:45 - 08238520 _____ () C:\Windows\System32\FNTCACHE.DAT
2014-08-20 10:46 - 2013-11-13 18:32 - 00699568 _____ (Adobe Systems Incorporated) C:\Windows\SysWOW64\FlashPlayerApp.exe
2014-08-20 10:46 - 2013-11-13 18:32 - 00071344 _____ (Adobe Systems Incorporated) C:\Windows\SysWOW64\FlashPlayerCPLApp.cpl
2014-08-19 16:21 - 2014-08-19 16:18 - 00000000 ____D () C:\Users\Patrick\Documents\Peter Kuiper
2014-08-19 15:17 - 2014-08-19 15:17 - 00001051 _____ () C:\Users\Public\Desktop\HEMA Fotoservice.lnk
2014-08-19 15:17 - 2014-08-19 15:17 - 00000000 ____D () C:\Users\Patrick\AppData\Local\HEMA Fotoservice
2014-08-19 15:17 - 2014-08-19 15:17 - 00000000 ____D () C:\ProgramData\HEMA Fotoservice
2014-08-19 15:12 - 2014-08-19 15:11 - 157652984 _____ ( ) C:\Users\Patrick\Downloads\HEMA_NL_Fotoservice.exe
2014-08-19 13:33 - 2014-08-19 13:33 - 06052529 _____ (Tim Kosse) C:\Users\Patrick\Downloads\FileZilla_3.9.0.3_win32-setup.exe
2014-08-15 16:56 - 2009-07-14 04:20 - 00000000 ____D () C:\Windows\rescache
2014-08-15 09:15 - 2009-07-14 04:20 - 00000000 ____D () C:\Windows\PolicyDefinitions
2014-08-15 09:12 - 2013-11-13 16:46 - 99218768 _____ (Microsoft Corporation) C:\Windows\System32\MRT.exe
2014-08-15 09:12 - 2013-11-13 16:46 - 00000000 ____D () C:\Windows\System32\MRT
2014-08-14 09:10 - 2013-11-13 17:29 - 00002203 _____ () C:\Users\Public\Desktop\Google Chrome.lnk
2014-08-13 22:26 - 2014-08-13 22:26 - 138174757 _____ () C:\Users\Patrick\Downloads\blijham deel 1 (Low).mp4
2014-08-13 17:04 - 2013-11-11 20:35 - 00004182 _____ () C:\Windows\System32\Tasks\avast! Emergency Update
2014-08-09 17:22 - 2010-11-21 04:47 - 00199724 _____ () C:\Windows\PFRO.log
2014-08-09 10:23 - 2013-11-13 20:29 - 00000000 ____D () C:\Program Files\Microsoft Office 15
2014-08-08 10:17 - 2014-01-17 22:06 - 00000000 ____D () C:\ProgramData\Oracle
2014-08-08 10:16 - 2014-08-08 10:17 - 00272808 _____ (Oracle Corporation) C:\Windows\SysWOW64\javaws.exe
2014-08-08 10:16 - 2014-08-08 10:17 - 00175528 _____ (Oracle Corporation) C:\Windows\SysWOW64\javaw.exe
2014-08-08 10:16 - 2014-08-08 10:17 - 00175528 _____ (Oracle Corporation) C:\Windows\SysWOW64\java.exe
2014-08-08 10:16 - 2014-08-08 10:17 - 00098216 _____ (Oracle Corporation) C:\Windows\SysWOW64\WindowsAccessBridge-32.dll
2014-08-06 19:07 - 2014-08-06 19:07 - 00000000 ____D () C:\Users\Patrick\Documents\Tosca
2014-08-06 14:10 - 2014-08-06 14:06 - 00000000 ____D () C:\Users\Patrick\Documents\Gerwin Wilkens
2014-08-05 08:20 - 2010-11-21 04:27 - 00270496 _____ (Microsoft Corporation) C:\Windows\System32\MpSigStub.exe
2014-08-04 23:14 - 2014-08-04 23:14 - 25931642 _____ () C:\Users\Patrick\Downloads\Autocross Ten Boer 1997 (Low).mp4
2014-08-04 17:54 - 2014-08-04 17:54 - 06004615 _____ (Tim Kosse) C:\Users\Patrick\Downloads\FileZilla_3.9.0.2_win32-setup.exe

Some content of TEMP:
====================
C:\Users\Patrick\AppData\Local\Temp\Creative Cloud Helper.exe
C:\Users\Patrick\AppData\Local\Temp\CreativeCloudSet-Up.exe
C:\Users\Patrick\AppData\Local\Temp\jre-7u51-windows-i586-iftw.exe
C:\Users\Patrick\AppData\Local\Temp\jre-7u55-windows-i586-iftw.exe
C:\Users\Patrick\AppData\Local\Temp\jre-7u65-windows-i586-iftw.exe
C:\Users\Patrick\AppData\Local\Temp\jre-7u67-windows-i586-iftw.exe
C:\Users\Patrick\AppData\Local\Temp\LMkRstPt.exe
C:\Users\Patrick\AppData\Local\Temp\nv3DVStreaming.dll
C:\Users\Patrick\AppData\Local\Temp\nvSCPAPI.dll
C:\Users\Patrick\AppData\Local\Temp\nvSCPAPI64.dll
C:\Users\Patrick\AppData\Local\Temp\nvStereoApiI.dll
C:\Users\Patrick\AppData\Local\Temp\nvStInst.exe
C:\Users\Patrick\AppData\Local\Temp\OfficeSetup.exe
C:\Users\Patrick\AppData\Local\Temp\_isE7DE.exe


==================== Known DLLs (Whitelisted) ================


==================== Bamital & volsnap Check =================

(There is no automatic fix for files that do not pass verification.)

C:\Windows\System32\winlogon.exe => MD5 is legit
C:\Windows\System32\wininit.exe => MD5 is legit
C:\Windows\SysWOW64\wininit.exe => MD5 is legit
C:\Windows\explorer.exe => MD5 is legit
C:\Windows\SysWOW64\explorer.exe => MD5 is legit
C:\Windows\System32\svchost.exe => MD5 is legit
C:\Windows\SysWOW64\svchost.exe => MD5 is legit
C:\Windows\System32\services.exe => MD5 is legit
C:\Windows\System32\User32.dll => MD5 is legit
C:\Windows\SysWOW64\User32.dll => MD5 is legit
C:\Windows\System32\userinit.exe => MD5 is legit
C:\Windows\SysWOW64\userinit.exe => MD5 is legit
C:\Windows\System32\rpcss.dll => MD5 is legit
C:\Windows\System32\Drivers\volsnap.sys => MD5 is legit

==================== Restore Points  =========================

Restore point made on: 2014-08-03 09:19:42
Restore point made on: 2014-08-05 09:22:34
Restore point made on: 2014-08-08 10:14:53
Restore point made on: 2014-08-08 10:16:46
Restore point made on: 2014-08-13 09:22:12
Restore point made on: 2014-08-15 09:10:56
Restore point made on: 2014-08-19 12:06:11
Restore point made on: 2014-08-27 08:16:02

==================== Memory info ===========================

Percentage of memory in use: 7%
Total physical RAM: 16271.96 MB
Available physical RAM: 15069.29 MB
Total Pagefile: 16270.16 MB
Available Pagefile: 15066.95 MB
Total Virtual: 8192 MB
Available Virtual: 8191.9 MB

==================== Drives ================================

Drive c: () (Fixed) (Total:232.79 GB) (Free:88.55 GB) NTFS
Drive e: (GSP1RMCHPXFREO_NL_DVD) (CDROM) (Total:2.97 GB) (Free:0 GB) UDF
Drive f: (MEMORYSTICK) (Removable) (Total:0.48 GB) (Free:0.48 GB) FAT32
Drive x: (Boot) (Fixed) (Total:0.03 GB) (Free:0.03 GB) NTFS
Drive y: (Door systeem gereserveerd) (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: 232.9 GB) (Disk ID: E77FCD23)
Partition 1: (Active) - (Size=100 MB) - (Type=07 NTFS)
Partition 2: (Not Active) - (Size=232.8 GB) - (Type=07 NTFS)

========================================================
Disk: 1 (Size: 500 MB) (Disk ID: 91F72D24)
Partition 1: (Active) - (Size=500 MB) - (Type=0B)


LastRegBack: 2014-08-27 08:36

==================== End Of Log ============================

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40589
  • Dragons by Sasha
    • Malware fixes
Re: Boot problems after power supply failure
« Reply #16 on: September 03, 2014, 06:16:14 PM »
You can attach the logs that makes it easier

Nothing apparent showing at this stage so we will try this first :

Download the attached fixlist.txt to the same location as FRST
Run FRST as before
Then try a normal boot
If that fails then run start up repair three times rebooting after each


REDACTED

  • Guest
Re: Boot problems after power supply failure
« Reply #17 on: September 03, 2014, 07:08:12 PM »
It succesfully restored the RegBack hives. First boot BSOD with the same error as usual.
1st startup repair: was scanning for problems for a few minutes, but computer could not be repaired, error: StartupRepairOffline
2nd startup repair: scanning was done in a few seconds, computer could not be repaired
3rd startup repair: also done within a few seconds, computer could not be repaired

I looked into the activity logs and noticed the last item (translated):
Recovery Operation: Control and restore integrity of system files
Result: Failed. Error code = 0x490
Duration: 178824ms

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40589
  • Dragons by Sasha
    • Malware fixes
Re: Boot problems after power supply failure
« Reply #18 on: September 03, 2014, 07:46:21 PM »
Can you go into the BIOS and let me know whether it is set to SATA, AHCI  or IDE for the hard drive

REDACTED

  • Guest
Re: Boot problems after power supply failure
« Reply #19 on: September 03, 2014, 07:59:34 PM »
Perhaps a video explanation along the lines of Essexboy thinking............
https://www.youtube.com/watch?v=ObRLHDy3JIk

Essexboy, depending on OPs answer blow away Avast install via Farbar and boot into Safe Mode and change the IDE in Device Manager ?
{Learning mode question from me and just brain storming}
« Last Edit: September 03, 2014, 08:03:05 PM by thekochs »

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40589
  • Dragons by Sasha
    • Malware fixes
Re: Boot problems after power supply failure
« Reply #20 on: September 03, 2014, 08:19:46 PM »
No I do not believe it is Avast.  This is a common windows problem although it normally stops on the classpnp if Avast is not installed 

REDACTED

  • Guest
Re: Boot problems after power supply failure
« Reply #21 on: September 03, 2014, 08:46:25 PM »
I cannot do the fix from the video, because I can't boot into safe mode.

SATA mode is set to AHCI. Other options: IDE or RAID

I also want to mention that the pc had four 2TB drives in RAID 10 at the moment of the crash. These drives are currently in an other pc for file recovery. The only drive left is an Samsung 840 EVO 250GB drive with Windows and programs on it.

I have also tried something to "reset" the drivers.  I used this guide: http://www.askvg.com/how-to-change-sata-hard-disk-mode-from-ide-to-ahci-raid-in-bios-after-installing-windows/
« Last Edit: September 03, 2014, 08:55:15 PM by robin12 »

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40589
  • Dragons by Sasha
    • Malware fixes
Re: Boot problems after power supply failure
« Reply #22 on: September 03, 2014, 09:19:11 PM »
Could you now set in the BIOS IDE mode as opposed to AHCI save the changes and reboot

REDACTED

  • Guest
Re: Boot problems after power supply failure
« Reply #23 on: September 03, 2014, 09:37:43 PM »
Set to IDE mode, but still 0x0000007B.

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40589
  • Dragons by Sasha
    • Malware fixes
Re: Boot problems after power supply failure
« Reply #24 on: September 03, 2014, 10:11:48 PM »
This will disable Avast could you let me know the result please

Download the attached fixlist.txt to the same location as FRST
Run FRST as before
Then try a normal boot

REDACTED

  • Guest
Re: Boot problems after power supply failure
« Reply #25 on: September 03, 2014, 10:16:14 PM »
Do I first have to set it back to AHCI mode?

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40589
  • Dragons by Sasha
    • Malware fixes
Re: Boot problems after power supply failure
« Reply #26 on: September 03, 2014, 10:20:38 PM »
You could try that although I feel it will have no effect

REDACTED

  • Guest
Re: Boot problems after power supply failure
« Reply #27 on: September 03, 2014, 10:49:17 PM »
Fix was successfully executed. But still getting the BSOD on boot...

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40589
  • Dragons by Sasha
    • Malware fixes
Re: Boot problems after power supply failure
« Reply #28 on: September 03, 2014, 11:06:32 PM »
I am afraid it is time for a re-install as there is little else I can do

REDACTED

  • Guest
Re: Boot problems after power supply failure
« Reply #29 on: September 03, 2014, 11:13:57 PM »
I was afraid of that. But thanks anyway for your help!

What would be the best way to recover files/documents from the SSD? Can I just connect it to an other pc and use ReclaiMe for example? Because I'm afraid the "faulty" drive might damage the other pc.