blue screen

Recherche :

Mot : Pseudo : Filtrer
Bas de page
Auteur	Sujet : blue screen

magricop

Salut,
Je suis perdu j'ai eu 3 bluescreen avec trois jeux différent (assassin's creed, mass effect et gear of war).
Je ne sait pas dechiffrer ce charabia mon systeme est tout neuf et pas o/c.
Asus p5e
Q9450 boite
ddr 2 g skill f2 pc 6400 (2* 2go en dual channel)
HD 4870 POWER COLOR 512 MB
Boitier ANTEC P182
vantirad cpu Asus Arctic Square
alim HKC USP 7630 630 WATT

Merci d'avance pour votre aide a tous.

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1036

Files that help describe the problem (some files may no longer be available)
Mini083008-01.dmp
sysdata.xml
Version.txt

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: 50
BCP1: A298E314
BCP2: 00000001
BCP3: 8A77753B
BCP4: 00000000
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Publicité

Mad_noob

Salut je pense que cela vient de ta carte graphique... essaye de voir ce que cela fait sur un autre PC?

Sinon tes composant on l'air d'être fait pour aller ensemble (bien proportionné)

Le mieux serait de pouvoir interprêter ce fichier Mini083008-01.dmp créé lors du crash et stocké dans C:\Windows\Minidump avec le débuggeur fourni par microsoft et te dirait quest ce qui est probablement en cause...

Je vois que tu as 4go de ram as tu une version 64Bit de vista? et est ce que ta carte mère P5E supporte bien les barette de 2Go unité sur un port de ram!

Je vais jetter un oeil à tout ça...

Message cité 1 fois
Message édité par Mad_noob le 31-08-2008 à 00:07:58

---------------
Topic Achat/Vente - Ancien Feed-back

magricop

Mad_noob a écrit :

Merci Mad_noob de m'avoir repondu,

je n'ai pas d'autre pc sous la main malheureusement, lost planet lui semble tourner des heures sans l'ombre d'un souci.
J'ai vista 32 bits qui lui ne prend en charge que 3,3 go max je crois, mais selon le vendeur qui me l'a assemblé il était preferable de prendre 2 barrettes de 2 go pour qu'elle fonctionne en dual channel il devait savoir a quoi s'en tenir avec cette carte mere.
Je vais essayé ce que tu m'a suggerer et je te tient au courant.
Encore une fois merci.

Mad_noob

[:ab614]

Message cité 1 fois

---------------
Topic Achat/Vente - Ancien Feed-back

magricop

Mad_noob a écrit :

[:ab614]

J'ai fait quelque recherche pour utiliser win dbg et j'ai pu ouvrir le fichier dmp,
j'ai pas les notion pour comprendre ou dechiffrer les ligne de texte qu'il m'a afficher peut etre tu peut y voir plus claire que moi.
Merci d'avance.

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

Loading Dump File [C:\Users\Ammouri family\AppData\Local\Temp\WER9781.tmp\Mini083008-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: "srv*c:\cache*http://msdl.microsoft.com/download/symbols;"
Executable search path is:
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 Server 2008 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81c3d000 PsLoadedModuleList = 0x81d54c70
Debug session time: Sat Aug 30 06:41:41.940 2008 (GMT+2)
System Uptime: 0 days 11:58:31.306
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 50, {a298e314, 1, 8a77753b, 0}

*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.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 ***
*** ***
*************************************************************************
Probably caused by : dxgkrnl.sys ( dxgkrnl+2c53b )

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: a298e314, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 8a77753b, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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

***** 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 ***
*** ***
*************************************************************************

AUTOBUG_OS_SKU: 1

MODULE_NAME: dxgkrnl

FAULTING_MODULE: 81c3d000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47918c64

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
a298e314

FAULTING_IP:
dxgkrnl+2c53b
8a77753b ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 81c97bb4 to 81ce2155

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
d833c93c 81c97bb4 00000001 a298e314 00000000 nt+0xa5155
d833c954 8a77753b badb0d00 9fa08434 84ed21c0 nt+0x5abb4
d833c9d4 8a77815b a8c56560 00000000 86259da0 dxgkrnl+0x2c53b
d833c9f0 8a7778eb 86259da0 00000000 893006a0 dxgkrnl+0x2d15b
d833ca58 8a7760ea d833cb88 d833cb28 d833cb54 dxgkrnl+0x2c8eb
d833ca70 8a77613d d833cb4c 893006a0 893006a0 dxgkrnl+0x2b0ea
d833ca8c 8a76c94a 89304be0 86b658b8 d833cacc dxgkrnl+0x2b13d
d833ca9c 8a74e9a1 893006a0 893006a0 86b76a18 dxgkrnl+0x2194a
d833cacc 8a76c876 86b84000 d833caf0 86b658b8 dxgkrnl+0x39a1
d833caf4 8a777e74 013006a0 86c5e000 86c5e000 dxgkrnl+0x21876
d833cb0c 8a777d97 86b658b8 8a7760ca d833cb4c dxgkrnl+0x2ce74
d833cb38 8a77802e d833cb4c a8c56560 86259da0 dxgkrnl+0x2cd97
d833cb70 8a777c6f d833cb88 00000000 a29131a8 dxgkrnl+0x2d02e
d833cbac 8a7783bd 00000000 00000000 a388d5b8 dxgkrnl+0x2cc6f
d833cbcc 8a779154 a29131a8 00000000 00000000 dxgkrnl+0x2d3bd
d833cc38 8a779955 00000000 00000000 a6bf0890 dxgkrnl+0x2e154
d833cc94 8a779eb2 d833ccf0 00000001 52455f69 dxgkrnl+0x2e955
d833cd58 81c94a7a 0fa4fe68 0fa4fe78 76e19a94 dxgkrnl+0x2eeb2
d833cd64 76e19a94 badb0d00 0fa4fe58 00000000 nt+0x57a7a
d833cd68 badb0d00 0fa4fe58 00000000 00000000 0x76e19a94
d833cd6c 0fa4fe58 00000000 00000000 00000000 0xbadb0d00
d833cd70 00000000 00000000 00000000 00000000 0xfa4fe58

STACK_COMMAND: kb

FOLLOWUP_IP:
dxgkrnl+2c53b
8a77753b ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgkrnl+2c53b

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: dxgkrnl.sys

BUCKET_ID: WRONG_SYMBOLS

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: a298e314, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 8a77753b, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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

***** 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 ***
*** ***
*************************************************************************

AUTOBUG_OS_SKU: 1

MODULE_NAME: dxgkrnl

FAULTING_MODULE: 81c3d000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47918c64

WRITE_ADDRESS: a298e314

FAULTING_IP:
dxgkrnl+2c53b
8a77753b ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 81c97bb4 to 81ce2155

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
d833c93c 81c97bb4 00000001 a298e314 00000000 nt+0xa5155
d833c954 8a77753b badb0d00 9fa08434 84ed21c0 nt+0x5abb4
d833c9d4 8a77815b a8c56560 00000000 86259da0 dxgkrnl+0x2c53b
d833c9f0 8a7778eb 86259da0 00000000 893006a0 dxgkrnl+0x2d15b
d833ca58 8a7760ea d833cb88 d833cb28 d833cb54 dxgkrnl+0x2c8eb
d833ca70 8a77613d d833cb4c 893006a0 893006a0 dxgkrnl+0x2b0ea
d833ca8c 8a76c94a 89304be0 86b658b8 d833cacc dxgkrnl+0x2b13d
d833ca9c 8a74e9a1 893006a0 893006a0 86b76a18 dxgkrnl+0x2194a
d833cacc 8a76c876 86b84000 d833caf0 86b658b8 dxgkrnl+0x39a1
d833caf4 8a777e74 013006a0 86c5e000 86c5e000 dxgkrnl+0x21876
d833cb0c 8a777d97 86b658b8 8a7760ca d833cb4c dxgkrnl+0x2ce74
d833cb38 8a77802e d833cb4c a8c56560 86259da0 dxgkrnl+0x2cd97
d833cb70 8a777c6f d833cb88 00000000 a29131a8 dxgkrnl+0x2d02e
d833cbac 8a7783bd 00000000 00000000 a388d5b8 dxgkrnl+0x2cc6f
d833cbcc 8a779154 a29131a8 00000000 00000000 dxgkrnl+0x2d3bd
d833cc38 8a779955 00000000 00000000 a6bf0890 dxgkrnl+0x2e154
d833cc94 8a779eb2 d833ccf0 00000001 52455f69 dxgkrnl+0x2e955
d833cd58 81c94a7a 0fa4fe68 0fa4fe78 76e19a94 dxgkrnl+0x2eeb2
d833cd64 76e19a94 badb0d00 0fa4fe58 00000000 nt+0x57a7a
d833cd68 badb0d00 0fa4fe58 00000000 00000000 0x76e19a94
d833cd6c 0fa4fe58 00000000 00000000 00000000 0xbadb0d00
d833cd70 00000000 00000000 00000000 00000000 0xfa4fe58

STACK_COMMAND: kb

FOLLOWUP_IP:
dxgkrnl+2c53b
8a77753b ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgkrnl+2c53b

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: dxgkrnl.sys

BUCKET_ID: WRONG_SYMBOLS

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: a298e314, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 8a77753b, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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

***** 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 ***
*** ***
*************************************************************************

AUTOBUG_OS_SKU: 1

MODULE_NAME: dxgkrnl

FAULTING_MODULE: 81c3d000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47918c64

WRITE_ADDRESS: a298e314

FAULTING_IP:
dxgkrnl+2c53b
8a77753b ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 81c97bb4 to 81ce2155

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
d833c93c 81c97bb4 00000001 a298e314 00000000 nt+0xa5155
d833c954 8a77753b badb0d00 9fa08434 84ed21c0 nt+0x5abb4
d833c9d4 8a77815b a8c56560 00000000 86259da0 dxgkrnl+0x2c53b
d833c9f0 8a7778eb 86259da0 00000000 893006a0 dxgkrnl+0x2d15b
d833ca58 8a7760ea d833cb88 d833cb28 d833cb54 dxgkrnl+0x2c8eb
d833ca70 8a77613d d833cb4c 893006a0 893006a0 dxgkrnl+0x2b0ea
d833ca8c 8a76c94a 89304be0 86b658b8 d833cacc dxgkrnl+0x2b13d
d833ca9c 8a74e9a1 893006a0 893006a0 86b76a18 dxgkrnl+0x2194a
d833cacc 8a76c876 86b84000 d833caf0 86b658b8 dxgkrnl+0x39a1
d833caf4 8a777e74 013006a0 86c5e000 86c5e000 dxgkrnl+0x21876
d833cb0c 8a777d97 86b658b8 8a7760ca d833cb4c dxgkrnl+0x2ce74
d833cb38 8a77802e d833cb4c a8c56560 86259da0 dxgkrnl+0x2cd97
d833cb70 8a777c6f d833cb88 00000000 a29131a8 dxgkrnl+0x2d02e
d833cbac 8a7783bd 00000000 00000000 a388d5b8 dxgkrnl+0x2cc6f
d833cbcc 8a779154 a29131a8 00000000 00000000 dxgkrnl+0x2d3bd
d833cc38 8a779955 00000000 00000000 a6bf0890 dxgkrnl+0x2e154
d833cc94 8a779eb2 d833ccf0 00000001 52455f69 dxgkrnl+0x2e955
d833cd58 81c94a7a 0fa4fe68 0fa4fe78 76e19a94 dxgkrnl+0x2eeb2
d833cd64 76e19a94 badb0d00 0fa4fe58 00000000 nt+0x57a7a
d833cd68 badb0d00 0fa4fe58 00000000 00000000 0x76e19a94
d833cd6c 0fa4fe58 00000000 00000000 00000000 0xbadb0d00
d833cd70 00000000 00000000 00000000 00000000 0xfa4fe58

STACK_COMMAND: kb

FOLLOWUP_IP:
dxgkrnl+2c53b
8a77753b ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgkrnl+2c53b

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: dxgkrnl.sys

BUCKET_ID: WRONG_SYMBOLS

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: a298e314, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 8a77753b, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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

***** 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 ***
*** ***
*************************************************************************

AUTOBUG_OS_SKU: 1

MODULE_NAME: dxgkrnl

FAULTING_MODULE: 81c3d000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47918c64

WRITE_ADDRESS: a298e314

FAULTING_IP:
dxgkrnl+2c53b
8a77753b ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 81c97bb4 to 81ce2155

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
d833c93c 81c97bb4 00000001 a298e314 00000000 nt+0xa5155
d833c954 8a77753b badb0d00 9fa08434 84ed21c0 nt+0x5abb4
d833c9d4 8a77815b a8c56560 00000000 86259da0 dxgkrnl+0x2c53b
d833c9f0 8a7778eb 86259da0 00000000 893006a0 dxgkrnl+0x2d15b
d833ca58 8a7760ea d833cb88 d833cb28 d833cb54 dxgkrnl+0x2c8eb
d833ca70 8a77613d d833cb4c 893006a0 893006a0 dxgkrnl+0x2b0ea
d833ca8c 8a76c94a 89304be0 86b658b8 d833cacc dxgkrnl+0x2b13d
d833ca9c 8a74e9a1 893006a0 893006a0 86b76a18 dxgkrnl+0x2194a
d833cacc 8a76c876 86b84000 d833caf0 86b658b8 dxgkrnl+0x39a1
d833caf4 8a777e74 013006a0 86c5e000 86c5e000 dxgkrnl+0x21876
d833cb0c 8a777d97 86b658b8 8a7760ca d833cb4c dxgkrnl+0x2ce74
d833cb38 8a77802e d833cb4c a8c56560 86259da0 dxgkrnl+0x2cd97
d833cb70 8a777c6f d833cb88 00000000 a29131a8 dxgkrnl+0x2d02e
d833cbac 8a7783bd 00000000 00000000 a388d5b8 dxgkrnl+0x2cc6f
d833cbcc 8a779154 a29131a8 00000000 00000000 dxgkrnl+0x2d3bd
d833cc38 8a779955 00000000 00000000 a6bf0890 dxgkrnl+0x2e154
d833cc94 8a779eb2 d833ccf0 00000001 52455f69 dxgkrnl+0x2e955
d833cd58 81c94a7a 0fa4fe68 0fa4fe78 76e19a94 dxgkrnl+0x2eeb2
d833cd64 76e19a94 badb0d00 0fa4fe58 00000000 nt+0x57a7a
d833cd68 badb0d00 0fa4fe58 00000000 00000000 0x76e19a94
d833cd6c 0fa4fe58 00000000 00000000 00000000 0xbadb0d00
d833cd70 00000000 00000000 00000000 00000000 0xfa4fe58

STACK_COMMAND: kb

FOLLOWUP_IP:
dxgkrnl+2c53b
8a77753b ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgkrnl+2c53b

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: dxgkrnl.sys

BUCKET_ID: WRONG_SYMBOLS

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

3: kd> g
^ No runnable debuggees error in 'g'
3: kd> lmvm dxgkrnl
start end module name
8a74b000 8a7ea000 dxgkrnl T (no symbols)
Loaded symbol image file: dxgkrnl.sys
Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
Image name: dxgkrnl.sys
Timestamp: Sat Jan 19 06:36:36 2008 (47918C64)
CheckSum: 0009A1A8
ImageSize: 0009F000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

Mad_noob

lol la prochaine fois poste pas un message long comme ça parce que si un modo passe c'est la merde... Dans ce cas là utilise plustôt un spoiler... Ensuite tu n'as pas les bonnes librairies de symbole pour que le debugger les utilise il faut aller les télécharger sur le site de microsoft ensuite dans windebugger il faut le faire pointer ver là ou tu as installé les symbols a proprement parlé...

Message cité 1 fois

---------------
Topic Achat/Vente - Ancien Feed-back

magricop

Mad_noob a écrit :

Lol dsl j'y cour merci :lol:

Message cité 1 fois

magricop

magricop a écrit :

Lol dsl j'y cour merci :lol:

Je ne m'en sort pas avec win debug j'ai instaler les pack de symboles et indiquer le chemin de ces dernier a win dbg rien n'y fait :??:

Message cité 1 fois

magricop

magricop a écrit :

Je ne m'en sort pas avec win debug j'ai instaler les pack de symboles et indiquer le chemin de ces dernier a win dbg rien n'y fait :??:

Bonjour,
j'ai compris comment faire finalement je crois, voila cce que j'ai pu en tirer :

Spoiler :

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

Loading Dump File [C:\Users\Ammouri family\AppData\Local\Temp\WERABCD.tmp\Mini083008-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Kernel base = 0x81c3d000 PsLoadedModuleList = 0x81d54c70
Debug session time: Sat Aug 30 06:41:41.940 2008 (GMT+2)
System Uptime: 0 days 11:58:31.306
Loading Kernel Symbols
................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {a298e314, 1, 8a77753b, 0}

Could not read faulting driver name
Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0 )

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: a298e314, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 8a77753b, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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

Could not read faulting driver name

AUTOBUG_OS_SKU: 1

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d74868
Unable to read MiSystemVaType memory at 81d54420
a298e314

FAULTING_IP:
dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0
8a77753b 895104 mov dword ptr [ecx+4],edx

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: iw3sp.exe

CURRENT_IRQL: 0

TRAP_FRAME: d833c954 -- (.trap 0xffffffffd833c954)
ErrCode = 00000002
eax=a8c56674 ebx=00000000 ecx=a298e310 edx=9fa08434 esi=8ea0a278 edi=a8c56560
eip=8a77753b esp=d833c9c8 ebp=d833c9d4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+0xa0:
8a77753b 895104 mov dword ptr [ecx+4],edx ds:0023:a298e314=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c97bb4 to 81ce2155

STACK_TEXT:
d833c93c 81c97bb4 00000001 a298e314 00000000 nt!MmAccessFault+0x10a
d833c93c 8a77753b 00000001 a298e314 00000000 nt!KiTrap0E+0xdc
d833c9d4 8a77815b a8c56560 00000000 86259da0 dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+0xa0
d833c9f0 8a7778eb 86259da0 00000000 893006a0 dxgkrnl!VIDMM_GLOBAL::NotifyAllocationEviction+0x37
d833ca58 8a7760ea d833cb88 d833cb28 d833cb54 dxgkrnl!VIDMM_GLOBAL::ProcessDeferredCommand+0x392
d833ca70 8a77613d d833cb4c 893006a0 893006a0 dxgkrnl!VidMmiProcessSystemCommand+0x20
d833ca8c 8a76c94a 89304be0 86b658b8 d833cacc dxgkrnl!VidSchiSubmitSystemCommand+0x2d
d833ca9c 8a74e9a1 893006a0 893006a0 86b76a18 dxgkrnl!VidSchiSubmitQueueCommand+0x7b
d833cacc 8a76c876 86b84000 d833caf0 86b658b8 dxgkrnl!VidSchiSubmitQueueCommandDirect+0x1ae
d833caf4 8a777e74 013006a0 86c5e000 86c5e000 dxgkrnl!VidSchiSubmitCommandPacketToQueue+0x171
d833cb0c 8a777d97 86b658b8 8a7760ca d833cb4c dxgkrnl!VidSchSubmitSystemCommand+0xa6
d833cb38 8a77802e d833cb4c a8c56560 86259da0 dxgkrnl!VIDMM_GLOBAL::QueueSystemCommandAndWait+0x40
d833cb70 8a777c6f d833cb88 00000000 a29131a8 dxgkrnl!VIDMM_GLOBAL::QueueDeferredCommandAndWait+0x3c
d833cbac 8a7783bd 00000000 00000000 a388d5b8 dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+0x8d
d833cbcc 8a779154 a29131a8 00000000 00000000 dxgkrnl!VIDMM_GLOBAL::CloseAllocation+0x37
d833cc38 8a779955 00000000 00000000 a6bf0890 dxgkrnl!DXGDEVICE::DestroyAllocations+0x176
d833cc94 8a779eb2 d833ccf0 00000001 52455f69 dxgkrnl!DXGDEVICE::DestroyAllocation+0x28a
d833cd58 81c94a7a 0fa4fe68 0fa4fe78 76e19a94 dxgkrnl!DxgkDestroyAllocation+0x538
d833cd58 76e19a94 0fa4fe68 0fa4fe78 76e19a94 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0fa4fe78 00000000 00000000 00000000 00000000 0x76e19a94

STACK_COMMAND: kb

FOLLOWUP_IP:
dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0
8a77753b 895104 mov dword ptr [ecx+4],edx

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47918c64

FAILURE_BUCKET_ID: 0x50_W_dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0

BUCKET_ID: 0x50_W_dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0

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

3: kd> .trap 0xffffffffd833c954
ErrCode = 00000002
eax=a8c56674 ebx=00000000 ecx=a298e310 edx=9fa08434 esi=8ea0a278 edi=a8c56560
eip=8a77753b esp=d833c9c8 ebp=d833c9d4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+0xa0:
8a77753b 895104 mov dword ptr [ecx+4],edx ds:0023:a298e314=????????
3: kd> lmvm dxgkrnl
start end module name
8a74b000 8a7ea000 dxgkrnl (pdb symbols) c:\symbols\dxgkrnl.pdb\2F308EDE36614CBAAE4C5F47132D6D312\dxgkrnl.pdb
Loaded symbol image file: dxgkrnl.sys
Mapped memory image file: c:\symbols\dxgkrnl.sys\47918C649f000\dxgkrnl.sys
Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
Image name: dxgkrnl.sys
Timestamp: Sat Jan 19 06:36:36 2008 (47918C64)
CheckSum: 0009A1A8
ImageSize: 0009F000
File version: 6.0.6001.18000
Product version: 6.0.6001.18000
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgkrnl.sys
OriginalFilename: dxgkrnl.sys
ProductVersion: 6.0.6001.18000
FileVersion: 6.0.6001.18000 (longhorn_rtm.080118-1840)
FileDescription: DirectX Graphics Kernel
LegalCopyright: © Microsoft Corporation. All rights reserved.
3: kd> .trap 0xffffffffd833c954
ErrCode = 00000002
eax=a8c56674 ebx=00000000 ecx=a298e310 edx=9fa08434 esi=8ea0a278 edi=a8c56560
eip=8a77753b esp=d833c9c8 ebp=d833c9d4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+0xa0:
8a77753b 895104 mov dword ptr [ecx+4],edx ds:0023:a298e314=????????

magricop

A l'aiiiiiiiiiiiiddddddddddeee ca plante sur tout les jeux maintenant!

Publicité

magricop

Bon bah tant pis merci quand meme.

magricop

Ultimate boot cd, une vrai merveille!
Ma ram etait defectueuse apparament, je l'ai changer et terminer.

armagad

perso j essayerai avec seulement 2 Go de ram pour voir ce que ca donne. Le probleme maintenant que qu avec ces crachs il peux avoir des fichiers corrompus

Cela fait quelque temps j avais eu un probleme de reboot egalement car j ai mis 4 * 512 ram et la carte mere n arrrive pas a gere les 4 slot de ram, avec 3 tout fonctionne avec 4 ca plante.

magricop

En faite j'ai 2 * 2go et a mem test elles m'avait afficher plus de 1200 erreur, avec les nouvelles sur 4 heure de test 0 erreur et depuis j'ai plus un seul blue screen (je prie pour que ca dure).
Si ca replante je ferais le test avec une barette pour voir.
Merci pour ta reponse armagad.

FORUM HardWare.fr

Windows & Software

Win Vista

blue screen

Sujets relatifs
Comment enlever Blue Screen	Erreur blue Screen
Blue screen de la mort : Unmountable_boot_volume	[PB] Blue screen a l'installation de windows [KERNEL_DATA_INPAGE_ERRO]
erreur blue screen suite redemarrage pc	BSOD (Blue Screen Of Death) erreur introuvable!
Blue screen suite au mise à jour de Vista (résolu)	Blue Screen 4 à 5 fois par jours
Blue screen > ai je identifié mon soucis ?	WinXP: Blue screen de la mort à l'install ou dans les premiers boot
Plus de sujets relatifs à : blue screen

Page générée en 0.078 secondes