Freeze, Crash and co

Freeze, Crash and co - Matériels & problèmes divers - Hardware

Marsh Posté le 06-01-2014 à 20:20:46    

Salut à tous,
 
Pour la petite histoire, je me suis refait ma config cet été la suivante :
 
Intel Core i7 3770K Cadencé à 3.50 GHz
ASUSTeK Computer INC. P8Z68-V PRO GEN3 Rev 1.xx
16 Go de mémoire totale de type DDR3 Barrette Kingston de 4 Go 800Mhz PC-12800
NVIDIA GeForce GTX 660 Twin Froza MSI OC 2Go
Disque dur SAMSUNGHD103SJ de 931.51 Go SATA II
Windows 7 Edition Intégrale ‎(X64)‎ Service Pack 1
 
 
 tout fonctionnais a la perfection, puis BF4 est sorti, et le jeu plantais non stop... j'ai jamais réussi a trouver l'erreur du coup j'ai formaté ma partition C: et fait une clean installe.
Seulement depuis, j'ai des soucis qui me rend fou et totalement aléatoire !! je m'explique :
 
- Lors de l’exécution de certains jeux qui demande de la ressource type cs:go, bf4 ou des applications type : Adobe Premiere ou le logiciel de Stream Open Broadcaster, elles plantes TOUTES de manière aléatoire, et sans réel rapport d'erreur..  
 
les syptomes : je perd du coup le son qui fait un bruit "zzzzzzzzzzzz" puis l'image freeze (ca c'est pour les jeux) pour les software type Adobe premiere ou OBS le logiciel crash... juste comme ca sans raison, et jamais au meme moment...
 
Ce qui est étrange c'est que des jeux type League of Legends, ne plante JAMAIS ! et également que quand le son fait un "zzzzzzzzzzzzz" si je coupe l’application, j'ai juste a aller désactiver la carte son la réactiver et je retrouve le son sans soucis et relance normalement mon jeu....
 
J'ai fait un MemTest c'est OK... j'ai vérifié manuellement tout mes pilotes, et tout désinstaller et remis rien n'y fait ! je ne peux pas stream sans que OBS crash ou simplement le son. OCCT tourne plutot bien meme si au bout de 20/30min mon core #1 chauffe trop (en stress test a 100%).
 
Sincèrement, j'ai des erreur de partout avec des BSOD tous différents... je ne sais plus quoi faire, j'ai besoin de vous ! merci..
 
Je vous laisse le rapport de Whocrashed au cas ou :
 
 
System Information (local)
 
computer name: PTIWIKI-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P8Z68-V PRO GEN3
CPU: GenuineIntel Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17145413632 total
VM: 2147352576, free: 1915256832
 
 
 
Crash Dump Analysis
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
On Sat 04/01/2014 00:49:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010414-32791-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)  
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF4, 0x0, 0xFFFFF80002BC3123, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 04/01/2014 00:49:20 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!W32pArgumentTable+0x1BFAC)  
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF4, 0x0, 0xFFFFF80002BC3123, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 04/01/2014 00:39:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010414-32651-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)  
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007B88028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).  
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.  
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 04/01/2014 00:31:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010414-32214-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)  
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.  
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.  
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 04/01/2014 00:24:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010414-32822-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D27D)  
Bugcheck code: 0xFE (0x6, 0xFFFFFA800E8DD0F0, 0x6368B845, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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 03/01/2014 22:03:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010314-23540-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)  
Bugcheck code: 0x124 (0x0, 0xFFFFFA800DC5C028, 0xF2000040, 0x10005)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).  
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.  
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.  

Reply

Marsh Posté le 06-01-2014 à 20:20:46   

Reply

Marsh Posté le 07-01-2014 à 11:31:17    

Petit up,
 
pour info : hier ma soirée de jeux c'est bien passé dans l'ensemble, j'ai juste eu à un moment donné la mystérieuse coupure de son, j'ai quitté teamspeak et LoL, puis fait "tester" ma sortie via le gestionnaire et c'est revenu, puis aucun soucis les heures suivantes.....
 
c'est super étrange !

Reply

Marsh Posté le 07-01-2014 à 11:40:31    

C'est peut-être un problème de carte mère, il y avait des problèmes sur la P8Z67 pro (+ de 6% de retours chez LDLC).

 

Le BIOS est à jour ?


Message édité par artouillassse le 07-01-2014 à 11:40:43

---------------
3000 tués sur les routes chaque année - c'est décidé, demain je roule sur les trottoirs ©brèves de comptoire
Reply

Marsh Posté le 07-01-2014 à 12:21:48    

Ouep Bios à jour :s, fait chier j'ai acheté en ligne sur cdiscount et le sac chez eux -_-

Reply

Sujets relatifs:

Leave a Replay

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