Bonjour,

Je possède un HP Pavilion 744.fr sous XP Home SP2.

Après avoir réinstallé Windows, mon pc n'arrive pas à démarrer : à la page Windows XP avec le défilement, il s'arrête, puis redémarre.

Seule solution, démarrage en mode sans échec : arrêt propre et là il démarre convenablement.

J'ai réussi à vider un dump, mais n'étant pas assez pointu, quelqu'un peut-il m'assister ? Merci d'avance.

============================================================­===============
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini090407-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Tue Sep 4 11:18:50.031 2007 (GMT+2)
System Uptime: 0 days 0:00:10.593
*********************************************************************
* 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+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
........................................................................................................
Loading User Symbols
Loading unloaded module list
..
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf811df4, f6c56e44, 0}

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

Probably caused by : win32k.sys ( win32k+11df4 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: bf811df4, The address that the exception occurred at
Arg3: f6c56e44, Trap Frame
Arg4: 00000000

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

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


MODULE_NAME: win32k

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 45f013f6

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+11df4
bf811df4 0300 add eax,dword ptr [eax]

TRAP_FRAME: f6c56e44 -- (.trap 0xfffffffff6c56e44)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000000 edi=f6c5715c
eip=bf811df4 esp=f6c56eb8 ebp=f6c57110 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+0x11df4:
bf811df4 0300 add eax,dword ptr [eax] ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from bf82447d to bf811df4

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f6c57110 bf82447d f6c5715c 00000002 00000004 win32k+0x11df4
f6c57154 bf84bce7 e14e89c8 00000002 00000004 win32k+0x2447d
f6c57184 bf8bd777 0101003a 00000002 00000004 win32k+0x4bce7
f6c571ac bf885e53 0101003a 00000002 00000004 win32k+0xbd777
f6c571d8 bf885d89 0101003a 00000000 00000000 win32k+0x85e53
f6c5729c bf885b03 0101003a f6c572d4 00000001 win32k+0x85d89
f6c572ec bf8852af e148cff8 bf9aa5a0 00000000 win32k+0x85b03
f6c574f4 bf88dfdd e148cff8 00000000 00000001 win32k+0x852af
f6c57520 bf88084e 82d170d8 7ffdfc0e 010119c2 win32k+0x8dfdd
f6c5779c bf881e8b f6c57818 00000001 02000000 win32k+0x8084e
f6c57d40 804de7ec 0006f658 02000000 000000a8 win32k+0x81e8b
f6c57d64 7c91eb94 badb0d00 0006f624 00000000 nt+0x77ec
f6c57d68 badb0d00 0006f624 00000000 00000000 0x7c91eb94
f6c57d6c 0006f624 00000000 00000000 00000000 0xbadb0d00
f6c57d70 00000000 00000000 00000000 00000000 0x6f624


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k+11df4
bf811df4 0300 add eax,dword ptr [eax]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: win32k.sys

SYMBOL_NAME: win32k+11df4

BUCKET_ID: WRONG_SYMBOLS

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

Configuration: HP Pavilion 744.fr
Windows XP SP2