BSOD aléatoire quand je redémarre Windows 7

[d a r t h]

bonjour

depuis quelques jour, j'ai un probleme avec mon pc : windows 7 SP1 provoque de temps en temps un écran bleu quand je demande un redémarrage ! ce n'est pas systématique.

le message de base est IRQ NOT LESS OR EQUAL (classique) soit Tcpip.sys soit un code exa

j'ai eu un probleme de crash disque dur cette semaine, j'en ai mis un nouveau - le problème date d'un peu avant.

je viens de tester ma ram avec windows, elle est clean

testé malware avec : avast, malwarebyte, roguekiller > rien (note : pour la sécurité j'utilise Avast et Comodo...

sinon en fonctionnement tout est correct , a part un probleme de crash explorer qui arrive de temps en temps depuis quelques mois (pas très handicapant)

des idées...?

merci d'avance

[Wullfk]

Bonjour,

 

Normalement les BSOD sont souvent du à un ou des pilotes qui ne sont pas à jour.

 

Pour en savoir plus, télécharge et installe Whocrashed et poste le rapport de plantage

[d a r t h]

System Information (local)

Computer name: ANAKIN
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: P5Q-PRO, , ASUSTeK Computer INC.
CPU: GenuineIntel Intel® Core2 Quad CPU Q9450 @ 2.66GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3488669696 bytes total

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 25/09/2015 17:16:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092515-14008-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5C64B)
Bugcheck code: 0x12E (0xFFFFFFFF89A0AD48, 0xFFFFFFFF89184B90, 0x29013640, 0x120)
Error: INVALID_MDL_RANGE
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: IoBuildPartialMdl was called with a virtual address range outside the range of the source MDL.
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 25/09/2015 17:16:11 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5C64B)
Bugcheck code: 0x12E (0xFFFFFFFF89A0AD48, 0xFFFFFFFF89184B90, 0x29013640, 0x120)
Error: INVALID_MDL_RANGE
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: IoBuildPartialMdl was called with a virtual address range outside the range of the source MDL.
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 25/09/2015 14:04:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092515-16536-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x55AC)
Bugcheck code: 0xD1 (0xF7DB1E8, 0x2, 0x0, 0xFFFFFFFF87DF5AE2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 24/09/2015 18:34:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092415-44288-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x8AB3B)
Bugcheck code: 0xD1 (0xFFFFFFFF900BA338, 0x2, 0x0, 0xFFFFFFFF8CEA2B3B)
Error: DRIVER_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 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 24/09/2015 08:35:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092415-14024-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x8AB3B)
Bugcheck code: 0xD1 (0xFFFFFFFF99CEBCC8, 0x2, 0x0, 0xFFFFFFFF8CEB3B3B)
Error: DRIVER_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 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 24/09/2015 06:26:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092415-14430-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x8AB3B)
Bugcheck code: 0xD1 (0xFFFFFFFFA57F2D68, 0x2, 0x0, 0xFFFFFFFF8CE99B3B)
Error: DRIVER_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 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 24/09/2015 05:54:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092415-14851-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x8AB3B)
Bugcheck code: 0xD1 (0xFFFFFFFF92E3B4A8, 0x2, 0x0, 0xFFFFFFFF8CEC7B3B)
Error: DRIVER_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 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 Mon 21/09/2015 06:47:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092115-13930-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x8AB3B)
Bugcheck code: 0xD1 (0xFFFFFFFF90284098, 0x2, 0x0, 0xFFFFFFFF8CE8BB3B)
Error: DRIVER_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 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.

[Wullfk]

Bonjour,

 

Vérifier sur le site d'ASUS (avec la référence de ta carte mère) s'il existe un driver récent de la carte réseau, c'est pas garantie car la carte mère ASUS P5Q-PRO n'est plus toute jeune.

 

Sinon essais en désinstallant le pilote de la carte réseau, redémarrer le PC, et réinstaller le driver le plus récent disponible.

[d a r t h]

je n'utilise pas le chipset réseau (100) mais une carte gigabit

sinon j'ai testé la ram avec memtest : ok et j'ai fait un sfc : windows est intègre...

[Wullfk]

Re,

 

Dans ce cas vérifie sur le site de Gigabyte si il y a un driver plus récent pour ta carte réseau.

 

Bon si MemTest et SFC n'ont pas retourné d'erreur, y a plus qu'a espéré que les BSOD ne reviennent pas, car dans le cas contraire je vois pas ce qu'on pourrait faire de plus.

[d a r t h]

ça revient de temps en temps, un uniquement avant de redémarrer, sinon le pc fonctionne normalement , j'ai vérifié les voltages :

cpu 1,208v

3,3v : 3,312V

5v : 5,112v

12v : 11,984v

 

pour moi c'est normal...