Probably caused by : ntoskrnl.exe ( nt+4bc18

meganightmare -  
 gri -
Bonjour, voilà mon soucis..
Depuis pas mal de temps j'ai toujours un problème que ce soit en fermant ou pendant certains jeux (pas tous), le pc plante et j'ai un bel écran bleu de vidage mémoire...

Le poblème à toujours persister même après plusiseurs formatages..

J'ai fais quelques recherches sur le net, mais en vain..

J'ai réussi à faire un dump et l'analyser avc Debugger, mais je n'en sais pas plus...

Voici l'analyse:
-----

* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {9d086240, 2, 0, 80522c18}

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

***** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+4bc18 )

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

Voilà, si quelqu'un pouvait m'aider..
Merci d'avance

2 réponses

Loic
 
Bonjour,

as tu réussi à régler ton pb lié au fichier ntoskrnl.exe. J'ai exactement le même pb et je ne sais plus quoi faire.

Merci.
0
gri
 
Bonjour

J'ai également le même problème

Avez-vous trouvé une solution ?

Merci
0