Aller au contenu

[VISTA] Analyse d'un rapport dump, gros problème !


rhcpaddict

Messages recommandés

Bonjour, depuis un certain temps, j'ai mon PC (Hp pavillon DV5-1130ef) qui plante sur un écran bleu (A problem has been detected...), j'ai fait une analyse de mon fichier dump avec Windbg mais bon pour résoudre le problème j'ai un peut de mal, je demande donc votre aide.

Voici le rapport :

Microsoft ® Windows Debugger Version 6.4.0007.2

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\Mini122008-04.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 Longhorn Kernel Version 6000 MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 6000.16754.x86fre.vista_gdr.080917-1612

Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10

Debug session time: Sat Dec 20 11:25:23.698 2008 (GMT+1)

System Uptime: 0 days 0:27:02.817

Loading Kernel Symbols

............................................................­...................

.........................................­..................................

Loading unloaded module list

...

Loading User Symbols

************************************************************­*******************

* *

* Bugcheck Analysis *

* *

************************************************************­*******************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, c0801698, ffff, 0}

Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+941 )

Followup: MachineOwner

---------

1: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

MEMORY_MANAGEMENT (1a)

# Any other values for parameter 1 must be individually examined.

Arguments:

Arg1: 00041790, The subtype of the bugcheck.

Arg2: c0801698

Arg3: 0000ffff

Arg4: 00000000

Debugging Details:

------------------

BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 820c1317 to 8204061e

STACK_TEXT:

a0f33bb8 820c1317 65000002 65037fff 86bee020 nt!MiDeleteVirtualAddresses+0x941

a0f33c88 820c0e50 86bee020 84d4ca08 9c284030 nt!MiRemoveMappedView+0x4a1

a0f33cb0 821e0e97 9c284030 00000000 ffffffff nt!MiRemoveVadAndView+0xe3

a0f33d14 821e0c25 86bee020 65000000 00000000 nt!MiUnmapViewOfSection+0x256

a0f33d34 8208caea ffffffff 65000000 01cceae8 nt!NtUnmapViewOfSection+0x55

a0f33d34 76f40f34 ffffffff 65000000 01cceae8 nt!KiFastCallEntry+0x12a

WARNING: Frame IP not in any known module. Following frames may be wrong.

01cce9f0 00000000 00000000 00000000 00000000 0x76f40f34

FOLLOWUP_IP:

nt!MiDeleteVirtualAddresses+941

8204061e 8bc3 mov eax,ebx

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MiDeleteVirtualAddresses+941

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b550

STACK_COMMAND: kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x1a_41790_nt!MiDeleteVirtualAddresses+941

BUCKET_ID: 0x1a_41790_nt!MiDeleteVirtualAddresses+941

Followup: MachineOwner

---------

Donc voilà, si vous pouvez m'aider a déchiffrer ce rapport et identifier mon problème ça serait sympa.

Merci.

Configuration: Windows Vista 32

Lien vers le commentaire
Partager sur d’autres sites

Merci beaucoup, voici le rapport :

Analysis

--------------------------------------------------------------------------------

Crash dumps are enabled for your computer.

On Sat 20/12/2008 09:48:03 your computer crashed

This was likely caused by the following module: dxgkrnl.sys

Bugcheck code: 0x1A (0x4000, 0x86CBA478, 0x20000, 0x23F538)

Error: MEMORY_MANAGEMENT

file path: C:\Windows\system32\drivers\dxgkrnl.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: DirectX Graphics Kernel

The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.

--------------------------------------------------------------------------------

Conclusion

--------------------------------------------------------------------------------

5 crash dumps have been found on your computer. Only 1 have been analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In the case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Reste plus qu'a trouver a quoi correspond dxgkrnl.sys...

Si vous avez des idées pour résoudre ce problème, n'hésitez pas, merci encore.

Lien vers le commentaire
Partager sur d’autres sites

Archivé

Ce sujet est désormais archivé et ne peut plus recevoir de nouvelles réponses.

×
×
  • Créer...