meridian-shaft Jump to content
Forums

Bsod ntoskrnl 0x139


Solved

Recommended Posts

Bonjour a tous, je viens vers vous car j'ai un petit soucis avec mon ordi il me fait des Bsod aléatoirement avec le code erreur ntoskrnl 0x139, c'est un 8.1 que j'ai évoluer en 10 quand c'était gratuit.

J'ai une carte mère ASUS CROSSBLADE RANGER

un processeur AMD A10-7890K (4.1 GHz) Black Low Noise Edition

une alim antec 550w plus gold non modulaire

une carte son asus xonar dg

une carte graphique que je viens juste de changé parce que j' avais déjà se problème donc carte graphique msi armor 1060 6gb

la mémoire vive est G.Skill RipJaws X Series 8 Go (2 x 4 Go) DDR3 2400 MHz CL11 16 go en tout.

Voici ce que dit whocrashed:

Révélation

System Information (local)



Computer name: PC
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., CROSSBLADE RANGER
CPU: AuthenticAMD AMD A10-7890K Radeon R7, 12 Compute Cores 4C+8G AMD586, level: 21
4 logical processors, active mask: 15
RAM: 17108557824 bytes total



 


Crash Dump Analysis



Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 24/06/2018 14:19:21 your computer crashed
crash dump file: C:\WINDOWS\Minidump\062418-8031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)
Bugcheck code: 0x139 (0x3, 0xFFFFF605CC64B820, 0xFFFFF605CC64B778, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 24/06/2018 14:19:21 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!NtUserWin32kSysCallFilterStub+0x3BD)
Bugcheck code: 0x139 (0x3, 0xFFFFF605CC64B820, 0xFFFFF605CC64B778, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: The kernel has detected the corruption of a critical data structure.
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 Sun 24/06/2018 13:19:18 your computer crashed
crash dump file: C:\WINDOWS\Minidump\062418-7218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)
Bugcheck code: 0x139 (0x3, 0xFFFFFB809581AED0, 0xFFFFFB809581AE28, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver 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.

Voici le rapport de bluescreenview:

Révélation

062418-8031-01.dmp    24/06/2018 14:19:21        0x00000139    00000000`00000003    fffff605`cc64b820    fffff605`cc64b778    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+198330                    64-bits    ntoskrnl.exe+198330                    C:\WINDOWS\Minidump\062418-8031-01.dmp    4    15    17134    550 012    24/06/2018 14:20:29    
062418-7218-01.dmp    24/06/2018 13:19:18        0x00000139    00000000`00000003    fffffb80`9581aed0    fffffb80`9581ae28    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+198330                    64-bits    ntoskrnl.exe+198330                    C:\WINDOWS\Minidump\062418-7218-01.dmp    4    15    17134    564 076    24/06/2018 14:15:55

et dans l'onglet du bas voici se qu'il y a de surligné:

Révélation

ntoskrnl.exe    ntoskrnl.exe+1a8e69    fffff804`0061d000    fffff804`00f7e000    0x00961000    0x5b1a4590    08/06/2018 11:00:00

et enfin le rapport de windebug:

Révélation

Microsoft (R) Windows Debugger Version 10.0.15063.468 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.


************* Symbol 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 17134 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff800`35204000 PsLoadedModuleList = 0xfffff800`355be1f0
Debug session time: Sun Jun 24 14:19:21.436 2018 (UTC + 2:00)
System Uptime: 0 days 0:03:42.449
Loading Kernel Symbols
...............................................................
..Page 19ddb7 not present in the dump file. Type ".hh dbgerr004" for details
..............................................................
..................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000e3`ec686018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 139, {3, fffff605cc64b820, fffff605cc64b778, 0}

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32kfull.sys - 
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+1552c1 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff605cc64b820, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff605cc64b778, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  0603

BIOS_DATE:  09/10/2014

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  CROSSBLADE RANGER

BASEBOARD_VERSION:  Rev X.0x

DUMP_TYPE:  1

BUGCHECK_P1: 3

BUGCHECK_P2: fffff605cc64b820

BUGCHECK_P3: fffff605cc64b778

BUGCHECK_P4: 0

TRAP_FRAME:  fffff605cc64b820 -- (.trap 0xfffff605cc64b820)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe201c3143a80 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffc3856c071158 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800353e4a41 rsp=fffff605cc64b9b0 rbp=ffffe201c313e180
 r8=0000000000000002  r9=0000000084995cc9 r10=0000000000000002
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!KiCommitThreadWait+0x1552c1:
fffff800`353e4a41 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  fffff605cc64b778 -- (.exr 0xfffff605cc64b778)
ExceptionAddress: fffff800353e4a41 (nt!KiCommitThreadWait+0x00000000001552c1)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

CPU_COUNT: 4

CPU_MHZ: 1004

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 38

CPU_STEPPING: 1

BUGCHECK_STR:  0x139

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000409 - Le syst me a d tect  la saturation de la m moire tampon dans cette application. Cette saturation pourrait permettre   un utilisateur mal intentionn  de prendre le contr le de cette application.

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - Le syst me a d tect  la saturation de la m moire tampon dans cette application. Cette saturation pourrait permettre   un utilisateur mal intentionn  de prendre le contr le de cette application.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000003

DEFAULT_BUCKET_ID:  FAIL_FAST_LIST_ENTRY_CORRUPT

ANALYSIS_SESSION_HOST:  PCJEROME

ANALYSIS_SESSION_TIME:  06-24-2018 14:41:20.0908

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

LAST_CONTROL_TRANSFER:  from fffff800353ace69 to fffff8003539c330

STACK_TEXT:  
fffff605`cc64b4f8 fffff800`353ace69 : 00000000`00000139 00000000`00000003 fffff605`cc64b820 fffff605`cc64b778 : nt!KeBugCheckEx
fffff605`cc64b500 fffff800`353ad210 : 00000000`00000000 00000000`00000000 fffff800`33e62180 fffff800`35294c4f : nt!KiBugCheckDispatch+0x69
fffff605`cc64b640 fffff800`353ab81f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiFastFailDispatch+0xd0
fffff605`cc64b820 fffff800`353e4a41 : ffffc385`6c5d9440 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x2df
fffff605`cc64b9b0 fffff800`3528efdf : fffff605`00000025 ffffc385`00000000 ffffc385`6ada2001 ffffc385`6c5d9580 : nt!KiCommitThreadWait+0x1552c1
fffff605`cc64ba50 fffff800`3528e805 : ffffc385`6be60a00 fffff800`00000006 fffff800`353ac901 00000000`00000000 : nt!KeWaitForSingleObject+0x1ff
fffff605`cc64bb30 fffff800`35705eb0 : fffff605`00000001 fffff605`cc64bcc0 00000000`00000000 fffff800`00000006 : nt!KeWaitForMultipleObjects+0x4b5
fffff605`cc64bc10 ffffd55e`33470d5d : 00000000`00000000 ffffd55e`34354ba8 00000000`00000000 fffff800`3528d287 : nt!ObWaitForMultipleObjects+0x2a0
fffff605`cc64c110 ffffd55e`3338f061 : 00000000`00000000 ffffd52d`c204e2e0 00000000`0000000f fffff800`00001cff : win32kfull!NtUserWin32kSysCallFilterStub+0x3bd
fffff605`cc64c1c0 fffff800`353ac943 : ffffc385`6c5d9440 00000000`00000000 000000e3`0000000f fffff605`00001cff : win32kfull!NtUserMsgWaitForMultipleObjectsEx+0x381
fffff605`cc64ca90 00007fff`559296e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000e3`ec9fe698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`559296e4


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  4effd5905a5c575d28e9373d3f2c88b31a3a7386

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  e25209e767e2a52f1be0c5448c11b7858a49f460

THREAD_SHA1_HASH_MOD:  0539fbe20e7ad4e0b8a84dcb0095896042a0d4ec

FOLLOWUP_IP: 
nt!KiCommitThreadWait+1552c1
fffff800`353e4a41 cd29            int     29h

FAULT_INSTR_CODE:  798029cd

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KiCommitThreadWait+1552c1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5b1a4590

BUCKET_ID_FUNC_OFFSET:  1552c1

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiCommitThreadWait

BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiCommitThreadWait

PRIMARY_PROBLEM_CLASS:  0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiCommitThreadWait

TARGET_TIME:  2018-06-24T12:19:21.000Z

OSBUILD:  17134

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:  2018-06-08 11:00:00

BUILDDATESTAMP_STR:  180410-1804

BUILDLAB_STR:  rs4_release

BUILDOSVER_STR:  10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME:  11fc

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x139_3_corrupt_list_entry_ktimer_list_corruption_nt!kicommitthreadwait

FAILURE_ID_HASH:  {369b7001-cfef-011b-6243-985c04f34d42}

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

Donc voici ce que j'ai pu obtenir pour les erreurs je viens vers vous car c'est assez agaçant comme problème, je n'ai pas mentionner que mon windows se trouve sur un ssd a part du reste de mes autres dossiers.

Je vous remercie d'avance de votre aide.

Edited by Le PoissonClown
Aide : mise en forme plus lisible
Link to comment

Se problème est arrivé quand j'étais sur un jeu (révélation online) et sa avait disparu quand j'ai viré amd catalyst. Aprés 6-7 bon mois plus rien et de nouveau retour page bleu sans rien faire, donc changé de carte graphique mais toujours pareil.

Je ne sais pas ce qui a pu arriver pour me recommencer les bsod que j'ai, mais j'ai déjà vérifier toute les mise a jour.

Link to comment

yop @jeje86

désinstallé le complètement Chrome, passer un coup de Ccleaner : https://filehippo.com/fr/download_ccleaner/

vous pouvez passer par iobit uninstaller aussi :

https://www.iobit.com/fr/advanceduninstaller.php

et oui prenez explorer ou Firefox choisissez bien votre version

  • 32 bit Firefox

ou

  • 64 bit Firefox

https://www.mozilla.org/fr/firefox/all/

Edited by Delta
Link to comment

1 heure plus tard bsod  avec toujours les mêmes codes

On Sun 24/06/2018 18:11:10 your computer crashed
crash dump file: C:\WINDOWS\Minidump\062418-7359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)
Bugcheck code: 0x139 (0x3, 0xFFFFF802C30623D0, 0xFFFFF802C3062328, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 24/06/2018 18:11:10 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: portcls.sys (portcls+0x132CD)
Bugcheck code: 0x139 (0x3, 0xFFFFF802C30623D0, 0xFFFFF802C3062328, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
Bug check description: The kernel has detected the corruption of a critical data structure.
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.

 

Link to comment

file path: C:\WINDOWS\system32\drivers\portcls.sys

 

il y a 42 minutes, jeje86 a dit :

description: Port Class (Class Driver for Port/Miniport Devices)

c'est un driver qui pose vraiment problème en fait ...

un drivers qui est pris par deux périphériques ou autre qui rentre en conflit ...

 

Link to comment

cela peut être du au sound .. .. difficile a dire comme cela..

tentez une fois de mettre iobit driver booster

https://www.iobit.com/fr/driver-booster.php

une fois le logiciel lancé, si il détecte des drivers obsolète il vous proposera de les installer et fera d’abord un point de restauration...

essayer de voir si il ne détecte pas un drivers obsolète ou autre sur Port/Miniport Devices

  • J'aime 1
Link to comment

Bonjour, de nouveau bsod sont apparus sur l'ordi voici ce que whocrashed dit:

Révélation

 

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 25/06/2018 15:14:02 your computer crashed
crash dump file: C:\WINDOWS\Minidump\062518-7984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)
Bugcheck code: 0x139 (0x3, 0xFFFFFD089039C7A0, 0xFFFFFD089039C6F8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 25/06/2018 15:14:02 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFFD089039C7A0, 0xFFFFFD089039C6F8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


 Je lance Windbg:

Microsoft (R) Windows Debugger Version 10.0.15063.468 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.


************* Symbol 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 17134 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff802`d9412000 PsLoadedModuleList = 0xfffff802`d97cc1f0
Debug session time: Mon Jun 25 15:14:02.626 2018 (UTC + 2:00)
System Uptime: 0 days 17:28:47.641
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`003e3018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 139, {3, fffffd089039c7a0, fffffd089039c6f8, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+153922 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffffd089039c7a0, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffffd089039c6f8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  0603

BIOS_DATE:  09/10/2014

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  CROSSBLADE RANGER

BASEBOARD_VERSION:  Rev X.0x

DUMP_TYPE:  1

BUGCHECK_P1: 3

BUGCHECK_P2: fffffd089039c7a0

BUGCHECK_P3: fffffd089039c6f8

BUGCHECK_P4: 0

TRAP_FRAME:  fffffd089039c7a0 -- (.trap 0xfffffd089039c7a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff958ed3f5d940 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000011697 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802d95f3632 rsp=fffffd089039c930 rbp=0000009283cd8b1b
 r8=fffff802d7fc7870  r9=fffff802d7fc5800 r10=fffff802d7fc2180
r11=fffff802d9412000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!KiInsertTimerTable+0x153922:
fffff802`d95f3632 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  fffffd089039c6f8 -- (.exr 0xfffffd089039c6f8)
ExceptionAddress: fffff802d95f3632 (nt!KiInsertTimerTable+0x0000000000153922)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

CPU_COUNT: 4

CPU_MHZ: 1004

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 38

CPU_STEPPING: 1

BUGCHECK_STR:  0x139

PROCESS_NAME:  DriverBooster.exe

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000409 - Le syst me a d tect  la saturation de la m moire tampon dans cette application. Cette saturation pourrait permettre   un utilisateur mal intentionn  de prendre le contr le de cette application.

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - Le syst me a d tect  la saturation de la m moire tampon dans cette application. Cette saturation pourrait permettre   un utilisateur mal intentionn  de prendre le contr le de cette application.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000003

DEFAULT_BUCKET_ID:  FAIL_FAST_LIST_ENTRY_CORRUPT

ANALYSIS_SESSION_HOST:  PC

ANALYSIS_SESSION_TIME:  06-25-2018 17:32:04.0419

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

LAST_CONTROL_TRANSFER:  from fffff802d95bae69 to fffff802d95aa330

STACK_TEXT:  
fffffd08`9039c478 fffff802`d95bae69 : 00000000`00000139 00000000`00000003 fffffd08`9039c7a0 fffffd08`9039c6f8 : nt!KeBugCheckEx
fffffd08`9039c480 fffff802`d95bb210 : ffffdc81`adc20180 ffff958e`ce5a0080 00000000`00000001 ffff958e`d2e2d700 : nt!KiBugCheckDispatch+0x69
fffffd08`9039c5c0 fffff802`d95b981f : 00000000`fffffffe 00000000`ffffffff 00000000`00000000 00000000`0000000f : nt!KiFastFailDispatch+0xd0
fffffd08`9039c7a0 fffff802`d95f3632 : 00000000`00000000 fffff802`d95b107f 00000000`00000000 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x2df
fffffd08`9039c930 fffff802`d949dae2 : ffff958e`d2e2d700 fffff802`d94e0ec8 00000000`01d8ebc6 ffffdc81`00000000 : nt!KiInsertTimerTable+0x153922
fffffd08`9039c9a0 fffff802`d94a97a2 : ffff958e`000000f3 ffff958e`00000000 fffffd08`00000001 00000000`00000002 : nt!KiCommitThreadWait+0x362
fffffd08`9039ca40 fffff802`d992069f : ffff958e`d2e2d700 fffff802`d95ba94b 00000000`00000000 00000000`00000206 : nt!KeDelayExecutionThread+0x3d2
fffffd08`9039cad0 fffff802`d95ba943 : 00000000`02a09620 ffffdc81`ae7a7a00 ffffffff`fffe7960 00000000`77d44620 : nt!NtDelayExecution+0x5f
fffffd08`9039cb00 00000000`77d41e4c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0a91f328 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77d41e4c


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  a87361c5e3a6d23a766164606eea6e4148fa41b1

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  1d09934af9b7e14bd5c8b5f62b2c843930c45659

THREAD_SHA1_HASH_MOD:  9f457f347057f10e1df248e166a3e95e6570ecfe

FOLLOWUP_IP:
nt!KiInsertTimerTable+153922
fffff802`d95f3632 cd29            int     29h

FAULT_INSTR_CODE:  798029cd

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KiInsertTimerTable+153922

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5b1a4590

BUCKET_ID_FUNC_OFFSET:  153922

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiInsertTimerTable

BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiInsertTimerTable

PRIMARY_PROBLEM_CLASS:  0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiInsertTimerTable

TARGET_TIME:  2018-06-25T13:14:02.000Z

OSBUILD:  17134

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:  2018-06-08 11:00:00

BUILDDATESTAMP_STR:  180410-1804

BUILDLAB_STR:  rs4_release

BUILDOSVER_STR:  10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME:  ee1

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x139_3_corrupt_list_entry_ktimer_list_corruption_nt!kiinserttimertable

FAILURE_ID_HASH:  {f89e8bcc-9d62-a3aa-7602-6fa1ac774850}

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

 

 

Edited by Delta
Link to comment
à l’instant, jeje86 a dit :

il ne se passe rien quand je tape sfc /scannow

 

Dsl,

c'est moi qui fait une erreur ..

  • cliquer sur le drapeau en bas a gauche
  • puis sur rechercher taper invité commande dos quand elle apparait dans la liste cliquer droit dessus et ouvrir en mode administrateur
  • la page dos s'ouvre et taper sfc /scannow

++

 

Link to comment

cliquer une fois :

  • cliquer droit sur le drapeau en bas a gauche
  • cliquer sur observateur d’évènement
  • et regarder a l'heure du écran bleu se que cela déclare..

 

cliquer sur journaux Windows

ensuite :

  • application
  • système

donnez nous se que cela dit ...

 

++

 

 

 

Link to comment

Bonjour, il y a énormément d'erreurs 

Erreur    21/06/2018 12:25:38    BugCheck    1001    Aucun

- System
   
- Provider
      [ Name] Microsoft-Windows-WER-SystemErrorReporting
      [ Guid] {ABCE23E7-DE45-4366-8631-84FA6C525952}
      [ EventSourceName] BugCheck
   
- EventID 1001
      [ Qualifiers] 16384
   
  Version 0
   
  Level 2
   
  Task 0
   
  Opcode 0
   
  Keywords 0x80000000000000
   
- TimeCreated
      [ SystemTime] 2018-06-21T10:25:38.421176100Z
   
  EventRecordID 8545
   
  Correlation
   
- Execution
      [ ProcessID] 0
      [ ThreadID] 0
   
  Channel System
   
  Computer pcjerome
   
  Security
- EventData
    param1 0x00000139 (0x0000000000000003, 0xffffc0067e5e7830, 0xffffc0067e5e7788, 0x0000000000000000)
    param2 C:\WINDOWS\MEMORY.DMP
 

 

param3

5f277610-5025-497b-875b-be991ccfa746

Critique    26/06/2018 06:26:46    Kernel-Power    41    (63)

 

- System
   
- Provider
      [ Name] Microsoft-Windows-Kernel-Power
      [ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
   
  EventID 41
   
  Version 6
   
  Level 1
   
  Task 63
   
  Opcode 0
   
  Keywords 0x8000400000000002
   
- TimeCreated
      [ SystemTime] 2018-06-26T04:26:46.632438200Z
   
  EventRecordID 10265
   
  Correlation
   
- Execution
      [ ProcessID] 4
      [ ThreadID] 8
   
  Channel System
   
  Computer pcjerome
   
- Security
      [ UserID] S-1-5-18
- EventData
    BugcheckCode 209
    BugcheckParameter1 0x1f8000aa0071
    BugcheckParameter2 0xff
    BugcheckParameter3 0x0
    BugcheckParameter4 0x1f8000aa0071
    SleepInProgress 0
    PowerButtonTimestamp 0
    BootAppStatus 0
    Checkpoint 0
    ConnectedStandbyInProgress false
    SystemSleepTransitionsToOn 1
    CsEntryScenarioInstanceId 0
    BugcheckInfoFromEFI false
    CheckpointStatus

0

 

 

 

Link to comment

Erreur    20/06/2018 15:59:57    nvlddmkm    14    Aucun

- System
   
- Provider
      [ Name] nvlddmkm
   
- EventID 14
      [ Qualifiers] 49322
   
  Level 2
   
  Task 0
   
  Keywords 0x80000000000000
   
- TimeCreated
      [ SystemTime] 2018-06-20T13:59:57.410329700Z
   
  EventRecordID 7979
   
  Channel System
   
  Computer pcjerome
   
  Security
- EventData
      \Device\Video3
      ffffffff(ffffffff) ffffffff ffffffff
      0000000002003000000000000E00AAC0000000000000000000000000000000000000000000000000

Données binaires :

En mots

0000: 00000000 00300002 00000000 C0AA000E
0010: 00000000 00000000 00000000 00000000
0020: 00000000 00000000

En octets

0000: 00 00 00 00 02 00 30 00 ......0.
0008: 00 00 00 00 0E 00 AA C0 ......ªÀ
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

 

voila les erreurs  que j'ai les plus courante sur système maintnant celle de l'aplication:

Erreur    26/06/2018 12:17:29    Application Error    1000    (100)

- System
   
- Provider
      [ Name] Application Error
   
- EventID 1000
      [ Qualifiers] 0
   
  Level 2
   
  Task 100
   
  Keywords 0x80000000000000
   
- TimeCreated
      [ SystemTime] 2018-06-26T10:17:29.708555800Z
   
  EventRecordID 11053
   
  Channel Application
   
  Computer pcjerome
   
  Security
- EventData
      ATKEX_cmd.exe
      0.0.0.0
      00000000
      KERNELBASE.dll
      10.0.17134.112
      c863c6f9
      0eedfade
      0010db52
      190c
      01d40d36e31eb593
      C:\Program Files\Realtek\Audio\HDA\ATKEX_cmd.exe
      C:\WINDOWS\System32\KERNELBASE.dll
      3a00db8c-af8f-4fb1-b7b7-138cdf9ef149
       
       
Link to comment
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...