ecran bleu( mis de côté)mais gros doutes d'infections

[débutants]

bonjour,

comme le sujet l'indique, notre pc s'arrête fréquemment en affichant un écran bleu , parfois il redémarre seul et parfois on doit l'arrêter manuellement.
le pc est récent, il a été changé dernièrement , donc on ne comprend pas trop , il y a très peu de logiciels aussi donc avec quoi serait-il incompatible ?

je vous remercie pour votre aide et le temps que vous y consacrez

bonne journée

windouws 7 familial premium service pack 1

[sherlock]

Avez-vous ajouté du matériel à l'ordinateur ? Nouvelle barette de ram par exemple.

[débutants]

bonjour

non il a fait cela dès le départ après son achat

merci pour votre aide

[nardino]

Bonjour,
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 .
Le rapport LOCALT~11.html sera dans le dossier du programme WhoCrashed.
@+

[grimpeur]

Bonjour nardino,
Le rapport est là http://www.forum-vista.net/forum/topic16654.html puisqu'il à posté sur les deux forum .

[débutants]

bonjour,

je vous remercie pour votre aide , en fait nous avons deux ordi un sous seven et un sous vista ( le vista marche beaucoup moins bien ) , donc il s'agit bien de deux pc sous systeme exploitation différents , donc meme sous seven puis-je faire comme vous m'avez indiqué plus haut ou que faire? merci et excusez nous pour le retard


bonne journée et merci pour le temps que vous y passer

[débutants]

bonjour

voici le rapport que vous m'avez indiquez précédemment

System Information (local)
--------------------------------------------------------------------------------

computer name: ...-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5800 @ 3.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4294172672 total
VM: 2147352576, free: 1947385856




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 26/10/2012 12:26:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102612-15912-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0xFFFFFB02F7DDB298, 0x2, 0x0, 0xFFFFF80002A394D7)
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 Fri 26/10/2012 12:26:27 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: l1c62x64.sys (L1C62x64+0x5534)
Bugcheck code: 0xA (0xFFFFFB02F7DDB298, 0x2, 0x0, 0xFFFFF80002A394D7)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\l1c62x64.sys
product: Atheros L1c PCI-E Gigabit Ethernet Controller
company: Atheros Communications, Inc.
description: Atheros L1c PCI-E Gigabit Ethernet Controller
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: l1c62x64.sys (Atheros L1c PCI-E Gigabit Ethernet Controller, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. IRQL_NOT_LESS_OR_EQUAL



On Wed 24/10/2012 12:55:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102412-15116-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF88001CF2360)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001CF2360)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote NDIS 6.20
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 that cannot be identified at this time.



On Wed 17/10/2012 13:52:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101712-17300-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002B3BCFB, 0xFFFFF88006C9DA60, 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 08/10/2012 14:21:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100812-15880-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF88001C89360)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001C89360)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote NDIS 6.20
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 that cannot be identified at this time.



On Fri 05/10/2012 17:32:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100512-15537-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF88001D107D1)
Bugcheck code: 0xD1 (0x29, 0x2, 0x0, 0xFFFFF88001D107D1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote NDIS 6.20
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 that cannot be identified at this time.



On Wed 03/10/2012 15:52:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100312-17160-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800440BA10, 0xFFFFF800047E14D8, 0xFFFFFA8004BEECC0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.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 that cannot be identified at this time.



On Sat 29/09/2012 18:30:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092912-17503-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x9B863000, 0x2, 0x0, 0xFFFFF80002AE82F0)
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 Fri 28/09/2012 07:14:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092812-16146-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF88001CC3360)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001CC3360)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote NDIS 6.20
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 that cannot be identified at this time.



On Tue 25/09/2012 06:33:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092512-16520-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF88001D12360)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001D12360)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote NDIS 6.20
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 that cannot be identified at this time.



On Fri 21/09/2012 16:40:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092112-16224-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF88001D02360)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001D02360)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote NDIS 6.20
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 that cannot be identified at this time.



On Fri 14/09/2012 18:23:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091412-18642-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF88001C3E360)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001C3E360)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote NDIS 6.20
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 that cannot be identified at this time.



On Tue 04/09/2012 16:05:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090412-14913-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF88001CCD650)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001CCD650)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote NDIS 6.20
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 that cannot be identified at this time.



On Thu 23/08/2012 08:02:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082312-17409-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF88001C5B650)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001C5B650)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote NDIS 6.20
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 that cannot be identified at this time.



On Sat 18/08/2012 12:37:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081812-14586-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF88001C26650)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001C26650)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote NDIS 6.20
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 that cannot be identified at this time.




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

21 crash dumps have been found and 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:

l1c62x64.sys (Atheros L1c PCI-E Gigabit Ethernet Controller, Atheros Communications, Inc.)

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.


---------------------

merci pour votre aide

[nardino]

Bonsoir,
Il semble que réinstaller le pilote de ta carte réseau soit une nécessite
@+

[débutants]

bonsoir

merci pour votre réponse

pouvez-vous m'indiquer comment réinstaller le pilote car je n'y connais absolument rien dans cette démarche ?

merci encore

[nardino]

Bonsoir,
Dans le menu démarrer, tape devmgmt.msc et valide par Entrer.
Dis-nous si tu vois une alerte sur le carte réseau.
Précise si tu as un pc de marque ou assemblé pour la suite.
@+
@