bonjour à toutes et tous,

c'est mon premier message et il est pour demander quelques conseils.

je pense que mon dual core est hs (ou va bientôt l'être).

caractéristique technique :

j'ai un intel(r) core(TM) 2 duo cpu E8400 @ 3.00GHz 2(CPUs), ~3.0GHz

carte mére une P5Q-E asus

et 4096MB ram kingston

windows 7 édition familiale premium 32 bits (6.1, version 7601) (un vrai)

depuis quelques jours mon pc fait de temps en temps des écrans bleu.

après avoir memtest qui me dit tout est ok sur la ram j'ai pris speedfan et la surprise : je n'ai que core : 0 alors que je devrais avoir logiquement core : 0 et core : 1

je me dit qu'un cœur a "lâché" prise. est-ce bien le cas?

si oui quel processeur acheter pour remplacer le miens? (je joue pas au jeux et je ne veut que du intel)

sur ldlc j'ai vu celui ci : Intel Core i3-2120 (3.3 GHz) a 94 euro est-ce compatible avec ma carte mère?

merci pour vos avis et peut etre votre aide.

bonne journée.

Modifié par eltarion le 22/09/2014 15:13

je ne sais pas si tes problemes viennent du cpu mais voici ceux supportés par cette carte mère

http://www.asus.com/fr/Motherboards/P5QE/HelpDesk_CPU/

edit :

lance whocrashed et poste le rapport pour voir

http://www.resplendence.com/download/whocrashedSetup.exe

Modifié par spokastuces le 22/09/2014 15:49

merci beaucoup, voici le rapport :

System Information (local)

---

computer name: ELTARION-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: P5Q-E, , ASUSTeK Computer INC.
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3488669696 total

---

Crash Dump Analysis

---

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 21/09/2014 16:12:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092114-24710-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC39E5)
Bugcheck code: 0xA (0x4CF, 0x2, 0x1, 0xFFFFFFFF82C99A49)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 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 Sun 21/09/2014 16:12:14 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngBitBlt+0x805E)
Bugcheck code: 0xA (0x4CF, 0x2, 0x1, 0xFFFFFFFF82C99A49)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 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 20/09/2014 06:32:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092014-25693-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x4571)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 19/09/2014 08:18:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091914-24616-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x19F82)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: AVAST Software UNEXPECTED_KERNEL_MODE_TRAP



On Thu 18/09/2014 15:24:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091814-23368-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x4804)
Bugcheck code: 0xD1 (0x7402587F, 0x2, 0x1, 0xFFFFFFFF8BC36804)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
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/09/2014 15:54:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091714-45708-01.dmp
This was probably caused by the following module: aswstm.sys (aswStm+0x476B)
Bugcheck code: 0xD1 (0xF15886, 0x2, 0x1, 0xFFFFFFFF8BC1DB50)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\aswstm.sys
product: avast! Antivirus
company: AVAST Software
description: Stream Filter
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: aswstm.sys (Stream Filter, AVAST Software).
Google query: AVAST Software DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 17/09/2014 11:32:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091714-43040-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x67D43)
Bugcheck code: 0xD1 (0x10, 0x2, 0x1, 0xFFFFFFFF8C29DD43)
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 Tue 16/09/2014 21:00:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091614-17596-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x474F)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFFFFF8BC4274F)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
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 16/09/2014 13:24:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091614-19250-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x49E0)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF8ADC453C, 0xFFFFFFFF82D608B8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
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 that cannot be identified at this time.

---

Conclusion

---

9 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:

aswstm.sys (Stream Filter, AVAST Software)
aswsnx.sys (avast! Virtualization Driver, AVAST Software)

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 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.

si tu as besoin de plus de détail n’hésite pas :)

Modifié par eltarion le 22/09/2014 16:47

CPU-Z TXT Report

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

Binaries

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

CPU-Z version1.70.0.x32

Processors

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

Number of processors1

Number of threads2

APICs

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

Processor 0

-- Core 0

-- Thread 00

-- Core 1

-- Thread 01

Timers

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

ACPI timer3.580 MHz

HPET timer14.318 MHz

Perf timer2.929 MHz

Sys timer1.000 KHz

Processors Information

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

Processor 1ID = 0

Number of cores2 (max 2)

Number of threads2 (max 2)

NameIntel Core 2 Duo E8400

CodenameWolfdale

SpecificationIntel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz

Package (platform ID)Socket 775 LGA (0x0)

CPUID6.7.A

Extended CPUID6.17

Core SteppingE0

Technology45 nm

TDP Limit65 Watts

Core Speed1970.8 MHz

Multiplier x Bus Speed6.0 x 328.5 MHz

Rated Bus speed1313.8 MHz

Stock frequency3000 MHz

Instructions setsMMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, EM64T, VT-x

L1 Data cache2 x 32 KBytes, 8-way set associative, 64-byte line size

L1 Instruction cache2 x 32 KBytes, 8-way set associative, 64-byte line size

L2 cache6144 KBytes, 24-way set associative, 64-byte line size

FID/VID Controlyes

FID range6.0x - 9.0x

Max VID1.250 V

Thread dumps

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

CPU Thread 0

APIC ID0

TopologyProcessor ID 0, Core ID 0, Thread ID 0

Type01008001h

Max CPUID level0000000Dh

Max CPUID ext. level80000008h

Cache descriptorLevel 1, D, 32 KB, 1 thread(s)

Cache descriptorLevel 1, I, 32 KB, 1 thread(s)

Cache descriptorLevel 2, U, 6 MB, 2 thread(s)

CPU Thread 1

APIC ID1

TopologyProcessor ID 0, Core ID 1, Thread ID 0

Type01008001h

Max CPUID level0000000Dh

Max CPUID ext. level80000008h

Cache descriptorLevel 1, D, 32 KB, 1 thread(s)

Cache descriptorLevel 1, I, 32 KB, 1 thread(s)

Cache descriptorLevel 2, U, 6 MB, 2 thread(s)

Chipset

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

NorthbridgeIntel P45/P43/G45/G43 rev. A2

SouthbridgeIntel 82801JR (ICH10R) rev. 00

Graphic InterfacePCI-Express

PCI-E Link Widthx16

PCI-E Max Link Widthx16

Memory TypeDDR2

Memory Size4 GBytes

ChannelsDual, (Symmetric)

Memory Frequency328.5 MHz (1:1)

CAS# latency (CL)5.0

RAS# to CAS# delay (tRCD)5

RAS# Precharge (tRP)5

Cycle Time (tRAS)15

Row Refresh Cycle Time (tRFC)44

Command Rate (CR)2T

MCHBAR I/O Base address0x0FED14000

MCHBAR I/O Size4096

Memory SPD

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

DIMM #1

SMBus address0x50

Memory typeDDR2

Module formatRegular UDIMM

Manufacturer (ID)Kingston (7F980000000000000000)

Size2048 MBytes

Max bandwidthPC2-5300 (333 MHz)

Part number2G-UDIMM

Serial numberA91D6B3A

Manufacturing dateWeek 30/Year 08

Number of banks2

Data width64 bits

CorrectionNone

Nominal Voltage1.80 Volts

EPPno

XMPno

AMPno

JEDEC timings tableCL-tRCD-tRP-tRAS-tRC @ frequency

JEDEC #13.0-3-3-9-12 @ 200 MHz

JEDEC #24.0-4-4-12-16 @ 266 MHz

JEDEC #35.0-5-5-15-20 @ 333 MHz

DIMM #2

SMBus address0x52

Memory typeDDR2

Module formatRegular UDIMM

Manufacturer (ID)Kingston (7F980000000000000000)

Size2048 MBytes

Max bandwidthPC2-5300 (333 MHz)

Part number2G-UDIMM

Serial numberA91DCD39

Manufacturing dateWeek 30/Year 08

Number of banks2

Data width64 bits

CorrectionNone

Nominal Voltage1.80 Volts

EPPno

XMPno

AMPno

JEDEC timings tableCL-tRCD-tRP-tRAS-tRC @ frequency

JEDEC #13.0-3-3-9-12 @ 200 MHz

JEDEC #24.0-4-4-12-16 @ 266 MHz

JEDEC #35.0-5-5-15-20 @ 333 MHz

Monitoring

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

Mainboard ModelP5Q-E (0x00000148 - 0x0002D0D0)

LPCIO

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

LPCIO VendorWinbond

LPCIO ModelW83667HG

LPCIO Vendor ID0x5CA3

LPCIO Chip ID0xA5

LPCIO Revision ID0x13

Config Mode I/O address0x2E

Config Mode LDN0xB

Config Mode registers

Hardware Monitors ------------------------------------------------------------------------- Hardware monitor Winbond W83667HG Voltage 0 0.92 Volts [0x73] (CPU VCORE) Voltage 1 1.70 Volts [0xD5] (VIN1) Voltage 2 3.22 Volts [0xC9] (+3.3V) Voltage 3 4.78 Volts [0xC7] (+5V) Voltage 4 11.54 Volts [0xCF] (+12V) Voltage 6 1.27 Volts [0x9F] (VIN6) Temperature 0 36°C (96°F) [0x24] (SYSTIN) Temperature 1 23°C (72°F) [0x2D] (CPUTIN) Temperature 2 21°C (69°F) [0x2A] (AUXTIN) Fan 1 1430 RPM [0x3B] (CPUFANIN0) Hardware registers Register space LPC, base address = 0x0290

ok, bon la quête de l'écran bleu continue ^^

c'est pas mon cpu, c'est pas ma ram, peut être la carte graphique, qu'en pensez vous?

pour mes pilotes je passe par tous les drivers et je ne prend que ceux certifié WHQL (et ils sont tous a jours à priori)

vu que dans le rapport de whocrashed il parle d'avast, j'ai désinstallé avast et réinstallé "propre" avec le programme du site avast (pas sur clubic ou 01net) vu que je l'ai payé j'aimerais bien qu'il fonctionne sans faire d'histoire avec mon pc ^^ (si le problème viens de la évidement)

Modifié par eltarion le 22/09/2014 17:46

bonsoir

possible alim capricieuse

marque et puissance en watts

possible machine infectée

scan malwarebytes et adwcleaner

puis

http://www.eset.com/fr/home/products/online-scanner/

a+

PhilDo94

Modifié par boubou38 le 22/09/2014 18:18

bonjour,

voici les nouvelles,

j'ai fait un chkdsk ca n'a rien donné.

j'ai fait :

scan malwarebytes et adwcleaner

puis

http://www.eset.com/fr/home/products/online-scanner/

il a trouvé quelques virus et autre trojan au moins ça a fait un peu de ménage ^^ mais l'écran bleu est revenu ce matin alors j'ai désinstalé le pilote de ma carte graphique, redémarré et réinstallé, idem avec la carte réseau. je vais regarder pour l'alim mais plus tard j'en profiterais pour faire la poussières, sait t'on jamais :)

bonjour a toutes et tous,

il semblerait que boubou38 as trouvé la solution a mon problème.

après avoir ouvert le pc et nettoyé il ne c’est jamais rallumé ^^'

après m'être assuré que rien n'avais bougé (connectique etc) qui justifierais ce refus de s’allumer je suis donc allé chercher à la cave l'alim qui était fournis avec la tour (ça date!!!!) et que j'avais remplacé par une antec 550w

après avoir tout re-démonté, changé l'alim et tout remonté le pc est repartis plus vaillant que jamais!!

(j'en ai même profité pour nettoyer mon processeur de sa vieille pâte et remis une nouvelle pâte thermique, puisque mon volumineux ventirad zalman m’empêchais d'enlever l'alim)

voila, je vais attendre quelques jours mais je penses que le problème est réglé, je reviendrais pour cliquer sur "résolu" si dans quelques jours toujours pas d'écran bleu.

en tous cas merci pour votre aide c'est vraiment super sympa :)

bonne soirée.

bonsoir

ah!! ces alim !!! finalement elles sont souvent en causes

content pour toi

a+

edit :coche ton sujet "résolu" si tu considères qu'il est

PhilDo94

Modifié par boubou38 le 27/09/2014 10:25

bonjour,

je n'ai plus aucun écran bleue, c'était donc bien l'alimentation.

merci beaucoup pour votre aide.

bonne journée.