Blue Screen Windows 7 (64bits)
Posté : dim. 7 mars 2010 01:59
Bonjour,
Content de découvrir ce forum qu'il a l'air fort passionant.
Malheuresement, je le découvre alors que j'ai des misères avec mon nouveau Vaio série F (personnalisable) qui m'a fait pas moins de 5 Blue screen depuis que je l'ai reçu.
J'ai installé "Whocrashed" (il porte bien son nom ) qui me dénnonce trois coupables : spsys.sys, wdf01000.sys et 1394ohci.sys à chaque fois à la rubrique "drivers".
Que puis-je faire ensuite?... Je commence à regretter cet achat moi
Merci d'avance.
Le rapport "Whocrashed" complet donne ceci :
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 06/03/2010 23:35:51 your computer crashed
This was likely caused by the following module: spsys.sys
Bugcheck code: 0x10D (0x5, 0x0, 0x1401, 0xFFFFFA800594D820)
Error: WDF_VIOLATION
Dump file: C:\Windows\Minidump\030710-8736-01.dmp
file path: C:\Windows\system32\drivers\spsys.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: security processor
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Sat 06/03/2010 16:48:52 your computer crashed
This was likely caused by the following module: wdf01000.sys
Bugcheck code: 0x10D (0x8, 0x57FFC5B5288, 0x3, 0xFFFFFA8006910E70)
Error: WDF_VIOLATION
Dump file: C:\Windows\Minidump\030610-8439-01.dmp
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Fri 05/03/2010 01:50:45 your computer crashed
This was likely caused by the following module: wdf01000.sys
Bugcheck code: 0x10D (0x8, 0x57FF9CDDAD8, 0x3, 0xFFFFFA8005B34E70)
Error: WDF_VIOLATION
Dump file: C:\Windows\Minidump\030510-10405-01.dmp
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Fri 05/03/2010 01:34:21 your computer crashed
This was likely caused by the following module: wdf01000.sys
Bugcheck code: 0x10D (0x8, 0x57FF86FB138, 0x3, 0xFFFFFA8005AB0C80)
Error: WDF_VIOLATION
Dump file: C:\Windows\Minidump\030510-10218-01.dmp
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Thu 04/03/2010 13:48:35 your computer crashed
This was likely caused by the following module: 1394ohci.sys
Bugcheck code: 0x10D (0x5, 0x0, 0x1401, 0xFFFFFA8005BAE570)
Error: WDF_VIOLATION
Dump file: C:\Windows\Minidump\030410-12963-01.dmp
file path: C:\Windows\system32\drivers\1394ohci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: 1394 OpenHCI Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
5 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.
Content de découvrir ce forum qu'il a l'air fort passionant.

Malheuresement, je le découvre alors que j'ai des misères avec mon nouveau Vaio série F (personnalisable) qui m'a fait pas moins de 5 Blue screen depuis que je l'ai reçu.
J'ai installé "Whocrashed" (il porte bien son nom ) qui me dénnonce trois coupables : spsys.sys, wdf01000.sys et 1394ohci.sys à chaque fois à la rubrique "drivers".
Que puis-je faire ensuite?... Je commence à regretter cet achat moi
Merci d'avance.
Le rapport "Whocrashed" complet donne ceci :
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 06/03/2010 23:35:51 your computer crashed
This was likely caused by the following module: spsys.sys
Bugcheck code: 0x10D (0x5, 0x0, 0x1401, 0xFFFFFA800594D820)
Error: WDF_VIOLATION
Dump file: C:\Windows\Minidump\030710-8736-01.dmp
file path: C:\Windows\system32\drivers\spsys.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: security processor
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Sat 06/03/2010 16:48:52 your computer crashed
This was likely caused by the following module: wdf01000.sys
Bugcheck code: 0x10D (0x8, 0x57FFC5B5288, 0x3, 0xFFFFFA8006910E70)
Error: WDF_VIOLATION
Dump file: C:\Windows\Minidump\030610-8439-01.dmp
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Fri 05/03/2010 01:50:45 your computer crashed
This was likely caused by the following module: wdf01000.sys
Bugcheck code: 0x10D (0x8, 0x57FF9CDDAD8, 0x3, 0xFFFFFA8005B34E70)
Error: WDF_VIOLATION
Dump file: C:\Windows\Minidump\030510-10405-01.dmp
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Fri 05/03/2010 01:34:21 your computer crashed
This was likely caused by the following module: wdf01000.sys
Bugcheck code: 0x10D (0x8, 0x57FF86FB138, 0x3, 0xFFFFFA8005AB0C80)
Error: WDF_VIOLATION
Dump file: C:\Windows\Minidump\030510-10218-01.dmp
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
On Thu 04/03/2010 13:48:35 your computer crashed
This was likely caused by the following module: 1394ohci.sys
Bugcheck code: 0x10D (0x5, 0x0, 0x1401, 0xFFFFFA8005BAE570)
Error: WDF_VIOLATION
Dump file: C:\Windows\Minidump\030410-12963-01.dmp
file path: C:\Windows\system32\drivers\1394ohci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: 1394 OpenHCI Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
5 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.