Blue screen lors de la mise en veille

[Jackynovice]

Bonjour,

Depuis le 2 Août lorsque je mets mon ordinateur en veille j' ai un blue screen ..
Mon ordinateur est un HP pavillon g6-2153 sf a 1,5 ans.
Je n' ai pas de point de restauration disponibles,
j' ai des mises à jours windows qui ont été effectuées ce 2 Août..

Je vous joint des images qui vous aiderons sûrement à régler mon problème :
https://drive.google.com/file/d/0B7HI92 ... sp=sharing

https://drive.google.com/file/d/0B7HI92 ... sp=sharing
https://drive.google.com/file/d/0B7HI92 ... sp=sharing

Merci d' avance
Jack

[EinsteinZero]

Bonsoir et bienvenue
les photos d'écran c'est bien, mais il existe des utilitaires pour récupérer les rapport de BSOD... c'est plus pratique pour essayer de comprendre

télécharge "Whocrashed" qui est sans installation >>ici sur external mirror 1<<

lance le logiciel est poste par un copier coller sont rapport, ça nous donnera peut-être une piste

[jyl2803]

salut mister jack ! (mister Jack, c'est mon neveu, si si !)
Tu verra, il fait bon ici, les modos sont sympas, et c'est le plus efficace et sérieux des foras que j'ai visité ! (qui a dit fayot ??non non, je demande pas d'augmentation ! sincère !)
Bon alors les gars, si vous pouvez aider Jack, ce serait sympa, on a déja essayé à distance, mais là, je vois plus très bien....

JYL

[Jackynovice]

Bonjour voici mon rapport de who crached


Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 03/09/2014 14:10:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090514-17066-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF8A0002C1FB8, 0x2, 0x1, 0xFFFFF80002ED793C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 03/09/2014 14:10:13 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: gubootstartup.sys (GUBootStartup+0x1103)
Bugcheck code: 0xA (0xFFFFF8A0002C1FB8, 0x2, 0x1, 0xFFFFF80002ED793C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\gubootstartup.sys
product: Glary Utilities
company: Glarysoft Ltd
description: The driver for the Startup Manager tool
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.
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: gubootstartup.sys (The driver for the Startup Manager tool, Glarysoft Ltd).
Google query: Glarysoft Ltd IRQL_NOT_LESS_OR_EQUAL



On Sun 31/08/2014 11:27:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090114-33212-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF8A000302F18, 0x2, 0x1, 0xFFFFF80002EDA93C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 31/08/2014 10:32:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-40934-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF8A000210FB8, 0x2, 0x1, 0xFFFFF80002E8693C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 31/08/2014 10:27:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-39983-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF8A00016D808, 0x2, 0x1, 0xFFFFF80002ED193C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 31/08/2014 10:11:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-25693-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF8A00016FDD8, 0x2, 0x1, 0xFFFFF80002E8D93C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 28/08/2014 16:45:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-15958-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF8A000201A48, 0x2, 0x1, 0xFFFFF80002E7D93C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 28/08/2014 12:14:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082814-20654-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF8A0002FAF18, 0x2, 0x1, 0xFFFFF80002E9793C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 28/08/2014 11:15:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082814-28938-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF8A0003009F8, 0x2, 0x1, 0xFFFFF80002EC793C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 28/08/2014 07:52:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082814-35755-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF8A0002E8488, 0x2, 0x1, 0xFFFFF80002ED993C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

11 crash dumps have been found and analyzed. Only 10 are included in this report. 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:

gubootstartup.sys (The driver for the Startup Manager tool, Glarysoft Ltd)

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.

[jyl2803]

Bon ben Jacques, tu as quasi la réponse !

"This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. " (tonton l'avait dit, c'est un pbm logiciel...) et " 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:
gubootstartup.sys (The driver for the Startup Manager tool, Glarysoft Ltd)"

Tu as du installer un truc zarbi... ça m'étonne de toi...

[EinsteinZero]

Bonjour
en effet c'est un truc zarbi ce pilote je serait toi... je commencerais par désinstaller Glary Utilities car, de toute façon, un logiciel qui nettoie "tout seul" le registre de façon automatique....quelque soit ce logiciel...ça fini toujours par des ennuis

le registre ne se nettoie qu'en cas de souci et sur commande....afin de pouvoir faire marche arrière en cas de souci

[jyl2803]

ccleaner fait ça très bien et avec sauvegardes au cas où....

[Jackynovice]

Tout est OK !
Une simple désinstallation
De galary utilities ..

Merci à tous
Jack

[jyl2803]

hé ben voila ! tu nous tiens au courant de la suite ?

[Jackynovice]

La suite ?

Hey bien tout fonctionne à merveille !!


Jack

[EinsteinZero]

comme quoi....on installe un truc pour avoir la paix....et c'est le bordel....pourtant on dit toujours

...l'enfer est pavé de bonnes intentions

A+ sur le fofo

[jyl2803]

un p'tit coup de ccleaner permettra de purger le registre des scories de ce genre de daube... (Pour peu qu'en plus ce soit téléchargé sur softonic ou 01net, c'est la galère assurée....)