Win 7 Boot PRoblem. Repaired OK, Woorks OK then Boot Probem Again

[Rincewindwiz]

Hi All
Win 7 PC (HP DV6 12Gb RM, 256GB Samsung EVO SSD Boot drive, all latest windows updates)
- All working fine then the keyboard stopped working (press keys, computer does not respond. Mouse OK, - USB keyboard OK) so I rebooted and it would not reboot. Sorry cant remember error code but required startup repair
- Used Macrium recovery disk to repair and it booted fine
- 2 weeks later the same problem occurred. Again start up repair fixed it.

Now I am starting to worry. I would suspect DSS problems but HD Sentinel reports SSD health as excellent (89%) expected lifetime 1000+


Event Viewer reports instances of each of

08:36 Session "RtcPalVideoEtwSession" failed to start with the following error: 0xC0000022 (and another earlier at 8:24)

8:41 Session "ReadyBoot" stopped due to the following error: 0xC0000188
8:41 Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D

8:41 Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

 

[wither 2]

If you're using MSE, go here-

C:\ProgramData\Microsoft\Microsoft Security Client\Support\EppOobe.etl

and delete the file.

Reboot.

I don't know if that has anything to do with your keyboard not working.

 

[Rincewindwiz]

Thanks.
I switched off MSE; deleted the file and the reboot failure has not (yet!) recurred.
Keyboard no problems either (but this may be coincidence)


I notice the file came back within 10 minutes so presumably the assumption was it had got corrupted? I have not yet switched MSE back on so I'll try that tonight


What does this file do?

Does it damage MSE functionality?

How on earth can MS write software that screws up the boot process and why haven't they fixed it?


If it doesn't happen again this week I'll consider it solved

 

[wither 2]

I don't know exactly what it is generated by but it is a log file (ETL File Extension - What is an .etl file and how do I open it?). It's associated with Oobe (Out Of The Box Experience). Since it's associated with Microsoft security, I would assume that it's logging some unwanted event. Why it has the effects that you had is beyond me.

If you find that the problem is solved, please mark the thread as solved.

 

[Megahertz07]

Please schedule a disk check.
Open a CMD window as administrator and type:
chkdsk c: /f
It will say that the drive is in use and ask if you what to schedule to next start = Yes
Reboot.