Reboots intempestifs
pepsib33
-
pepsib33 -
pepsib33 -
Bonjour à tous
Depuis quelques temps j'ai des reboots intempestifs .....
Ma config
k7s5a
Athlon 1800xp
xp pro sp1
256 mo noname
geforce 4 mx 440
Voici les traces récupérées à l'aide de windbg ( analyse des dumps )
Si quelqu'un peux m'aider dans l'analyse ......
Microsoft (R) Windows Debugger Version 6.2.0013.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini032304-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 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp1.020828-1920
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Tue Mar 23 19:36:58 2004
System Uptime: 0 days 2:48:29.522
Loading Kernel Symbols
.................................................................................................................
Loading unloaded module list
............
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {5c840ffc, 402, 1, 804ec96e}
Probably caused by : ntoskrnl.exe ( nt!KiUnlinkThread+c )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 5c840ffc, memory referenced
Arg2: 00000402, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804ec96e, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 5c840ffc
CURRENT_IRQL: 402
FAULTING_IP:
nt!KiUnlinkThread+c
804ec96e 8916 mov [esi],edx
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: f9e4dde4 -- (.trap fffffffff9e4dde4)
ErrCode = 00000002
eax=8057f8a1 ebx=815f7118 ecx=815f7020 edx=4589c085 esi=5c840ffc edi=00000000
eip=804ec96e esp=f9e4de58 ebp=f9e4de6c iopl=0 nv up ei ng nz na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287
nt!KiUnlinkThread+0xc:
804ec96e 8916 mov [esi],edx ds:0023:5c840ffc=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 804ec78a to 804ec96e
STACK_TEXT:
f9e4de58 804ec78a 815f7110 815f7118 00000102 nt!KiUnlinkThread+0xc
f9e4de6c 804ecf28 00000000 f9e4de88 00000000 nt!KiUnwaitThread+0x10
f9e4de98 804ec1dc 89bee8a0 0000005a f9e4dfc0 nt!KiWaitTest+0xac
f9e4dfa4 804ec448 89bec2b0 00000017 ffdff000 nt!KiTimerListExpire+0x78
f9e4dfd0 804f1e02 8054ace0 00000000 000f675a nt!KiTimerExpiration+0xb0
f9e4dff4 804f1b0b f432bd54 00000000 00000000 nt!KiRetireDpcList+0x46
FOLLOWUP_IP:
nt!KiUnlinkThread+c
804ec96e 8916 mov [esi],edx
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiUnlinkThread+c
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 3d6de35c
STACK_COMMAND: .trap fffffffff9e4dde4 ; kb
BUCKET_ID: 0xA_W_nt!KiUnlinkThread+c
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.2.0013.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini032404-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 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp1.020828-1920
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Tue Mar 23 21:07:33 2004
System Uptime: 0 days 1:30:10.298
Loading Kernel Symbols
...............................................................................................................
Loading unloaded module list
..............
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 804da11c, f579b8c0, 0}
Probably caused by : ntoskrnl.exe ( nt!KiSystemService+a0 )
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.
An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates
that an unaligned data reference was encountered. The trap frame will
supply additional information.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804da11c, The address that the exception occurred at
Arg3: f579b8c0, 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:
nt!KiSystemService+a0
804da11c 8b5f0c mov ebx,[edi+0xc]
TRAP_FRAME: f579b8c0 -- (.trap fffffffff579b8c0)
ErrCode = 00000000
eax=0000029a ebx=00000002 ecx=bf875c66 edx=0012ecbc esi=0012ecbc edi=00000000
eip=804da11c esp=f579b934 ebp=f579b934 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!KiSystemService+0xa0:
804da11c 8b5f0c mov ebx,[edi+0xc] ds:0023:0000000c=????????
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 7ffe0304 to 804da11c
STACK_TEXT:
f579b934 7ffe0304 00000023 00000000 00000000 nt!KiSystemService+0xa0
0012ed4c 000002bc 01000000 f40107f4 77c7c020 SharedUserData!SystemCallStub+0x4
f579bbf0 80595d2c f579bc78 f579bc7c f579bc8c nt!KiCallUserMode+0x4
f579bc4c bf871e98 00000002 f579bc9c 00000018 nt!KeUserModeCallback+0x87
f579bccc bf871522 bc657b08 0000000f 00000000 win32k!SfnDWORD+0xa0
f579bd0c bf87215b 73d21b81 f579bd64 0012fa28 win32k!xxxDispatchMessage+0x1da
f579bd58 804da140 004deb8c 00000000 817ce7c8 win32k!NtUserDispatchMessage+0x39
f579bd58 7ffe0304 004deb8c 00000000 817ce7c8 nt!KiSystemService+0xc4
0012fa60 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4
FOLLOWUP_IP:
nt!KiSystemService+a0
804da11c 8b5f0c mov ebx,[edi+0xc]
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiSystemService+a0
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 3d6de35c
STACK_COMMAND: .trap fffffffff579b8c0 ; kb
BUCKET_ID: 0x8E_nt!KiSystemService+a0
Followup: MachineOwner
Merci d'avance
Depuis quelques temps j'ai des reboots intempestifs .....
Ma config
k7s5a
Athlon 1800xp
xp pro sp1
256 mo noname
geforce 4 mx 440
Voici les traces récupérées à l'aide de windbg ( analyse des dumps )
Si quelqu'un peux m'aider dans l'analyse ......
Microsoft (R) Windows Debugger Version 6.2.0013.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini032304-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 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp1.020828-1920
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Tue Mar 23 19:36:58 2004
System Uptime: 0 days 2:48:29.522
Loading Kernel Symbols
.................................................................................................................
Loading unloaded module list
............
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {5c840ffc, 402, 1, 804ec96e}
Probably caused by : ntoskrnl.exe ( nt!KiUnlinkThread+c )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 5c840ffc, memory referenced
Arg2: 00000402, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804ec96e, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 5c840ffc
CURRENT_IRQL: 402
FAULTING_IP:
nt!KiUnlinkThread+c
804ec96e 8916 mov [esi],edx
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: f9e4dde4 -- (.trap fffffffff9e4dde4)
ErrCode = 00000002
eax=8057f8a1 ebx=815f7118 ecx=815f7020 edx=4589c085 esi=5c840ffc edi=00000000
eip=804ec96e esp=f9e4de58 ebp=f9e4de6c iopl=0 nv up ei ng nz na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287
nt!KiUnlinkThread+0xc:
804ec96e 8916 mov [esi],edx ds:0023:5c840ffc=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 804ec78a to 804ec96e
STACK_TEXT:
f9e4de58 804ec78a 815f7110 815f7118 00000102 nt!KiUnlinkThread+0xc
f9e4de6c 804ecf28 00000000 f9e4de88 00000000 nt!KiUnwaitThread+0x10
f9e4de98 804ec1dc 89bee8a0 0000005a f9e4dfc0 nt!KiWaitTest+0xac
f9e4dfa4 804ec448 89bec2b0 00000017 ffdff000 nt!KiTimerListExpire+0x78
f9e4dfd0 804f1e02 8054ace0 00000000 000f675a nt!KiTimerExpiration+0xb0
f9e4dff4 804f1b0b f432bd54 00000000 00000000 nt!KiRetireDpcList+0x46
FOLLOWUP_IP:
nt!KiUnlinkThread+c
804ec96e 8916 mov [esi],edx
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiUnlinkThread+c
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 3d6de35c
STACK_COMMAND: .trap fffffffff9e4dde4 ; kb
BUCKET_ID: 0xA_W_nt!KiUnlinkThread+c
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.2.0013.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini032404-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 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp1.020828-1920
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Tue Mar 23 21:07:33 2004
System Uptime: 0 days 1:30:10.298
Loading Kernel Symbols
...............................................................................................................
Loading unloaded module list
..............
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 804da11c, f579b8c0, 0}
Probably caused by : ntoskrnl.exe ( nt!KiSystemService+a0 )
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.
An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates
that an unaligned data reference was encountered. The trap frame will
supply additional information.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804da11c, The address that the exception occurred at
Arg3: f579b8c0, 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:
nt!KiSystemService+a0
804da11c 8b5f0c mov ebx,[edi+0xc]
TRAP_FRAME: f579b8c0 -- (.trap fffffffff579b8c0)
ErrCode = 00000000
eax=0000029a ebx=00000002 ecx=bf875c66 edx=0012ecbc esi=0012ecbc edi=00000000
eip=804da11c esp=f579b934 ebp=f579b934 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!KiSystemService+0xa0:
804da11c 8b5f0c mov ebx,[edi+0xc] ds:0023:0000000c=????????
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 7ffe0304 to 804da11c
STACK_TEXT:
f579b934 7ffe0304 00000023 00000000 00000000 nt!KiSystemService+0xa0
0012ed4c 000002bc 01000000 f40107f4 77c7c020 SharedUserData!SystemCallStub+0x4
f579bbf0 80595d2c f579bc78 f579bc7c f579bc8c nt!KiCallUserMode+0x4
f579bc4c bf871e98 00000002 f579bc9c 00000018 nt!KeUserModeCallback+0x87
f579bccc bf871522 bc657b08 0000000f 00000000 win32k!SfnDWORD+0xa0
f579bd0c bf87215b 73d21b81 f579bd64 0012fa28 win32k!xxxDispatchMessage+0x1da
f579bd58 804da140 004deb8c 00000000 817ce7c8 win32k!NtUserDispatchMessage+0x39
f579bd58 7ffe0304 004deb8c 00000000 817ce7c8 nt!KiSystemService+0xc4
0012fa60 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4
FOLLOWUP_IP:
nt!KiSystemService+a0
804da11c 8b5f0c mov ebx,[edi+0xc]
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiSystemService+a0
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 3d6de35c
STACK_COMMAND: .trap fffffffff579b8c0 ; kb
BUCKET_ID: 0x8E_nt!KiSystemService+a0
Followup: MachineOwner
Merci d'avance
4 réponses
Tes plantages ont lieu régulièrement ?
Peux-tu définir ce qui en ai la source ? (tu lances un prog particulier, tu inseres un CD, tu imprimes, tu vas sur internet...)
L'état du PC quand çà arrive ? (beaucoup de prog, RAM chargée ou pas...)
Si tu démarres et que tu ne fais rien (va prendre un café ;-) ), reboot-il?
a+
dje-dje
Il y a 10 types de personne dans le monde,
ceux qui comprennent le binaire et les autres ...
Peux-tu définir ce qui en ai la source ? (tu lances un prog particulier, tu inseres un CD, tu imprimes, tu vas sur internet...)
L'état du PC quand çà arrive ? (beaucoup de prog, RAM chargée ou pas...)
Si tu démarres et que tu ne fais rien (va prendre un café ;-) ), reboot-il?
a+
dje-dje
Il y a 10 types de personne dans le monde,
ceux qui comprennent le binaire et les autres ...
Les reboots sont parfaitement aleatoires sans que j ai jamais pu etablir une quelconque coincidence .
Seule constante modem wifi via ethernet + logiciel de peer to peer .
Seule constante modem wifi via ethernet + logiciel de peer to peer .
Salut,
Supprime le pilote de ta carte video et remplace le par le dernier ForceWare de chez Nvidia.
Normalement c'est le 56.64(enfin hier c'etait ça)
Voilà le lien:
http://ns8.telecharger.com/windows/Pilotes/cartes_graphique/fiches/18907.html
Ensuite tu peux pratiquer un test Memtest 86 sur ta barrette de memoire .
Et ton Modem c'est quoi comme marque, car si c'est un Sagem de la serie 800, il faut faire une mise à jour.
Plus tu pédales moins vite, et moins t'avances plus vite!!
Supprime le pilote de ta carte video et remplace le par le dernier ForceWare de chez Nvidia.
Normalement c'est le 56.64(enfin hier c'etait ça)
Voilà le lien:
http://ns8.telecharger.com/windows/Pilotes/cartes_graphique/fiches/18907.html
Ensuite tu peux pratiquer un test Memtest 86 sur ta barrette de memoire .
Et ton Modem c'est quoi comme marque, car si c'est un Sagem de la serie 800, il faut faire une mise à jour.
Plus tu pédales moins vite, et moins t'avances plus vite!!
