killerbadd
New Member
- Joined
- Nov 2, 2010
- Messages
- 6
REGISTRY_ERROR (51)
Something has gone badly wrong with the registry. If a kernel debugger
is available, get a stack trace. It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.
It may occur due to a failure in a refresh operation, which is used only
in by the security system, and then only when resource limits are encountered.
Arguments:
Arg1: 00000001, (reserved)
Arg2: 8be1b6f0, (reserved)
Arg3: 00e0f000, depends on where Windows bugchecked...
REGISTRY_ERROR (51)
Something has gone badly wrong with the registry. If a kernel debugger
is available, get a stack trace. It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.
It may occur due to a failure in a refresh operation, which is used only
in by the security system, and then only when resource limits are encountered.
Arguments:
Arg1: 00000001, (reserved)
Arg2: 8be1b6f0, (reserved)
Arg3: 00e0f000, depends on where Windows bugchecked, may be pointer to hive
Arg4: 00000374, depends on where Windows bugchecked, may be return code of
HvCheckHive if the hive is corrupt.
Debugging Details:
------------------
[lang=nl]zaterdag is mijn pc op nieuw clean geinstalleerd en mijn bios staat op optimized defaults , heb ook geprobeerd mijn I5 zijn turbo boost uittezetten.[/lang]Hello and welcome.
Go to the bios settings. Load the Optimized Defaults and save.
Then clean install Windows if errors continue:
Don't use any registry cleaners at all, except Ccleaner.Code:REGISTRY_ERROR (51) Something has gone badly wrong with the registry. If a kernel debugger is available, get a stack trace. It can also indicate that the registry got an I/O error while trying to read one of its files, so it can be caused by hardware problems or filesystem corruption. It may occur due to a failure in a refresh operation, which is used only in by the security system, and then only when resource limits are encountered. Arguments: Arg1: 00000001, (reserved) Arg2: 8be1b6f0, (reserved) Arg3: 00e0f000, depends on where Windows bugchecked, may be pointer to hive Arg4: 00000374, depends on where Windows bugchecked, may be return code of HvCheckHive if the hive is corrupt. Debugging Details: ------------------