Bonjour
j'ai très souvent un ecran bleu avec du texte qui apparait
et le pc redémarre
j'ai ceci :
System Information (local)
--------------------------------------------------------------------------------
computer name: PC-TOSHIBA
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU M 430 @ 2.27GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4146774016 total
VM: 2147352576, free: 1989455872
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 02/03/2011 17:59:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030211-27456-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x2AF9F)
Bugcheck code: 0x100000B8 (0xFFFFFA8004B59B60, 0xFFFFF880009F3FC0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote NDIS 6.20
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Wed 02/03/2011 17:59:58 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xB8 (0xFFFFFA8004B59B60, 0xFFFFF880009F3FC0, 0x0, 0x0)
Error: ATTEMPTED_SWITCH_FROM_DPC
Bug check description: This indicates that an illegal operation was attempted by a delayed procedure call (DPC) routine.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 02/03/2011 17:55:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030211-27549-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x82EDA)
Bugcheck code: 0x100000B8 (0xFFFFFA8003B2D9C0, 0xFFFFF8800396DFC0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 02/03/2011 17:47:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030211-27830-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x25C2)
Bugcheck code: 0x100000B8 (0xFFFFFA8004B56B60, 0xFFFFFA8003B52B60, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Wed 02/03/2011 13:57:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030211-18111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x82EDA)
Bugcheck code: 0x100000B8 (0xFFFFFA8003B6EB60, 0xFFFFFA800758C060, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 02/03/2011 13:55:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030211-17862-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80610)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 25/02/2011 11:33:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022511-44288-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80610)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 25/02/2011 10:57:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022511-20451-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x82EDA)
Bugcheck code: 0x100000B8 (0xFFFFFA8004041660, 0xFFFFF80003254CC0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 25/02/2011 06:04:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022511-17300-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80610)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 25/02/2011 06:00:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022511-20451-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x85D22)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
10 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
merci de m'aider pour ce pc portable