Problème démarrage fréquent et bluescreens occasionnels

[Malekal_morte]

Fais un memtest : http://forum.malekal.com/tester-materie ... 44006.html

[Fab100584]

Salut Malekal_morte,

Le memtest a déjà été fait. 2 pass et 0 erreur.

[SkyTech]

Bonjour,

Est-ce que je peux me contenter de désinstaller complètement les drivers pour voir ce que ça donne ? Si non, est-ce qu'il y a un moyen de désactiver la carte sans avoir à l'a retirer ?

Oui tu peux désactiver la carte dans le Gestionnaire de périphériques.

[Fab100584]

Salut,

Ok merci, je vais essayer alors parce que malgré un énième "désinstaller/nettoyer/réinstaller" j'ai toujours des problèmes :



On Mon 12/05/2014 19:36:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051214-8548-01.dmp
This was probably caused by the following module: ha20x22k.sys (0xFFFFF880060F1485)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880060F1485, 0xFFFFF88003976828, 0xFFFFF88003976080)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ha20x22k.sys
product: Creative Audio Product
company: Creative Technology Ltd
description: Creative 20X2 HAL (WDM)
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.
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: ha20x22k.sys (Creative 20X2 HAL (WDM), Creative Technology Ltd).
Google query: Creative Technology Ltd SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Mon 12/05/2014 19:36:28 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: emupia2k.sys (emupia2k+0x8400)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF880060F1485, 0xFFFFF88003976828, 0xFFFFF88003976080)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\emupia2k.sys
product: E-mu Plug-In Architecture
company: Creative Technology Ltd
description: E-mu Plug-in Architecture Driver (WDM)
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: emupia2k.sys (E-mu Plug-in Architecture Driver (WDM), Creative Technology Ltd).
Google query: Creative Technology Ltd SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Mon 12/05/2014 13:19:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051214-8829-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800059D510, 0xFFFF, 0x0)
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 that cannot be identified at this time.

[SkyTech]

Si le périphérique est défectueux, manipulé le pilote n'y changera rien.