Robair2b
Nouveau membre
Bonjour,
j'ai un problème d'écran bleu et d'erreur minidump.
Voici le lien du dernier fichier dmp :
Et voici le rapport de windbg: Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini112309-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/Windows Vista Kernel Version 6001 (Service Pack 1) MP (3 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18304.x86fre.vistasp1_gdr.090805-0102
Machine Name:
Kernel base = 0x8204e000 PsLoadedModuleList = 0x82165c70
Debug session time: Mon Nov 23 04:25:30.260 2009 (GMT+1)
System Uptime: 0 days 5:49:00.196
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\DRIVERS\sis163u.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sis163u.sys
*** ERROR: Module load completed but symbols could not be loaded for sis163u.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 8f224522, 8c60bc24, 8c60b920}
Probably caused by : sis163u.sys ( sis163u+17522 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 8f224522, The address that the exception occurred at
Arg3: 8c60bc24, Exception Record Address
Arg4: 8c60b920, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction 0x%08lx emploie l'adresse m moire 0x%08lx. La m moire ne peut pas tre en tat
FAULTING_IP:
sis163u+17522
8f224522 8b484f mov ecx,dword ptr [eax+4Fh]
EXCEPTION_RECORD: 8c60bc24 -- (.exr 0xffffffff8c60bc24)
ExceptionAddress: 8f224522 (sis163u+0x00017522)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 0000004f
Attempt to read from address 0000004f
CONTEXT: 8c60b920 -- (.cxr 0xffffffff8c60b920)
eax=00000000 ebx=8726000c ecx=86bb63a0 edx=8c60bca4 esi=86bb5000 edi=00000000
eip=8f224522 esp=8c60bcec ebp=8c60bd00 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
sis163u+0x17522:
8f224522 8b484f mov ecx,dword ptr [eax+4Fh] ds:0023:0000004f=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - L'instruction 0x%08lx emploie l'adresse m moire 0x%08lx. La m moire ne peut pas tre en tat
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 0000004f
READ_ADDRESS: GetPointerFromAddress: unable to read from 82185868
Unable to read MiSystemVaType memory at 82165420
0000004f
FOLLOWUP_IP:
sis163u+17522
8f224522 8b484f mov ecx,dword ptr [eax+4Fh]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 8f22489f to 8f224522
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8c60bd00 8f22489f 00000000 0026000c 8726000c sis163u+0x17522
8c60bd18 8f2301c6 86bb5000 8726000c 8726000c sis163u+0x1789f
8c60bd38 8f20e935 00bb5000 00000060 40000100 sis163u+0x231c6
8c60bd58 8f20f7ac 00000006 00000000 00000000 sis163u+0x1935
8c60bd7c 82223b22 86dd8000 d3252dd5 00000000 sis163u+0x27ac
8c60bdc0 8207ca2e 8f20f4bc 86dd8000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: sis163u+17522
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: sis163u
IMAGE_NAME: sis163u.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4588ab7f
STACK_COMMAND: .cxr 0xffffffff8c60b920 ; kb
FAILURE_BUCKET_ID: 0x7E_sis163u+17522
BUCKET_ID: 0x7E_sis163u+17522
Followup: MachineOwner
---------
1: kd> lmvm sis163u
start end module name
8f20d000 8f242200 sis163u T (no symbols)
Loaded symbol image file: sis163u.sys
Image path: \SystemRoot\system32\DRIVERS\sis163u.sys
Image name: sis163u.sys
Timestamp: Wed Dec 20 04:18:23 2006 (4588AB7F)
CheckSum: 0003EC1A
ImageSize: 00035200
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Voilà, je suis arrivé à faire fonctionner windbg tant bien que mal, en suivant des tutos mais maintenant je sais plus quoi faire; sachant que le pilote en défaut (sis163u.sys) est à jour. Il s'agit du pilote de ma carte réseau sans fil (802.11 USB Wireless LAN Adapter)
Pourriez-vous me donner votre avis et me dire ce qu'il faut faire.
Merci d'avance pour votre aide!
j'ai un problème d'écran bleu et d'erreur minidump.
Voici le lien du dernier fichier dmp :
Vous devez être connecté pour voir les liens.
Et voici le rapport de windbg: Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini112309-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/Windows Vista Kernel Version 6001 (Service Pack 1) MP (3 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18304.x86fre.vistasp1_gdr.090805-0102
Machine Name:
Kernel base = 0x8204e000 PsLoadedModuleList = 0x82165c70
Debug session time: Mon Nov 23 04:25:30.260 2009 (GMT+1)
System Uptime: 0 days 5:49:00.196
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\DRIVERS\sis163u.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sis163u.sys
*** ERROR: Module load completed but symbols could not be loaded for sis163u.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 8f224522, 8c60bc24, 8c60b920}
Probably caused by : sis163u.sys ( sis163u+17522 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 8f224522, The address that the exception occurred at
Arg3: 8c60bc24, Exception Record Address
Arg4: 8c60b920, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction 0x%08lx emploie l'adresse m moire 0x%08lx. La m moire ne peut pas tre en tat
FAULTING_IP:
sis163u+17522
8f224522 8b484f mov ecx,dword ptr [eax+4Fh]
EXCEPTION_RECORD: 8c60bc24 -- (.exr 0xffffffff8c60bc24)
ExceptionAddress: 8f224522 (sis163u+0x00017522)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 0000004f
Attempt to read from address 0000004f
CONTEXT: 8c60b920 -- (.cxr 0xffffffff8c60b920)
eax=00000000 ebx=8726000c ecx=86bb63a0 edx=8c60bca4 esi=86bb5000 edi=00000000
eip=8f224522 esp=8c60bcec ebp=8c60bd00 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
sis163u+0x17522:
8f224522 8b484f mov ecx,dword ptr [eax+4Fh] ds:0023:0000004f=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - L'instruction 0x%08lx emploie l'adresse m moire 0x%08lx. La m moire ne peut pas tre en tat
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 0000004f
READ_ADDRESS: GetPointerFromAddress: unable to read from 82185868
Unable to read MiSystemVaType memory at 82165420
0000004f
FOLLOWUP_IP:
sis163u+17522
8f224522 8b484f mov ecx,dword ptr [eax+4Fh]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 8f22489f to 8f224522
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8c60bd00 8f22489f 00000000 0026000c 8726000c sis163u+0x17522
8c60bd18 8f2301c6 86bb5000 8726000c 8726000c sis163u+0x1789f
8c60bd38 8f20e935 00bb5000 00000060 40000100 sis163u+0x231c6
8c60bd58 8f20f7ac 00000006 00000000 00000000 sis163u+0x1935
8c60bd7c 82223b22 86dd8000 d3252dd5 00000000 sis163u+0x27ac
8c60bdc0 8207ca2e 8f20f4bc 86dd8000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: sis163u+17522
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: sis163u
IMAGE_NAME: sis163u.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4588ab7f
STACK_COMMAND: .cxr 0xffffffff8c60b920 ; kb
FAILURE_BUCKET_ID: 0x7E_sis163u+17522
BUCKET_ID: 0x7E_sis163u+17522
Followup: MachineOwner
---------
1: kd> lmvm sis163u
start end module name
8f20d000 8f242200 sis163u T (no symbols)
Loaded symbol image file: sis163u.sys
Image path: \SystemRoot\system32\DRIVERS\sis163u.sys
Image name: sis163u.sys
Timestamp: Wed Dec 20 04:18:23 2006 (4588AB7F)
CheckSum: 0003EC1A
ImageSize: 00035200
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Voilà, je suis arrivé à faire fonctionner windbg tant bien que mal, en suivant des tutos mais maintenant je sais plus quoi faire; sachant que le pilote en défaut (sis163u.sys) est à jour. Il s'agit du pilote de ma carte réseau sans fil (802.11 USB Wireless LAN Adapter)
Pourriez-vous me donner votre avis et me dire ce qu'il faut faire.
Merci d'avance pour votre aide!
