New
#51
Please try a cold boot again and run SFC, see if that gives repaired corruption.also today morning after cold start
Please try a cold boot again and run SFC, see if that gives repaired corruption.also today morning after cold start
Ran sfc and had no corruption. Then performed a cold boot and ran sfc again. Result was no corruption.
I found something worth mentioning regarding the file corruption. after the test in my previous post I did another one.
this time I cleaned the system from temporary and unused files prior shutting down. I like to have a slim system without any mess in it and I use mostly CCleaner and Wise Care 365. I deleted all files both applications found and also cleaned the registry then shut the system down.
this morning after cold boot I ran "sfc /scannow" and got a surprise: there was a file corruption again. it could be repaired as always it seems to be caused by the applications I use for cleaning and slimming the system. I have a screenshot from sfc as well as a CBS.log after the first sfc which found the corruption.
what' your opinion?
could this be related to the BSOD or maybe even cause it?
I have been able to find the files, they are all in the C:\Windows\Help directory.
Please do NOT 'clean' the registry with any program, if there is a bug somewhere you're the one that is having a problem.
Please do NOT use Wise Care 365, the reason is that this program has caused quite some problems.
Code:2016-02-21 08:52:44, Info CSI 000013ea [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:13]"artnoloc.mshi" from store 2016-02-21 08:52:44, Info CSI 000013eb [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:13]"artnoloc.mshc" from store 2016-02-21 08:52:44, Info CSI 0000141a [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:8]"art.mshc" from store 2016-02-21 08:52:44, Info CSI 0000141b [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:8]"art.mshi" from store 2016-02-21 08:52:45, Info CSI 00001460 [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:10]"noarm.mshc" from store 2016-02-21 08:52:45, Info CSI 00001461 [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:10]"noarm.mshi" from store 2016-02-21 08:52:45, Info CSI 00001469 [SR] Repairing corrupted file [l:25 ml:26]"\??\C:\WINDOWS\Help\tr-TR"\[l:11]"credits.rtf" from store 2016-02-21 08:52:45, Info CSI 00001472 [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:18]"windowsclient.mshc" from store 2016-02-21 08:52:45, Info CSI 00001473 [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:18]"windowsclient.mshi" from store 2016-02-21 08:52:45, Info CSI 00001475 [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:17]"clientserver.mshi" from store 2016-02-21 08:52:45, Info CSI 00001476 [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:17]"clientserver.mshc" from store 2016-02-21 08:52:46, Info CSI 00001494 [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:14]"resources.mshc" from store 2016-02-21 08:52:46, Info CSI 00001495 [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:14]"resources.mshi" from store 2016-02-21 08:53:06, Info CSI 00001955 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:11]"cliconf.chm" from store 2016-02-21 08:53:06, Info CSI 00001956 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:12]"odbcinst.chm" from store 2016-02-21 08:53:06, Info CSI 00001957 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:12]"sqlsodbc.chm" from store 2016-02-21 08:53:06, Info CSI 00001958 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:12]"sqlsoldb.chm" from store 2016-02-21 08:53:06, Info CSI 00001959 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:10]"msdasc.chm" from store 2016-02-21 08:54:40, Info CSI 000032cc [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:7]"mmc.CHM" from store 2016-02-21 08:55:15, Info CSI 00003c9b [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:11]"odbcjet.chm" from store 2016-02-21 08:55:15, Info CSI 00003c9c [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:12]"msorcl32.chm" from store 2016-02-21 08:56:30, Info CSI 000050a7 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:11]"odbcjet.chm" from store 2016-02-21 08:56:30, Info CSI 000050a8 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:12]"msorcl32.chm" from store 2016-02-21 08:56:30, Info CSI 000050aa [SR] Repairing corrupted file [l:25 ml:26]"\??\C:\WINDOWS\Help\tr-TR"\[l:11]"credits.rtf" from store 2016-02-21 08:56:30, Info CSI 000050ac [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:18]"windowsclient.mshc" from store 2016-02-21 08:56:30, Info CSI 000050ad [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:18]"windowsclient.mshi" from store 2016-02-21 08:56:30, Info CSI 000050af [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:17]"clientserver.mshi" from store 2016-02-21 08:56:30, Info CSI 000050b0 [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:17]"clientserver.mshc" from store 2016-02-21 08:56:30, Info CSI 000050b2 [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:14]"resources.mshc" from store 2016-02-21 08:56:30, Info CSI 000050b3 [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:14]"resources.mshi" from store 2016-02-21 08:56:30, Info CSI 000050b5 [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:13]"artnoloc.mshi" from store 2016-02-21 08:56:30, Info CSI 000050b6 [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:13]"artnoloc.mshc" from store 2016-02-21 08:56:30, Info CSI 000050b8 [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:10]"noarm.mshc" from store 2016-02-21 08:56:30, Info CSI 000050b9 [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:10]"noarm.mshi" from store 2016-02-21 08:56:30, Info CSI 000050bb [SR] Repairing corrupted file [l:46 ml:47]"\??\C:\WINDOWS\Help\Windows\ContentStore\tr-TR"\[l:8]"art.mshc" from store 2016-02-21 08:56:30, Info CSI 000050bc [SR] Repairing corrupted file [l:44 ml:45]"\??\C:\WINDOWS\Help\Windows\IndexStore\tr-TR"\[l:8]"art.mshi" from store 2016-02-21 08:56:30, Info CSI 000050be [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:7]"mmc.CHM" from store 2016-02-21 08:56:30, Info CSI 000050c0 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:11]"cliconf.chm" from store 2016-02-21 08:56:30, Info CSI 000050c1 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:12]"odbcinst.chm" from store 2016-02-21 08:56:30, Info CSI 000050c2 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:12]"sqlsodbc.chm" from store 2016-02-21 08:56:30, Info CSI 000050c3 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:12]"sqlsoldb.chm" from store 2016-02-21 08:56:30, Info CSI 000050c4 [SR] Repairing corrupted file [l:28 ml:29]"\??\C:\WINDOWS\Help\mui\041F"\[l:10]"msdasc.chm" from store
thanks for the warning, I've been using CCleaner for years now whitout any issues.
I started using Wise Care 365 a couple of months a go but I'm deleting it right now.
I'II stop cleaning the registry even with CCleaner immediately.
could there be any relation to the BSOD issue?
Depending on what has actually been removed there could.could there be any relation to the BSOD issue?
ok, I'll keep an eye on what happens from now on without touching the registry.
any other suggestion what to try except waiting for a casual BSOD with the current settings?
Last edited by sahafiec; 22 Feb 2016 at 08:28.
after so many days without BSOD or other issues I decided to make a clean Windows 10 install.
after doing so, everything went smooth, suddenly I got a BSOD while updating my Origin games.
the BSOD is of the kind "Memory_Management" with "ntoskrnl.exe" as a cause.
I don't understand that, the only difference was my ram was on XPM.
could this be the simple cause for all that axe0?
XMP is overclocking the memory, overclocking stresses the component what may cause it to malfunction if it is not stable.
I get your point and agree on that. Another question is why should a memory be unstable at it's stock speed?!
The ram is advertised as 2400mhz memory and sold as such. Maybe I should contact Corsair about this issue.
Any other clues within the log files?