Vista Blue Screen sous World Of Warcraft

[Laurenzo]

Salut,

Je demande votre aide pour un problème, mon ordinateur n'arrete pas de faire des blue screen lorsque je suis sous wow, çà arrive tout les 15-30min et c'est vraiment embêtant.

Mon PC n'a même pas 10jours je l'ai deja ramener au magasin ou ils l'on analyser et il n'a aucun problème pourtant il bug toujours et que sous wow et pas d'autre jeu.

lors du bleu screen il parle de dump mémory j'ai réussi a recuperer une image du noyau de l'erreur.


Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:UserslaurentDesktopMEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.amd64fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0xfffff800`01e1f000 PsLoadedModuleList = 0xfffff800`01fe4db0
Debug session time: Mon Jul 6 11:47:09.284 2009 (GMT+2)
System Uptime: 0 days 0:31:34.306
*********************************************************************
* 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd9018). Type ".hh dbgerr001" for details
Loading unloaded module list
..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff800036b2043, 1, fffff80001e9b8f7, 2}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for portcls.sys -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ks.sys -
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for ksthunk.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Page b3f00 not present in the dump file. Type ".hh dbgerr004" for details
*************************************************************************
*** ***
*** ***
*** 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 : portcls.sys ( portcls!PcNewInterruptSync+a83d )

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


J'ai pas réussi a prendre une photo du blue screen je vais essayer.
Voila si certains peuvent m'aider ca serais sympas.

Cordialement Laurenzo.

[georgiou]

Concernant l'écran bleu, pas besoin de photo. Désactive le redémarrage automatique (Panneau de Configuration -> Système -> Paramètres système avancés -> Démarrage et Récupération -> Paramètres ->Redémarrer automatiquement). Ensuite tu pourras nous communiquer le code erreur de la forme 0x0000008E.

Tu as mis les pilotes de ta carte graphique à jour ?

[Laurenzo]

j'ai deja désactiver pour faire la photo mais pas de bleu screen encore ^^

sinon normalement les pilotes sont en a jour quand je fait rechercher la derniere version des pilotes il me dit que la derniere version est deja installer.

Sinon avec la résolution des problemes windows j'ai ca :

Signature du problème
Nom d'événement du problème : BlueScreen
Version du système: 6.0.6001.2.1.0.768.3
Identificateur de paramètres régionaux: 1036

Fichiers facilitant la description du problème (certains fichiers ne sont peut-être plus disponibles)
Mini070609-01.dmp
sysdata.xml
Version.txt

Afficher une copie temporaire de ces fichiers
Avertissement : Si un virus ou une autre menace à la sécurité a causé le problème, l'ouverture d'une copie des fichiers pourrait endommager votre ordinateur.

Informations complémentaires sur le problème
BCCode: 50
BCP1: FFFFF800036B2043
BCP2: 0000000000000001
BCP3: FFFFF80001E9B8F7
BCP4: 0000000000000002
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1
Informations du serveur : 0a09a7a8-5ddc-4adc-a781-c5835700cdfa

[georgiou]

sinon normalement les pilotes sont en a jour quand je fait rechercher la derniere version des pilotes il me dit que la derniere version est deja installer.

Ca ne fonctionne pas ça. Rends-toi ici :
==> http://www.nvidia.fr/Download/index.aspx?lang=fr

Pense à installer le SP2 de Vista.

[Laurenzo]

oki je suis en train de dl le SP2 de vista par contre pour les pilote Nvidia je suis deja allez sur le site mais je ne sais pas prendre quelle pilote du moins j'ai peur de faire une connerie ^^

pour infos carte graphique NVIDIA Geforce 9800M GTS je pense donc a :

Type de produit: Geforce
Série de produits: Geforce 9M Series
Système d'exploitation: Widows vista 64bit
Langue: Francais

c'est bien ca et apres je fait Pilotes graphiques?

[georgiou]

Oui, si c'est pas la bonne version, ça ne s'installera pas.

[Laurenzo]

donc blue screen ca a mis

PAGE_FAULT_IN_NONPAGED_AREA

STOP : 0X00000050. (0xFFFFF800036AB043, 0x0000000000000001, 0xFFFFF80001E918F7, 0x0000000000000002)

apres il parle de crash dump .....
physical memory

[Laurenzo]

la version des mes pilotes est 176.89 et la dernière qu'il y a que je suis en train de dl est la 186.03 je pense qu'une fois que j'aurais mis les pilotes a jour et installer le SP2 je n'aurais plus de problème je vous tiendrais au courant des que ça seras fait et si j'ai encore ou pas des problèmes.

En tout cas un grand merci pour ton aide Georgiou.