Forum Clubic

Bad pool caller et ntkrnlpa.exe

Bonjour,

je travaille sous Vista pro et j’ai régulièrement des écran bleus BAD POOL CALLER qui serait causé par ceci: ntkrnlpa.exe.

Voici ma config: E8400, 2Gb RAM 1066 crutial ballistix, Motherboard Gigabyte DS4 EX38, 8800GT MSI 512.

voici une copie du rapport rendu par le débugger windows:

Microsoft ® Windows Debugger Version 6.9.0003.113 X86
Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\minidump.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
********************************************­

  • Symbol loading may be unreliable without a symbol search path. *
  • Use .symfix to have the debugger choose a symbol path. *
  • After setting your symbol path, use .reload to refresh symbol locations. *
    ********************************************­
    Executable search path is:
    ***************************************************­
  • Symbols can not be loaded because symbol path is not initialized. *
  • The Symbol Path can be set by: *
  • using the _NT_SYMBOL_PATH environment variable. *
  • using the -y <symbol_path> argument when starting the debugger. *
  • using .sympath and .sympath+ *

Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Thu Oct 2 11:00:10.192 2008 (GMT+2)
System Uptime: 0 days 0:06:08.974


  • Symbols can not be loaded because symbol path is not initialized. *
  • The Symbol Path can be set by: *
  • using the _NT_SYMBOL_PATH environment variable. *
  • using the -y <symbol_path> argument when starting the debugger. *
  • using .sympath and .sympath+ *

Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols

Loading User Symbols
Loading unloaded module list


  • Bugcheck Analysis *

Use !analyze -v to get detailed debugging information.

BugCheck C2, {99, 84612498, 0, 0}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
***** Kernel symbols are WRONG. 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 (such 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 (such 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 (such 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 (such 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 (such 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 (such 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 (such 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 (such 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 ***




  • Symbols can not be loaded because symbol path is not initialized. *
  • The Symbol Path can be set by: *
  • using the _NT_SYMBOL_PATH environment variable. *
  • using the -y <symbol_path> argument when starting the debugger. *
  • using .sympath and .sympath+ *


  • Symbols can not be loaded because symbol path is not initialized. *
  • The Symbol Path can be set by: *
  • using the _NT_SYMBOL_PATH environment variable. *
  • using the -y <symbol_path> argument when starting the debugger. *
  • using .sympath and .sympath+ *

Probably caused by : ntkrnlpa.exe ( nt+d8681 )

Followup: MachineOwner
---------.

Pourriez-vous m’aider à savoir d’où ça vient?

merci.

Salut,
Tu a fait un scan anti-virus ?

oui, rien n’est détecté.

il faut dire que je viens de reformater…