HI,
Been using Microsoft products since DOS, all incarnations, never had so much trouble with any as I've had with Windows 7. After fixing a multitude of errors I'm finally one away from a clean event log. Rant over!
From what I can gather it's something to do with the file size being too small and that editing the DWORD in registry may solve the problem just want to confirm before I do.
Looks like the research you did is correct.
Are you using any optimization software?
In nearly all cases, optimization software does not mix well with Windows 7 and causes errors like this to occur. Obviously, there are other factors that can cause errors to occur, but I usually ask the question when atypical errors show up in Event Viewer.
Could you please indicate which file sixe to go for?
BTW: does filesize=0 actually mean unlimited size?
A DWORD is a unsigned integer, and mostly the DWORD value of a registry key is used to set a BOOL value, either true or false; enabled or disabled. What registry key are you trying to change?
Circular Kernel Context Logger error: 0xC0000188
The key is:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\Circular Kernel Context Logger\MaxFileSize
According to advice in the thread, the filesize is too small and should be enlarged. In this context it is har to understand the MaxFileSize value zero. A hard condition to put on ANY real files ;-)
Knud
My registry key is set to 0, and I have had no problems.
The MaxFileSize DWORD key is used to set the maximum file size of the log file which is created by Autologger, 0 means unlimited file size, but it also seems to depend upon the type log mode your using.
Configuring and Starting an AutoLogger Session (Windows)
Thank you!
Quote