Possible causes for the page fault include the following events: This bug check is usually caused by drivers that have used improper memory addresses. You can use dx (display debugger object model expression), a debugger command, to display this: dx KiBugCheckDriver. If a driver that is responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver. This can be caused by:ĭereferencing a bad pointer (such as a NULL or freed pointer) while executing at or above DISPATCH_LEVEL.Īccessing pageable data at or above DISPATCH_LEVEL.Įxecuting pageable code at or above DISPATCH_LEVEL. Typically, when this error occurs, a driver has tried to access an address that is pageable (or that is completely invalid) while the interrupt request level (IRQL) was too high. To determine the cause requires the Windows debugger, programming experience and access to the source code for the faulting module. ![]() Use ln (list nearest symbols) on this address to see the name of the function. DRIVER_IRQL_NOT_LESS_OR_EQUAL parameters ParameterĪddress that referenced memory. ![]() If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
0 Comments
Leave a Reply. |