Windows Update not working and multiple BoSD happening

Autaka

Autaka

New member
Joined
Nov 6, 2024
Posts
3
Hello !

So a few month ago i saw that's my window update were not working. I tried to fix it but i was not able to do it so i forgot it
Then a few week ago, i started to have more and more BoSD crash happening, at first it was once a week and now it is several time a day.
Moreover, sometime when i'm booting my pc, it says "repairing C:/ disk" then boot normally.
Then since today, when i try to open iCUE.exe (corsair keyboard app) or Overwolf (an app for third party app in games) it gives me this error then it start normally.

1730928047050.webpTranslation :"C:\WINDOWS\SYSTEM32\directxdatabasehelper.dll is not made to be execute on Window or there is an error inside the file. Try to install again this program using the OG support installation tools, or try to contact your SYS admin or the supplier of this software to have support. State of the error : Oxc0000020. "


Moreover, window defender seems to not working correctly anymore

1730928333965.webp
1730928352527.webp


So i tried this tuto :

How to Reset Windows Update Components in Windows 11/10? - MiniTool


At one point, it told me to open HKEY_Local_Machine/COMPONENTS

but the components folder was missing from the registry editor. i found a fix to manually add the file and when i open the file i saw this :
1730928596523.webp


I suspect all my problem are because this file got corrupted somehow.

I would love to have some help on this i'm a bit loss and thx in advance for it !

N.B : here is the list of software update than did not install :

1730928929907.webp




1730928966062.webp

All driver updates and other update did work tho.


Also here's my PC spec :



1730929247919.webp

Windows is install on the NVME drive
 

Attachments

  • 1730929068839.webp
    1730929068839.webp
    59.8 KB · Views: 1
Hello ! Thx for the advice !

So right know i'm doing your list of thing to do ! I'm at the point 4 : here's are the result : 1730941297325.webp

and i got this from the repair : 1730941676366.webp

Do i need to put the COMPONENTS files as the sources ?
 
Last edited:
Does it proceed to install the updates?
If no, and the bsods are diminished, start a topic in the Windows update sub forum.
niemiro

Thread 'Windows Update Forum Posting Instructions'

Welcome to Sysnative's Windows Update forum.

Here you may seek help and support for Windows Update errors, System File Checker (SFC) corruptions, DISM corruptions, Side by Side Configuration errors, System Service errors, and related errors, corruptions, and problems. These instructions apply to all of the above problems.

If you are, for whatever reason, not able to complete part of these instructions, please just create a new thread with a description of your problem and we will help you from there.

Important Information​

Warning: Please do not follow the...
  • Thanks
  • Love
 
Autaka said:
Moreover, sometime when i'm booting my pc, it says "repairing C:/ disk" then boot normally.
Click to expand...
That for me is the biggest clue. I rather suspect your problems may be down to a flaky drive. Download the Sabrent Contol Panel and use that to check on the drive's health. Upload that display. Also check for a firmware update for the drive.

Please also follow the BSOD Posting Instructions. The data colelcted by our tool will help us diagnose your problem.
 
Hey ! So i dl the sabrent control panel . My drive is at 100% health and up to date . @ubuysa

1730997974789.webp

@xilolee no, the window updater is not working. The phase 4 of your use did not finish. The phase 5 told me they were corrputed data but they were not able to get rid of them :/ .
Here's is the report froml the Sysnative file collection app :
and here's the speccy result : http://speccy.piriform.com/results/eKGQouFUCUkE6jD2mZSJfUf
 

Attachments

xilolee said:
I would open a new topic in the windows update subforum.
Click to expand...
I rather suspect that the Windows Update issue is just a symptom of a deeper problem - the user is reporting BSODs also.

@Autaka Despite the apparent clean bill of health from the Sabrent Control Panel I still firmly believe that your problems are related to a flaky system drive. In your System log there are a great many errors relating to the C: drive:

There are many (a great many) of these errors, followed by an automatic repair...
Code: 
Log Name:      System
Source:        Microsoft-Windows-Ntfs
Date:          07/11/2024 02:41:11
Event ID:      7
Task Category: None
Level:         Warning
Keywords:  
User:          SYSTEM
Computer:      DESKTOP-V9VLSSB
Description:
Ntfs has detected MFT torn write on a volume.

           Volume correlation Id: {9b960f1b-05a6-42a4-affb-0c079ad503e7}
           Volume name: C:
           Volume label: SSD M.1
           File reference: 0x0
           File name: \$Mft
           Byte offset of the buffer within the file: 2321563648
           Byte offset of the torn structure within the buffer: 1024
           Block index: 0
           Expected sequence number: 16
           Actual sequence number: 28
           FRS file reference: 0x229811
           FRS file name: <impossible de déterminer le nom de fichier>
           Is child FRS: false
Code: 
Log Name:      System
Source:        Ntfs
Date:          07/11/2024 02:43:34
Event ID:      130
Task Category: None
Level:         Warning
Keywords:  
User:          SYSTEM
Computer:      DESKTOP-V9VLSSB
Description:
The file system structure on volume C: has now been repaired.
Thse alone indicate that all is not well with that drive. We would never expect to see errors like this in a happy system.

But there's more. We also see a great many errors requesting various forms of chkdsk to be run on that System drive...
Code: 
Log Name:      System
Source:        Microsoft-Windows-Ntfs
Date:          07/11/2024 10:55:08
Event ID:      98
Task Category: None
Level:         Error
Keywords:      (2)
User:          SYSTEM
Computer:      DESKTOP-V9VLSSB
Description:
Volume SSD M.1 (\Device\HarddiskVolumeShadowCopy2) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.
Code: 
Log Name:      System
Source:        Microsoft-Windows-Ntfs
Date:          07/11/2024 01:21:25
Event ID:      98
Task Category: None
Level:         Warning
Keywords:      (2)
User:          SYSTEM
Computer:      DESKTOP-V9VLSSB
Description:
Volume C: (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
Code: 
Log Name:      System
Source:        Ntfs
Date:          06/11/2024 22:14:22
Event ID:      55
Task Category: None
Level:         Error
Keywords:  
User:          SYSTEM
Computer:      DESKTOP-V9VLSSB
Description:
A corruption was discovered in the file system structure on volume C:.

La table MFT (Master File Table) contient un enregistrement de fichier endommagé. Le numéro de référence du fichier est 0x6200000001b338. Le nom du fichier est « <impossible de déterminer le nom de fichier> ».
That drive is very clearly not happy and that is most likely the cause of all your problems.

It might be as simple a fix a removing and re-seating the drive. I have seen several M.2 drives that caused niggly problems which were resolved by re-seating the drive. Give that a try first.

Also, can you expand on the Drive Health on that Sabrent Control Panel? I'd like to see the SMART data for this drive.

TBH if this were mine I would already be replacing that drive. The errors we see above clearly indiocate that something is wrong with that drive.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top