Bonjour tout le monde ,
 
 
Voila, un problème qui est assez agaçant  ! BSOD  , il y a 3 semaine j'ai une un  message ressemblant à ceci " https://www.youtube.com/watch?v=JKq9CR5qm3U " , puis 2 semaine sans soucis , mis à jour ma carte graphique en 13.3 cataclyst.
Aparament c'est un driver son d'apres la conclusion who crashed , ( j'ai installer il y a quelque jour usb 3 avec ma CM avant le problème ) et comme juste avant ceci je venais de de changer l emplacement de mon clavier de port USB 3 ( mon casque ce branche sur le clavier ) et j'ai eu des grésillement ! les grésillements ont disparus après avoir remis le port d'origine.
 
Depuis vendredi 3 Blue Screen en 20 min ! ( des fois en jeux , des fois sans jouer ) , j'ai fais un test " Diagnostique de mémoire ram avec window car who crashed  et un teste avec Windows qui diagnostique la mémoire m'a annoncer ceci :
 
 
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
On Sun 07/04/2013 12:24:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040713-8845-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)  
Bugcheck code: 0x19 (0x21, 0xFFFFFA80072BA000, 0x1E10, 0x3000100031E13)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time.  
 
 
 
On Sun 07/04/2013 12:24:52 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: rtkvhd64.sys (RTKVHD64+0x1DAADC)  
Bugcheck code: 0x19 (0x21, 0xFFFFFA80072BA000, 0x1E10, 0x3000100031E13)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\rtkvhd64.sys
product: Realtek(r) High Definition Audio Function Driver
company: Realtek Semiconductor Corp.
description: Realtek(r) High Definition Audio Function Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.  
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: rtkvhd64.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.).  
Google query: Realtek Semiconductor Corp. BAD_POOL_HEADER
 
 
 
On Fri 05/04/2013 20:26:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040513-11450-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032C5C22, 0xFFFFF88009B00E30, 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 Fri 05/04/2013 19:56:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040513-7862-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)  
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800032747C8, 0xFFFFFFFFFFFFFFFF, 0x0)
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 that cannot be identified at this time.  
 
 
 
On Fri 05/04/2013 19:48:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040513-7690-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x1453A)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800171C53A, 0xFFFFF880033EE918, 0xFFFFF880033EE170)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 that cannot be identified at this time.  
 
 
 
On Fri 05/04/2013 19:37:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040513-7784-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)  
Bugcheck code: 0x18 (0x0, 0xFFFFFA8006B6FEF0, 0x2, 0xFFFFFFF3FFFFFFF4)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time.  
 
 
 
On Fri 05/04/2013 19:12:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040513-9500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003106C22, 0xFFFFF8800995BE30, 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.  
 
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
7 crash dumps have been found and analyzed. 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:  
 
rtkvhd64.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.)
 
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.  
 
---------------------------
RAPPORT WINDOW TEST MEMOIRE
Version=1
EventType=MemDiagV1
EventTime=130098130700029577
Consent=1
ReportIdentifier=bffb4735-9f82-11e2-bd22-08606e84e2fe
Response.type=4
Sig[0].Name=Plage de tailles de mémoire
Sig[0].Value=4097
Sig[1].Name=Type de lancement
Sig[1].Value=BootManager
Sig[2].Name=Type de planification
Sig[2].Value=Immediate
Sig[3].Name=Type de fin d’opération
Sig[3].Value=Pass
Sig[4].Name=Type de test
Sig[4].Value=Standard
Sig[5].Name=Échec des tests
Sig[5].Value=0
Sig[6].Name=Nombre de pages incorrectes
Sig[6].Value=0
Sig[7].Name=Durée du test en secondes
Sig[7].Value=300
DynamicSig[1].Name=Version du système
DynamicSig[1].Value=6.1.7600.2.0.0.256.1
DynamicSig[2].Name=Identificateur de paramètres régionaux
DynamicSig[2].Value=1036
File[0].CabName=MemDiag.bin
File[0].Path=MemDiag.bin
File[0].Flags=65536
File[0].Type=5
File[0].Original.Path=C:\Windows\System32\LogFiles\MemDiag\MemDiag.bin
FriendlyEventName=Résultats du test mémoire renvoyés
ConsentKey=MemDiagV1
AppName=Diagnostic de mémoire Windows
AppPath=C:\Windows\System32\RelPost.exe
ReportDescription=Les résultats de l’exécution du Diagnostic de mémoire Windows ont été envoyés à Microsoft pour être analysés afin d’améliorer le produit.
 
J'aimerais savoir si une restauration suffirais? Est vraiment la RAM ?Un composant autre que la ram?Un driver?Un virus ? car je peux avoir 3-4 voir plus sans coupure c'est vraiment RANDOM le blue screen sauf  vendredi 3 en 15/20 min
 
Je suis un peu perdu j'ai regarder pas mal de forum , mais il y n'y a pas de solution magique            
 
voici ma configuration:
ASUS MAXIMUS V GENE
G SKILL 4X2
I5 3750K
7970 VAPOR X ghz edition
Merci a ceux qui on pris la peine de lire jusqu'au bout

J'oubliais j'ai copier coller le rapport window après certain blue screen :
Signature du problème :
  Nom d’événement de problème: BlueScreen
  Version du système: 6.1.7600.2.0.0.256.1
  Identificateur de paramètres régionaux: 1036
 
Informations supplémentaires sur le problème :
  BCCode: 3b
  BCP1: 00000000C0000005
  BCP2: FFFFF80003106C22
  BCP3: FFFFF8800995BE30
  BCP4: 0000000000000000
  OS Version: 6_1_7600
  Service Pack: 0_0
  Product: 256_1
   
   
  ---
 
  BCCode: 18
  BCP1: 0000000000000000
  BCP2: FFFFFA8006B6FEF0
  BCP3: 0000000000000002
  BCP4: FFFFFFF3FFFFFFF4
  OS Version: 6_1_7600
  Service Pack: 0_0
  Product: 256_1

uP Up !

Bonjour,

As tu vérifier que tes divers sont correctement installés ? Le plus souvent l'écran bleu apparaît à cause de problèmes de compatibilité.

Voilà voilà

Salut suniron,
 
merci pour ta réponse avant tout ^_^, j'ai mis a jour les pilotes graphique , mais continuant mes recherche  les causes sont un peux varié : S
Driver apparemment , le son ? le bios ? le chipset ? peut être mais je sais pas du tout comment m'y prendre pour mettre à jour cela.  
 
rtkvhd64.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.)  , Apparemment un pb de son ? ntoskrnl.exe?( l erreur survenue sur 3 crash ) ?  
 

Up !

tu vas là: http://www.touslesdrivers.com/index.php?v_page=29 et tu lances la détection, tu auras une installation du soft à faire, et tu auras la liste des drivers de ton système, y compris les bétas si tu veux...

Tu n'auras plus qu'à installer les drivers qui te manquent...
Si ça ne suffit pas, c'est plus coton...

Merci Beaucoup ,ça m'a l'air bien efficace !
 
Après une petite recherche j'ai vu 3 logiciel :FileHippo UpdateChecker SIW, Everest, Aida32. Auriez vous un avis ou déjà utiliser l'un deux ?
 
PS : Est t -il un outil de confiance par un grand nombre ? Sans trop prendre de risque lors du téléchargement du plu-gins et des drivers proposés  

tous les drivers est sûr et en français. ça aide.

Ok je test ce soir .-)
 
Merci encore :-)

+1 pour touslesdrivers.com

+2

Regarde au niveau chipset je pense.

Je vous remercie énormément j'avais le chipset, usb , carte reseau ( pr le moment la mise a jour se bloque a 70 %) , le casque , le clavier , les ports sata et usb qui n’était pas à jours    j’espère que cetait la cause des blue screen ^^' on verra bien

Ah bah il y a des chances que ça remarche bien