Ecrans bleus intempestfis

Ecrans bleus intempestfis - Matériels & problèmes divers - Hardware

Marsh Posté le 04-01-2012 à 08:20:22    

Bonjour à tous,
 
Depuis que j'ai acheté mon PC, c'est à dire il y a un an, j'ai énormément d'écrans bleus. Le Pc a été monté par mes soins, pour la première fois, et je reste persuadé que je l'ai mal monté à cause de ça.
En terme d'écran bleu, depuis un an, j'ai tout eu, à savoir :
- System service exception (le plus souvent)
- Mémory management (en 2e position)
- bad pool header
- page bault in nonpage area, cache manager et epc uindex mismach qui ne sont arrivées qu'une ou deux fois.
 
Voici la config' de mon PC :
- Phenom II 955 BE
- CM MSI 870A-G54
- Boitier Fractal R3  
- CG Sapphire HD 5770 1Go
- DD Caviar Blue 1To
- Hyper Plus 212
- Graveur LG GH22NS50  
- 4 Go OCZ PC3-10666  
- Alim Corsair 400W
- Win Seven 64bits  
 
J'étais déjà venu cherche de l'aide, j'espère que vous pourrez m'aider davantage cette fois-ci...
 
Merci,

Reply

Marsh Posté le 04-01-2012 à 08:20:22   

Reply

Marsh Posté le 04-01-2012 à 19:19:28    

Personne après une journée pour m'aider ?

Reply

Marsh Posté le 04-01-2012 à 19:34:11    

Salut, as-tu fait les mises à jour BIOS ainsi que les mises à jour Windows Update (comme SP1 par exemple)?


---------------
Intel Core i7 2600K / Corsair H60 / Asus P8P67 Deluxe / Asus GTX 580 DirectCUII / Corsair Vengeance 1866 MHz 2x4 Go CAS9 / NZXT Phantom rouge et blanc / Seasonic X-850 / Corsair Force Series GT 240 Go / Western Digital Caviar Blue 1 To SATA III / Lite-On
Reply

Marsh Posté le 04-01-2012 à 19:42:46    

salut, qu'entend tu par "enormement"....la frequence ?
 
ecran bleu a répétition = soit un probleme driver/bios, soit un probleme "physique" de materiel...
 
il faudrai telecharger des logicieles de "test de stabilité" type occt, memtest etc...
de facon a pouvoir faire des test de stabilité...

Reply

Marsh Posté le 04-01-2012 à 22:49:04    

Ca fonctionne par vague, je peux en avoir une dizaine par jour, et pendant 3-4 jours rien.
 
Pour les MAJ, je les fais toutes via le téléchargement automatique de windows. Pour le BIOS, non je n'ai jamais fait.

Reply

Marsh Posté le 04-01-2012 à 23:08:56    

commence par ca déjà...

Reply

Marsh Posté le 05-01-2012 à 01:04:19    

Je vote pour un bon gros memtest !

 

Avant même la tentative de flashage du bios (toujours un poil dangereux ça...)


Message édité par Fraisouille le 05-01-2012 à 01:04:38
Reply

Marsh Posté le 05-01-2012 à 01:19:29    

Oué mais faut savoir vivre dangereusement.


---------------
Intel Core i7 2600K / Corsair H60 / Asus P8P67 Deluxe / Asus GTX 580 DirectCUII / Corsair Vengeance 1866 MHz 2x4 Go CAS9 / NZXT Phantom rouge et blanc / Seasonic X-850 / Corsair Force Series GT 240 Go / Western Digital Caviar Blue 1 To SATA III / Lite-On
Reply

Marsh Posté le 05-01-2012 à 09:56:49    

salut, pour la màj bios, ne la fait pas sous windows, tu risques d'avoir un bsod à ce moment et après ouille ouille ouille
enfin bref, sinon memetest au démarrage de la machine en dos
ensuite whocrashed et diskinfo pour essayer d'en savoir un peu plus
moi j'ai aussi eu de gros soucis début décembre et c'est mon hdd qui était en train de flancher... avant de trouver j'ai changer de ram et de CM!
bonne chance


---------------
Feedback  - Mes ventes
Reply

Marsh Posté le 05-01-2012 à 10:10:14    

Les alim corsair 400w sont pas terrible, non ?


---------------
Dans la vie, y a ceux qui cherchent, et ceux qui trouvent !
Reply

Marsh Posté le 05-01-2012 à 10:10:14   

Reply

Marsh Posté le 05-01-2012 à 14:29:18    

L'alim corsair, on me la conseillait !
 
Sinon, j'ai fait whocrashed, et voilà ce que j'ai eu :
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
 
On Thu 05/01/2012 12:32:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010512-28220-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5B68)  
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88002A0B8D8, 0xFFFFF88002A0B140, 0xFFFFF880012B0787)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.  
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 which cannot be identified at this time.  
 
 
On Thu 05/01/2012 12:32:55 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5B68)  
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88002A0B8D8, 0xFFFFF88002A0B140, 0xFFFFF880012B0787)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.  
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 which cannot be identified at this time.  
 
 
On Thu 05/01/2012 12:26:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010512-27783-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x360682)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800033B5682, 0xFFFFF880031AFA48, 0xFFFFF880031AF2B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.  
 
 
On Mon 02/01/2012 21:04:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010312-27034-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x360682)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003365682, 0xFFFFF880031AFA48, 0xFFFFF880031AF2B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.  
 
 
On Mon 02/01/2012 20:59:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010212-27128-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x360682)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800033B7682, 0xFFFFF880031AFA48, 0xFFFFF880031AF2B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.  
 
 
On Mon 02/01/2012 20:55:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010212-27643-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x360682)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003375682, 0xFFFFF880031AFA48, 0xFFFFF880031AF2B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.  
 
 
On Mon 02/01/2012 20:50:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010212-28204-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031BD90D, 0xFFFFF8800AD42D20, 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 which cannot be identified at this time.  
 
 
On Mon 02/01/2012 16:14:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010212-23836-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x360682)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800033BD682, 0xFFFFF880031CBA48, 0xFFFFF880031CB2B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.  
 
 
On Mon 02/01/2012 10:47:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010212-23150-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x360682)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800033AB682, 0xFFFFF880031BDA48, 0xFFFFF880031BD2B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.  
 
 
On Sat 31/12/2011 10:30:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123111-20014-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x49AE, 0x49AC00009358)
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 which cannot be identified at this time.  
 
 
On Thu 29/12/2011 17:16:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122911-20046-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x159D95)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001B9D95, 0xFFFFF8800AC38100, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.  
 
 
On Thu 29/12/2011 17:14:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122911-17940-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5BC5E)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800165BC5E, 0xFFFFF880031A1948, 0xFFFFF880031A11B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.  
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 which cannot be identified at this time.  
 
 
On Sun 18/12/2011 20:43:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121811-24304-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800033A667F, 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 which cannot be identified at this time.  
 
 
On Sun 18/12/2011 20:38:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121811-26582-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1F08)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88005331F08, 0xFFFFF8800A4DB6F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.  
 
 
On Fri 16/12/2011 22:55:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121711-24850-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000016140, 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 which cannot be identified at this time.  
 
 
Sinon, comment utilise t-on memtest86 ?
Une fois dans le menu, l'analyse dure 6 secondes et c'est tout...
 
Sinon, j'ai fait une analyse hier avec memtest tout court :
-------------------------------------------------------------------------
 
Binaries
-------------------------------------------------------------------------
 
HWMonitor version 1.1.7.0
 
Monitoring
-------------------------------------------------------------------------
 
Mainboard Model 870A-G54 (MS-7599) (0x000003D9 - 0xD2734720)
 
LPCIO
-------------------------------------------------------------------------
 
LPCIO Vendor Fintek
LPCIO Model F71889ED
LPCIO Vendor ID 0x1934
LPCIO Chip ID 0x909
Config Mode I/O address 0x4E
Config Mode LDN 0x4
Config Mode registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 FF FF 00 FF FF FF FF 04 FF FF FF FF FF FF FF FF
10 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
20 09 09 10 19 34 00 00 12 00 FF C5 FC 03 08 00 00
30 01 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
40 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
50 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
60 06 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
70 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Register space LPC, base address = 0x0600
 
 
Hardware Monitors
-------------------------------------------------------------------------
 
Hardware monitor Fintek F71889ED
Voltage 0 3.36 Volts [0xD2] (+3.3V)
Voltage 1 1.32 Volts [0xA5] (CPU VCORE)
Voltage 2 2.21 Volts [0x8A] (VIN2)
Voltage 3 1.28 Volts [0x6D] (VIN3)
Voltage 4 3.07 Volts [0x49] (+5V)
Voltage 5 14.17 Volts [0xA1] (+12V)
Voltage 6 3.15 Volts [0xC5] (VIN6)
Voltage 7 3.36 Volts [0xD2] (VSB3V)
Voltage 8 3.28 Volts [0xCD] (VBAT)
Temperature 0 29°C (84°F) [0x1D] (TMPIN0)
Temperature 2 32°C (89°F) [0x20] (TMPIN2)
Fan 0 2063 RPM [0x2D7] (FANIN0)
Fan 1 1279 RPM [0x495] (FANIN1)
Fan PWM 0 100 pc [0xFF] (CPU)
Fan PWM 1 100 pc [0xFF] (System Fan 1)
Fan PWM 2 100 pc [0xFF] (System Fan 2)
Fan PWM 3 100 pc [0xFF] (System Fan 3)
Register space LPC, base address = 0x0600
 
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 FF C3 00 01 01 FF FF 00 FF FF 01 00 55 4C 00 30
10 00 00 00 00 00 00 FF FF FF FF FF FF FF FF FF FF
20 D2 74 8B 6D 49 A1 C5 D2 CD FF FF FF FF FF FF FF
30 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
40 44 FF FF 00 00 00 00 FF FF FF FF FF FF FF FF FF
50 FF FF FF FF FF FF FF FF FF FF 03 04 10 19 34 FF
60 00 00 AA 00 FF FF 00 78 00 00 FF 0E 40 24 FF 04
70 FF FF 1D FF 80 FF 20 FF 00 00 00 00 00 1D 00 00
80 FF FF FF FF FF FF FF FF FF FF FF FF FF FF A8 FF
90 00 04 04 00 16 FF 3F FF 42 04 FF 2A 55 05 99 0A
A0 02 D7 00 FF 03 C1 3C 32 28 1E FF E5 CE B7 A0 0D
B0 04 95 00 FF 03 FF 3C 32 28 1E FF D9 B2 99 80 0E
C0 0F FF 00 FF 03 FF 3C 32 28 1E FF D9 B2 99 80 0F
D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
E0 00 00 00 00 00 00 00 00 00 FF FF FF 00 00 01 00
F0 00 00 00 00 00 00 33 FF 01 88 FF 00 FF 00 FF FF
 
Hardware monitor AMD ADL
Voltage 0 1.00 Volts [0x3E8] (VIN0)
Temperature 0 39°C (102°F) [0x27] (TMPIN0)
 
 
Processors
-------------------------------------------------------------------------
 
Number of processors 1
Number of threads 4
 
APICs
-------------------------------------------------------------------------
 
Processor 0
-- Core 0
-- Thread 0 0
-- Core 1
-- Thread 0 1
-- Core 2
-- Thread 0 2
-- Core 3
-- Thread 0 3
 
Processors Information
-------------------------------------------------------------------------
 
Processor 1 ID = 0
Number of cores 4 (max 4)
Number of threads 4 (max 4)
Name AMD Phenom II X4 955
Codename Deneb
Specification AMD Phenom(tm) II X4 955 Processor
Package Socket AM3 (938)
CPUID F.4.3
Extended CPUID 10.4
Brand ID 13
Core Stepping RB-C3
Technology 45 nm
Core Speed 800.0 MHz
Multiplier x FSB 4.0 x 200.0 MHz
HT Link speed 2000.0 MHz
Instructions sets MMX (+), 3DNow! (+), SSE, SSE2, SSE3, SSE4A, x86-64, AMD-V
L1 Data cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L1 Instruction cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 4 x 512 KBytes, 16-way set associative, 64-byte line size
L3 cache 6 MBytes, 48-way set associative, 64-byte line size
FID/VID Control yes
Min FID 4.0x
P-State FID 0x10 - VID 0x12 - IDD 21 (16.0x - 1.325 V)
P-State FID 0x9 - VID 0x1A - IDD 15 (12.5x - 1.225 V)
P-State FID 0x5 - VID 0x22 - IDD 11 (10.5x - 1.125 V)
P-State FID 0x100 - VID 0x30 - IDD 5 (4.0x - 0.950 V)
 
Package Type 0x1
Model 55
String 1 0x3
String 2 0x6
Page 0x0
CmpCap 4
TDP Limit 125 Watts
TDC Limit 84 Amps
Attached device PCI device at bus 0, device 24, function 0
Attached device PCI device at bus 0, device 24, function 1
Attached device PCI device at bus 0, device 24, function 2
Attached device PCI device at bus 0, device 24, function 3
Attached device PCI device at bus 0, device 24, function 4
 
 
Thread dumps
-------------------------------------------------------------------------
 
CPU Thread 0
APIC ID 0
Topology Processor ID 0, Core ID 0, Thread ID 0
Type 02004009h
Max CPUID level 00000005h
Max CPUID ext. level 8000001Bh
Cache descriptor Level 1, I, 64 KB, 1 thread(s)
Cache descriptor Level 1, D, 64 KB, 1 thread(s)
Cache descriptor Level 2, U, 512 KB, 1 thread(s)
Cache descriptor Level 3, U, 6 MB, 4 thread(s)
 
CPUID
0x00000000 0x00000005 0x68747541 0x444D4163 0x69746E65
0x00000001 0x00100F43 0x00040800 0x00802009 0x178BFBFF
0x00000002 0x00000000 0x00000000 0x00000000 0x00000000
0x00000003 0x00000000 0x00000000 0x00000000 0x00000000
0x00000004 0x00000000 0x00000000 0x00000000 0x00000000
0x00000005 0x00000040 0x00000040 0x00000003 0x00000000
0x80000000 0x8000001B 0x68747541 0x444D4163 0x69746E65
0x80000001 0x00100F43 0x10001B76 0x000037FF 0xEFD3FBFF
0x80000002 0x20444D41 0x6E656850 0x74286D6F 0x4920296D
0x80000003 0x34582049 0x35353920 0x6F725020 0x73736563
0x80000004 0x0000726F 0x00000000 0x00000000 0x00000000
0x80000005 0xFF30FF10 0xFF30FF20 0x40020140 0x40020140
0x80000006 0x20800000 0x42004200 0x02008140 0x0030B140
0x80000007 0x00000000 0x00000000 0x00000000 0x000001F9
0x80000008 0x00003030 0x00000000 0x00002003 0x00000000
0x80000009 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000A 0x00000001 0x00000040 0x00000000 0x0000000F
0x8000000B 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000C 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000D 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000E 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000F 0x00000000 0x00000000 0x00000000 0x00000000
0x80000010 0x00000000 0x00000000 0x00000000 0x00000000
0x80000011 0x00000000 0x00000000 0x00000000 0x00000000
0x80000012 0x00000000 0x00000000 0x00000000 0x00000000
0x80000013 0x00000000 0x00000000 0x00000000 0x00000000
0x80000014 0x00000000 0x00000000 0x00000000 0x00000000
0x80000015 0x00000000 0x00000000 0x00000000 0x00000000
0x80000016 0x00000000 0x00000000 0x00000000 0x00000000
0x80000017 0x00000000 0x00000000 0x00000000 0x00000000
0x80000018 0x00000000 0x00000000 0x00000000 0x00000000
0x80000019 0xF0300000 0x60100000 0x00000000 0x00000000
0x8000001A 0x00000003 0x00000000 0x00000000 0x00000000
0x8000001B 0x0000001F 0x00000000 0x00000000 0x00000000
 
MSR 0x0000001B 0x00000000 0xFEE00900
MSR 0xC0010114 0x00000000 0x00000008
MSR 0xC0010061 0x00000000 0x00000030
MSR 0xC0010062 0x00000000 0x00000000
MSR 0xC0010063 0x00000000 0x00000000
MSR 0xC0010064 0x800001D1 0x48002410
MSR 0xC0010065 0x80000194 0x48003409
MSR 0xC0010066 0x8000016D 0x48004405
MSR 0xC0010067 0x80000130 0x48006040
MSR 0xC0010068 0x00000000 0x00000000
MSR 0xC0010071 0x00800000 0x48002410
MSR 0xC0010015 0x00000000 0x01000010
MSR 0xC001001F 0x40584000 0x00000008
MSR 0xC0010058 0x00000000 0xE0000021
MSR 0xC0010004 0x0000DA44 0x080BF7EB
MSR 0xC0010071 0x00800000 0x48036040
MSR 0xC0010070 0x00000000 0x48036040
 
CPU Thread 1
APIC ID 1
Topology Processor ID 0, Core ID 1, Thread ID 0
Type 02004009h
Max CPUID level 00000005h
Max CPUID ext. level 8000001Bh
Cache descriptor Level 1, I, 64 KB, 1 thread(s)
Cache descriptor Level 1, D, 64 KB, 1 thread(s)
Cache descriptor Level 2, U, 512 KB, 1 thread(s)
Cache descriptor Level 3, U, 6 MB, 4 thread(s)
 
CPUID
0x00000000 0x00000005 0x68747541 0x444D4163 0x69746E65
0x00000001 0x00100F43 0x01040800 0x00802009 0x178BFBFF
0x00000002 0x00000000 0x00000000 0x00000000 0x00000000
0x00000003 0x00000000 0x00000000 0x00000000 0x00000000
0x00000004 0x00000000 0x00000000 0x00000000 0x00000000
0x00000005 0x00000040 0x00000040 0x00000003 0x00000000
0x80000000 0x8000001B 0x68747541 0x444D4163 0x69746E65
0x80000001 0x00100F43 0x10001B76 0x000037FF 0xEFD3FBFF
0x80000002 0x20444D41 0x6E656850 0x74286D6F 0x4920296D
0x80000003 0x34582049 0x35353920 0x6F725020 0x73736563
0x80000004 0x0000726F 0x00000000 0x00000000 0x00000000
0x80000005 0xFF30FF10 0xFF30FF20 0x40020140 0x40020140
0x80000006 0x20800000 0x42004200 0x02008140 0x0030B140
0x80000007 0x00000000 0x00000000 0x00000000 0x000001F9
0x80000008 0x00003030 0x00000000 0x00002003 0x00000000
0x80000009 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000A 0x00000001 0x00000040 0x00000000 0x0000000F
0x8000000B 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000C 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000D 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000E 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000F 0x00000000 0x00000000 0x00000000 0x00000000
0x80000010 0x00000000 0x00000000 0x00000000 0x00000000
0x80000011 0x00000000 0x00000000 0x00000000 0x00000000
0x80000012 0x00000000 0x00000000 0x00000000 0x00000000
0x80000013 0x00000000 0x00000000 0x00000000 0x00000000
0x80000014 0x00000000 0x00000000 0x00000000 0x00000000
0x80000015 0x00000000 0x00000000 0x00000000 0x00000000
0x80000016 0x00000000 0x00000000 0x00000000 0x00000000
0x80000017 0x00000000 0x00000000 0x00000000 0x00000000
0x80000018 0x00000000 0x00000000 0x00000000 0x00000000
0x80000019 0xF0300000 0x60100000 0x00000000 0x00000000
0x8000001A 0x00000003 0x00000000 0x00000000 0x00000000
0x8000001B 0x0000001F 0x00000000 0x00000000 0x00000000
 
MSR 0x0000001B 0x00000000 0xFEE00800
MSR 0xC0010114 0x00000000 0x00000008
MSR 0xC0010061 0x00000000 0x00000030
MSR 0xC0010062 0x00000000 0x00000000
MSR 0xC0010063 0x00000000 0x00000000
MSR 0xC0010064 0x800001D1 0x48002410
MSR 0xC0010065 0x80000194 0x48003409
MSR 0xC0010066 0x8000016D 0x48004405
MSR 0xC0010067 0x80000130 0x48006040
MSR 0xC0010068 0x00000000 0x00000000
MSR 0xC0010071 0x00800000 0x48002410
MSR 0xC0010015 0x00000000 0x01000010
MSR 0xC001001F 0x40584000 0x00000008
MSR 0xC0010058 0x00000000 0xE0000021
MSR 0xC0010004 0x000044C8 0xFD70F49C
MSR 0xC0010071 0x00800000 0x48036040
MSR 0xC0010070 0x00000000 0x48036040
 
CPU Thread 2
APIC ID 2
Topology Processor ID 0, Core ID 2, Thread ID 0
Type 02004009h
Max CPUID level 00000005h
Max CPUID ext. level 8000001Bh
Cache descriptor Level 1, I, 64 KB, 1 thread(s)
Cache descriptor Level 1, D, 64 KB, 1 thread(s)
Cache descriptor Level 2, U, 512 KB, 1 thread(s)
Cache descriptor Level 3, U, 6 MB, 4 thread(s)
 
CPUID
0x00000000 0x00000005 0x68747541 0x444D4163 0x69746E65
0x00000001 0x00100F43 0x02040800 0x00802009 0x178BFBFF
0x00000002 0x00000000 0x00000000 0x00000000 0x00000000
0x00000003 0x00000000 0x00000000 0x00000000 0x00000000
0x00000004 0x00000000 0x00000000 0x00000000 0x00000000
0x00000005 0x00000040 0x00000040 0x00000003 0x00000000
0x80000000 0x8000001B 0x68747541 0x444D4163 0x69746E65
0x80000001 0x00100F43 0x10001B76 0x000037FF 0xEFD3FBFF
0x80000002 0x20444D41 0x6E656850 0x74286D6F 0x4920296D
0x80000003 0x34582049 0x35353920 0x6F725020 0x73736563
0x80000004 0x0000726F 0x00000000 0x00000000 0x00000000
0x80000005 0xFF30FF10 0xFF30FF20 0x40020140 0x40020140
0x80000006 0x20800000 0x42004200 0x02008140 0x0030B140
0x80000007 0x00000000 0x00000000 0x00000000 0x000001F9
0x80000008 0x00003030 0x00000000 0x00002003 0x00000000
0x80000009 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000A 0x00000001 0x00000040 0x00000000 0x0000000F
0x8000000B 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000C 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000D 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000E 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000F 0x00000000 0x00000000 0x00000000 0x00000000
0x80000010 0x00000000 0x00000000 0x00000000 0x00000000
0x80000011 0x00000000 0x00000000 0x00000000 0x00000000
0x80000012 0x00000000 0x00000000 0x00000000 0x00000000
0x80000013 0x00000000 0x00000000 0x00000000 0x00000000
0x80000014 0x00000000 0x00000000 0x00000000 0x00000000
0x80000015 0x00000000 0x00000000 0x00000000 0x00000000
0x80000016 0x00000000 0x00000000 0x00000000 0x00000000
0x80000017 0x00000000 0x00000000 0x00000000 0x00000000
0x80000018 0x00000000 0x00000000 0x00000000 0x00000000
0x80000019 0xF0300000 0x60100000 0x00000000 0x00000000
0x8000001A 0x00000003 0x00000000 0x00000000 0x00000000
0x8000001B 0x0000001F 0x00000000 0x00000000 0x00000000
 
MSR 0x0000001B 0x00000000 0xFEE00800
MSR 0xC0010114 0x00000000 0x00000008
MSR 0xC0010061 0x00000000 0x00000030
MSR 0xC0010062 0x00000000 0x00000003
MSR 0xC0010063 0x00000000 0x00000003
MSR 0xC0010064 0x800001D1 0x48002410
MSR 0xC0010065 0x80000194 0x48003409
MSR 0xC0010066 0x8000016D 0x48004405
MSR 0xC0010067 0x80000130 0x48006040
MSR 0xC0010068 0x00000000 0x00000000
MSR 0xC0010071 0x00800000 0x48036040
MSR 0xC0010015 0x00000000 0x01000010
MSR 0xC001001F 0x40584000 0x00000008
MSR 0xC0010058 0x00000000 0xE0000021
MSR 0xC0010004 0x00005B51 0x3C58855B
MSR 0xC0010071 0x00800000 0x48036040
MSR 0xC0010070 0x00000000 0x48036040
 
CPU Thread 3
APIC ID 3
Topology Processor ID 0, Core ID 3, Thread ID 0
Type 02004009h
Max CPUID level 00000005h
Max CPUID ext. level 8000001Bh
Cache descriptor Level 1, I, 64 KB, 1 thread(s)
Cache descriptor Level 1, D, 64 KB, 1 thread(s)
Cache descriptor Level 2, U, 512 KB, 1 thread(s)
Cache descriptor Level 3, U, 6 MB, 4 thread(s)
 
CPUID
0x00000000 0x00000005 0x68747541 0x444D4163 0x69746E65
0x00000001 0x00100F43 0x03040800 0x00802009 0x178BFBFF
0x00000002 0x00000000 0x00000000 0x00000000 0x00000000
0x00000003 0x00000000 0x00000000 0x00000000 0x00000000
0x00000004 0x00000000 0x00000000 0x00000000 0x00000000
0x00000005 0x00000040 0x00000040 0x00000003 0x00000000
0x80000000 0x8000001B 0x68747541 0x444D4163 0x69746E65
0x80000001 0x00100F43 0x10001B76 0x000037FF 0xEFD3FBFF
0x80000002 0x20444D41 0x6E656850 0x74286D6F 0x4920296D
0x80000003 0x34582049 0x35353920 0x6F725020 0x73736563
0x80000004 0x0000726F 0x00000000 0x00000000 0x00000000
0x80000005 0xFF30FF10 0xFF30FF20 0x40020140 0x40020140
0x80000006 0x20800000 0x42004200 0x02008140 0x0030B140
0x80000007 0x00000000 0x00000000 0x00000000 0x000001F9
0x80000008 0x00003030 0x00000000 0x00002003 0x00000000
0x80000009 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000A 0x00000001 0x00000040 0x00000000 0x0000000F
0x8000000B 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000C 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000D 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000E 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000F 0x00000000 0x00000000 0x00000000 0x00000000
0x80000010 0x00000000 0x00000000 0x00000000 0x00000000
0x80000011 0x00000000 0x00000000 0x00000000 0x00000000
0x80000012 0x00000000 0x00000000 0x00000000 0x00000000
0x80000013 0x00000000 0x00000000 0x00000000 0x00000000
0x80000014 0x00000000 0x00000000 0x00000000 0x00000000
0x80000015 0x00000000 0x00000000 0x00000000 0x00000000
0x80000016 0x00000000 0x00000000 0x00000000 0x00000000
0x80000017 0x00000000 0x00000000 0x00000000 0x00000000
0x80000018 0x00000000 0x00000000 0x00000000 0x00000000
0x80000019 0xF0300000 0x60100000 0x00000000 0x00000000
0x8000001A 0x00000003 0x00000000 0x00000000 0x00000000
0x8000001B 0x0000001F 0x00000000 0x00000000 0x00000000
 
MSR 0x0000001B 0x00000000 0xFEE00800
MSR 0xC0010114 0x00000000 0x00000008
MSR 0xC0010061 0x00000000 0x00000030
MSR 0xC0010062 0x00000000 0x00000002
MSR 0xC0010063 0x00000000 0x00000002
MSR 0xC0010064 0x800001D1 0x48002410
MSR 0xC0010065 0x80000194 0x48003409
MSR 0xC0010066 0x8000016D 0x48004405
MSR 0xC0010067 0x80000130 0x48006040
MSR 0xC0010068 0x00000000 0x00000000
MSR 0xC0010071 0x00800000 0x48024405
MSR 0xC0010015 0x00000000 0x01000010
MSR 0xC001001F 0x40584000 0x00000008
MSR 0xC0010058 0x00000000 0xE0000021
MSR 0xC0010004 0x00004AD6 0x3E3BDD99
MSR 0xC0010071 0x00800000 0x48036040
MSR 0xC0010070 0x00000000 0x48036040
 
 
 
Storage
-------------------------------------------------------------------------
 
USB Device Périphérique d’entrée USB, class=0x00, subclass=0x00, vendor=0x046D, product=0xC069
 
Graphic APIs
-------------------------------------------------------------------------
 
API ATI I/O
API ADL SDK
 
Display Adapters
-------------------------------------------------------------------------
 
Display adapter 0
Name Radeon HD 5770
Codename RV840
Technology 40 nm
GPU ref clock 27000
PCI device bus 1 (0x1), device 0 (0x0), function 0 (0x0)
Vendor ID 0x1002 (0x174B)
Model ID 0x68B8 (0x1482)
 

Reply

Marsh Posté le 05-01-2012 à 14:30:20    

J'ai aussi pas mal de plantage avec thunderbird et firefox...

Reply

Marsh Posté le 05-01-2012 à 14:41:25    

Memtest86, il dure indéfiniment si tu veux :)
 
T'as pas du lancer le bon test. Faut faire un test complet et faire plusieurs passes avec 0 erreur.

Reply

Marsh Posté le 05-01-2012 à 18:42:21    

J'ai testé memtest86 sur une barrette, pas d'erreur.
Et la 2e barrette, je n'arrive pas à la tester...

Reply

Marsh Posté le 05-01-2012 à 20:09:53    

Comment ça "j'arrive pas à la tester" ?
Message d'erreur ? Ça te fait quoi ?

Reply

Marsh Posté le 05-01-2012 à 20:34:30    

moi première chose que je ferais, voir si avec un système sur live CD style linux, si c'est stable ou non...


---------------
Swisscore
Reply

Marsh Posté le 05-01-2012 à 21:09:40    

Fraisouille a écrit :

Comment ça "j'arrive pas à la tester" ?
Message d'erreur ? Ça te fait quoi ?


 
Je ne parviens pas à lancer le test, alors que sur la première barrette, oui.
 
Et j'ai testé cette 2e barrette sur memtest, et là, il me trouve plusieurs erreurs, alors que sur la barrette n° aucune.
 
En ce moment, je vis avec 2GO avec la barrette où il y a eu des erreurs. Pas d'écran bleu pour le moment. Est-il possible que deux barrettes ne soient pas compatibles (pourtant, même marque) ?

Reply

Marsh Posté le 05-01-2012 à 21:12:49    

jooorule a écrit :


Je ne parviens pas à lancer le test, alors que sur la première barrette, oui.


(lut)
 :heink:  wtf :??:

 

qu'entend tu par... je vis ?
si elles ont des erreurs; bah vires les, et vois si tu as encore des ecrans bleu qui surviennent...


Message édité par thierry-golo le 05-01-2012 à 21:13:27
Reply

Marsh Posté le 05-01-2012 à 21:16:51    

Vivre, façon de parler, mais le Pc tourne sous 2Go pour voir comment ça se passe.

Reply

Marsh Posté le 05-01-2012 à 21:22:24    

non mais j'ai pas compris le sens de ta phrase en faite...
 
qu'entend tu par là; que tu tournes actuelement avec les barretes qui t'on été indiqué "defectueuse"...
 
si c le cas, tu eteinds, vire tes barretes defectueuse, mets celles testé, et... tu attend le prochain ecran bleu; si il y'en a un...
 
au moins, on sera fixé !

Reply

Marsh Posté le 08-01-2012 à 18:49:29    

1er écran bleu ce jour avec la barrette défectueuse à mon sens, car memtest trouve des erreurs et metest86 ne se lance même pas...
 
Je l'ai donc enlevé et j'ai remis celle avec laquelle les erreurs n'apparaissent pas. donc, wait and see bis !

Reply

Marsh Posté le    

Reply

Sujets relatifs:

Leave a Replay

Make sure you enter the(*)required information where indicate.HTML code is not allowed