System crash

Fermé
xeeper - 25 oct. 2011 à 21:01
 Jojo-stick - 26 oct. 2011 à 00:34
Bonjour,

depuis deux jour,
mon pc n'arrête pas d'avoir des écran bleu. j'ai enlevé une de mes deux rames de 2Go, et il a réussi à démarrer normalement.

voici le rapport du programme Whocrashed:






5.3.1.0044

Signature du problème :
Nom d'événement de problème: BlueScreen
Version du système: 6.0.6002.2.2.0.768.3
Identificateur de paramètres régionaux: 1036

Informations supplémentaires sur le problème :
BCCode: 1000008e
BCP1: C0000005
BCP2: 00000000
BCP3: 8BBD35DC
BCP4: 00000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Fichiers aidant à décrire le problème :
C:\Windows\Minidump\Mini102511-07.dmp
C:\Users\anis\AppData\Local\Temp\WER-123115-0.sysdata.xml
C:\Users\anis\AppData\Local\Temp\WER952D.tmp.version.txt

Lire notre déclaration de confidentialité :
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x040c





Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.




On Tue 25/10/2011 17:39:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102511-07.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF8BBD35DC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED_M






On Tue 25/10/2011 17:39:14 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ci.dll (CI!CiInitialize+0x8DF)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF8BBD35DC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ci.dll
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Module d'intégrité du code
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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 Tue 25/10/2011 16:59:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102511-06.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x21B132)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8244F132, 0xFFFFFFFF9EB172F4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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 Tue 25/10/2011 10:33:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102511-05.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x19FFF)
Bugcheck code: 0x24 (0x1904AA, 0xFFFFFFFF909D8A30, 0xFFFFFFFF909D872C, 0xFFFFFFFF8B0A36C0)
Error: NTFS_FILE_SYSTEM
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
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Tue 25/10/2011 09:21:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102511-04.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xA (0x4, 0x2, 0x0, 0xFFFFFFFF822AFBF7)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 25/10/2011 09:17:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102511-02.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x61121)
Bugcheck code: 0x50 (0xFFFFFFFF816754B6, 0x1, 0xFFFFFFFF8AD67121, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that invalid system memory has been referenced.
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.





On Mon 24/10/2011 21:09:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102511-01.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF8BBC35DC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED_M




The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\Mini102511-03.dmp




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

On your computer a total of 8 crash dumps have been found. Only 7 could be analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

unknown

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


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.


1 réponse

Si en enlevant une barrette de RAM ton PC fonctionne correctement, j'vois même pas pkoi tu vas chercher plus loin... et en échangeant celle en place avec celle enlevé, ca change quelque chose? si le résultat est le même, ton PC n'accepte peut être pas autant de RAM, ou ton port est HS, ou ta carte mère aussi...
0