Bonjour,
Depuis quelques jours j'ai des écrans bleus à répétition et ce à n'importe quels moments et sans que je fasse quelque chose en particulier!!
J'ai testé ma ram avec memtest, j'ai fait un checkdisk, j'ai mis mes pilotes à jour mais rien n'y fait..........
merci d'avance de votre aide
Je joins un rapport de whocrashed
Ma config: Intel(R) Core(TM)2 Duo CPU E8400
2Go RAM Corsair
CM: Gigabyte EP45-DS4
RAdeon HD5750
DD Western Digital WD6400
Windows Seven Integrale 32 bits
merci d'avance de votre aide
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 07/03/2011 19:05:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030711-13322-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x4E23)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFFFFF8E77EE23)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 07/03/2011 18:11:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030711-13603-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x9F973)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82CB9973, 0xFFFFFFFF8B12B934, 0xFFFFFFFF8B12B510)
Error: SYSTEM_THREAD_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 system thread 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 Sat 05/03/2011 17:24:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030511-14414-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x11F1B6)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x110A0706, 0xFFFFFFFF94CBCB60)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 05/03/2011 16:42:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030511-13946-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x9F973)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82CE4973, 0xFFFFFFFF8B127934, 0xFFFFFFFF8B127510)
Error: SYSTEM_THREAD_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 system thread 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 01/03/2011 17:25:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030111-13712-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x59B0)
Bugcheck code: 0xC2 (0x99, 0xFFFFFFFF8A6ACB00, 0x0, 0x0)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 26/02/2011 16:15:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022611-17550-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x231334)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E42334, 0xFFFFFFFF8A3B6C50, 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 Sat 26/02/2011 15:25:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022611-14648-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4681B)
Bugcheck code: 0xA (0x30, 0x2, 0x0, 0xFFFFFFFF82F22F69)
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 Sat 26/02/2011 14:57:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022611-14242-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x231334)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E6D334, 0xFFFFFFFF8B003C50, 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 Sun 20/02/2011 09:58:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022011-19266-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x859EB)
Bugcheck code: 0x1A (0x41287, 0x4, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 19/02/2011 14:32:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021911-35583-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x85323)
Bugcheck code: 0xA (0x60F209, 0x2, 0x0, 0xFFFFFFFF82CDB66A)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Fri 18/02/2011 16:44:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021811-14071-01.dmp
This was probably caused by the following module: hdaudio.sys (HdAudio+0x36E33)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF9490FE33, 0xFFFFFFFF98174AFC, 0xFFFFFFFF981746E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\hdaudio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: High Definition Audio Function Driver
Bug check description: This indicates that a system thread 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 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 Wed 16/02/2011 18:26:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021611-14601-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x230EE4)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E3CEE4, 0xFFFFFFFF821B7C50, 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 Wed 16/02/2011 17:53:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021611-13977-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x1276)
Bugcheck code: 0x113 (0x4, 0xFFFFFFFF88369398, 0x0, 0x0)
Error: VIDEO_DXGKRNL_FATAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the dxg kernel has detected a violation.
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.
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 37 crash dumps have been found. Only 36 could be analyzed. Only 15 are included in this report. 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:
sptd.sys
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.
Ecran bleu .........
Re: Ecran bleu .........
Bonsoir,
Tu as bien installé un émulateur de CD comme Alcohol ou DaemonTools ?
Si oui désinstalle-le .
@+
Tu as bien installé un émulateur de CD comme Alcohol ou DaemonTools ?
Si oui désinstalle-le .
@+
En cas de problème constaté sur un sujet, contactez un modérateur par MP. N'intervenez pas vous-même. Merci
Re: Ecran bleu .........
bonjour,
ca y est je l'ai désinstallé mais j'ai toujours des problèmes............ce que je ne comprends pas dans le rapport whocrashed c'est que l'erreur change presque à chaque fois!!!
A l'aide
merci
ca y est je l'ai désinstallé mais j'ai toujours des problèmes............ce que je ne comprends pas dans le rapport whocrashed c'est que l'erreur change presque à chaque fois!!!
A l'aide
merci
Re: Ecran bleu .........
Bonsoir
AS-tu encore des BSoD depuis la désinstallation de ton émulateur ?
@
AS-tu encore des BSoD depuis la désinstallation de ton émulateur ?
@
En cas de problème constaté sur un sujet, contactez un modérateur par MP. N'intervenez pas vous-même. Merci
Re: Ecran bleu .........
oui toujours je renvoie le rapport whocrashed avec les 2 BSOD depuis que j'ai désinstallé daemon tools.
merci
@+
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 09/03/2011 16:43:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030911-11996-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x9F973)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82CF2973, 0xFFFFFFFF8C8BFAE0, 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 Wed 09/03/2011 16:36:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030911-12339-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x859EB)
Bugcheck code: 0x1A (0x41287, 0x40000024, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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.
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 41 crash dumps have been found. Only 40 could be analyzed. Only 15 are included in this report. 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:
sptd.sys
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
merci
@+
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 09/03/2011 16:43:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030911-11996-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x9F973)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82CF2973, 0xFFFFFFFF8C8BFAE0, 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 Wed 09/03/2011 16:36:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030911-12339-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x859EB)
Bugcheck code: 0x1A (0x41287, 0x40000024, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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.
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 41 crash dumps have been found. Only 40 could be analyzed. Only 15 are included in this report. 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:
sptd.sys
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
Re: Ecran bleu .........
Bonsoir
Télécharge DeFogger de Jpshortstuff sur le bureau.
http://www.jpshortstuff.247fixes.com/Defogger.exe
Double clic sur DeFogger
Sous Vista et Sept, clique droit e sur l'icône et sur "Exécuter en tant qu'administrateur".
Clique sur le bouton Disable pour désactiver les drivers d'émulateurs CD.
Cliquer sur Yes pour continuer.
Un message 'Finished!' apparaîtra, clique sur OK.
Il sera demander de redémarrer la machine, OK accepte.
@+
Télécharge DeFogger de Jpshortstuff sur le bureau.
http://www.jpshortstuff.247fixes.com/Defogger.exe
Double clic sur DeFogger
Sous Vista et Sept, clique droit e sur l'icône et sur "Exécuter en tant qu'administrateur".
Clique sur le bouton Disable pour désactiver les drivers d'émulateurs CD.
Cliquer sur Yes pour continuer.
Un message 'Finished!' apparaîtra, clique sur OK.
Il sera demander de redémarrer la machine, OK accepte.
@+
En cas de problème constaté sur un sujet, contactez un modérateur par MP. N'intervenez pas vous-même. Merci
Re: Ecran bleu .........
bonjour,
j'ai fait ta manip pour l'instant ça tourne pas de BSOD....................
je reposte si jamais
Merci bcp
@+
j'ai fait ta manip pour l'instant ça tourne pas de BSOD....................
je reposte si jamais
Merci bcp
@+
Re: Ecran bleu .........
Bonsoir
Il faudrait supprimer ce fichier :
C:/Windows/system32/sptd.sys
(je mets des slashes car je suis sous Mac et je n'ai pas encore trouvé les antislashes)
@+
Il faudrait supprimer ce fichier :
C:/Windows/system32/sptd.sys
(je mets des slashes car je suis sous Mac et je n'ai pas encore trouvé les antislashes)
@+
En cas de problème constaté sur un sujet, contactez un modérateur par MP. N'intervenez pas vous-même. Merci