BSOD aléatoire

Tous les problèmes de Windows : message d'erreur, BSOD et écran bleu, erreur Windows Update ou d'installation, etc

Modérateur : Mods Windows

Omegagoth

BSOD aléatoire

par Omegagoth »

Bonjour,

je viens vers vous car je suis un peu désespéré. J'ai des BSOD à répétition. Le rapport WhoCrashed (cf fin de message) m'indique une erreur mémoire mais pas que ?! plein d'autre choses je ne sais pas quoi faire j'ai l'impression que tout plante il doit bien il y avoir une cause commune non ?
Je précise que je suis sur un aspire T160 et que j'ai déjà eu des soucis dessus (certe il a 5 ans mais bon) j'ai du changer des ports USB de façade qui avaient des problèmes d'alimentation.
System Information (local)
--------------------------------------------------------------------------------

computer name: PC-JIJI
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) 64 Processor 3400+ AMD586, level: 15
1 logical processors, active mask: 1
RAM: 1005117440 total
VM: 2147352576, free: 1945923584



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 05/09/2012 21:14:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090512-27421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x120F1F)
Bugcheck code: 0x10000050 (0xFFFFFFFF9462884A, 0x0, 0xFFFFFFFF82B22F1F, 0x2)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 05/09/2012 20:52:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090512-31312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xDEE9C)
Bugcheck code: 0x1A (0x411, 0xFFFFFFFFC0000908, 0x11007884, 0xFFFFFFFFC5000909)
Error: MEMORY_MANAGEMENT
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 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 Tue 04/09/2012 21:00:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090412-33546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x8474B)
Bugcheck code: 0x21 (0x0, 0x0, 0x40B03A0, 0x3F1711C)
Error: QUOTA_UNDERFLOW
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 quota charges have been mishandled by returning more quota to a particular block than was previously charged.
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 03/09/2012 20:25:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090312-23718-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xDB3E9)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9452B3E9, 0xFFFFFFFF9BC03708, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 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 04/08/2012 16:18:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080412-29296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22D0D6)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A670D6, 0xFFFFFFFFA0429A3C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 04/08/2012 12:48:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080412-26796-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9AF)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF8B2F47C8, 0xFFFFFFFF8B2F43A0, 0xFFFFFFFF8284195A)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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 04/08/2012 12:23:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080412-29593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x12068C)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF84640700, 0xFFFFFFFF84F40700, 0xFFFFFFFF84640700)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
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 Thu 26/07/2012 06:43:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072612-27875-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCDE1D)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF801DB000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
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 a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 21/07/2012 21:48:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072312-21109-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x9FC36)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF823EFC36, 0xFFFFFFFFACC29C28, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 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 20/07/2012 07:17:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072012-36828-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x184616)
Bugcheck code: 0x100000D1 (0xFFFFFFFF823B4616, 0xFF, 0x8, 0xFFFFFFFF823B4616)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 18/07/2012 19:20:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071812-19250-01.dmp
This was probably caused by the following module: epfwlwf.sys (EpfwLWF+0x3AAD)
Bugcheck code: 0x100000D1 (0x10, 0x2, 0x1, 0xFFFFFFFF87A6BE8F)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\epfwlwf.sys
product: ESET Smart Security
company: ESET
description: Epfw NDIS LightWeight Filter
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: epfwlwf.sys (Epfw NDIS LightWeight Filter, ESET).
Google query: epfwlwf.sys ESET CUSTOM_ERROR




On Sun 15/07/2012 21:40:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071512-23718-01.dmp
This was probably caused by the following module: sptd.sys (sptd+0x18E31)
Bugcheck code: 0x100000D1 (0x1000BB8D, 0x2, 0x1, 0xFFFFFFFF8DAAA360)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\sptd.sys
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 CUSTOM_ERROR




On Sun 15/07/2012 16:44:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071512-26156-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x19D19)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF8463F538, 0xFFFFFFFFF4D3F538, 0xFFFFFFFF8463F538)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that a pool header is corrupt.
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 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 14/07/2012 14:09:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071412-28328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xC8F30)
Bugcheck code: 0x1000000A (0xFFFFFFFFC03E59D0, 0x0, 0x0, 0xFFFFFFFF82903F30)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 11/07/2012 15:31:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071112-43328-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2D48C)
Bugcheck code: 0x10000050 (0xFFFFFFFFB5176914, 0x1, 0xFFFFFFFF8E58E48C, 0x2)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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
--------------------------------------------------------------------------------

15 crash dumps have been found and analyzed. 2 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:

epfwlwf.sys (Epfw NDIS LightWeight Filter, ESET)

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.


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.
Avatar de l’utilisateur
angelique
Messages : 31147
Inscription : 28 févr. 2008 13:58
Localisation : Breizhilienne

Re: BSOD aléatoire

par angelique »

Desinstalle ton antivirus ESET Smart Security voir si ç'est mieux !
Avec Gnu_Linux t'as un Noyau ... avec Ѡindows t'as que les pépins
https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/
Ne soyez pas Rat!Je fais parti des millions de pauvres en France
Image
Omegagoth

Re: BSOD aléatoire

par Omegagoth »

Non ça ne change rien, j'avais déjà essayé suite au BSOD où WhoCrashed m'avait dit que c'était à cause d'ESET mais ça na rien changé.
  • Sujets similaires
    Réponses
    Vues
    Dernier message

Revenir à « Windows : Résoudre les problèmes »