windows 10 BSOD à répétition

[alain louis]

Bonjour

je ne sais pas si je suis au bon endroit je suis novice en informatique.

Mon papa a un pc portable Toshiba c870-1J6. avec Windows 10

j'ai des Plantage BSOD aléatoire régulièrement voir plusieurs par jour depuis plusieurs mois et il ne fait rien de spécial soit il est sur Skype soit il joue au solitaire de Windows soit il lit ses mail et souvent quand il n'est pas dessus il entend le pc qui redémarre.

D'habitude j'en avais 1 qui revenait souvent donc j'ai vu sur internet qu'il fallait mettre à jour les pilotes ce que j'ai fait avec driver cloud et driver booster mais ici j'ai un autre écran et ca continue.

j'ai vu sur internet que l'on pouvais avoir des rapports pour savoir ce qui plante avec bluescreenview - windgb - who crashed.

je vous poste les rapport de chaque programme

bluescreenview ( 7 rapports )

1er rapport ( 13 fois )

==================================================
Dump File : 112717-28437-01.dmp
Crash Time : 27-11-17 15:28:18
Bug Check String : CRITICAL_PROCESS_DIED
Bug Check Code : 0x000000ef
Parameter 1 : ffffd80b`e92ec640
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+16c580
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+16c580
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\112717-28437-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 15063
Dump File Size : 431.332
Dump File Time : 27-11-17 15:32:10
==================================================


2 eme rapport ( 4 fois )

==================================================
Dump File : 112717-29125-01.dmp
Crash Time : 27-11-17 12:01:13
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x1000009f
Parameter 1 : 00000000`00000004
Parameter 2 : 00000000`0000012c
Parameter 3 : ffffa605`12476040
Parameter 4 : ffffbb80`a8ab4910
Caused By Driver : volsnap.sys
Caused By Address : volsnap.sys+1a1ec
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+1713b6
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\112717-29125-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 15063
Dump File Size : 814.356
Dump File Time : 27-11-17 12:03:51
==================================================

3 eme rapport ( 5 fois )

==================================================
Dump File : 112417-27406-01.dmp
Crash Time : 24-11-17 19:39:44
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00006001
Parameter 2 : ffffffff`c000000e
Parameter 3 : 00000000`03df0000
Parameter 4 : ffff9d8b`a23d9d90
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+16c580
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+16c580
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\112417-27406-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 15063
Dump File Size : 332.532
Dump File Time : 24-11-17 19:42:01
==================================================


4 eme rapport ( 4 fois )

==================================================
Dump File : 110617-30296-01.dmp
Crash Time : 06-11-17 20:56:36
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : ffffbc07`d813fac0
Parameter 2 : ffffffff`c000000e
Parameter 3 : 00000001`006c5860
Parameter 4 : fffff801`131f2a34
Caused By Driver : srv.sys
Caused By Address : srv.sys+52a34
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+16c580
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\110617-30296-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 15063
Dump File Size : 519.940
Dump File Time : 06-11-17 20:59:30
==================================================


5 eme rapport ( 5 fois )

==================================================
Dump File : 110217-29218-01.dmp
Crash Time : 02-11-17 23:15:48
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : ffff8986`26c5df00
Parameter 2 : ffffffff`c000000e
Parameter 3 : 00000000`3c172860
Parameter 4 : fffff801`fe3f8640
Caused By Driver : MpKsl95ed3628.sys
Caused By Address : MpKsl95ed3628.sys+8640
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+16c580
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\110217-29218-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 15063
Dump File Size : 519.204
Dump File Time : 02-11-17 23:18:13
==================================================


6 eme rapport ( 1 fois )

==================================================
Dump File : 103017-30343-01.dmp
Crash Time : 30-10-17 11:49:31
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : ffffa20e`6a233a80
Parameter 2 : ffffffff`c000000e
Parameter 3 : 00000000`3b02d860
Parameter 4 : fffff801`7df1aae0
Caused By Driver : srvnet.sys
Caused By Address : srvnet.sys+3aae0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+16c580
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\103017-30343-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 15063
Dump File Size : 489.212
Dump File Time : 30-10-17 11:53:19
==================================================

7 eme rapport ( 1 fois )

==================================================
Dump File : 102317-28546-01.dmp
Crash Time : 23-10-17 22:07:28
Bug Check String : CRITICAL_PROCESS_DIED
Bug Check Code : 0x000000ef
Parameter 1 : ffffc900`d151d080
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+73641902
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+16c580
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\102317-28546-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 15063
Dump File Size : 433.604
Dump File Time : 23-10-17 22:09:01
==================================================



who crashed


--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.54
--------------------------------------------------------------------------------

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

Whenever a computer suddenly reboots without displaying any notice or blue (or black) 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 or black 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. It 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

Click here to check if you have the latest version or if an update is available.

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 get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: JYPY
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: SATELLITE C870-1J6, TOSHIBA, Intel, PLCSF8
CPU: GenuineIntel Intel(R) Core(TM) i3-2348M CPU @ 2.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4170420224 bytes total




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 27-11-17 15:28:18 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112717-28437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0xEF (0xFFFFD80BE92EC640, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 27-11-17 15:28:18 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntdll.sys (ntdll!RtlLookupFunctionEntry+0x1AD)
Bugcheck code: 0xEF (0xFFFFD80BE92EC640, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
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: ntdll.sys .
Google query: ntdll.sys CRITICAL_PROCESS_DIED



On Mon 27-11-17 12:01:13 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112717-29125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1713B6)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFFA60512476040, 0xFFFFBB80A8AB4910)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 27-11-17 00:56:54 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112717-32734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1713B6)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFFE50B306BA040, 0xFFFFD5001CAB4910)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 27-11-17 00:34:49 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112717-32375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1713B6)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFFAC8007737700, 0xFFFFF8037FA3B910)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





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

51 crash dumps have been found and analyzed. Only 5 are included in this report. 2 third party drivers have 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:

mpksl95ed3628.sys
ntdll.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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.




win dgb


Microsoft (R) Windows Debugger Version 10.0.16299.15 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\SymbolsSrvCache*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\SymbolsSrvCache*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff800`b4201000 PsLoadedModuleList = 0xfffff800`b454d660
Debug session time: Mon Nov 27 23:01:06.422 2017 (UTC + 1:00)
System Uptime: 0 days 7:32:00.155
Loading Kernel Symbols
...............................................................
.Page 5440a not present in the dump file. Type ".hh dbgerr004" for details
...............................................................
................................................................
......
Loading User Symbols

Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {4, 12c, ffffc2055ee55040, fffff800b663b910}

Implicit thread is now ffffc205`5ee55040
Probably caused by : BthEnum.sys

Followup: MachineOwner
---------

0: kd> !analyse -v
No export analyse found
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffc2055ee55040, The thread currently holding on to the Pnp lock.
Arg4: fffff800b663b910, nt!TRIAGE_9F_PNP on Win7 and higher

Debugging Details:
------------------

Implicit thread is now ffffc205`5ee55040

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 15063.0.amd64fre.rs2_release.170317-1834

SYSTEM_MANUFACTURER: TOSHIBA

SYSTEM_PRODUCT_NAME: SATELLITE C870-1J6

SYSTEM_SKU: PSCBAE

SYSTEM_VERSION: PSCBAE-0CH00GBT

BIOS_VENDOR: Insyde Corp.

BIOS_VERSION: 6.30

BIOS_DATE: 12/05/2012

BASEBOARD_MANUFACTURER: Intel

BASEBOARD_PRODUCT: PLCSF8

BASEBOARD_VERSION: Type2 - Board Version

DUMP_TYPE: 1

BUGCHECK_P1: 4

BUGCHECK_P2: 12c

BUGCHECK_P3: ffffc2055ee55040

BUGCHECK_P4: fffff800b663b910

DRVPOWERSTATE_SUBCODE: 4

IMAGE_NAME: BthEnum.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: BthEnum

FAULTING_MODULE: fffff800bc030000 BthEnum

CPU_COUNT: 4

CPU_MHZ: 8f7

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 2a

CPU_STEPPING: 7

CPU_MICROCODE: 6,2a,7,0 (F,M,S,R) SIG: 29'00000000 (cache) 29'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: JYPY

ANALYSIS_SESSION_TIME: 11-28-2017 12:17:15.0693

ANALYSIS_VERSION: 10.0.16299.15 amd64fre

STACK_TEXT:
fffff800`b663b8d8 fffff800`b43f6f24 : 00000000`0000009f 00000000`00000004 00000000`0000012c ffffc205`5ee55040 : nt!KeBugCheckEx
fffff800`b663b8e0 fffff800`b4617336 : fffff800`b45faa00 00000000`00000001 00000000`00000001 fffff800`b663bb10 : nt!PnpBugcheckPowerTimeout+0x60
fffff800`b663b940 fffff800`b4272c68 : ffff8000`3edcd630 ffff8000`3edcd670 00000000`00000004 0000003f`00000002 : nt!PopBuildDeviceNotifyListWatchdog+0x16
fffff800`b663b970 fffff800`b4273ad7 : fffff800`b3065180 00000000`002231f7 00000000`00000ac8 00000000`000fc94f : nt!KiProcessExpiredTimerList+0x248
fffff800`b663ba60 fffff800`b437062a : 00000000`00000000 fffff800`b3065180 00000000`001a6fd0 fffff800`b45faa40 : nt!KiRetireDpcList+0x367
fffff800`b663bc60 00000000`00000000 : fffff800`b663c000 fffff800`b6636000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


THREAD_SHA1_HASH_MOD_FUNC: 0efaf37e6601d7f65db9dbe50a219f0403a414f7

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: b5bfd627712d5077c444565ed7d7a84aba13225a

THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 10.0.15063.502

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x9F_4_BthA2DP_IMAGE_BthEnum.sys

BUCKET_ID: 0x9F_4_BthA2DP_IMAGE_BthEnum.sys

PRIMARY_PROBLEM_CLASS: 0x9F_4_BthA2DP_IMAGE_BthEnum.sys

TARGET_TIME: 2017-11-27T22:01:06.000Z

OSBUILD: 15063

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-11-02 05:21:12

BUILDDATESTAMP_STR: 170317-1834

BUILDLAB_STR: rs2_release

BUILDOSVER_STR: 10.0.15063.0.amd64fre.rs2_release.170317-1834

ANALYSIS_SESSION_ELAPSED_TIME: a6b

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9f_4_btha2dp_image_bthenum.sys

FAILURE_ID_HASH: {b7908ee9-a10a-bc18-f9db-351c4efc48e8}

Followup: MachineOwner
---------


voila si quelqu'un peut m'aider

merci

Alain Louis

[Malekal_morte]

Salut,

Faudrait faire une analyse FRST :

Suis le tutoriel FRST. ( prends le temps de lire attentivement - tout y est bien expliqué ).

Télécharge et lance le scan FRST,
Attendre la fin du scan, un message indique que l'analyse est terminée.

Trois rapports FRST seront générés :
* FRST.txt
* Shortcut.
* Additionnal.txt

Envoie ces 3 rapports sur le site https://pjjoint.malekal.com/ et en retour donne les 3 liens pjjoint qui mènent aux rapports ici dans une nouvelle réponse afin que l'on puisse les consulter.

[alain louis]

Merci pour la réponse voici les liens demandé (FRST - ADDITION - SHORTCUT)

https://pjjoint.malekal.com/files.php?i ... 2k12n14z11

https://pjjoint.malekal.com/files.php?i ... b10w7s8q11

https://pjjoint.malekal.com/files.php?i ... 11y13p15w7

[Malekal_morte]

Désinstalle

EasyPDFCombine Internet Explorer Homepage and New Tab
WildTangent Games

sinon :

PRIMARY_PROBLEM_CLASS: 0x9F_4_BthA2DP_IMAGE_BthEnum.sys

J'aurai tendance à dire que c'est le bluethooth qui plante.
Si tu as des périphériques autre que le clavier ou souris qui sont branchés test sans.

Tu peux aussi désactiver le périphérique bluetthoth depuis le gestionnaire de périphériques de Windows, pour voir.