Bluescreens a répétition

[sixcoups]

Bonsoir les loulous!!

Me revoici avec un nouveau soucis... Cela fait bientot un an que ma config perso est montée est quasiment aucun soucis a déplorer... Jusqu'a ... AUJOURD'HUI!!

Alors voila je vous fais le topo:

Lors de bonnes sessions de jeux, le pc freeze, un fort bourdonnement sort des enceintes et boum écran bleu.

Durant trois écrans bleus differents j'ai eu le temps de noter 3 elements qui me semblent importants

- Bugcode USB
-Driver SQL
-Dxgmms

Je suis désolé l'écran disparait si vite que j'ai a peine le temps de lire ...

Quelqu'un a une piste?

Cordialement Sixcoups

PS: Windows 7 32bits
Phenom II x4 965 Black, Gainward 275 GTX, G-skill DDR3 2*2go 1600Mhz, Western digital Caviar black 32mo de cache, Artic cooling freezer 7

[EinsteinZero]

Bonsoir,

si tes BSOD ont créé des fichier d'erreur, whochrased >>ici (mirror 1)<< devrait, par son rapport nous les donner

installe whocrashed, lance le et poste son rapport. ON en saura peut-être plus

[sixcoups]

Code: Tout sélectionner

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

Welcome to WhoCrashed HOME EDITION v 3.01

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



This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.



Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.



This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.





To obtain technical support visit www.resplendence.com/support



To check if an update of this program is available, click here.



Just click the Analyze button for a comprehensible report ...







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

Home Edition Notice

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



This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should ge the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.



Click here for more information on the professional edition.

Click here to buy the the professional edition of WhoCrashed.







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

System Information (local)

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



computer name: SIKOO-PC

windows version: Windows 7 , 6.1, build: 7600

windows dir: C:\Windows

CPU: AuthenticAMD AMD Phenom(tm) II X4 965 Processor AMD586, level: 16

4 logical processors, active mask: 15

RAM: 3487682560 total

VM: 2147352576, free: 1990541312







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

Crash Dump Analysis

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



Crash dump directory: C:\Windows\Minidump



Crash dumps are enabled on your computer.





On Mon 04/04/2011 20:04:59 GMT your computer crashed

crash dump file: C:\Windows\Minidump\040411-13759-01.dmp

This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x16BB1)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF9518CBB1, 0xFFFFFFFF905DC9E8, 0xFFFFFFFF905DC5C0)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

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 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 Mon 04/04/2011 20:04:59 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)

Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFFFF9518CBB1, 0xFFFFFFFF905DC9E8, 0xFFFFFFFF905DC5C0)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.

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: ntkrpamp.exe .

Google query: ntkrpamp.exe SYSTEM_THREAD_EXCEPTION_NOT_HANDLED









On Sun 03/04/2011 22:42:08 GMT your computer crashed

crash dump file: C:\Windows\Minidump\040411-13416-01.dmp

This was probably caused by the following module: usbohci.sys (usbohci+0x2A66)

Bugcheck code: 0xD1 (0x28, 0x2, 0x1, 0xFFFFFFFF951D5A66)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\usbohci.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: OHCI USB Miniport Driver

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 which cannot be identified at this time.





On Sun 03/04/2011 22:25:34 GMT your computer crashed

crash dump file: C:\Windows\Minidump\040411-15225-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x2750A3)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82C900A3, 0xFFFFFFFF92FFCC5C, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\ntkrnlpa.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 03/04/2011 20:35:27 GMT your computer crashed

crash dump file: C:\Windows\Minidump\040311-17612-01.dmp

This was probably caused by the following module: usbport.sys (USBPORT+0x31EE)

Bugcheck code: 0xFE (0x5, 0xFFFFFFFF865C60E0, 0x10024398, 0xFFFFFFFF87233780)

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 which cannot be identified at this time.





On Sun 03/04/2011 20:32:39 GMT your computer crashed

crash dump file: C:\Windows\Minidump\040311-15163-01.dmp

This was probably caused by the following module: win32k.sys (win32k+0xCB5B6)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9CB8B5B6, 0xFFFFFFFFAAF66A8C, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

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 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 which cannot be identified at this time.





On Sun 03/04/2011 18:34:58 GMT your computer crashed

crash dump file: C:\Windows\Minidump\040311-20685-01.dmp

This was probably caused by the following module: usbport.sys (USBPORT+0x31EE)

Bugcheck code: 0xFE (0x5, 0xFFFFFFFF864E00E0, 0x10024398, 0xFFFFFFFF87322F90)

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 which cannot be identified at this time.





On Sun 03/04/2011 18:30:57 GMT your computer crashed

crash dump file: C:\Windows\Minidump\040311-20108-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x4681B)

Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFFFFF8606E6A9)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntkrnlpa.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.







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

Conclusion

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



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



ntkrpamp.exe



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.


[EinsteinZero]

Re,

tu aurais du mettre ton rapport entre balise "Code" afin que ta réponse soit moins longue (il n'est pas trop tard pour corriger en éditant)

vu le descriptif, (le fait que pleins de pilotes sans rapport plantent l'un après l'autre) me ferait assez penser à un problème avec un composant mémoire, tu devrais peut-être faire un test Ram

pour commencer tu peux faire un test rapide avec l'utilitaire de test de win 7 (il est pas top, mais tu l'as sous la main)

->démarrer->tape dans la ligne de recherche: memoire

alors en haut de la liste il apparait "Diagnostic de mémoire windows"

commence par utiliser cet outils, s'il ne trouve rien, passe à du sérieux avec memtest

[sixcoups]

Je fais ça de suite et rapporte les infos!!

[sixcoups]

me revoilou , désolé pour le réveil de topic.pas le temps de m'occuper du pc , travaux a la maison
Mais toujours des soucis de blue screen...

Depuis je suis passé a 12go de ram, testée avec l'outil windows et avec memtest, no soucis de ce coté la.

Serait-ce un possible manque de puissance dans mes ports usb?
écrans bleus avec seulement un clavier usb rétroéclairé , ma cyborg rat 9 , et mon casque usb Ttesport.
Je désespère...

entre temps formatage aussi... réinstallation complète , seulement mes pilotes utiles, donc souris et casque.

Je me suis aussi demandé s'il n'y avait pas un problème entre mon casque USB et ma carte son.
Apparement il y a une bidouille , désinstaller tous les ports et donc périphériques usb puis redémarrer, tenté, pas concluant.

[EinsteinZero]

Bonjour

un pb d'alim...??? ça dépend c'est quoi la marque et la puissance ?

[sixcoups]

Bonsoir , il s'agit d'une corsair 750w certifiée 80+, mais écoute j'ai fait sauter mes deux barettes de ram de 2 go, et depuis... nickel, affaire a suivre

[EinsteinZero]

Bonsoir

c'était donc bien la Ram...les symptômes allaient dans ce sens (c'est souvent ça quand plein de pilotes partent en vrille)

pour l'alim corsair 80+ 750 W...c'est du sérieux et déjà bien costaud...je ne crois absolument pas à un problème d'alimentation...sauf si tu expérimentes un "fer à repasser USB"

tu dis quand on peut mettre en résolu

[skanner]

Bonjour,

bien que 3 mois plus tard le sujet est toujours d'actualité avec écran bleu.
J'ai moi aussi 4 barrettes corsair 4x4.
J'ai aussi une alim corsair 750w

J'ai lu sur un autre forum qu'il fallait overclocker le voltage de la ram.
En regardant je m'aperçoit que celle-ci s'affiche souvent en dessous de 1,5 volts,
et cela expliquerais le fait qu'en enlevant 2 cela ne saute plus..

je viens donc doverclocker à 1,65 et... cela semble aller.

Je reviendrais dans un jour ou deux pour confirmer ou non la solution.

@+

[H3bus]

Salut,

Overclocker la RAM ? Pourquoi faire ?

Fais plutôt un memtest : http://netah25.developpez.com/Tutoriels/TutoMemtest86/

[skanner]

Salut,

Overclocker la RAM ? Pourquoi faire ?

Fais plutôt un memtest : http://netah25.developpez.com/Tutoriels/TutoMemtest86/

Bonjour,

le memtest avait été fait sans pointer aucun probleme.

Pourquoi l'overclocker ? , je ne sais pas , je l'ai lu sur un forum US où plusieurs personnes avait le même probleme avec des 64 bits et différente config en Vista et W7.
Quoiqu'il en soit , j'ai travaillé sans discontinuer depuis, et j'ai laissé ouvert H24 (en téléchargement la nuit).
et j'ai visionné aussi un film et du streaming ( ça le faisait au minimum une fois par film.)
Depuis plus de problème... alors que cela pétait 3 -4 fois par jour.

Donc, pour moi, ça fonctionne, je suis passé de 1,5 à 1,59 (+6%) . ça marche aussi à 1,65( testé) mais comme je ne vois pas beaucoup la différence et que je n'en ai pas l'usage, je suis redescendu à 1,59 Vlt.

Voilà Pour ceux que ça peut aider.

Bonjour de Tahiti

[H3bus]

Bon, je vais laisser ma place au tenors du Bluescreen, ça aurait été un kernel panic, j'aurais peut être su te dire...

Bonjour de France !

[routman54]

Bonsoir,
C'est toujours bon à savoir , l'overclocking n'étant pas dans mes habitudes j'aurai peut être du mal à m'en rappeller.
Fais nous un petit coucou du soleil de temps en temps pour nous dire si ça tient.
Bonne continuation.