Home > OS >  Computer blue screen, turn to god for help to see the log
Computer blue screen, turn to god for help to see the log

Time:09-20


16.1: kd: x86 & gt; ! Analyze the -v
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* *
* Bugcheck Analysis *
* *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at An
Interrupt request level (IRQL) that is too high. This is
Under caused by drivers that have corrupted the system pool. Run the driver
Verifier against any new (or suspect) drivers, and if that doesn 't turn up
The culprit, then use gflags to enable the special pool.
The Arguments:
Arg1:000000000000 FFFF, referenced memory
Arg2:0000000000000002, IRQL
Arg3:0000000000000000, the value 0=read operation, 1=write operation
Arg4: fffff800041c96fb, address which referenced memory

Was Debugging Details:
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

* * * * * the Kernel symbols are WRONG. Both Please fix symbols to do analysis.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * *
* * * * * *
* * * Your debugger is not using the correct symbols * * *
* * * * * *
* * * In order for this command to work properly, your symbol path * * *
* * * must point to.. PDB files that have full type information. * * *
* * * * * *
* * * Certain. PDB files (to the as the public OS symbols) do not * * *
* * * contain the required information. Contact the group that * * *
* * * provided you with these symbols if you need this command to * * *
* * * work. * * *
* * * * * *
* * * Type referenced: nt! _KPRCB * * *
* * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * *
* * * * * *
* * * Your debugger is not using the correct symbols * * *
* * * * * *
* * * In order for this command to work properly, your symbol path * * *
* * * must point to.. PDB files that have full type information. * * *
* * * * * *
* * * Certain. PDB files (to the as the public OS symbols) do not * * *
* * * contain the required information. Contact the group that * * *
* * * provided you with these symbols if you need this command to * * *
* * * work. * * *
* * * * * *
* * * Type referenced: nt! KPRCB * * *
* * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * *
* * * * * *
* * * Your debugger is not using the correct symbols * * *
* * * * * *
* * * In order for this command to work properly, your symbol path * * *
* * * must point to.. PDB files that have full type information. * * *
* * * * * *
* * * Certain. PDB files (to the as the public OS symbols) do not * * *
* * * contain the required information. Contact the group that * * *
* * * provided you with these symbols if you need this command to * * *
* * * work. * * *
* * * * * *
* * * Type referenced: nt! _KPRCB * * *
* * * * * *
nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull
  • Related