Factory reset or could this be fixed?

Ive bought a new hard drive.. **** this drive seriously.. it cant be any of the problems above, because everything I have used or installed, was fine from the start until the attack of the virus. @Cycloid Torus btw, I tried to use the low level format program from Seagate... my manufacturer.. drive so ****ed up that it couldn't even find the drive to format.
 
T,
Advice doesn't really change...
Initialize / partition.
Confirm disconnected from Internet
Install OS clean and fresh.
Turn OFF updates
Turn on Windows defender and firewall
Now connect to internet
Now request and install Windows updates (1st run) - restart when asked
Now request and install Windows updates (2nd run) - restart when asked
Now request and install Windows updates (3rd run) - restart, should have almost all at this point.
Go to MSI site and download FRESH drivers and install those

If errors along the way. Stop, do not take next step, take notes, share.
 
  • Like
Reactions: bazz2004
Cycloid Torus said:
T,
Advice doesn't really change...
Initialize / partition.
Confirm disconnected from Internet
Install OS clean and fresh.
Turn OFF updates
Turn on Windows defender and firewall
Now connect to internet
Now request and install Windows updates (1st run) - restart when asked
Now request and install Windows updates (2nd run) - restart when asked
Now request and install Windows updates (3rd run) - restart, should have almost all at this point.
Go to MSI site and download FRESH drivers and install those

If errors along the way. Stop, do not take next step, take notes, share.
Click to expand...

Ill perform a normal format from windows installation disk. And follow these advice any problems ill screen shot and send it to you, how do you screen shot when youre in window mode ? Like ss a BSOD for example.
 
Shift-PrintScreen, open PAINT, Control-V, save as gif or png (jpg is too big). BSOD - I use a camera (webcam? / cell phone? / etc).
 
There’s a danger of trying to move too fast. You prepped the old drive properly as Cycloid suggested and the fresh install wasn’t working properly. There is no certainty that a replacement drive will do any better.



Hold back on all the software you are keen to reinstall. Concentrate on installing Windows 7 and only install the bare minimum. Until you have a solid base you are just making more difficulties. Get the computer working properly and accessing the internet then fully update Windows. Forget stuff like virtual drives, Steam and Catalyst Control Centre for the present.



Once W7 is fully updated you could download and use Microsoft’s media creation tool to upgrade to Windows 10 (which is still free). If you prefer to stick with the past you can carefully install the software you need a bit at a time checking thoroughly that everything is still OK. More haste less speed.
 
  • Like
Reactions: Cycloid Torus
Cycloid Torus said:
Shift-PrintScreen, open PAINT, Control-V, save as gif or png (jpg is too big). BSOD - I use a camera (webcam? / cell phone? / etc).
Click to expand...
bazz2004 said:
There’s a danger of trying to move too fast. You prepped the old drive properly as Cycloid suggested and the fresh install wasn’t working properly. There is no certainty that a replacement drive will do any better.



Hold back on all the software you are keen to reinstall. Concentrate on installing Windows 7 and only install the bare minimum. Until you have a solid base you are just making more difficulties. Get the computer working properly and accessing the internet then fully update Windows. Forget stuff like virtual drives, Steam and Catalyst Control Centre for the present.



Once W7 is fully updated you could download and use Microsoft’s media creation tool to upgrade to Windows 10 (which is still free). If you prefer to stick with the past you can carefully install the software you need a bit at a time checking thoroughly that everything is still OK. More haste less speed.
Click to expand...

Yeah I understand its exactly what I did.. Today though, windows found 160+ important updates.... So I installed them, well tried.. It installed half and half of it didnt install I believe, then I restarted my computer windows ... Crash, constant chkdsk and start uo repair... Why so many updates...
 
If you interrupt Windows when it is updating you screw up your OS. You need to sit it out. There will be hundreds of updates and I think there was SP1 too with W7.
 
"Now connect to internet
Now request and install Windows updates (1st run) - restart when asked
Now request and install Windows updates (2nd run) - restart when asked
Now request and install Windows updates (3rd run) - restart, should have almost all at this point.
If errors along the way. Stop, do not take next step, take notes, share."

THREE times 'request and install' because Microsoft is braindead about updates for ended OSs..
The first time you get updated to get updates.
The second time you get the last 'BIG' update.
The third time you get 160 odd updates since there is no 2nd big update.

They want you to upgrade to Win10. Try to get your system running on Windows7. DO NOT restart without being TOLD to do so. Be patient...wait an extra 15 minutes as the update program figures out what it is doing. It takes lunch breaks all the time.

Try to locate the failed updates in update history and try to update them again - otherwise, start from the beginning.

Microsoft only checks for updates ONCE A DAY. So you have to force it by making the request yourself. If some updates are giving you a bad time, 'hide' them until you have a stable system. Then bring them out one or two at a time - and be sure to make RESTORE POINTS for this.

Consider upgrading to Win10 the moment you have a stable Win7.
 
  • Like
Reactions: Tuyen and bazz2004
bazz2004 said:
If you interrupt Windows when it is updating you screw up your OS. You need to sit it out. There will be hundreds of updates and I think there was SP1 too with W7.
Click to expand...
Cycloid Torus said:
"Now connect to internet
Now request and install Windows updates (1st run) - restart when asked
Now request and install Windows updates (2nd run) - restart when asked
Now request and install Windows updates (3rd run) - restart, should have almost all at this point.
If errors along the way. Stop, do not take next step, take notes, share."

THREE times 'request and install' because Microsoft is braindead about updates for ended OSs..
The first time you get updated to get updates.
The second time you get the last 'BIG' update.
The third time you get 160 odd updates since there is no 2nd big update.

They want you to upgrade to Win10. Try to get your system running on Windows7. DO NOT restart without being TOLD to do so. Be patient...wait an extra 15 minutes as the update program figures out what it is doing. It takes lunch breaks all the time.

Try to locate the failed updates in update history and try to update them again - otherwise, start from the beginning.

Microsoft only checks for updates ONCE A DAY. So you have to force it by making the request yourself. If some updates are giving you a bad time, 'hide' them until you have a stable system. Then bring them out one or two at a time - and be sure to make RESTORE POINTS for this.

Consider upgrading to Win10 the moment you have a stable Win7.
Click to expand...


Reinstalling OS again, ill try to upgrade it to win 10 once I have windows configured and service pack 1 configured. I have not interupted any updates, I did everything you said, checked for updates and restarted when asked, but it seems like the windows could not install the updates and cause corruption, then the whole computer just get ****ed again. I dont understand why... Why can they not install the updates ? The first 2 or 3 updates were fine... Till couple of restarts and 4th or 5th time it gets ****ed because there were error installing updates.... Ill try upgrade to win 10
 
If you think W7 takes a long time to reinstall you should try XP which went to SP3 and beyond. Once you get to W7 SP1 there will still be a load more updates. Be warned too that although Windows 10 is the latest OS it has been going for sometime now so you will have loads of updates. I'd try the media creation tool method for the free upgrade to W10 once you have W7 sorted. Cycloids walk through is very helpful.
 
bazz2004 said:
If you think W7 takes a long time to reinstall you should try XP which went to SP3 and beyond. Once you get to W7 SP1 there will still be a load more updates. Be warned too that although Windows 10 is the latest OS it has been going for sometime now so you will have loads of updates. I'd try the media creation tool method for the free upgrade to W10 once you have W7 sorted. Cycloids walk through is very helpful.
Click to expand...

This is ****ing crazy, I have just reinstalled my OS and before it even load into window for the first time, chkdsk already performed and deleting and recovring loads if ****....could it be my installation disk ? Or its hard drive ? It must be either these 2
 
Last edited:
Do you have any specific error messages or codes? What appears in Event Viewer? Can you be more specific about "chkdsk already performed and deleting and recovring loads if ****." - as this is 'venting' and not really useful.

Chkdsk on its own should not harm your files. It merely 'checks the disk' (hence the name) and attempts to recover BAD sectors and clean up BAD file structures. Earlier you said "this time it says it cannot start chkdsk cuz of recent installed software" - but we need SPECIFICS..

Do you have a repair disk? Will it run? What are the results?

We are stumbling in the dark. Many things could cause the BAD files issue. Flaky memory is one of the first to eliminate. Download and burn a bootable ISO on a stable machine, then boot on your problem system and let it run overnight.

Background infio: https://en.wikipedia.org/wiki/Memtest86 Best source: http://www.memtest.org/

If your are inclined to think that what you are using for installation media may have issues, try to locate and borrow alternative - but be sure to use YOUR key, not the lender's.
 
Cycloid Torus said:
Do you have any specific error messages or codes? What appears in Event Viewer? Can you be more specific about "chkdsk already performed and deleting and recovring loads if ****." - as this is 'venting' and not really useful.

Chkdsk on its own should not harm your files. It merely 'checks the disk' (hence the name) and attempts to recover BAD sectors and clean up BAD file structures. Earlier you said "this time it says it cannot start chkdsk cuz of recent installed software" - but we need SPECIFICS..

Do you have a repair disk? Will it run? What are the results?

We are stumbling in the dark. Many things could cause the BAD files issue. Flaky memory is one of the first to eliminate. Download and burn a bootable ISO on a stable machine, then boot on your problem system and let it run overnight.

Background infio: https://en.wikipedia.org/wiki/Memtest86 Best source: http://www.memtest.org/

If your are inclined to think that what you are using for installation media may have issues, try to locate and borrow alternative - but be sure to use YOUR key, not the lender's.
Click to expand...


Currently running memtest, I will do 3 passes or 4 and I have also installed OS in a new hard drive. Hopefully everything will go well.

Chkdsk was literally deleting a variety of file and recovering orphaned files with differnent names and it was running too fast for me to record...
 
There looks to be a problem other than the hard drive. Unstable ram or a failing DVD drive maybe? I'm out of suggestions.
 
bazz2004 said:
There looks to be a problem other than the hard drive. Unstable ram or a failing DVD drive maybe? I'm out of suggestions.
Click to expand...
Concur. Without something more specific to work on - like error codes - it could be many things and I do not like suggesting that Tuyen spend on uncertain 'fixes'. Do you know any way to narrow this down other than Event Viewer errors or mini-dump. I'm hoping that Tuyen booted memtest from its own OS and so we get both memory test, but also an idea if the core hardware (cpu, memory, motherboard) is sound. I hope he is regularly checking Device Manager for any component failures. I would be unhappy to learn this was all the result of a bad NIC or sound chip fighting its driver.
Do you think DxDiag would give us anything?
 
Your expertise is more advanced than mine so I can't say. The one occasion where updates were constantly failing for me was when I bought a second hand desktop with a defective stick of ram. The result was lots of blue screening when I tried to update Windows. I tried repeatedly to reinstall Windows but it wasn't possible. A new installation CD failed too so I took a chance and replaced the single stick of ram which sorted it. It was a lucky guess.
 
Ok, I installed OS into new hard drive. Installed all updates before downloading any thing. Im talking about the Critical Updates, SP1 etc. Then after hours and hours of searching for new updates. Windows found 200+ updates.. so... I installed them all but in order. First I installed all "Security updates of windows" then "Updates for Windows" and then all other updates after. like .NET etc.. once thats done...I let it search for more updates so it found some more security updates... so I tried to install that but it failed ! ? WHY ? then... I restarted computer CHKDSK happens ! omg.. here are the errors in the event logs.

Screenshot_1.png Screenshot_1.png Screenshot_2.png Screenshot_1.png Screenshot_3.png Screenshot_4.png Screenshot_5.png Screenshot_6.png Screenshot_7.png


All the other errors ill copy as text down below:




Code: 
Log Name:      Application
Source:        Application Error
Date:          21/04/2016 04:43:42
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      tuyen-PC
Description:
Faulting application name: Fuel.Service.exe, version: 1.0.0.0, time stamp: 0x52125a25
Faulting module name: ntdll.dll, version: 6.1.7601.19160, time stamp: 0x56bcd74c
Exception code: 0xc0000005
Fault offset: 0x000000000004a604
Faulting process id: 0x5d8
Faulting application start time: 0x01d19b6edfd6a65e
Faulting application path: C:\Program Files\ATI Technologies\ATI.ACE\Fuel\Fuel.Service.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 3dad3d3a-0773-11e6-b5d5-448a5b2e5d33
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-04-21T03:43:42.000000000Z" />
    <EventRecordID>1803</EventRecordID>
    <Channel>Application</Channel>
    <Computer>tuyen-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Fuel.Service.exe</Data>
    <Data>1.0.0.0</Data>
    <Data>52125a25</Data>
    <Data>ntdll.dll</Data>
    <Data>6.1.7601.19160</Data>
    <Data>56bcd74c</Data>
    <Data>c0000005</Data>
    <Data>000000000004a604</Data>
    <Data>5d8</Data>
    <Data>01d19b6edfd6a65e</Data>
    <Data>C:\Program Files\ATI Technologies\ATI.ACE\Fuel\Fuel.Service.exe</Data>
    <Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
    <Data>3dad3d3a-0773-11e6-b5d5-448a5b2e5d33</Data>
  </EventData>
</Event>

---------------------------------------------------------------------------------------------------------------------------


Code: 
Log Name:      Application
Source:        Application Error
Date:          21/04/2016 04:43:13
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      tuyen-PC
Description:
Faulting application name: TrustedInstaller.exe, version: 6.1.7601.17514, time stamp: 0x4ce7989b
Faulting module name: wcp.dll, version: 6.1.7601.17592, time stamp: 0x4da00342
Exception code: 0xc0000005
Fault offset: 0x00000000000a4682
Faulting process id: 0x168
Faulting application start time: 0x01d19b6ed62fd204
Faulting application path: C:\Windows\servicing\TrustedInstaller.exe
Faulting module path: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wcp.dll
Report Id: 2c23d9f9-0773-11e6-b5d5-448a5b2e5d33
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-04-21T03:43:13.000000000Z" />
    <EventRecordID>1802</EventRecordID>
    <Channel>Application</Channel>
    <Computer>tuyen-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>TrustedInstaller.exe</Data>
    <Data>6.1.7601.17514</Data>
    <Data>4ce7989b</Data>
    <Data>wcp.dll</Data>
    <Data>6.1.7601.17592</Data>
    <Data>4da00342</Data>
    <Data>c0000005</Data>
    <Data>00000000000a4682</Data>
    <Data>168</Data>
    <Data>01d19b6ed62fd204</Data>
    <Data>C:\Windows\servicing\TrustedInstaller.exe</Data>
    <Data>C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wcp.dll</Data>
    <Data>2c23d9f9-0773-11e6-b5d5-448a5b2e5d33</Data>
  </EventData>
</Event>

---------------------------------------------------------------------------------------------------------------------------

  • ]Warning 21/04/2016 04:18:37 RestartManager 10010 None
'C:\Users\tuyen\AppData\Roaming\GameRanger\GameRanger\GameRanger.exe' (pid 3932) cannot be restarted - Application SID does not match Conductor SID..

  • Warning 21/04/2016 04:18:37 RestartManager 10010 None
Application 'C:\Program Files (x86)\Avira\Antivirus\avgnt.exe' (pid 4036) cannot be restarted - Application SID does not match Conductor SID..

  • Warning 21/04/2016 04:18:37 RestartManager 10010 None
Application 'C:\Program Files (x86)\Avira\Launcher\Avira.Systray.exe' (pid 3100) cannot be restarted - Application SID does not match Conductor SID..

  • Warning 21/04/2016 04:18:37 RestartManager 10010 None
Application 'C:\Windows\explorer.exe' (pid 3008) cannot be restarted - Application SID does not match Conductor SID..

  • Warning 21/04/2016 04:18:38 RestartManager 10010 None
Application 'C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\MOM.exe' (pid 2736) cannot be restarted - Application SID does not match Conductor SID..

  • Warning 21/04/2016 04:18:38 RestartManager 10010 None
Application 'C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\CCC.exe' (pid 2032) cannot be restarted - Application SID does not match Conductor SID..

  • Warning 21/04/2016 03:59:13 ASP.NET 4.0.30319.0 1020 Setup
Updates to the IIS metabase were aborted because IIS is either not installed or is disabled on this machine. To configure ASP.NET to run in IIS, please install or enable IIS and re-register ASP.NET using aspnet_regiis.exe /I.

  • Warning 21/04/2016 03:58:43 RestartManager 10010 None ( lots of these warnings come every 3-5 mins, different files in this folder not just CCC.exe)
Application 'C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\CCC.exe' (pid 2032) cannot be restarted - Application SID does not match Conductor SID..

  • Warning 21/04/2016 03:58:41 RestartManager 10010 None ( lots of these warnings)
Application 'C:\Program Files (x86)\Avira\Launcher\Avira.Systray.exe' (pid 3100) cannot be restarted - Application SID does not match Conductor SID.

Code: 
Error    20/04/2016 16:58:07    Application Error    1005    (100)
Windows cannot access the file  for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program McAfee Remediation Manager because of this error.

Program: McAfee Remediation Manager
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
    - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
    - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0

is it because of this one that it causes chkdsk ???

  • Error 20/04/2016 16:58:07 Application Error 1000 (100)
Faulting application name: upgrade.exe, version: 8.6.6046.0, time stamp: 0x56392162
Faulting module name: upgrade.exe, version: 8.6.6046.0, time stamp: 0x56392162
Exception code: 0xc000001d
Fault offset: 0x000000000005eda3
Faulting process id: 0xe9c
Faulting application start time: 0x01d19b1d6aa66325
Faulting application path: C:\Program Files\Common Files\AV\McAfee Anti-Virus And Anti-Spyware\upgrade.exe
Faulting module path: C:\Program Files\Common Files\AV\McAfee Anti-Virus And Anti-Spyware\upgrade.exe
Report Id: abf75b35-0710-11e6-950a-448a5b2e5d33

  • Error 20/04/2016 16:52:24 Application Error 1000 (100)
Faulting application name: upgrade.exe, version: 8.6.6046.0, time stamp: 0x56392162
Faulting module name: upgrade.exe, version: 8.6.6046.0, time stamp: 0x56392162
Exception code: 0xc000001d
Fault offset: 0x000000000005eda3
Faulting process id: 0xb4c
Faulting application start time: 0x01d19b1c9f7b3404
Faulting application path: C:\Program Files\Common Files\AV\McAfee Anti-Virus And Anti-Spyware\upgrade.exe
Faulting module path: C:\Program Files\Common Files\AV\McAfee Anti-Virus And Anti-Spyware\upgrade.exe
Report Id: df9f8e8d-070f-11e6-950a-448a5b2e5d33

  • Error 20/04/2016 15:17:40 Application Error 1000 (100)
Faulting application name: InstallManagerApp.exe, version: 0.0.0.0, time stamp: 0x521252d1
Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b
Exception code: 0xc0000006
Fault offset: 0x000000000003548f
Faulting process id: 0x868
Faulting application start time: 0x01d19b0e86303b6c
Faulting application path: D:\ChipSet\W7_W8\Bin64\InstallManagerApp.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: a369bf35-0702-11e6-b112-448a5b2e5d33

Code: 
Error    20/04/2016 15:18:06    Application Error    1005    (100)
Windows cannot access the file D:\ChipSet\W7_W8\Bin64\InstallManagerApp.exe for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program CATALYST™ Install Manager because of this error.

Program: CATALYST™ Install Manager
File: D:\ChipSet\W7_W8\Bin64\InstallManagerApp.exe

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
    - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
    - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: C0000012
Disk type: 5
Screenshot_8.png Screenshot_8.png

I know this is a lot but its all the errors I can give you =S if I get any more of the update error code ill give it you... should I restore my system if a lot of the files are corrupted ? and also I will give you an update once I finish Memtest86
 

Attachments

  • failed.png
    failed.png
    30.8 KB · Views: 1
Last edited:
Oh and also, this is the log for Check disk
Code: 
Checking file system on C:
The type of the file system is NTFS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 3)...
  230144 file records processed.                                          File verification completed.
  2799 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              44 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 3)...
The VCN 0x603 of index $I30 in file 0xe2d is already in use.
The VCN 0x95c of index $I30 in file 0xe2d is already in use.
The VCN 0x604 of index $I30 in file 0xe2d is already in use.
The VCN 0x958 of index $I30 in file 0xe2d is already in use.
The VCN 0x605 of index $I30 in file 0xe2d is already in use.
The VCN 0x606 of index $I30 in file 0xe2d is already in use.
Correcting error in index $I30 for file 3629.
The index bitmap $I30 in file 0xe2d is incorrect.
Correcting error in index $I30 for file 3629.
The two index entries of length 0x110 and 0x108 are either identical
or appear in the wrong order.
62 2e 00 00 00 00 01 00 10 01 fc 00 00 00 00 00  b...............
2d 0e 00 00 00 00 01 00 de 4e 42 19 32 04 ca 01  -........NB.2...
dc f7 3e 21 32 04 ca 01 18 3b 45 e8 55 9b d1 01  ..>!2....;E.U...
dc f7 3e 21 32 04 ca 01 00 00 00 00 00 00 00 00  ..>!2...........
00 00 00 00 00 00 00 00 00 00 00 10 00 00 00 00  ................
5d 01 78 00 38 00 36 00 5f 00 6d 00 69 00 63 00  ].x.8.6._.m.I.c.
72 00 6f 00 73 00 6f 00 66 00 74 00 2d 00 77 00  r.o.s.o.f.t.-.w.
69 00 6e 00 64 00 6f 00 77 00 73 00 2d 00 69 00  I.n.d.o.w.s.-.I.
6d 00 65 00 2d 00 6b 00 6f 00 72 00 65 00 61 00  m.e.-.k.o.r.e.a.
6e 00 2d 00 63 00 61 00 63 00 70 00 61 00 64 00  n.-.c.a.c.p.a.d.
5f 00 33 00 31 00 62 00 66 00 33 00 38 00 35 00  _.3.1.b.f.3.8.5.
36 00 61 00 64 00 33 00 36 00 34 00 65 00 33 00  6.a.d.3.6.4.e.3.
35 00 5f 00 36 00 2e 00 31 00 2e 00 37 00 36 00  5._.6...1...7.6.
30 00 30 00 2e 00 31 00 36 00 33 00 38 00 35 00  0.0...1.6.3.8.5.
5f 00 6e 00 6f 00 6e 00 65 00 5f 00 37 00 30 00  _.n.o.n.e._.7.0.
35 00 37 00 66 00 62 00 35 00 66 00 65 00 33 00  5.7.f.b.5.f.e.3.
63 00 30 00 65 00 64 00 32 00 61 00 00 00 00 00  c.0.e.d.2.a.....
----------------------------------------------------------------------
40 2e 00 00 00 00 01 00 08 01 ee 00 01 00 00 00  @...............
2d 0e 00 00 00 00 01 00 67 6c 99 32 44 04 ca 01  -.......gl.2D...
67 6c 99 32 44 04 ca 01 18 3b 45 e8 55 9b d1 01  gl.2D....;E.U...
67 6c 99 32 44 04 ca 01 00 00 00 00 00 00 00 00  gl.2D...........
00 00 00 00 00 00 00 00 00 00 00 10 00 00 00 00  ................
56 01 78 00 38 00 36 00 5f 00 6d 00 69 00 63 00  V.x.8.6._.m.I.c.
72 00 6f 00 73 00 6f 00 66 00 74 00 2d 00 77 00  r.o.s.o.f.t.-.w.
69 00 6e 00 64 00 6f 00 77 00 73 00 2d 00 69 00  I.n.d.o.w.s.-.I.
65 00 2d 00 69 00 65 00 73 00 68 00 69 00 6d 00  e.-.I.e.s.h.I.m.
73 00 5f 00 33 00 31 00 62 00 66 00 33 00 38 00  s._.3.1.b.f.3.8.
35 00 36 00 61 00 64 00 33 00 36 00 34 00 65 00  5.6.a.d.3.6.4.e.
33 00 35 00 5f 00 38 00 2e 00 30 00 2e 00 37 00  3.5._.8...0...7.
36 00 30 00 30 00 2e 00 31 00 36 00 33 00 38 00  6.0.0...1.6.3.8.
35 00 5f 00 6e 00 6f 00 6e 00 65 00 5f 00 36 00  5._.n.o.n.e._.6.
32 00 31 00 64 00 63 00 64 00 35 00 30 00 37 00  2.1.d.c.d.5.0.7.
32 00 38 00 65 00 39 00 30 00 63 00 31 00 00 00  2.8.e.9.0.c.1...
08 06 00 00 00 00 00 00 63 2e 00 00 00 00 01 00  ........c.......
Sorting index $I30 in file 3629.
The index bitmap $I30 in file 0x268f is incorrect.
Correcting error in index $I30 for file 9871.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xfd37 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
The multi-sector header signature for VCN 0x1 of index $I30
in file 0xfd37 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Correcting error in index $I30 for file 64823.
The index bitmap $I30 in file 0xfd37 is incorrect.
Correcting error in index $I30 for file 64823.
The down pointer of current index entry with length 0xa0 is invalid.
5a e0 02 00 00 00 02 00 a0 00 84 00 01 00 00 00  Z...............
37 fd 00 00 00 00 0a 00 25 27 f7 46 4b 9b d1 01  7.......%'.FK...
20 36 00 b3 14 97 d0 01 19 1c 5a 97 7b 9b d1 01   6........Z.{...
25 27 f7 46 4b 9b d1 01 00 10 00 00 00 00 00 00  %'.FK...........
00 0c 00 00 00 00 00 00 20 00 00 00 00 00 00 00  ........ .......
21 01 61 00 70 00 69 00 2d 00 6d 00 73 00 2d 00  !.a.p.I.-.m.s.-.
77 00 69 00 6e 00 2d 00 63 00 6f 00 72 00 65 00  w.I.n.-.c.o.r.e.
2d 00 66 00 69 00 62 00 65 00 72 00 73 00 2d 00  -.f.I.b.e.r.s.-.
6c 00 31 00 2d 00 31 00 2d 00 30 00 2e 00 64 00  l.1.-.1.-.0...d.
6c 00 6c 00 00 00 02 00 ff ff ff ff ff ff ff ff  l.l.............
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
Sorting index $I30 in file 64823.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xfd38 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
The multi-sector header signature for VCN 0x1 of index $I30
in file 0xfd38 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Correcting error in index $I30 for file 64824.
The index bitmap $I30 in file 0xfd38 is incorrect.
Correcting error in index $I30 for file 64824.
The down pointer of current index entry with length 0xa0 is invalid.
5b e0 02 00 00 00 02 00 a0 00 84 00 01 00 00 00  [...............
38 fd 00 00 00 00 0a 00 46 75 f7 46 4b 9b d1 01  8.......Fu.FK...
70 50 30 3f 16 97 d0 01 14 21 61 97 7b 9b d1 01  pP0?.....!a.{...
46 75 f7 46 4b 9b d1 01 00 10 00 00 00 00 00 00  Fu.FK...........
00 0c 00 00 00 00 00 00 20 00 00 00 00 00 00 00  ........ .......
21 01 61 00 70 00 69 00 2d 00 6d 00 73 00 2d 00  !.a.p.I.-.m.s.-.
77 00 69 00 6e 00 2d 00 63 00 6f 00 72 00 65 00  w.I.n.-.c.o.r.e.
2d 00 66 00 69 00 62 00 65 00 72 00 73 00 2d 00  -.f.I.b.e.r.s.-.
6c 00 31 00 2d 00 31 00 2d 00 30 00 2e 00 64 00  l.1.-.1.-.0...d.
6c 00 6c 00 00 00 02 00 ff ff ff ff ff ff ff ff  l.l.............
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
Sorting index $I30 in file 64824.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xfd39 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
The multi-sector header signature for VCN 0x1 of index $I30
in file 0xfd39 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Correcting error in index $I30 for file 64825.
The index bitmap $I30 in file 0xfd39 is incorrect.
Correcting error in index $I30 for file 64825.
The down pointer of current index entry with length 0xa0 is invalid.
5c e0 02 00 00 00 02 00 a0 00 84 00 01 00 00 00  \...............
39 fd 00 00 00 00 0a 00 78 ea f7 46 4b 9b d1 01  9.......x..FK...
e0 f6 37 f6 13 97 d0 01 50 c2 68 97 7b 9b d1 01  ..7.....P.h.{...
78 ea f7 46 4b 9b d1 01 00 10 00 00 00 00 00 00  x..FK...........
00 0c 00 00 00 00 00 00 20 00 00 00 00 00 00 00  ........ .......
21 01 61 00 70 00 69 00 2d 00 6d 00 73 00 2d 00  !.a.p.I.-.m.s.-.
77 00 69 00 6e 00 2d 00 63 00 6f 00 72 00 65 00  w.I.n.-.c.o.r.e.
2d 00 66 00 69 00 62 00 65 00 72 00 73 00 2d 00  -.f.I.b.e.r.s.-.
6c 00 31 00 2d 00 31 00 2d 00 30 00 2e 00 64 00  l.1.-.1.-.0...d.
6c 00 6c 00 00 00 02 00 ff ff ff ff ff ff ff ff  l.l.............
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
Sorting index $I30 in file 64825.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xfd3d is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Correcting error in index $I30 for file 64829.
The index bitmap $I30 in file 0xfd3d is incorrect.
Correcting error in index $I30 for file 64829.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff 78 ea f7 46 4b 9b d1 01  ........x..FK...
e0 f6 37 f6 13 97 d0 01 50 c2 68 97 7b 9b d1 01  ..7.....P.h.{...
Sorting index $I30 in file 64829.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xfd47 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Correcting error in index $I30 for file 64839.
The index bitmap $I30 in file 0xfd47 is incorrect.
Correcting error in index $I30 for file 64839.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff 78 ea f7 46 4b 9b d1 01  ........x..FK...
e0 f6 37 f6 13 97 d0 01 50 c2 68 97 7b 9b d1 01  ..7.....P.h.{...
Sorting index $I30 in file 64839.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xfe8c is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Correcting error in index $I30 for file 65164.
The index bitmap $I30 in file 0xfe8c is incorrect.
Correcting error in index $I30 for file 65164.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff 78 ea f7 46 4b 9b d1 01  ........x..FK...
e0 f6 37 f6 13 97 d0 01 50 c2 68 97 7b 9b d1 01  ..7.....P.h.{...
Sorting index $I30 in file 65164.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xfe90 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Correcting error in index $I30 for file 65168.
The index bitmap $I30 in file 0xfe90 is incorrect.
Correcting error in index $I30 for file 65168.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff 78 ea f7 46 4b 9b d1 01  ........x..FK...
e0 f6 37 f6 13 97 d0 01 50 c2 68 97 7b 9b d1 01  ..7.....P.h.{...
Sorting index $I30 in file 65168.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xfe95 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Correcting error in index $I30 for file 65173.
The index bitmap $I30 in file 0xfe95 is incorrect.
Correcting error in index $I30 for file 65173.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff 78 ea f7 46 4b 9b d1 01  ........x..FK...
e0 f6 37 f6 13 97 d0 01 50 c2 68 97 7b 9b d1 01  ..7.....P.h.{...
Sorting index $I30 in file 65173.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xfebe is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Correcting error in index $I30 for file 65214.
The index bitmap $I30 in file 0xfebe is incorrect.
Correcting error in index $I30 for file 65214.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff 78 ea f7 46 4b 9b d1 01  ........x..FK...
e0 f6 37 f6 13 97 d0 01 50 c2 68 97 7b 9b d1 01  ..7.....P.h.{...
Sorting index $I30 in file 65214.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xfec2 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Correcting error in index $I30 for file 65218.
The index bitmap $I30 in file 0xfec2 is incorrect.
Correcting error in index $I30 for file 65218.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff 78 ea f7 46 4b 9b d1 01  ........x..FK...
e0 f6 37 f6 13 97 d0 01 50 c2 68 97 7b 9b d1 01  ..7.....P.h.{...
Sorting index $I30 in file 65218.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xfec5 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Correcting error in index $I30 for file 65221.
The index bitmap $I30 in file 0xfec5 is incorrect.
Correcting error in index $I30 for file 65221.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff 78 ea f7 46 4b 9b d1 01  ........x..FK...
e0 f6 37 f6 13 97 d0 01 50 c2 68 97 7b 9b d1 01  ..7.....P.h.{...
Sorting index $I30 in file 65221.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xfec6 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Correcting error in index $I30 for file 65222.
The index bitmap $I30 in file 0xfec6 is incorrect.
Correcting error in index $I30 for file 65222.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff 78 ea f7 46 4b 9b d1 01  ........x..FK...
e0 f6 37 f6 13 97 d0 01 50 c2 68 97 7b 9b d1 01  ..7.....P.h.{...
Sorting index $I30 in file 65222.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xfec7 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Correcting error in index $I30 for file 65223.
The index bitmap $I30 in file 0xfec7 is incorrect.
Correcting error in index $I30 for file 65223.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff 78 ea f7 46 4b 9b d1 01  ........x..FK...
e0 f6 37 f6 13 97 d0 01 50 c2 68 97 7b 9b d1 01  ..7.....P.h.{...
Sorting index $I30 in file 65223.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xfec8 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Correcting error in index $I30 for file 65224.
The index bitmap $I30 in file 0xfec8 is incorrect.
Correcting error in index $I30 for file 65224.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff 78 ea f7 46 4b 9b d1 01  ........x..FK...
e0 f6 37 f6 13 97 d0 01 50 c2 68 97 7b 9b d1 01  ..7.....P.h.{...
Sorting index $I30 in file 65224.
  290166 index entries processed.                                         Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file X8489E~1.MAN (43556) into directory file 9871.
Recovering orphaned file X848AA~1.MAN (43688) into directory file 9871.
Recovering orphaned file X84851~1.MAN (44512) into directory file 9871.
Recovering orphaned file X8486A~1.MAN (54035) into directory file 9871.
Recovering orphaned file X84835~1.MAN (54055) into directory file 9871.
Recovering orphaned file X848A7~1.MAN (54308) into directory file 9871.
Recovering orphaned file X848C2~1.MAN (54707) into directory file 9871.
Recovering orphaned file X84863~1.MA
 
And this is the windows update failure code... but this is not just it. Before this update.. there were a couple more that also failed.
 

Attachments

  • Screenshot_10.png
    Screenshot_10.png
    15.6 KB · Views: 2
Do you have access to another SATA hard drive you can use in place of your current one?

IF you do, before proceeding further, pull the current hard disk and connect the new one.

Then locate another DVD containing your OS and install from that instead. Do not connect any other hard drives or USB storage devices (including USB memory sticks).

Essentially this is verifying whether the hard disk really is at fault, and whether the OS media is the issue.

If everything works fine on the borrowed hard disk, remove it and use the same OS media with your original hard disk and report back your findings.

If the OS DVD media is at fault it will behave the same with the borrowed hard disk. If the hard drive is at fault, Windows will install fine and without errors on the borrowed disk. If the latter is the case, you need to order a new hard drive.
 
Leeky said:
Do you have access to another SATA hard drive you can use in place of your current one?

IF you do, before proceeding further, pull the current hard disk and connect the new one.

Then locate another DVD containing your OS and install from that instead. Do not connect any other hard drives or USB storage devices (including USB memory sticks).

Essentially this is verifying whether the hard disk really is at fault, and whether the OS media is the issue.

If everything works fine on the borrowed hard disk, remove it and use the same OS media with your original hard disk and report back your findings.

If the OS DVD media is at fault it will behave the same with the borrowed hard disk. If the hard drive is at fault, Windows will install fine and without errors on the borrowed disk. If the latter is the case, you need to order a new hard drive.
Click to expand...


I have bought a new hard drive and these errors are coming from it... So its definitely either windows updates failure or dvd media or memory (currently being tested, ill come back with result in 5 hours) and I have also bought a new OS dvd waiting for it to come.

The updates failed maybe because some of the program that are installed or running might interrupts ?
 
Generally speaking you shouldn't install any new software whilst Windows Update is running. When you install Windows the first priority is always to install the necessary drivers to make sure all hardware components are located, verified and working. The next stage is to apply all Windows Updates and ensure .NET framework is installed and fully updated. Only after that do you start installing other Windows applications.

If you are getting these errors with the new hard disk it is more than likely the OS media at fault. It could also be the memory -- hopefully you'll have an answer to that shortly.
 
T,
I looked over the 'errors' and I am puzzled.
You have original authentic WIndows 7 installation disk? You have a new HDD? You have no connection to the internet? You have no other media (USB, HDD, CDs) attached to or in the system? All 4 questions the answer should be 'yes'. If any negatives responses, please tell us.

Please tell me how these came to be introduced to your system?:
C:\Program Files\ATI Technologies\ATI.ACE\Fuel\Fuel.Service.exe?
C:\Users\tuyen\AppData\Roaming\GameRanger\GameRanger\GameRanger.exe?
C:\Program Files (x86)\Avira\Antivirus\avgnt.exe?
C:\Program Files\Common Files\AV\McAfee Anti-Virus And Anti-Spyware\upgrade.exe?
D:\ChipSet\W7_W8\Bin64\InstallManagerApp.exe?
C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\MOM.exe?

If this isn't from your original and authentic Windows 7 installation disk (and it should not be), then you must be introducing these from somewhere else (like the drivers disk from the manufacturer? or a USB still attached?). To me, it looks like that and it also looks like you have several programs and a couple of anti-malware programs fighting over your system. To control this situation DO NOT introduce anything beyond an original and authentic Windows 7 install. Please tell us if you have any idea where this influx of programs unrelated to Windows is coming from.

When you have an error, it is important to look at the FIRST one - if using Event Viewer, check time stamp.

There is a possibility that this is a hardware issue, but I think it is caused by corruption caused by aggressive anti-malware programs asserting simultaneous rights while being blind to the other program.
 
You must log in or register to reply here.

Similar threads

J
USB PC speakers convert to RCA?
Replies
1
Views
220
Nelson28
N
H
Legion 5 15ARH05H Type-C Video Output Stopped Working
Replies
0
Views
394
Hal19
H
B
Help with "special permissions" please
Replies
1
Views
510
Nelson28
N

Latest posts

Back