[SOLVED] Cannot boot into Safe Mode,Windows does Automatic repair instead..

D

dokha

Active member
Joined
Feb 7, 2022
Posts
35
I cannot boot into safe mode for some reason, I suspect Comodo Antivirus is behind my troubles.. but I have already uninstalled it and my problem is still there..
The Automatic Repair fails and directs me to a log files that says "E:\PCIIDEX.SYS is corrupt."
And so I have downloaded this file from the internet (trusted website), the site tells me it should be in the following directories

1- C:\Windows\System32\drivers\
2- C:\Windows\System32\DriverStore\FileRepository\mshdc.inf_x86_74136ef4a48e4644\

I have replaced it in the first directory no problem, but the second directory (folder: mshdc.inf_x86_74136ef4a48e4644) DOES NOT EXIST..
The DISM online check health command detected nothing..
I cannot repair usind Windows disk because its just the same as using Startup Repair (Automatic Repair) which fails because the E:\PCIIDEX.SYS is corrupt

I will attach my sfc / scannow log too
I need to go to safe mode because I have other issues that need to be repaired in Safe Mode.. (programs not having write permissions)
I am stomped and really despaired..
 

Attachments

wHAT IS E.PNG

Something that I do not understand is that (As mentioned in my explanation) the corrupted file resides in E:/
However as you can see in this screenshot E:/ is non-existent...
help?
 
E: is there but could be a recovery partition.

dokha said:
I have replaced it in the first directory no problem, but the second directory (folder: mshdc.inf_x86_74136ef4a48e4644) DOES NOT EXIST..
Click to expand...
I think what you are calling a folder, : mshdc.inf_x86_74136ef4a48e4644 is a file and not a folder.

dokha said:
C:\Windows\System32\DriverStore\FileRepository
Click to expand...
So you do not have this path?
 
xrobwx71 said:
E: is there but could be a recovery partition.


I think what you are calling a folder, : mshdc.inf_x86_74136ef4a48e4644 is a file and not a folder.


So you do not have this path?
Click to expand...
Yes I do.. There are new advances which I wrote in another help forum (superuser)... I do not know if I can link it or not..
Edit: I have read the rules I do not see anything against linking my posts elsewhere, all you need to do is reply here..
superuser post
My last challenge is Error 50 "DISM does not support servicing Windows PE with the /online option"
when using DISM CMD command DISM /Online /Cleanup-Image /RestoreHealth /Source:G\Sources\install.wim /LimitAccess in my RE to repair using my bootable windows usb image
 
Last edited:
In most cases, it's inadvisable to post in 2 different forums. It can be confusing and a waste of time for all involved.

They are really knowledgeable at Superuser and I would ask that you continue there as you are further along in the process.

If they come up with a solution, you are welcome to post the solution here as it will help others with the same issue in the future.

Thanks.
 
xrobwx71 said:
In most cases, it's inadvisable to post in 2 different forums. It can be confusing and a waste of time for all involved.

They are really knowledgeable at Superuser and I would ask that you continue there as you are further along in the process.

If they come up with a solution, you are welcome to post the solution here as it will help others with the same issue in the future.

Thanks.
Click to expand...
I definitely will...
 
I eliminated all possibilities... Now I am sure uninstalling the Intel chipset driver was the cause, I am going to put my HD in another computer and fix it there, hopefully it boots up I am going to follow up tomorrow..
 
dokha said:
I eliminated all possibilities... Now I am sure uninstalling the Intel chipset driver was the cause, I am going to put my HD in another computer and fix it there, hopefully it boots up I am going to follow up tomorrow..
Click to expand...
I can boot into Windows now.. however still cannot access safe mode.. perhaps the problem began after I cloned my HD but I cannot say for sure..

The SrtTrail.txt log file states

Root cause found: --------------------------- Boot critical file e:\windows\system32\drivers\pciide.sys is corrupt.. Repair action: File repair Result: Failed. Error code = 0x2 Time taken = 1750 ms Root cause found: --------------------------- Boot critical file E:\PCIIDEX.SYS is corrupt.

HOWEVER, The E: drive im My PC is the optical drive and this will remain a mystery for me as to why its looking for this file in E: and obviously this is the wrong drive to look in.. It should look in C:
 
Rich (BB code): 
2022-02-07 15:08:49, Info                  CSI    0000090e Hashes for file member \SystemRoot\WinSxS\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys do not match actual file [l:22{11}]"pciidex.sys" :
  Found: {l:32 b:VLFQjBQZ80ZfOuEdPez1C51410i+o+Cc0kaEQPTz9Uk=} Expected: {l:32 b:1q7BUZtGYot1TW2nqa6JTfzkMCF1nlbFaxDHDhHWMxM=}
2022-02-07 15:08:49, Info                  CSI    0000090f [SR] Cannot repair member file [l:22{11}]"pciidex.sys" of mshdc.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2022-02-07 15:08:49, Info                  CSI    00000910 Hashes for file member \SystemRoot\WinSxS\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys do not match actual file [l:22{11}]"pciidex.sys" :
  Found: {l:32 b:VLFQjBQZ80ZfOuEdPez1C51410i+o+Cc0kaEQPTz9Uk=} Expected: {l:32 b:1q7BUZtGYot1TW2nqa6JTfzkMCF1nlbFaxDHDhHWMxM=}

I haven't got a Windows 8 VM anymore so you'll have to give me some time to install one again. I'll look at sourcing a good copy of the driver for you.
 
SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

x BlueRobot said:
SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
Click to expand...
okay, but after I take a short break from this nightmare..
I am also going to try a program called EasyBCD
 
x BlueRobot said:
Why? It isn't going to replace the corrupted driver.
Click to expand...
I am not sure a driver is the problem, maybe its just Windows..
infact I think its Windows because my only issue (other than that some programs do not have write permissions for some reason) is that I cannot boot into Safe Mode
 
SFCFix version 3.0.2.1 by niemiro. Start time: 2022-02-18 19:16:03.974 Microsoft Windows 8.1 Update 3 - amd64 Using .zip script file at C:\Users\Adm\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys Successfully copied file C:\Users\Adm\AppData\Local\niemiro\Archive\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys to C:\Windows\WinSxS\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys. Successfully restored ownership for C:\Windows\WinSxS\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys Successfully restored permissions on C:\Windows\WinSxS\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys PowerCopy:: directive completed successfully. Successfully processed all directives. Failed to generate a complete zip file. Upload aborted. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 1 datablocks. Finish time: 2022-02-18 19:19:16.003 Script hash: /T44zTpWwTslFRJXmAw7CVquhRLKcQ8E2w4gIzIU3yQ= ----------------------EOF-----------------------
 
Still cannot boot into safe mode,
The log file Srttrail.txt states : Root cause found: --------------------------- Boot critical file g:\windows\system32\drivers\pciide.sys is corrupt. Repair action: File repair Result: Failed. Error code = 0x2 Time taken = 1703 ms Root cause found: --------------------------- Boot critical file G:\PCIIDEX.SYS is corrupt.

I dont have a drive letter G:

I suspect the main cause is something got messed up when I cloned my drive..
 
Back
Top