Bonjour à tous. Voilà mon soucis. Je suis passé à windows 7 il y a environ 1 mois en remplacement de XP pro. J en suis très satisfait à tous les niveaux. Cependant par moment j ai de jolies écrans bleu qui aparaissent, surtout lors de navigation sur le net. J amais eu le cas en jouant ou sur de la bureautique.
Le message qui apparait est donc le suivant,
Systeme_service_exception
Alors comme mes compétences en matières d informatique ont leur limites, je m en remets à vous pour un petit coup de main. Pour info ma config est la suivante si ça peut aider ??
Athlon 64x2 5000+ 2.7Ghz (légèrement overclocké)
carte mère Alive NF6P
2*1 go de RAM corsair PC6400
CG Twintech 8800 GTX 768 Mo
2*320 Go Maxtor en Raid0
1*320 go Maxtor
1*200go Maxtor
Il n y a qu au niveau de la CG que j ai fait une nouvelle mise à jour hier qui n a rien résolu.
Merci d avance Cyril
blue screen Msg Systeme service exception
Re: blue screen Msg Systeme service exception
Bonjour,
Connaissez-vous le logiciel "Whocrashed"...non ? téléchargez-le et après l'avoir installé, faites avec celui-ci un balayage de votre machine et vous connaitrez alors la ou les raisons de vos écrans bleus.
A votre service et bonne journée.
Connaissez-vous le logiciel "Whocrashed"...non ? téléchargez-le et après l'avoir installé, faites avec celui-ci un balayage de votre machine et vous connaitrez alors la ou les raisons de vos écrans bleus.
A votre service et bonne journée.
Re: blue screen Msg Systeme service exception
Voilà donc le rapport reçu suite à l analyse avec ce fameux logiciel. Maintenant si quelqu un pouvait me traduire ces infos, et m expliquer vers quoi m orienter ?? Merci d avance.
--------------------------------------------------------------------------------
Welcome to WhoCrashed Home Edition 2.10
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often though about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, most computers do not show a blue screen unless they are configured to do so. Instead these systems suddenly reboot without any notice.
This program does post-mortem crash dump analysis with the single click of a button.
To obtain technical support visit www.resplendence.com/support
To check if a newer version of this program is available, click here.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition. The professional edition of WhoCrashed also allows analysis of crashdumps on remote drives and computers on the network and offers more detailed analysis.
--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 21/10/2010 07:20:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002DB3EFE, 0xFFFFF88002B567B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\102110-18609-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Wed 20/10/2010 19:34:08 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFF80000004, 0xFFFFF80002D31467, 0xFFFFFA8002900550, 0xFFFFFA8001837148)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\102010-19296-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Wed 20/10/2010 11:48:58 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x109 (0xA3A039D893ED4650, 0xB3B7465EE66A18B6, 0xFFFFF80002D53E5E, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
Dump file: C:\Windows\Minidump\102010-20750-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Mon 18/10/2010 16:05:55 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x124 (0x0, 0xFFFFFA800309E038, 0xB635C000, 0x145)
Error: WHEA_UNCORRECTABLE_ERROR
Dump file: C:\Windows\Minidump\101810-22500-01.dmp
On Mon 18/10/2010 09:31:36 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x50 (0xFFFFF900CC86F030, 0x0, 0xFFFFF960000F98E8, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\101810-20953-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 17/10/2010 18:51:56 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3D (0xFFFFF880009A8C40, 0x0, 0x0, 0xFFFFF88005892F6F)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\101710-17968-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 17/10/2010 17:30:17 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880, 0x8, 0xFFFFF880)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\101710-15390-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Tue 12/10/2010 06:21:42 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x2961, 0x8, 0x2961)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\101210-15578-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 10/10/2010 07:06:11 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800028D2820, 0xFFFFF88008D2A0C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\101010-15968-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 09/10/2010 15:10:00 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xD1 (0x7E0, 0x2, 0x8, 0x7E0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\100910-16750-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Thu 07/10/2010 05:06:07 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009613E58, 0xFFFFF880096136C0, 0xFFFFF8800122AF96)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\100710-16640-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Wed 06/10/2010 14:43:42 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA8005790BD5, 0x1, 0x289DE88)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\100610-15593-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Wed 06/10/2010 12:15:36 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF800028D2820, 0x2, 0xFFFFFFFFFFFFFF00)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\100610-15187-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Fri 01/10/2010 11:01:37 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x109 (0xA3A039D8942D14FD, 0xB3B7465EE6A9E763, 0xFFFFF80002B53E5E, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
Dump file: C:\Windows\Minidump\100110-16843-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 26/09/2010 17:34:55 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x109 (0xA3A039D8939175F5, 0xB3B7465EE60E485B, 0xFFFFF800028D2750, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
Dump file: C:\Windows\Minidump\092610-20812-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 26/09/2010 11:13:34 your computer crashed
This was likely caused by the following module: storport.sys
Bugcheck code: 0xD1 (0x68, 0x2, 0x0, 0xFFFFF880011310ED)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\092610-15953-01.dmp
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 25/09/2010 07:16:23 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x109 (0xA3A039D8936686BD, 0xB3B7465EE5E35923, 0xFFFFF80002BB3DD0, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
Dump file: C:\Windows\Minidump\092510-14515-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Mon 20/09/2010 11:30:08 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x109 (0xA3A039D8936475CB, 0xB3B7465EE5E14831, 0xFFFFF800028B27D8, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
Dump file: C:\Windows\Minidump\092010-19578-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Wed 15/09/2010 05:37:39 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000103775, 0xFFFFF88008338070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\091510-32171-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
19 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.
--------------------------------------------------------------------------------
Welcome to WhoCrashed Home Edition 2.10
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often though about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, most computers do not show a blue screen unless they are configured to do so. Instead these systems suddenly reboot without any notice.
This program does post-mortem crash dump analysis with the single click of a button.
To obtain technical support visit www.resplendence.com/support
To check if a newer version of this program is available, click here.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition. The professional edition of WhoCrashed also allows analysis of crashdumps on remote drives and computers on the network and offers more detailed analysis.
--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 21/10/2010 07:20:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002DB3EFE, 0xFFFFF88002B567B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\102110-18609-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Wed 20/10/2010 19:34:08 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFF80000004, 0xFFFFF80002D31467, 0xFFFFFA8002900550, 0xFFFFFA8001837148)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\102010-19296-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Wed 20/10/2010 11:48:58 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x109 (0xA3A039D893ED4650, 0xB3B7465EE66A18B6, 0xFFFFF80002D53E5E, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
Dump file: C:\Windows\Minidump\102010-20750-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Mon 18/10/2010 16:05:55 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x124 (0x0, 0xFFFFFA800309E038, 0xB635C000, 0x145)
Error: WHEA_UNCORRECTABLE_ERROR
Dump file: C:\Windows\Minidump\101810-22500-01.dmp
On Mon 18/10/2010 09:31:36 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x50 (0xFFFFF900CC86F030, 0x0, 0xFFFFF960000F98E8, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\101810-20953-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 17/10/2010 18:51:56 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3D (0xFFFFF880009A8C40, 0x0, 0x0, 0xFFFFF88005892F6F)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\101710-17968-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 17/10/2010 17:30:17 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880, 0x8, 0xFFFFF880)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\101710-15390-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Tue 12/10/2010 06:21:42 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x2961, 0x8, 0x2961)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\101210-15578-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 10/10/2010 07:06:11 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800028D2820, 0xFFFFF88008D2A0C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\101010-15968-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 09/10/2010 15:10:00 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xD1 (0x7E0, 0x2, 0x8, 0x7E0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\100910-16750-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Thu 07/10/2010 05:06:07 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009613E58, 0xFFFFF880096136C0, 0xFFFFF8800122AF96)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\100710-16640-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Wed 06/10/2010 14:43:42 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA8005790BD5, 0x1, 0x289DE88)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\100610-15593-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Wed 06/10/2010 12:15:36 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF800028D2820, 0x2, 0xFFFFFFFFFFFFFF00)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\100610-15187-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Fri 01/10/2010 11:01:37 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x109 (0xA3A039D8942D14FD, 0xB3B7465EE6A9E763, 0xFFFFF80002B53E5E, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
Dump file: C:\Windows\Minidump\100110-16843-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 26/09/2010 17:34:55 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x109 (0xA3A039D8939175F5, 0xB3B7465EE60E485B, 0xFFFFF800028D2750, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
Dump file: C:\Windows\Minidump\092610-20812-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 26/09/2010 11:13:34 your computer crashed
This was likely caused by the following module: storport.sys
Bugcheck code: 0xD1 (0x68, 0x2, 0x0, 0xFFFFF880011310ED)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\092610-15953-01.dmp
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 25/09/2010 07:16:23 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x109 (0xA3A039D8936686BD, 0xB3B7465EE5E35923, 0xFFFFF80002BB3DD0, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
Dump file: C:\Windows\Minidump\092510-14515-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Mon 20/09/2010 11:30:08 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x109 (0xA3A039D8936475CB, 0xB3B7465EE5E14831, 0xFFFFF800028B27D8, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
Dump file: C:\Windows\Minidump\092010-19578-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Wed 15/09/2010 05:37:39 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000103775, 0xFFFFF88008338070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\091510-32171-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
19 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.
Re: blue screen Msg Systeme service exception
Personne n aurait une petite idée de ce qu il se passe dans ma tour adorée ?? 
Re: blue screen Msg Systeme service exception
Bonjour
Voici ce que nous indique DOCmemo
@+
Voici ce que nous indique DOCmemo
Avec tout cela, tu as des pistes de recherche, n'est-il pas ?Code 0x0000003b
Logiciel : Erreur STOP Windows
Intitulé : SYSTEM_SERVICE_EXCEPTION
Solution
Cette erreur est due à un service mis en place par une application récemment installée ou à un service défectueux
Code 0x0000001e
Logiciel : Erreur STOP Windows
Intitulé : KMODE_EXCEPTION_NOT_HANDLED
Solution
[1] Le noyau de Windows a détecté que le processeur tente d'exécuter une instruction inconnue ou non valide. C'est souvent dû à un pilote de périphérique ou à un périphérique. Essayez de le réinstaller ou d'installer un pilote plus récent.
\r\n[2] Windows XP ou Vista - Le problème survient si vous redémarrez votre ordinateur pendant ou après la procédure d'installation de Windows. Il peut être dû à trois causes : le lecteur où vous installez Windows manque d'espace libre, un pilote de périphérique est défectueux ou obsolète, il y a une incompatibilité au niveau du BIOS. Résolution du problème : installez WIndows sur un lecteur disposant de suffisamment d'espace libre, supprimez ou désactivez le pilote en cause (en mode sans échec), mettez à jour le BIOS (voyez sur le site du constructeur de l'ordinateur ou celui du frabricant de la carte mère).
\r\n[3] Windows XP ou Vista - Si le message d'erreur fait référence à aspi32.sys, un fichier système de gestion des périphériques SCSI. Procurez-vous chez Adaptec la version 4.57 (ou ultérieure) de ASPI.
Code 0x00000109
Logiciel : Erreur STOP Windows
Intitulé : CRITICAL_STRUCTURE_CORRUPTION
Solution
Un pilote de périphérique est défectueux.
Code 0x00000124
Logiciel : Erreur STOP Windows
Intitulé : UNCORRECTABLE HARDWARE ERROR
Solution
erreur matérielle non définie précisément
Code 0x00000050
Logiciel : Erreur STOP Windows
Intitulé : PAGE_FAULT_IN_NONPAGED_AREA
Solution
[1] Un pilote de périphérique ou un service cherche en mémoire vive des données qui n'y sont pas.
[2] Une barrette de mémoire vive peut être défectueuse ou un logiciel (souvent un antivirus ou une application de contrôle à distance) est incompatible avec la version de Windows que vous utilisez.
[3] Windows XP - Vous utilisez Easy CD Creator 5, incompatible avec Windows XP . Téléchargez une mise à jour sur le site de l'éditeur : Roxio.
[4] Windows XP - Vous utilisez le scanner HP ScanJet 4400 ou 4470 connecté sur le port parallèle. Installez se Service Pack 1 ou 2 de WIndows XP.
[5] Windows XP - Si l'erreur sruvient au redémarrage de l'ordinateur après l'installation du Service Pack 1, elle est due au pilote de la carte graphique. Désinstallez-la et installez un pilote plus récent en mode sans échec).
[6] Windows XP - Le pilote du lecteur USB Lexar Media est incompatible avec Windows XP. Téléchargez un pilote plus récent sur le site de Lexar Media.
[7] Windows XP SP2 - Si l'erreur survient pendant l'installation du SP2, il est possible que le logiciel BootSkin ou ZoneAlarm soit responsable. téléchargez un correctif ou une nouvelle version sur le site de l'éditeur.
Code 0x0000003d
Logiciel : Erreur STOP Windows
Intitulé : INTERRUPT_EXCEPTION_NOT_HANDLED
Solution
Problème de gestion de mémoire ou problème matériel.
[1] Si vous venez d'installer un nouveau matériel, désinstallez-le.
[2] La mémoire vive est peut-être endommagée. Voyez si les barrettes sont bien clipsées sur la carte mère. Si c'est le cas, essayez de repérer une éventuelle barrette défectueuse. Retirez une barrette et redémarrez. SI l'erreur n'apparaît plus, remplacez la barrette extraite par une nouvelle.
Code 0x000000d1
Logiciel : Erreur STOP Windows
Intitulé : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Solution
[1] Vous avez inséré et débranché rapidement une PC Card. ne le faites plus !
[2] Windows XP ou Vista : le problème survient juste après l'installation de Windows. Il est peut-être dû à des barrettes de mémoire vive défectueuses ou incompatibles avec la carte mère. La cause est peut-être également le gestionnaire de mémoire virtuelle. Dans ce cas, annulez-le (dans le module Système du Panneau de configuration : cliquez sur l'onglet Performances).
[3] Le message d'erreur se produit lorsque vous éteignez l'ordinateur. L'origine est peut-être dans le programme de gestion de la souris Logitech Mouseware, trop ancien. Désinstallez-le et installez une version plus récente.
[4] Windows XP ou Vista : si vous avez installé le pare-feu ATGuard de WRQ. Mettez à jour le logiciel avec une version plus récente.
[5] Windows XP ou Vista : le problème apparaît lorsque vous éteignez l'ordinateur. Il est dû à une mauvaise gestion des périphériques USB. Installez les correctifs proposés sur WIndows Update.
[6] Plus généralement, le problème est provoqué par un pilote non adapté.
Code 0x00000024
Logiciel : Erreur STOP Windows
Intitulé : NTFS_FILE_SYSTEM
Solution
Problème dans le gestionnaire de fichiers NTFS. Il est dû à un contrôleur IDE, un disque ou un câblage IDE défaillant.
@+
En cas de problème constaté sur un sujet, contactez un modérateur par MP. N'intervenez pas vous-même. Merci
Re: blue screen Msg Systeme service exception
Bonjour,
Au vu des nombreuses anomalies détectées par "Whocrashed", je vous suggèrerai dans un premier temps de voir si tous vos pilotes sont à jour ou tout au moins si vous utilisez une version correcte. Pour cela allez à l'url suivant - http://www.ma-config.com et suivez les indications données dans la procédure.
- Avant d'installer windows 7, avez-vous testé la compatibilité de tout votre matériel (y compris les périphériques) avec ce nouvel OS ?
si non allez à l'url suivant - http://www.maximerastello.com/windows-7 ... -vista-120
téléchargez le logiciel indiqué et déroulez le.
vous devriez déjà avoir des indications précieuses qui vous aideront dans la résolution de votre pb.
Bon courage.
Au vu des nombreuses anomalies détectées par "Whocrashed", je vous suggèrerai dans un premier temps de voir si tous vos pilotes sont à jour ou tout au moins si vous utilisez une version correcte. Pour cela allez à l'url suivant - http://www.ma-config.com et suivez les indications données dans la procédure.
- Avant d'installer windows 7, avez-vous testé la compatibilité de tout votre matériel (y compris les périphériques) avec ce nouvel OS ?
si non allez à l'url suivant - http://www.maximerastello.com/windows-7 ... -vista-120
téléchargez le logiciel indiqué et déroulez le.
vous devriez déjà avoir des indications précieuses qui vous aideront dans la résolution de votre pb.
Bon courage.
Re: blue screen Msg Systeme service exception
Bon alors j ai lancé le logiciel sur ma config.com et j ai eu 2 ou 3 mises à jour nvidia, carte réseau et son. On va voir ce que cela donne maintenant dans les jours à venir ...
Me reste le problème de jeux à résoudre aussi lol
Merci pour l aide et peut etre à bientot si cela ne fonctionne pas
Me reste le problème de jeux à résoudre aussi lol
Merci pour l aide et peut etre à bientot si cela ne fonctionne pas
Re: blue screen Msg Systeme service exception
Re-bonjour,
Vous n'avez pas répondu à la question: compatibilité de votre matériel avec W7. Faites le test comme demandé, il ce pourrait que vous trouviez encore quelque anomalie.
Après avoir fait tout ceci et rectifié les anomalies éventuelles, vous devriez faire un nouveau test avec "Whocrashed" pour voir ce qu'il reste d'anormal dans votre machine.
Remarque: ce dernier balayage devra etre effectué après avoir effacé le contenu de "minidump" en faisant:
C/windows/minidump , clic gauche sur minidump pour voir le contenu, clic droit sur la totalité du contenu, supprimer.
Vous n'avez pas répondu à la question: compatibilité de votre matériel avec W7. Faites le test comme demandé, il ce pourrait que vous trouviez encore quelque anomalie.
Après avoir fait tout ceci et rectifié les anomalies éventuelles, vous devriez faire un nouveau test avec "Whocrashed" pour voir ce qu'il reste d'anormal dans votre machine.
Remarque: ce dernier balayage devra etre effectué après avoir effacé le contenu de "minidump" en faisant:
C/windows/minidump , clic gauche sur minidump pour voir le contenu, clic droit sur la totalité du contenu, supprimer.