Bluescreen, impossible de trouvé le probleme, fichier dump
Bluescreen, impossible de trouvé le probleme, fichier dump - Matériels & problèmes divers - Hardware
Marsh Posté le 31-05-2010 à 16:43:53
p5gz-mx----> ddr2 en 533mhz max
Je post au cas ou cela interresserais quelqu un.... 
Sujets relatifs:
- Problème graveur lg qui ne lit pas les cd
- Problème de drivers carte son => écran bleu
- ati 3650 catalyst 8.9 probleme
- Problème de détection de disque dur
- Problème de débits sur RAID 0 Sil3112
- Probleme avec le SATA sous install W2000
- Probleme carte graphique ?? ou autre ??
- [résolu] Problème de secteurs non trouvés
- problème fps
- Problème de son avec kit 5.1
Marsh Posté le 07-10-2008 à 09:56:28
Bonjour, je viens ici dans le dernier espoirs de trouvé un réponse à un probleme de bluescreen.
voici le contexte :
CM : asus P5GZ-MX
Mem : kingston 1go 667 MHz ( PC2-5300 ) ddr2
DD : 80 / 160 go sata
lect cd / graveur
(ordi du boulot)
J'avais des crashs de systeme assez fréquents et de manière totalement aléatoire.
j'ai voulu reformaté seulement impossible d'arrivé a terminé une seul installation sans avoir se crash lors de l'installation
- 2 barettes de mémoires testé (512mo d'origine et une neuve 1go pour la remplacé)
- 2 disques SATA
- Remplacement d'alim
- Remplacement de lecteurs / napes
Testé avec 4 windows XP différents :
- Windows XP SP3 corp (officiel)
- Windows XP trust3 (celui-ci marché avant sur cet ordinateur)
- Windows XP SP1 "maxdata" (officiel)
- Windows XP SP3 corp + intégrations des drivers du PC
Rien n'y fait!, Le seul Windows qui a passé et le Maxdata, et d'apres mon impression se probleme de mémoire reviens à partir du moment ou j'installe le SP3, à partir de la il et impossible d'arrivé a faire quoi que se sois sans un crash toutes les minutes.
Avant ces crash il n'y avais pas de SP3 sur mon Windows, seulement apres test sur un autre ordinateur qui contient exactement le même matériel, il n'y as pas de probleme...
Bref j'ai vraiment tout essayé (remplacement matériels, logiciels, reglages du bios, maj des drivers....) ceci n'est qu'un apercu
la seul solution non testé et que je ne métrise pas vraiment et la lecture du fichier "Minidump" mais cela ne m'aide pas vraiment alors je viens demandé si quelqu'un arriverais à y interprété quelques chose :
dump complet
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [Z:\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available
************************************************************
WARNING: Dump file has been truncated. Data may be missing.
************************************************************
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3.5512) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Tue Oct 7 09:07:49.906 2008 (GMT+1)
System Uptime: 0 days 0:01:30.578
Loading Kernel Symbols
................................................................................................................
Loading User Symbols
...............................................................................................
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 8E, {c0000005, bf8125eb, aa3adcac, 0}
*** ERROR: Symbol file could not be found. Defaulted to export symbols for USER32.dll -
*************************************************************************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
Probably caused by : win32k.sys ( win32k!ESTROBJ::vInit+241 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf8125eb, The address that the exception occurred at
Arg3: aa3adcac, Trap Frame
Arg4: 00000000
Debugging 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction "0x%08lx" emploie l'adresse m moire "0x%08lx". La m moire ne peut pas tre "%s".
FAULTING_IP:
win32k!ESTROBJ::vInit+241
bf8125eb ff7530 push dword ptr [ebp+30h]
TRAP_FRAME: aa3adcac -- (.trap 0xffffffffaa3adcac)
ErrCode = 00000000
eax=e20e5b18 ebx=aa3adffc ecx=aa3addb8 edx=00000000 esi=aa3addb8 edi=00001460
eip=bf8125eb esp=aa3add20 ebp=aa3add40 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!ESTROBJ::vInit+0x241:
bf8125eb ff7530 push dword ptr [ebp+30h] ss:0010:aa3add70=00000000
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: explorer.exe
LAST_CONTROL_TRANSFER: from 805221e9 to 80537672
STACK_TEXT:
aa3ad874 805221e9 0000008e c0000005 bf8125eb nt!KeBugCheckEx+0x1b
aa3adc3c 804de3f3 aa3adc58 00000000 aa3adcac nt!KiDispatchException+0x3b1
aa3adca4 804de3a4 aa3add40 bf8125eb badb0d00 nt!CommonDispatchException+0x4d
aa3adcb8 bf8055b0 00000000 00000000 e179c560 nt!Kei386EoiHelper+0x18a
aa3add40 bf8118b7 aa3ae0b0 00000016 aa3ae030 win32k!HANDLELOCK::vLockHandle+0x75
aa3adfe4 bf828b4a aa3ae030 00000011 00000001 win32k!GreExtTextOutWLocked+0x666
aa3ae028 bf8b0767 e144a870 00000011 00000001 win32k!GreExtTextOutWInternal+0x6e
aa3ae058 bf8f02c4 01010051 00000011 00000001 win32k!GreExtTextOutW+0x26
aa3ae2b4 bf8efd57 bc691168 01010051 00000011 win32k!xxxDrawMenuItemText+0x119
aa3ae324 bf8ef282 01010051 00000011 00000017 win32k!xxxRealDrawMenuItem+0x561
aa3ae370 bf8ef7c7 01010051 0110005f aa3ae3b8 win32k!xxxDrawState+0x1c7
aa3ae3e0 bf8ef472 01010051 bc692cd0 00000000 win32k!xxxDrawMenuItem+0x39d
aa3ae444 bf854d0d 01010051 00000000 0000000f win32k!xxxMenuDraw+0x19c
aa3ae4e0 bf814099 bc692fe0 0000000f 00000000 win32k!xxxMenuWindowProc+0x1ce
aa3ae520 bf80ecc6 bc692fe0 0000000f 00000000 win32k!xxxSendMessageTimeout+0x18a
aa3ae544 bf823e63 bc692fe0 0000000f 00000000 win32k!xxxSendMessage+0x1b
aa3ae570 bf823d33 bc692fe0 00000001 bc692fe0 win32k!xxxUpdateWindow2+0x79
aa3ae590 bf83654d bc692fe0 00000001 aa3ae664 win32k!xxxInternalUpdateWindow+0x6f
aa3ae5a0 bf8f11ac bc692fe0 bf9ab860 bc692e80 win32k!xxxUpdateWindow+0xf
aa3ae664 bf854b0f bc692fe0 bf9ab860 00000104 win32k!xxxMNOpenHierarchy+0x771
aa3ae700 bf80349f bc692e80 00000113 0000fffe win32k!xxxMenuWindowProc+0x8d4
aa3ae730 bf8f350b aa3ae748 bc692e80 e25d8538 win32k!xxxDispatchMessage+0x187
aa3ae774 bf923a7d e25d8538 bf9ab860 00000000 win32k!xxxMNLoop+0x2ac
aa3ae7d4 bf91287c 000000dd 00000102 000000a7 win32k!xxxTrackPopupMenuEx+0x4d1
aa3ae844 804dd98f 00050281 00000102 000000a7 win32k!NtUserTrackPopupMenuEx+0xb4
aa3ae844 7c91e4f4 00050281 00000102 000000a7 nt!KiFastCallEntry+0xfc
0273e378 7e3ecf6e 7e3e5339 00050281 00000102 ntdll!KiFastSystemCallRet
WARNING: Stack unwind information not available. Following frames may be wrong.
0273e39c 7cab8d07 00050281 00000102 000000a7 USER32!TrackPopupMenuEx+0xc
0273e6b8 7cabbc36 00163d38 00000010 000000a7 SHELL32!CDefView::_DoContextMenuPopup+0x284
0273e704 7ca120e0 016f00a7 00000000 00170008 SHELL32!CDefView::ContextMenu+0x1e4
0273e878 7ca02f48 000201e8 0000007b 000301d0 SHELL32!CDefView::WndProc+0x840
0273e8bc 7e398734 000201e8 0000007b 000301d0 SHELL32!CDefView::s_WndProc+0x72
0273e8e8 7e398816 7ca02ef2 000201e8 0000007b USER32!GetDC+0x6d
0273e950 7e3a8ea0 0009d8a0 7ca02ef2 000201e8 USER32!GetDC+0x14f
0273e9a4 7e3a8eec 005948d0 0000007b 000301d0 USER32!DefWindowProcW+0x180
0273e9cc 7c91e453 0273e9dc 00000018 005948d0 USER32!DefWindowProcW+0x1cc
0273e9cc 804e4d14 0273e9dc 00000018 005948d0 ntdll!KiUserCallbackDispatcher+0x13
aa3aeb18 8056f1ea aa3aebd4 aa3aebd8 aa3aeba8 nt!KiCallUserMode+0x4
aa3aeb74 bf813d9b 00000002 aa3aebb8 00000018 nt!KeUserModeCallback+0x87
aa3aebf8 bf813f31 bc6948d0 0000007b 000301d0 win32k!SfnDWORD+0xa8
aa3aec40 bf814123 006948d0 0000007b 000301d0 win32k!xxxSendMessageToClient+0x176
aa3aec8c bf80ecc6 bc6948d0 0000007b 000301d0 win32k!xxxSendMessageTimeout+0x1a6
aa3aecb0 bf80b1e9 bc6948d0 0000007b 000301d0 win32k!xxxSendMessage+0x1b
aa3aed14 bf80ec8c bc6976c8 0000007b 000301d2 win32k!xxxRealDefWindowProc+0xaeb
aa3aed2c bf820a67 bc6976c8 0000007b 000301d2 win32k!xxxWrapRealDefWindowProc+0x16
aa3aed48 bf80eed3 bc6976c8 0000007b 000301d2 win32k!NtUserfnNCDESTROY+0x27
aa3aed80 804dd98f 000301d0 0000007b 000301d2 win32k!NtUserMessageCall+0xae
aa3aed80 7c91e4f4 000301d0 0000007b 000301d2 nt!KiFastCallEntry+0xfc
0273e9cc 7c91e453 0273e9dc 00000018 005948d0 ntdll!KiFastSystemCallRet
0273e9cc 804e4d14 0273e9dc 00000018 005948d0 ntdll!KiUserCallbackDispatcher+0x13
aa3af058 8056f1ea aa3af114 aa3af118 aa3af0e8 nt!KiCallUserMode+0x4
aa3af0b4 bf813d9b 00000002 aa3af0f8 00000018 nt!KeUserModeCallback+0x87
aa3af138 bf813f31 bc6976c8 0000007b 000301d2 win32k!SfnDWORD+0xa8
aa3af180 bf814123 006976c8 0000007b 000301d2 win32k!xxxSendMessageToClient+0x176
aa3af1cc bf80ecc6 bc6976c8 0000007b 000301d2 win32k!xxxSendMessageTimeout+0x1a6
aa3af1f0 bf80b1e9 bc6976c8 0000007b 000301d2 win32k!xxxSendMessage+0x1b
aa3af254 bf80ec8c bc697778 0000007b 000301d4 win32k!xxxRealDefWindowProc+0xaeb
aa3af26c bf820a67 bc697778 0000007b 000301d4 win32k!xxxWrapRealDefWindowProc+0x16
aa3af288 bf80eed3 bc697778 0000007b 000301d4 win32k!NtUserfnNCDESTROY+0x27
aa3af2c0 804dd98f 000301d2 0000007b 000301d4 win32k!NtUserMessageCall+0xae
aa3af2c0 7c91e4f4 000301d2 0000007b 000301d4 nt!KiFastCallEntry+0xfc
0273ec64 7c91e453 0273ec74 00000018 005976c8 ntdll!KiFastSystemCallRet
0273ec64 804e4d14 0273ec74 00000018 005976c8 ntdll!KiUserCallbackDispatcher+0x13
aa3af598 8056f1ea aa3af654 aa3af658 aa3af628 nt!KiCallUserMode+0x4
aa3af5f4 bf813d9b 00000002 aa3af638 00000018 nt!KeUserModeCallback+0x87
aa3af678 bf813f31 bc697778 0000007b 000301d4 win32k!SfnDWORD+0xa8
aa3af6c0 bf814123 00697778 0000007b 000301d4 win32k!xxxSendMessageToClient+0x176
aa3af70c bf80ecc6 bc697778 0000007b 000301d4 win32k!xxxSendMessageTimeout+0x1a6
aa3af730 bf80b1e9 bc697778 0000007b 000301d4 win32k!xxxSendMessage+0x1b
aa3af794 bf80ec8c bc693888 0000007b 000301c6 win32k!xxxRealDefWindowProc+0xaeb
aa3af7ac bf820a67 bc693888 0000007b 000301c6 win32k!xxxWrapRealDefWindowProc+0x16
aa3af7c8 bf80eed3 bc693888 0000007b 000301c6 win32k!NtUserfnNCDESTROY+0x27
aa3af800 804dd98f 000301d4 0000007b 000301c6 win32k!NtUserMessageCall+0xae
aa3af800 7c91e4f4 000301d4 0000007b 000301c6 nt!KiFastCallEntry+0xfc
0273f01c 7c91e453 0273f02c 00000018 00597778 ntdll!KiFastSystemCallRet
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!ESTROBJ::vInit+241
bf8125eb ff7530 push dword ptr [ebp+30h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!ESTROBJ::vInit+241
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48025f2a
FAILURE_BUCKET_ID: 0x8E_win32k!ESTROBJ::vInit+241
BUCKET_ID: 0x8E_win32k!ESTROBJ::vInit+241
Followup: MachineOwner
---------
merci d'avance, sinon je se soir je balance la bécane par la fenetre, cela fait 2 semaines que j'essaye de l'arrangé (heurement vous inquiétez pas je fait d'autres taches a coté quand même
si quelqu'un trouve le probleme, chapeau