The key name can be found in the raw stack.
Notice how often the reserved bugcheck parameter appears in our call stack? Interesting, it appears that the reserved parameter may be the address of the key’s registry hive which had been marked as modified. Since the stack contained some compiler optimisations, I’ve used CMKD’s stack unwind extension. Let’s check where the system bugchecked by examining the call stack. However, the bugcheck description does hint towards either filesystem corruption or hard disk failure. The documentation on this bugcheck is very sparse and the parameter description provides no conclusive information.
In by the security system, and then only when resource limits are encountered.Īrg3: 0000000005d96000, depends on where Windows bugchecked, may be pointer to hiveĪrg4: 0000000000000 374, depends on where Windows bugchecked, may be return code of It may occur due to a failure in a refresh operation, which is used only Hardware problems or filesystem corruption. It can also indicate that the registry gotĪn I/O error while trying to read one of its files, so it can be caused by Something has gone badly wrong with the registry.
0 kommentar(er)
