Erreur Sérieuse
golf72
Messages postés
54
Statut
Membre
-
magicien10024 Messages postés 3317 Statut Membre -
magicien10024 Messages postés 3317 Statut Membre -
Bonjour,
Je rencontre une erreur sérieuse depuis quelques jours et pourtant je ne me rappelle pas avoir installé une mise à jour de pilote sur mon PC. J'ai cherché sur le net et j'ai vu que lorsque l'on avait un message type BSOD (écran bleu) avec VSDATANT.SYS c'est que cela venait de Zone Alarm. J'ai donc désinstallé ZA mais le message c'est répété encore hier alors que j'étais sur le net. J'ai installé débug et voilà le rapport. Je n'y comprends rien. Si quelqu'un peut m'aider :
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Copie Minidump\Minidump\Mini040908-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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Wed Apr 9 22:37:24.406 2008 (GMT+2)
System Uptime: 0 days 2:57:53.013
Loading Kernel Symbols
....................................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 806ee753, ae5673e0, 0}
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
Unable to load image aswSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
Probably caused by : aswMon2.SYS ( aswMon2+6a1e )
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: 806ee753, The address that the exception occurred at
Arg3: ae5673e0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
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:
hal!ExAcquireFastMutex+f
806ee753 ff09 dec dword ptr [ecx]
TRAP_FRAME: ae5673e0 -- (.trap 0xffffffffae5673e0)
ErrCode = 00000002
eax=00000000 ebx=ae567518 ecx=00000002 edx=88538c20 esi=8823e0f0 edi=89821890
eip=806ee753 esp=ae567454 ebp=ae567464 iopl=0 nv up ei pl nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010213
hal!ExAcquireFastMutex+0xf:
806ee753 ff09 dec dword ptr [ecx] ds:0023:00000002=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: iwctrl.exe
LAST_CONTROL_TRANSFER: from 804f267e to 806ee753
STACK_TEXT:
ae567450 804f267e 89821890 00000000 ae567518 hal!ExAcquireFastMutex+0xf
ae567464 baf46bf8 8823e0f0 88538c20 00000000 nt!FsRtlLookupPerStreamContextInternal+0x14
ae5674c8 baf579bd 88538c20 89821890 00000000 fltmgr!FltpGetStreamListCtrl+0x5a
ae5674e4 baf43b19 88538c20 89821890 885f7020 fltmgr!FltpCleanupStreamListCtrlForFileObjectClose+0x17
ae567500 baf44059 ae567518 887819d0 89b0e1f8 fltmgr!FltpPassThrough+0x93
ae567530 804e37f7 885f7020 887819d0 00000000 fltmgr!FltpDispatch+0x10d
ae567540 ae656a1e 887819e0 897d0a10 89821890 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
ae567564 ae65083c 885b8020 007819d0 804e37f7 aswMon2+0x6a1e
ae5675b8 805638f7 00821890 89821878 00000000 aswMon2+0x83c
ae5675d4 804e36d5 89821890 00000000 00000000 nt!ObpRemoveObjectRoutine+0xdf
ae5675f8 b0a1ddc8 ae567614 0012faa0 ae567614 nt!ObfDereferenceObject+0x5f
ae567608 804de7ec 000001a4 0012faa0 7c91eb94 aswSP+0x7dc8
ae567608 7c91eb94 000001a4 0012faa0 7c91eb94 nt!KiFastCallEntry+0xf8
0012faa0 00000000 00000000 00000000 00000000 0x7c91eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
aswMon2+6a1e
ae656a1e ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: aswMon2+6a1e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: aswMon2
IMAGE_NAME: aswMon2.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 47ed2dff
FAILURE_BUCKET_ID: 0x8E_aswMon2+6a1e
BUCKET_ID: 0x8E_aswMon2+6a1e
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: 806ee753, The address that the exception occurred at
Arg3: ae5673e0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
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:
hal!ExAcquireFastMutex+f
806ee753 ff09 dec dword ptr [ecx]
TRAP_FRAME: ae5673e0 -- (.trap 0xffffffffae5673e0)
ErrCode = 00000002
eax=00000000 ebx=ae567518 ecx=00000002 edx=88538c20 esi=8823e0f0 edi=89821890
eip=806ee753 esp=ae567454 ebp=ae567464 iopl=0 nv up ei pl nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010213
hal!ExAcquireFastMutex+0xf:
806ee753 ff09 dec dword ptr [ecx] ds:0023:00000002=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: iwctrl.exe
LAST_CONTROL_TRANSFER: from 804f267e to 806ee753
STACK_TEXT:
ae567450 804f267e 89821890 00000000 ae567518 hal!ExAcquireFastMutex+0xf
ae567464 baf46bf8 8823e0f0 88538c20 00000000 nt!FsRtlLookupPerStreamContextInternal+0x14
ae5674c8 baf579bd 88538c20 89821890 00000000 fltmgr!FltpGetStreamListCtrl+0x5a
ae5674e4 baf43b19 88538c20 89821890 885f7020 fltmgr!FltpCleanupStreamListCtrlForFileObjectClose+0x17
ae567500 baf44059 ae567518 887819d0 89b0e1f8 fltmgr!FltpPassThrough+0x93
ae567530 804e37f7 885f7020 887819d0 00000000 fltmgr!FltpDispatch+0x10d
ae567540 ae656a1e 887819e0 897d0a10 89821890 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
ae567564 ae65083c 885b8020 007819d0 804e37f7 aswMon2+0x6a1e
ae5675b8 805638f7 00821890 89821878 00000000 aswMon2+0x83c
ae5675d4 804e36d5 89821890 00000000 00000000 nt!ObpRemoveObjectRoutine+0xdf
ae5675f8 b0a1ddc8 ae567614 0012faa0 ae567614 nt!ObfDereferenceObject+0x5f
ae567608 804de7ec 000001a4 0012faa0 7c91eb94 aswSP+0x7dc8
ae567608 7c91eb94 000001a4 0012faa0 7c91eb94 nt!KiFastCallEntry+0xf8
0012faa0 00000000 00000000 00000000 00000000 0x7c91eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
aswMon2+6a1e
ae656a1e ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: aswMon2+6a1e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: aswMon2
IMAGE_NAME: aswMon2.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 47ed2dff
FAILURE_BUCKET_ID: 0x8E_aswMon2+6a1e
BUCKET_ID: 0x8E_aswMon2+6a1e
Followup: MachineOwner
J'espère que vous avez une idée de ce qui cloche !
Merci
Je rencontre une erreur sérieuse depuis quelques jours et pourtant je ne me rappelle pas avoir installé une mise à jour de pilote sur mon PC. J'ai cherché sur le net et j'ai vu que lorsque l'on avait un message type BSOD (écran bleu) avec VSDATANT.SYS c'est que cela venait de Zone Alarm. J'ai donc désinstallé ZA mais le message c'est répété encore hier alors que j'étais sur le net. J'ai installé débug et voilà le rapport. Je n'y comprends rien. Si quelqu'un peut m'aider :
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Copie Minidump\Minidump\Mini040908-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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Wed Apr 9 22:37:24.406 2008 (GMT+2)
System Uptime: 0 days 2:57:53.013
Loading Kernel Symbols
....................................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 806ee753, ae5673e0, 0}
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
Unable to load image aswSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
Probably caused by : aswMon2.SYS ( aswMon2+6a1e )
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: 806ee753, The address that the exception occurred at
Arg3: ae5673e0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
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:
hal!ExAcquireFastMutex+f
806ee753 ff09 dec dword ptr [ecx]
TRAP_FRAME: ae5673e0 -- (.trap 0xffffffffae5673e0)
ErrCode = 00000002
eax=00000000 ebx=ae567518 ecx=00000002 edx=88538c20 esi=8823e0f0 edi=89821890
eip=806ee753 esp=ae567454 ebp=ae567464 iopl=0 nv up ei pl nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010213
hal!ExAcquireFastMutex+0xf:
806ee753 ff09 dec dword ptr [ecx] ds:0023:00000002=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: iwctrl.exe
LAST_CONTROL_TRANSFER: from 804f267e to 806ee753
STACK_TEXT:
ae567450 804f267e 89821890 00000000 ae567518 hal!ExAcquireFastMutex+0xf
ae567464 baf46bf8 8823e0f0 88538c20 00000000 nt!FsRtlLookupPerStreamContextInternal+0x14
ae5674c8 baf579bd 88538c20 89821890 00000000 fltmgr!FltpGetStreamListCtrl+0x5a
ae5674e4 baf43b19 88538c20 89821890 885f7020 fltmgr!FltpCleanupStreamListCtrlForFileObjectClose+0x17
ae567500 baf44059 ae567518 887819d0 89b0e1f8 fltmgr!FltpPassThrough+0x93
ae567530 804e37f7 885f7020 887819d0 00000000 fltmgr!FltpDispatch+0x10d
ae567540 ae656a1e 887819e0 897d0a10 89821890 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
ae567564 ae65083c 885b8020 007819d0 804e37f7 aswMon2+0x6a1e
ae5675b8 805638f7 00821890 89821878 00000000 aswMon2+0x83c
ae5675d4 804e36d5 89821890 00000000 00000000 nt!ObpRemoveObjectRoutine+0xdf
ae5675f8 b0a1ddc8 ae567614 0012faa0 ae567614 nt!ObfDereferenceObject+0x5f
ae567608 804de7ec 000001a4 0012faa0 7c91eb94 aswSP+0x7dc8
ae567608 7c91eb94 000001a4 0012faa0 7c91eb94 nt!KiFastCallEntry+0xf8
0012faa0 00000000 00000000 00000000 00000000 0x7c91eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
aswMon2+6a1e
ae656a1e ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: aswMon2+6a1e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: aswMon2
IMAGE_NAME: aswMon2.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 47ed2dff
FAILURE_BUCKET_ID: 0x8E_aswMon2+6a1e
BUCKET_ID: 0x8E_aswMon2+6a1e
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: 806ee753, The address that the exception occurred at
Arg3: ae5673e0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
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:
hal!ExAcquireFastMutex+f
806ee753 ff09 dec dword ptr [ecx]
TRAP_FRAME: ae5673e0 -- (.trap 0xffffffffae5673e0)
ErrCode = 00000002
eax=00000000 ebx=ae567518 ecx=00000002 edx=88538c20 esi=8823e0f0 edi=89821890
eip=806ee753 esp=ae567454 ebp=ae567464 iopl=0 nv up ei pl nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010213
hal!ExAcquireFastMutex+0xf:
806ee753 ff09 dec dword ptr [ecx] ds:0023:00000002=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: iwctrl.exe
LAST_CONTROL_TRANSFER: from 804f267e to 806ee753
STACK_TEXT:
ae567450 804f267e 89821890 00000000 ae567518 hal!ExAcquireFastMutex+0xf
ae567464 baf46bf8 8823e0f0 88538c20 00000000 nt!FsRtlLookupPerStreamContextInternal+0x14
ae5674c8 baf579bd 88538c20 89821890 00000000 fltmgr!FltpGetStreamListCtrl+0x5a
ae5674e4 baf43b19 88538c20 89821890 885f7020 fltmgr!FltpCleanupStreamListCtrlForFileObjectClose+0x17
ae567500 baf44059 ae567518 887819d0 89b0e1f8 fltmgr!FltpPassThrough+0x93
ae567530 804e37f7 885f7020 887819d0 00000000 fltmgr!FltpDispatch+0x10d
ae567540 ae656a1e 887819e0 897d0a10 89821890 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
ae567564 ae65083c 885b8020 007819d0 804e37f7 aswMon2+0x6a1e
ae5675b8 805638f7 00821890 89821878 00000000 aswMon2+0x83c
ae5675d4 804e36d5 89821890 00000000 00000000 nt!ObpRemoveObjectRoutine+0xdf
ae5675f8 b0a1ddc8 ae567614 0012faa0 ae567614 nt!ObfDereferenceObject+0x5f
ae567608 804de7ec 000001a4 0012faa0 7c91eb94 aswSP+0x7dc8
ae567608 7c91eb94 000001a4 0012faa0 7c91eb94 nt!KiFastCallEntry+0xf8
0012faa0 00000000 00000000 00000000 00000000 0x7c91eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
aswMon2+6a1e
ae656a1e ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: aswMon2+6a1e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: aswMon2
IMAGE_NAME: aswMon2.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 47ed2dff
FAILURE_BUCKET_ID: 0x8E_aswMon2+6a1e
BUCKET_ID: 0x8E_aswMon2+6a1e
Followup: MachineOwner
J'espère que vous avez une idée de ce qui cloche !
Merci
A voir également:
- Erreur Sérieuse
- Erreur t32 ✓ - Forum Livebox
- Erreur 3000 france tv - Forum Lecteurs et supports vidéo
- Erreur 0x80070643 - Accueil - Windows
- Erreur 0x80070643 Windows 10 : comment résoudre le problème de la mise à jour KB5001716 - Accueil - Windows
- Code erreur f3500-31 ✓ - Forum Bbox Bouygues
1 réponse
bonsoir
tu as 2 solutions
regarde ici
https://support.microsoft.com/en-us/help/903251/you-may-receive-an-error-message-on-a-windows-based-computer-stop-0x00
réparer xp
http://www.informatruc.com/reparer-windows-xp-2
tu as 2 solutions
regarde ici
https://support.microsoft.com/en-us/help/903251/you-may-receive-an-error-message-on-a-windows-based-computer-stop-0x00
réparer xp
http://www.informatruc.com/reparer-windows-xp-2
J'ai essayé de voir dans la base de registre mais pas de trace du fichier en question.
Quant à ré-installer XP je n'y songe pas pour le moment.
En regardant sur le net j'ai vu que cela pouvait être un problème de gestion de la mémoire virtuelle également mais bon...
J'ai viré le fichier Minidump également tout en le sauvegardant et le système en a créé un nouveau. J'ai trouvé l'info sur un forum : http://www.laboratoire-microsoft.org/articles/teched_2002/4/.
Merci de me dire ce que vous en pensez ?
https://forums.cnetfrance.fr