Bluescreen sous windows 7
Triol
-
Triol -
Triol -
Bonjour,
Nous rencontrons dernièrement un souci pour le moins génant. En effet, à n'importe quel moment, le PC est susceptible de nous afficher un "bluescreen" et de s'éteindre de façon impromptu.
Nous avons mis à jour les différents drivers, sans succès.
Voici une copie de l'analyse de WhoCrashed, mais qui ne nous permet pas d'apporter une réponse à notre problème au vue de nos compétences en informatique :
System Information (local)
--------------------------------------------------------------------------------
computer name: VALERIE-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5400 @ 2.70GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 6441549824 total
VM: 2147352576, free: 1968029696
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 26/09/2011 04:27:17 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x03087C40)
Bugcheck code: 0x5BF5A30 (0xFFFFFFFFFFFFF910, 0x0, 0x0, 0x308F6EC)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Mon 26/09/2011 04:10:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092611-23556-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF88003AE6000, 0x0, 0xFFFFF8000307D081, 0x0)
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 Sat 24/09/2011 05:06:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092411-29983-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x49460)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF96000099460, 0xFFFFF88002851BD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 Sat 17/09/2011 03:55:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091711-32604-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003368E6E, 0xFFFFF880086406E0, 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.
On Tue 13/09/2011 17:52:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091311-27924-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x18 (0x0, 0xFFFFFA8008DFF740, 0x2, 0xFFFFFFFFFFFFFFFF)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 10/09/2011 18:56:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091011-25896-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x49, 0x2, 0x0, 0xFFFFF800030D3791)
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 Tue 08/03/2011 05:10:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030811-35443-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x41, 0x2, 0x1, 0xFFFFF80002ED3CD8)
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
7 crash dumps have been found and 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.
Si quelqu'un pouvait nous apporter une solution, nous en serions ravis.
Merci d'avance pour votre assistance,
Cordialement.
Nous rencontrons dernièrement un souci pour le moins génant. En effet, à n'importe quel moment, le PC est susceptible de nous afficher un "bluescreen" et de s'éteindre de façon impromptu.
Nous avons mis à jour les différents drivers, sans succès.
Voici une copie de l'analyse de WhoCrashed, mais qui ne nous permet pas d'apporter une réponse à notre problème au vue de nos compétences en informatique :
System Information (local)
--------------------------------------------------------------------------------
computer name: VALERIE-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5400 @ 2.70GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 6441549824 total
VM: 2147352576, free: 1968029696
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 26/09/2011 04:27:17 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x03087C40)
Bugcheck code: 0x5BF5A30 (0xFFFFFFFFFFFFF910, 0x0, 0x0, 0x308F6EC)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Mon 26/09/2011 04:10:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092611-23556-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF88003AE6000, 0x0, 0xFFFFF8000307D081, 0x0)
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 Sat 24/09/2011 05:06:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092411-29983-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x49460)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF96000099460, 0xFFFFF88002851BD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 Sat 17/09/2011 03:55:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091711-32604-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003368E6E, 0xFFFFF880086406E0, 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.
On Tue 13/09/2011 17:52:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091311-27924-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x18 (0x0, 0xFFFFFA8008DFF740, 0x2, 0xFFFFFFFFFFFFFFFF)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 10/09/2011 18:56:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091011-25896-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x49, 0x2, 0x0, 0xFFFFF800030D3791)
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 Tue 08/03/2011 05:10:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030811-35443-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x41, 0x2, 0x1, 0xFFFFF80002ED3CD8)
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
7 crash dumps have been found and 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.
Si quelqu'un pouvait nous apporter une solution, nous en serions ravis.
Merci d'avance pour votre assistance,
Cordialement.
A voir également:
- Bluescreen sous windows 7
- Clé windows 7 - Guide
- Photofiltre 7 - Télécharger - Retouche d'image
- Passer de windows 7 à windows 10 - Accueil - Mise à jour
- Windows defender windows 7 - Télécharger - Antivirus & Antimalwares
- Movie maker windows 7 - Télécharger - Montage & Édition
6 réponses
vous avez un dvd de windows 7?
si c'est le cas booter dessus, réparer/invite de commande
taper : bootcfg /rebuild
si c'est le cas booter dessus, réparer/invite de commande
taper : bootcfg /rebuild
Malheureusement nous n'avons qu'un disque de restauration qui ne permet pas d'accéder à l'invite de commande une fois booté...
Par expérience, lorsqu'on veut mettre à jour un pilote suite à un problème, que ce soit un bluescreen ou pas, il est préférable de désinstaller tout ce qu'on peut de l'ancienne version avant d'installer la nouvelle. De cette façon, on est 100% certain que le driver est clean(qu'il a pas mis des trucs par dessus le vieux, à côté, qui pourraient entrer en conflit) et que l'écran bleu ne provient pas d'un mauvais pilote.
C'est bien beau mettre à jour les pilotes... mais si il y a des résidus de l'ancien ça pourrait faire que le problème persiste même si en temps normal ça aurait réglé le trouble
C'est bien beau mettre à jour les pilotes... mais si il y a des résidus de l'ancien ça pourrait faire que le problème persiste même si en temps normal ça aurait réglé le trouble
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Merci pour la procédure Eclipse, cela fonctionne bien, nous arrivons au menu invite de commande.
Mais la commande "bootcfg /rebuild" n'est pas reconnue...
Nous avons le choix pour bootcfg, au lieu de "rebuild", entre
Copy
Delete
Query
Raw
Timeout
EMS
Debug
ADDSW
RMSW
Dbg1394
Default
@smuatres : Nous ne nous y connaissons pas suffisament pour savoir quoi désinstaller et si c'est sans risque pour la stabilité du système...
Mais la commande "bootcfg /rebuild" n'est pas reconnue...
Nous avons le choix pour bootcfg, au lieu de "rebuild", entre
Copy
Delete
Query
Raw
Timeout
EMS
Debug
ADDSW
RMSW
Dbg1394
Default
@smuatres : Nous ne nous y connaissons pas suffisament pour savoir quoi désinstaller et si c'est sans risque pour la stabilité du système...
Essayes ceci:
https://www.thesiteoueb.net/faq-astuces/fiche-pratique-709-comment-reparer-le-demarrage-de-windows-7.html
ps: bootcfg /rebuild n'est plus une commande valide pour vista et 7even. désolé.
https://www.thesiteoueb.net/faq-astuces/fiche-pratique-709-comment-reparer-le-demarrage-de-windows-7.html
ps: bootcfg /rebuild n'est plus une commande valide pour vista et 7even. désolé.
