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

x BlueRobot said:
Could you please run SFC again then provide the CBS log if it fails.
Click to expand...
Hello thank you for your care..

SFCFix version 3.0.2.1 by niemiro. Start time: 2022-02-21 12:40:37.125 Microsoft Windows 8.1 Update 3 - amd64 Not using a script file. AutoAnalysis:: CORRUPT: C:\Windows\winsxs\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com. CBS & SFC total detected corruption count: 1 CBS & SFC total unimportant corruption count: 0 CBS & SFC total fixed corruption count: 0 SURT total detected corruption count: 0 SURT total unimportant corruption count: 0 SURT total fixed corruption count: 0 AutoAnalysis:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 1 datablocks. Finish time: 2022-02-21 13:18:09.792 ----------------------EOF-----------------------

In the begining when I tried the fix the issue ,myself I actually attempted to fix that file BUT IN ANOTHER DIRECTORY (LOL)..
it seems that I had the wrong file all along..
What i did was download it from the internet and replaced it in my pc.. I do not know if thats what you would do so I am going to wait for a response..
 
Please run the SFCFix script from previous post (post #15), if you get the successfully replaced message then please open command prompt and then the following command:

Rich (BB code): 
sfc /scannow

If it fails i.e. gives an error message, then please attach the latest CBS log.
 
x BlueRobot said:
Please run the SFCFix script from previous post (post #15), if you get the successfully replaced message then please open command prompt and then the following command:

Rich (BB code): 
sfc /scannow

If it fails i.e. gives an error message, then please attach the latest CBS log.
Click to expand...

SFCfix was succesfull and here is the log from sfc /Scannow attached (it said it found corrupted files)


SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-02-21 18:41:02.185
Microsoft Windows 8.1 Update 3 - amd64
Using .zip script file at C:\Users\Adm\Desktop\SFCFix.zip [1]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys

WARNING: File C:\Windows\WinSxS\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys was not backed up as that would replace the current backup.
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.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2022-02-21 18:41:02.811
Script hash: /T44zTpWwTslFRJXmAw7CVquhRLKcQ8E2w4gIzIU3yQ=
----------------------EOF-----------------------
Click to expand...

I do not know why the bb code is not working it was supposed to be in quotes..
 

Attachments

Last edited by a moderator:
dokha said:
I do not know why the bb code is not working it was supposed to be in quotes..
Click to expand...
It's because you haven't put the correct opening tag, it should be [QUOTE] but you've put [/QUOTE] instead. I've fixed it now.
 
Could you please run the command once more and then let me know the result?

Rich (BB code): 
sfc /scannow
 
Sorry for the delay, I made the scan yesterday and got busy and forgot to post, here it is:
 

Attachments

The CBS log looks fine, did SFC complete without any errors or with the message that it was able to successfully repair them? If it didn't, then please run DISM using the following command from an elevated command prompt:

Rich (BB code): 
DISM /Online /Cleanup-Image /RestoreHealth
 
x BlueRobot said:
The CBS log looks fine, did SFC complete without any errors or with the message that it was able to successfully repair them? If it didn't, then please run DISM using the following command from an elevated command prompt:

Rich (BB code): 
DISM /Online /Cleanup-Image /RestoreHealth
Click to expand...


Okay, I will do that..
Today I decided to remove the BIOS password just to be on the safe side of troubleshooting..
After that I tried EasyBCD and I got this screen telling me basically the same problem..

Error Screen.JPG

Please notice the first two lines " A recent hardware or software change might be the cause"...
I am sure this is the cause since the problem started to happen after I cloned my drive (old HD to SSD) and I also used it on another laptop.. I would appreciate you experts think with me as to what are the potential problems to happen with this particular error message?...
I really don't want to reformat knowing that problem is probably very solvable,
I am sure I am not the first one this happened to, and I am not even a professional..

For whatever reason I want to blame my bios driver because I can't find anything else to blame..

[EDIT]: I forgot to mention that following the instructions in the image, FAILS ..

Here is the contents of the log:

Startup Repair diagnosis and repair log --------------------------- Last successful boot time: ‎22/‎02/‎2022 18:55:16 (GMT) Number of repair attempts: 1 Session details --------------------------- System Disk = \Device\Harddisk0 Windows directory = F:\Windows AutoChk Run = 0 Number of root causes = 1 Test Performed: --------------------------- Name: Check for updates Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Test Performed: --------------------------- Name: System disk test Result: Completed successfully. Error code = 0x0 Time taken = 16 ms Test Performed: --------------------------- Name: Disk failure diagnosis Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Test Performed: --------------------------- Name: Disk metadata test Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Test Performed: --------------------------- Name: Target OS test Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Test Performed: --------------------------- Name: Volume content check Result: Completed successfully. Error code = 0x0 Time taken = 78 ms Test Performed: --------------------------- Name: Boot manager diagnosis Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Test Performed: --------------------------- Name: System boot log diagnosis Result: Completed successfully. Error code = 0x0 Time taken = 16 ms Test Performed: --------------------------- Name: Event log diagnosis Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Test Performed: --------------------------- Name: Internal state check Result: Completed successfully. Error code = 0x0 Time taken = 15 ms Test Performed: --------------------------- Name: Boot status test Result: Completed successfully. Error code = 0x0 Time taken = 0 ms Root cause found: --------------------------- Boot status indicates that the OS booted successfully. --------------------------- ---------------------------

Note: It is important to mention that Windows is NOT in F: !!
 
Last edited:
I think I came close My SSD driver shows "Disk Drive" instead of "Standard SATA AHCI Controller"
ssd driver.PNG

The Standard SATA Driver is not listed when I try to change it for some reason.. What can I do?
 
What should I do if my recovery partition (Windows Recovery Environment) is messed up..?
I don't think Windows fixes that using the commands mentioned previously..
I just confirmed that its no good..
 
Do you remember if this is a GPT or MBR disk? Please boot into Windows normally and then the following commands sequentially in an elevated Command Prompt:

Rich (BB code): 
diskpart
list disk

Please provide a screenshot or copy/paste the output in your next post. Just looking back over this thread, I noticed that you mentioned that the Driver Store directory was missing for the said driver.

Could you please open the registry editor and then navigate to the following key path:

Rich (BB code): 
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/pciidex.sys

Please copy/paste the Source value in your next post as well. You also wish to attach the setupapi.dev.log too, which can be found in the following directory:

Rich (BB code): 
%systemroot%/Inf
 
x BlueRobot said:
Do you remember if this is a GPT or MBR disk? Please boot into Windows normally and then the following commands sequentially in an elevated Command Prompt:

Rich (BB code): 
diskpart
list disk

Please provide a screenshot or copy/paste the output in your next post. Just looking back over this thread, I noticed that you mentioned that the Driver Store directory was missing for the said driver.

Could you please open the registry editor and then navigate to the following key path:

Rich (BB code): 
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/pciidex.sys

Please copy/paste the Source value in your next post as well. You also wish to attach the setupapi.dev.log too, which can be found in the following directory:

Rich (BB code): 
%systemroot%/Inf
Click to expand...


I assigned a drive letter to the System Reserved partition to make it visible, I then found that the Recovery folder inside the partition is empty, and I also cannot access it telling me: "It is not accessible , access denied"
Is this normal?
 
x BlueRobot said:
Do you remember if this is a GPT or MBR disk? Please boot into Windows normally and then the following commands sequentially in an elevated Command Prompt:

Rich (BB code): 
diskpart
list disk

Please provide a screenshot or copy/paste the output in your next post. Just looking back over this thread, I noticed that you mentioned that the Driver Store directory was missing for the said driver.

Could you please open the registry editor and then navigate to the following key path:

Rich (BB code): 
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/pciidex.sys

Please copy/paste the Source value in your next post as well. You also wish to attach the setupapi.dev.log too, which can be found in the following directory:

Rich (BB code): 
%systemroot%/Inf
Click to expand...
Here is everything.. I thought I should mention that there are two other "setupapi.dev" files but the have a string of numbers after the name..

list disk.PNG

registry pciidex.PNG
 

Attachments

Thanks, looks like you've got an MBR disk which would explain why the MSR partition is missing.

dokha said:
I then found that the Recovery folder inside the partition is empty, and I also cannot access it telling me: "It is not accessible , access denied"
Is this normal?
Click to expand...
The System Reserved Partition is usually hidden to prevent users from making any modifications to it. Most of the files will be hidden and inaccessible in File Explorer as well. Let's focus on trying to resolve what appears to be the imminent problem and that is the pciidex.sys driver:

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

Back
Top