Bluescreens et plantages par cycles
ramsay31
-
ramsay31 -
ramsay31 -
Bonjour,
Je possède mon ordinateur depuis un bon moment, mais les composants sont relativement récents, un intel i5 de première génération, une bonne CG 3go de ram et une bonne alim.
Bref, un jour, ayant perdus des fichiers sans le faire exprès, j'ai fait une restauration du système.
Tout s'est bien passé, j'ai récupéré mes fichiers.
Mais après ça, mon ordinateur a commencé à ramer.
Il ramait anormalement, j'ai donc défragmenté, utilisé spy bot, avast et ccleaner tout en désinstallant les programmes dont je ne me servais plus.
En vain.
J'utilise mon ordinateur principalement pour le jeu et pour regarder des films.
Je peux l'utiliser pendant 2 voire 3 semaines sans plantage ni bluescreen.
Et puis un jour, je suis bloqué en plein milieu d'une série avec un bruit de bourdonnement "robotique" dans les oreilles, un plantage.
J'éteins le PC "à la barbare" puisque je n'ai aucun contrôle.
je redémarre, le pc plante sur le petit bruit de windows quand le pc démarre.
Blue screen of death etc...
et ce, pendant 3 ou quatre fois d'affilée. J'attends un peu avant de rallumer l'ordi, et là c'est reparti pour une semaine sans plantage, ou un plantage une fois peut-être.
Le pc restant lent, je me suis dis que j'avais trop chargé de conneries.
J'ai décidé de formater et de tout réinstaller.
En vain.
Le problème persiste et semble être matériel...
J'espère donc trouver de l'aide.
Merci d'avance
Ramsay31
Je possède mon ordinateur depuis un bon moment, mais les composants sont relativement récents, un intel i5 de première génération, une bonne CG 3go de ram et une bonne alim.
Bref, un jour, ayant perdus des fichiers sans le faire exprès, j'ai fait une restauration du système.
Tout s'est bien passé, j'ai récupéré mes fichiers.
Mais après ça, mon ordinateur a commencé à ramer.
Il ramait anormalement, j'ai donc défragmenté, utilisé spy bot, avast et ccleaner tout en désinstallant les programmes dont je ne me servais plus.
En vain.
J'utilise mon ordinateur principalement pour le jeu et pour regarder des films.
Je peux l'utiliser pendant 2 voire 3 semaines sans plantage ni bluescreen.
Et puis un jour, je suis bloqué en plein milieu d'une série avec un bruit de bourdonnement "robotique" dans les oreilles, un plantage.
J'éteins le PC "à la barbare" puisque je n'ai aucun contrôle.
je redémarre, le pc plante sur le petit bruit de windows quand le pc démarre.
Blue screen of death etc...
et ce, pendant 3 ou quatre fois d'affilée. J'attends un peu avant de rallumer l'ordi, et là c'est reparti pour une semaine sans plantage, ou un plantage une fois peut-être.
Le pc restant lent, je me suis dis que j'avais trop chargé de conneries.
J'ai décidé de formater et de tout réinstaller.
En vain.
Le problème persiste et semble être matériel...
J'espère donc trouver de l'aide.
Merci d'avance
Ramsay31
A voir également:
- Bluescreens et plantages par cycles
- Combien de cycles dure mon Macbook Pro ? - Forum MacOS
- BlueScreens 0xF4 ntoskrnl.exe au "shut down" - Forum Windows
- Plantages smartphone réguliers, redémarre tout seul, bugs au démarrage. - Forum Téléphones & tablettes Android
- BlueScreen causé par ntoskrnl.exe ✓ - Forum Pilotes (drivers)
- Pb de plantage et affichage de ntoskrnl.exe - Forum Virus
12 réponses
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
No valid crash dumps have been found on your computer
Crash dumps are enabled on your computer.
No valid crash dumps have been found on your computer
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: GAUTHIER-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: MS-7635, MSI, H55M-ED55 (MS-7635)
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 661 @ 3.33GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3144802304 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 30/08/2014 10:21:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083014-19188-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x1F862)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880011BF862, 0xFFFFF880035D9918, 0xFFFFF880035D9170)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
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 Sat 30/08/2014 10:21:44 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x1F862)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF880011BF862, 0xFFFFF880035D9918, 0xFFFFF880035D9170)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 30/08/2014 10:16:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083014-21949-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x1F862)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800106B862, 0xFFFFF880035D9918, 0xFFFFF880035D9170)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.
Voilà mon rapport who crashed.
que dois- je faire ?
System Information (local)
--------------------------------------------------------------------------------
computer name: GAUTHIER-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: MS-7635, MSI, H55M-ED55 (MS-7635)
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 661 @ 3.33GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3144802304 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 30/08/2014 10:21:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083014-19188-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x1F862)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880011BF862, 0xFFFFF880035D9918, 0xFFFFF880035D9170)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
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 Sat 30/08/2014 10:21:44 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x1F862)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF880011BF862, 0xFFFFF880035D9918, 0xFFFFF880035D9170)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 30/08/2014 10:16:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083014-21949-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x1F862)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800106B862, 0xFFFFF880035D9918, 0xFFFFF880035D9170)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.
Voilà mon rapport who crashed.
que dois- je faire ?
