[SOLVED] Drivers, ide/sata/ata/atapi/ahci from 2017 don't work !!! from 2006 do work

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Sep 2, 2019
69
2
45
i have a problem, my pc is rebooting all the time and try to fix reapir etc and hang's and does not want to start win10.

it's the new drivers for ide/sata/ahci from 2017 !

the one's from 2006 worked fine...


I found out that if i update pc with driver booster from iobit, it finds new ide/sata/ahci drivers, when you look in device manager, on the window ide/sat/ahci, normal drivers are from year 2006, they work fine. but if i update does to drivers from 2017,

then my pc reboots all the time, same problem as you get then. so i just ignore does drivers for now...

the one's from AMD drivers for ide/atat/ahci (2017) don't work !

but is there any FIX to this ?? anybody ???


thx and greets, Jørn Mulder
 
Solution
With windows 10 and these types of problems, I have learned that doing these things first is always a good idea to make sure there are no problems with the Windows install:

1. Open Start.

2. Search for Command Prompt, right-click the top result, and select the Run as administrator option.

3. Type the following command and press Enter, let run until its complete: SFC /scannow

4. Type the following command and press Enter, let run until its complete: DISM /Online /Cleanup-Image /CheckHealth

5.ype the following command and press Enter, let run until its complete: DISM /Online /Cleanup-Image /ScanHealth

6.ype the following command and press Enter, let run until its complete: DISM /Online /Cleanup-Image /RestoreHealth

Report back when...
C:\Windows\system32>DISM /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.329

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.
 
and this one is going now:

C:\Windows\system32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.329

[===========================90.3%==================== ]
 
done:

C:\Windows\system32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.329

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.


what did it do? did it fixed something now ?
 
done:

C:\Windows\system32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.329

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.


what did it do? did it fixed something now ?
Now that you completed the DISM commands do the /scannow one again. These commands fix corruption in windows 10 that can carry over from win7 and win8 upgrades as well as bad installs of win10.
 
oh i see now :

C:\Windows\system32>SFC /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\system32>

it did repaired something,
 
oh i see now :

C:\Windows\system32>SFC /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\system32>

it did repaired something,
Now, win10 should be completely stable. This may have been the source of your original problem or at least a contributing factor. That should have fixed any leftover issues.