PDA

Voir la version complète : Blue Screen =(



elyanes
27/01/2011, 23h00
Bonjour depuis aujourd'hui 18h45 après l'installation d'un .exe mon ordinateur s'est arrêté brusquement, je tente de la redémarré,... Blue Screen. Je tente de réparer le système a partir du CD de Windows 7, rien, je relance à partir de la dernière configuration fonctionnelle, (après avoir bourriné sur la touche f8 pour réussir à ouvrir l'écran), rien, je recommence je fait analyse par rescue system de Avira Antivir, rien, je refait avec dernière configuration marchante, sa se branche... 10 minutes après sa recrash. Là je suis en mode sans échec avec prise en charge réseau... rien ne se passe pour le moment j'ai le message d'erreur suivant :

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

Informations supplémentaires sur le problème :
BCCode: a
BCP1: 0000000000000008
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF800034F844B
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

J'ai essayé le logiciel WhosCrashed qui donne sa :

On Thu 27/01/2011 21:34:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012711-20857-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF800034F844B)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Thu 27/01/2011 21:34:13 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: 0xA (0x8, 0x2, 0x1, 0xFFFFF800034F844B)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Thu 27/01/2011 21:31:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012711-22682-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF800034ACD29)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Thu 27/01/2011 21:30:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012711-19203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFFFFF80000708, 0x1, 0xFFFFF880010F0004, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 27/01/2011 21:26:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012711-18564-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1B7E0)
Bugcheck code: 0xBE (0xFFFFF8800161B7E0, 0x5393121, 0xFFFFF8800961B490, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
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 is issued if a driver attempts to write to a read-only memory segment.
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 Thu 27/01/2011 21:11:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012711-20389-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x680, 0x2, 0x1, 0xFFFFF80002CA3CDC)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Thu 27/01/2011 21:07:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012711-18610-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CA4518)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Thu 27/01/2011 20:50:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012711-16489-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CA7448, 0xFFFFF8800766BB10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.


SVP Aidez moi =(
Merci,

hYper_activitY
28/01/2011, 00h32
Ca ressemble fort à un probleme de Ram

un memtest s'impose

Syntaxerror
28/01/2011, 01h31
D'après le logiciel que je connais pas, ça serait plutôt un problème de drivers.

"This appears to be a typical software driver bug and is not likely to be caused by a hardware problem."

C'est quoi le .exe que tu dis avoir installé juste avant les crashs?

Enfin, tester la mémoire ça peut pas faire de mal.

smokytoks
28/01/2011, 09h46
C'est un message générique ça...

Je penche également pour un soucis de RAM si il n'y a pas de merde niveau soft...

elyanes
28/01/2011, 19h52
Je viens de miser le tout pour le tout et j'ai réinstaller windows et pour le moment tout fonctionne depuis environ 2h...

Merci,

Syntaxerror
29/01/2011, 00h59
C'est un message générique ça...



Ha mince, il génère pas de petits messages personnalisés pour chaque crash relevé?