W7/64 freeze after few seconds; strange items in WMI

A week ago (April 1st, possibly pertinent), my computer became inoperable in Normal Mode. A few seconds after my desktop appears, the mouse continues to control the on-screen cursor, but no input from mouse or keyboard is recognized, and the only exit is a hardware reset. I am now in Safe Mode. Multiple diagnostic attempts have failed to find the problem. Various AV scans have found nothing.
The Event View shows that during each boot, these items

Code:

SQLServerEventProvider
    InvProv
    SQLServerEventProvider
    ActiveScriptEventConsumer
    CommandLineEventConsumer
    LogFileEventConsumer
    WpcClamperProv
    MS_NT_EVENTLOG_EVENT_PROVIDER
    HiPerfCooker_v1

are registered with the Windows Management Interface; they didn't used to be, and I think they are the problem. I also see that the only Restore Point on my system now is one that was created a few seconds after midnight on April 1st.
In another sevenforums thread, I found this sequence

Code:

Change startup type of Window Management Instrumentation (WMI) Service to disabled
     Stop the WMI Service; you may need to stop IP Helper Service first or other dependent services before it allows you to stop WMI Service
     Rename the repository folder: C:\WINDOWS\system32\wbem\Repository to Repository.old
     Open a CMD Prompt with elevated privileges
     CD windows\system32\wbem
     for /f %s in ('dir /b /s *.dll') do regsvr32 /s %s
     Set the WMI Service type back to Automatic and start WMI Service
     cd /d c:\ ((go to the root of the c drive, this is important))
     for /f %s in ('dir /s /b *.mof *.mfl') do mofcomp %s
     Reboot the server

to run in Safe Mode. The first few times I did this, the next Normal Mode boot would succeed, but then even this method stopped working, so I am stuck in Safe Mode.
Any suggestions will be welcome.

Yes, I think it's malware. You can see my results from sfc; the three files are the results of one run, not 3, broken into 3 files because of the forum's limits on uploaded file size.
The more telling result comes from chkdsk. I ran it with the /f argument at boot time, then without the argument while running in safe mode. As you see, I have an MFT problem, not fixed by chkdsk. I wish there were a way to fix this without scrubbing the disk, but I am not hopeful.

I said in the last message that chkdsk had found a telltale Master File Table problem, and that was true. I ran it at boot time with the /F option, its results passed by too fast to read, then I ran it from the (Safe Mode) desktop without the /F, and it showed an unfixed MFT error. Then I ran it again from the desktop, this time piping it to the text file that I uploaded for the forum. I didn't look at the text file, assuming that it would show the same MFT problem, but of course it doesn't. Now, FWIW, I have determined with other software that the MFT, whether or not it is sound, is identical to its mirror copy. I don't know what's going on.

I am not looking forward to reloading Windows, but I think I'll have to do that. Just reloading from the DVD doesn't take much time, but there are any number of wanted updates and a small number of distinctly unwanted updates that I'll need to be alert to avoid, and then there'll be a few days of reinstalling all my applications.

I vaguely remember hearing of DVDs that provided Windows 7/64 in a moderately-updated state, speeding up the reloading process by at least a few hours. Are people on this forum familiar with those?

Exactly what security programs were used to scan the computer?

Kaspersky, MSE

Just exactly what Windows 7 are you using?

7/64 SP1, up to date with updates through last fall, when I lost confidence in my ability to keep MS from forcing Windows 10 on me

Do you have any backups or Clones?

I have good backups of all my data, but no clone that would allow for painless scrub-and-reload.

Do others have access to your computer?

No.
Also, you should know that I have probably found the original source of my problem, but not how to fix it. Yesterday I tried to write a new DVD of my recent data, and the DVD writer complained during the pre-write caching phase that one file had a bad handle. The DVD writer (Nero), thought this was non-critical, so I let it go ahead. During the write phase, Nero froze, possibly trying to copy this file, and I had to stop it from the Task Manager.
The file in question was I2CDEV.cpp, a file I had extracted from a GitHub ZIP file 8 months ago. Its claimed size on my disk was 56K, probably much bigger than it legitimately should be, and it showed up green (encrypted) in Windows Explorer. I can imagine ways of hiding malware between the declared EOF and the actual end of an ASCII file like <xxx>.cpp, although I'd never heard of this as a means of malpropagation before. I deleted this file; I'm sure I have it on a backup somewhere, if anyone wants it for forensic purposes.

I didn't describe my whole backup system; DVDs are a small part of it. I also use CrashPlan to provide minute-by-minute backup of data.
I hadn't thought about cloning before, but I'm glad that Layback Bear and (more forcefully) you brought it up. I will be looking into when I'm back to some sort of steady state.