Undocumented serious error (0x101a)

[Roadkil]

Ok. Just out of the blue nod32 av version 3.0.669.0 doesnt update and it spits out that error msg. undocumented serious error (0x101a) any idea why it would suddenly do that i have changed nothing in system in months.

[Marcos]

Originally Posted by Roadkil

Ok. Just out of the blue nod32 av version 3.0.669.0 doesnt update and it spits out that error msg. undocumented serious error (0x101a) any idea why it would suddenly do that i have changed nothing in system in months.

This error occurs if the kernel service cannot write to the system temp folder. Could you please check out if the system TEMP variable points to an existing folder, or whether the folder contains thousands of redundant temp files? If neither is the case, try checking permissions to that folder for the system account - it must have full permissions to that folder.

[viruscraft]

I have the same problem since I got up this morning.
I tried to clear the update cache , checked system TEMP variable and the permissions to TEMP folder but nothing useful.

BTW I didnt change any setting in system those days.

So any idea?

[Marcos]

Originally Posted by viruscraft

I have the same problem since I got up this morning.
I tried to clear the update cache , checked system TEMP variable and the permissions to TEMP folder but nothing useful.

BTW I didnt change any setting in system those days.

So any idea?

Could you please run Process Monitor, filter out entries from ekrn.exe, update EAV and then monitor what folder ekrn.exe is trying to write to? This should give you a clue where to search for the cause.

[TBacker]

Add two of my machines to the list.

I am responsible for a large cluster of machines running 3.0.650, two turned up with this error out of the blue. No changes have been made to those machines, so this "broke itself".

Stopped updating after 3343.

I will look into this further when I get into the office and give details if possible.

[viruscraft]

Originally Posted by Marcos

Could you please run Process Monitor, filter out entries from ekrn.exe, update EAV and then monitor what folder ekrn.exe is trying to write to? This should give you a clue where to search for the cause.

Thx,Marcos.

But the issue is resloved by a system reboot.

[Roadkil]

Thx Marcus,
It was fixed by a Vulcan Nerve Pinch of ekern.exe and egui.exe. then a restart of egui.