Diverses problèmes plutôt embêtant m'ont amenés à créer un sujet sur ce forum, étant donner que dans le passé j'avais eu des problèmes du même acabit et qu'un membre Einstein avait tenté de m'aider.
Je recevais de nombreuses écran bleues de manières aléatoire suite au branchement d'un casque microphone, et je pense que le problème venait du port rose microphone. Je pensais que le problème était résolu mais quelque temps après les écrans bleues revenait.
J'ai donc formaté mon pc et réinstallé Windows 7, mais le problème survenait encore parfois.
Mais depuis un certain temps, les écrans bleues sont devenues plus fréquentes.
Et depuis 4/5 jours, mon pc exécute un CHKDISK à chaque démarrage.
Mon problème me semble étrange puisque le rapport Whocrashed indique un problème de driver alors que le port microphone ne requiert pas de driver :
- Code: Tout sélectionner
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU E2200 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4294172672 total
VM: 2147352576, free: 1918353408
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 03/09/2013 20:10:26 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF80002ACF692)
Bugcheck code: 0x8 (0x40000000, 0x2, 0x0, 0xFFFFF80002ACF692)
Error: IRQL_NOT_DISPATCH_LEVEL
Bug check description: IRQL_NOT_DISPATCH_LEVEL
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.
Google query: IRQL_NOT_DISPATCH_LEVEL
On Sun 01/09/2013 13:31:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090113-32588-01.dmp
This was probably caused by the following module: hal.dll (hal+0x2CC60)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80073B4480, 0xFFFFFA80073B4560, 0x40E0008)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 that cannot be identified at this time.
On Fri 30/08/2013 09:00:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083013-29530-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000002.sys (Unloaded_Unknown_Module_00000000`00000002+0x8)
Bugcheck code: 0xD1 (0x44, 0x2, 0x0, 0xFFFFF88006C0AB0E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
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: unknown_module_00000000`00000002.sys .
Google query: unknown_module_00000000`00000002.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Thu 29/08/2013 13:16:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082913-28173-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xC5 (0x1E, 0x2, 0x0, 0xFFFFF80002BBFA9B)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid 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. 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.
On Tue 27/08/2013 08:12:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082713-25006-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFFA800709F060, 0xFFFFF88004625230, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.
On Tue 30/07/2013 20:33:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-28298-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002AB2F60, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 that cannot be identified at this time.
On Tue 30/07/2013 09:58:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-28204-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002AB7F60, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 that cannot be identified at this time.
On Mon 29/07/2013 11:42:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072913-29343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002A7C0D8, 0xFFFFF88005FE6E50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.
On Sun 28/07/2013 16:58:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072813-28033-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002A77610)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 that cannot be identified at this time.
On Sun 28/07/2013 16:52:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072813-29062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000047, 0xFFFFF80002AF47FC, 0xFFFFF880093016F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.
On Thu 18/07/2013 12:27:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071813-27190-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002ACC98D, 0xFFFFF8800AC7E130, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.
On Mon 01/07/2013 11:59:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070113-27846-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x18 (0xFFFFFA8003CDC100, 0xFFFFFA800436EC60, 0x1, 0x2)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
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 that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
12 crash dumps have been found and analyzed. 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:
unknown_module_00000000`00000002.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.
Je pense que toute les écrans bleues ne sont pas dans ce rapport, puisque parfois j'en reçoi mais le pc redémarre à 75% de la génération du log.
J'ai aussi vu une écran bleu System Hardware Failure (je crois) s'afficher pendant une seconde environ, qui s'est ensuite transformé en un autre écran bleu.
Merci pour votre aide, et désolé pour mon message qui doit être fortement confus.
N'hésitez pas à me demander des précisions ou des tests à faire.
Edit: Les appareils qui sont branchés sur mon ordinateur sur des ports usb sont :
- Une petite chose pour permettre à ma souris d'être reconnu par l'ordinateur.
- Une clé D-Link faisant office de carte internet.
Cela m'étonnerait quand même que le problème vienne de là, mais je donne quand même cette information.
je te dit demain !
