[Win10] STATUS_FILE_CORRUPT_ERROR in CBS.log

[eddyhall]

Hi all, first time here trying to troubleshoot some errors.

Windows 10 clean install 4 days ago. I am having trouble today with a taskhostsw.exe error message which won't go away:
The instruction at 0x00007FFF29B5371A referenced memory at 0x0000000000000. The memory could not be written

As a result I scanned my RAM (with Windows Memory Diagnostic, 100% OK) and the ran SFC/scannow. The scan quit at 9% with the attached log. It seems that there were at least 3 STATUS_FILE_CORRUPT_ERRORs in the log. I am inexperienced in reading these logs so I don't know if that was the source of the "main" error.

Can anyone help with figuring out what the problem is?

Cheers,
Eddy

 

[eddyhall]

Re: STATUS_FILE_CORRUPT_ERROR in CBS.log

Hi all,

In a further worsening of my symptoms, it seems like Windows itself is glitching - the Start button and taskbar are seeming to crash and refresh 2 or 3 times per second and their graphics flash in and out. Essentially rendering the machine unusable. I might try a fresh installation tomorrow unless I can salvage this.

Cheers,
Eddy

 

[eddyhall]

Re: STATUS_FILE_CORRUPT_ERROR in CBS.log

Hi all,

PC is pretty royally messed up. I will be away for the next week and I will post this in the Not Received Help? thread when I get back in the country.

Cheers,
Eddy

 

[eddyhall]

Re: STATUS_FILE_CORRUPT_ERROR in CBS.log

I have done a reinstallation of Win10 and formatted the primary drive. This seems to have sorted things out.

After installing I ran update to get SP1. After getting to th elatest build I have run SFC /scannow (no integrity violations) and SFCFix.

SFCFix is giving me a strange scenario. After checking the logs it tells me it is "attempting repair" but not specifying the issue and then
crashing out when the remote procedure call fails. The DSIM log has numerous Errors relating to "Failed finalising changes".

Cheers,
Eddy

 

[eddyhall]

Re: STATUS_FILE_CORRUPT_ERROR in CBS.log

Hi all,

After 4 days of fairly clean running, Windows clammed up completely. No ability to get bast the boot repair screen. I can get to CMD and I have tried the following:
1) chkdisk on boot drive (somehow changed to E:\): "Windows has scanned tyhe file system and found no problems", "Failed to transfer logged messages to the event log with status 50"
2) SFC /scannow: "Windows Resource Protection could not perform the requested operation"

Any suggestions?

Cheers,
Eddy

 

[eddyhall]

I am going to try and reinstal Win10 as none of the repair options seem to be able to process.

Cheers,
Eddy

 

[eddyhall]

So the reinstallation went fine, everything working well. I decided to reboot to see if things would stay stable - turns out Windows Update was running in the background and the PC wanted to update. I had hoped to prevent that to try and get a stable platform.

Anyway, now it won't reboot - I have used bios to only allow boot from the primary drive but it asks for a "proper boot device". Something is very wrong with my PC.

Eddy

 

[eddyhall]

Final conclusion on this topic.

I RMA'ed my 4yr old SSD (well done OCZ / Toshiba!) after my master boot drive was even unable to be detected over SATA at BIOS stage.

With the replacement SSD, everything seems to be working just fine. So my underlying assumption is that this was a hardware issue which casued the boot record errors.

Cheers,
Eddy