Blue screen récurent sous Windows 7

[simo_be_01]

Bonjour s'il vous plait j'ai besoin de votre aide
Mon problème et le suivant :
j'obtiens un écran bleu quand je retire le modem ou quand je mets le mon PC portable en veille

Description du problème :

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: 00000004
BCP2: 00000002
BCP3: 00000001
BCP4: 83075AE6
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Fichiers aidant à décrire le problème*:
C:\Windows\Minidump\062111-23556-01.dmp
C:\Users\hp\AppData\Local\Temp\WER-63554-0.sysdata.xml

Lire notre déclaration de confidentialité en ligne*:
http://go.microsoft.com/fwlink/?link...8&clcid=0x040c

Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion*:
C:\Windows\system32\fr-FR\erofflps.txt

merci

[Jeuhty]

Salut essaye de faire réparer W7 .

[simo_be_01]

Bonjour
je l'ai déjà fais et j'ai même réinstaller le système mais l’écran bleu continue à apparaître

[nardino]

Bonjour,
Ce type d'erreur s'affiche le plus souvent quand un pilote de périphérique n'est pas compatible avec le système d'exploitation.
Vérifie qu'il n'y a pas une alerte sur l'un d'eux dans le gestionnaire de périphériques.

Télécharge WhoCrashed Home Edition 3.01 de Resplendence

Tu l'installes et tu le lances par Analyze.
Tu postes un copier-coller de ce qui apparait .

@+

[simo_be_01]

Bonjour voila le rapport que j'ai obtenu merci
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: HP-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2072264704 total
VM: 2147352576, free: 2011193344



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 21/06/2011 13:43:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062111-23556-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467FB)
Bugcheck code: 0xA (0x4, 0x2, 0x1, 0xFFFFFFFF83075AE6)
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 21/06/2011 13:43:03 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt+0x467FB)
Bugcheck code: 0xA (0x4, 0x2, 0x1, 0xFFFFFFFF83075AE6)
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL




On Sun 19/06/2011 14:27:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061911-32807-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCCFA7)
Bugcheck code: 0xA (0x4, 0x2, 0x1, 0xFFFFFFFF830BDAE6)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 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 Sun 19/06/2011 10:35:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061911-46971-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x3102A)
Bugcheck code: 0xA (0x4, 0x2, 0x1, 0xFFFFFFFF8306BAE6)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 16/06/2011 20:49:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061611-24866-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x9F (0x3, 0xFFFFFFFF85FF6030, 0xFFFFFFFF83177AE0, 0xFFFFFFFF87651ED8)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Mon 13/06/2011 10:00:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061311-22276-01.dmp
This was probably caused by the following module: sptd.sys (sptd+0x11BA0)
Bugcheck code: 0xA (0x60, 0x2, 0x1, 0xFFFFFFFF8310D90E)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\sptd.sys
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.
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: sptd.sys .
Google query: sptd.sys IRQL_NOT_LESS_OR_EQUAL




On Mon 23/05/2011 22:29:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052311-23524-01.dmp
This was probably caused by the following module: sptd.sys (sptd+0x11BA0)
Bugcheck code: 0xA (0x60, 0x2, 0x1, 0xFFFFFFFF82F0790E)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\sptd.sys
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.
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: sptd.sys .
Google query: sptd.sys IRQL_NOT_LESS_OR_EQUAL





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

7 crash dumps have been found and analyzed. 3 third party drivers have 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:

sptd.sys

ntkrpamp.exe

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.

[nardino]

Bonjour
Il semble que Alcohol ou DaemonTools soit en cause dans ton problème.
Il faut désactiver tous les lecteurs virtuels avant de désinstaller le programme et vérifier à l'usage si c'est bien la seule source du problème.
Comme la chose est parfois compliquée, je te conseille de le faire par Revo Uninstaller
Tutoriel RevoUnisntaller
Mais surtout commence par désactiver les lecteurs virtuels.
@+

[simo_be_01]

Bonjour

j'ai aucun lecteur virtuel installé sur mon ordi ??

[nardino]

Bonsoir,
Supprime ce fichier :
C:\Windows\system32\sptd.sys
@+