Event 5, Kernel-General

[intzepatorii]

Hi,

I gave up googling and I remembered this great site...

I have a problem, I found a serious error among the Administrative Events:

{Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\SOFTWARE' was corrupted and it has been recovered. Some data might have been lost.

xml:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

<Provider Name="Microsoft-Windows-Kernel-General" Guid="{A68CA8B7-004F-D7B6-A698-07E2DE0F1F5D}" />

<EventID>5</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000000</Keywords>

<TimeCreated SystemTime="2014-04-13T15:34:52.843750000Z" />

<EventRecordID>1362621</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="408" />

<Channel>System</Channel>

<Computer> </Computer>

<Security UserID="S-1-5-18" />

</System>

- <EventData>

<Data Name="FinalStatus">0x8000002a</Data>

<Data Name="ExtraStringLength">36</Data>

<Data Name="ExtraString">\SystemRoot\System32\Config\SOFTWARE</Data>

</EventData>

</Event>

Can you please help solving it please?

I already ran sfc /scannow but without result.

Thanks!

intzepatorii

[nitroshift]

How often does it happen? Is it a singular occurrence or does it happen every time the PC is powered on? Please provide more details.

nitroshift

[intzepatorii]

it happens every time the PC is powered on... for about one month.

[bphlpt]

And then it quit happening? Everything is fine now?

Cheers and Regards

[intzepatorii]

And then it quit happening? Everything is fine now?

Cheers and Regards

no, it is still happening with every login.

performance is not affected but I think the boot could be faster without the hive recovering.

also please note this is a red event.

[nitroshift]

Since it happens every time you power on the PC, it means that something else is causing the corruption. In order to get to the bottom of this, first of all please make sure the HDD is in good condition. Run a health check on your HDD using the appropriate software from the manufacturer of the HDD.

nitroshift

[intzepatorii]

Since it happens every time you power on the PC, it means that something else is causing the corruption. In order to get to the bottom of this, first of all please make sure the HDD is in good condition. Run a health check on your HDD using the appropriate software from the manufacturer of the HDD.

nitroshift

thanks a lot.

I ran a quick Hdtune test recently and it was OK.

I will perform it thouroughly next time but S.M.A.R.T. also says it is OK...

I'll try also to install software from HDD manufacturer.

Happy Easter!

[intzepatorii]

ran checkdisk, installed seatools.

the drive passed all tests... maybe it's because of the hardware change, what do you think?...

[dencorso]

I have a question: isn't a Kernel-General higher ranked than a Lieutenant-General ?

And, if so, wouldn't a plain Colonel do?

[nitroshift]

What EXACTLY do you mean by hardware change?

nitroshift

[intzepatorii]

What EXACTLY do you mean by hardware change?

nitroshift

I have upgraded the motherboard, processor and memory...

But it's not that, I have changed them on 03.03 and the problem occurred first on 26.03...

[nitroshift]

I'm placing my bet on uninstalled drivers before changing hardware causing this. Now again... what is holding you back from a fresh install?

nitroshift

[intzepatorii]

installing again the 3rd party software considering the Windows is running otherwise very well... about 4 columns at the Programs and features section.

I think I have found the problem though:Test 11, Bit fade Test from Memtest86, v5.01 is showing thousand of errors.

Do you think it could be this?

Thanks...

[nitroshift]

What happens if you take out the faulty memory module? Any more errors in the event log?

nitroshift

[jaclaz]

The {A68CA8B7-004F-D7B6-A698-07E2DE0F1F5D} is Windows Time Service.

Cannot say if connected, but here:

http://superuser.com/questions/359180/windows-7-clock-jumps-back-about-every-hour-internet-disconnects

a similar error was solved replacing the motherboard battery.

I would check anyway the Windows Time Service, like stopping it, unregister it, re-registering and re-starting it, and/or keeping it temporarily logged, see:

http://blogs.technet.com/b/industry_insiders/archive/2006/08/29/w32-tm-service.aspx

jaclaz