Aller au contenu
Site Communauté

jeje86

Membres
  • Nbre de contenus

    20
  • Inscription

  • Dernière visite

Configuration PC

  • Système d'exploitation
    Windows 10

Visiteurs récents du profil

Le bloc de visiteurs récents est désactivé et il n’est pas visible pour les autres utilisateurs.

Succès de jeje86

Matelot breveté

Matelot breveté (2/24)

  • Premier message
  • Collaborateur Rare
  • Une semaine déjà
  • 30 jours déjà
  • Un an déjà

Badges récents

2

Réputation dans la communauté

  1. jeje86

    Bsod ntoskrnl 0x139

    Bonjour, après plusieurs semaines sans bsod je pense que le problème est résolue. j'ai changé mon processeur et depuis plus rien. Merci pour votre aide.
  2. jeje86

    Bsod ntoskrnl 0x139

    Pour la carte graphique c'est une msi armor 1060 6gb J'ai changer le processeur il y a 2 jours et plus de nouvelle de bsod se que je trouve pas plus mal. On va continué comme sa et voir si sa reviens.
  3. jeje86

    Bsod ntoskrnl 0x139

    Radeon R9 380X le processeur a été changer on va bien voir si sa tiens.
  4. jeje86

    Bsod ntoskrnl 0x139

    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`5a804000 PsLoadedModuleList = 0xfffff800`5abbe1f0 Debug session time: Wed Jun 27 17:30:38.867 2018 (UTC + 2:00) System Uptime: 0 days 18:34:32.882 Loading Kernel Symbols ............................................................... .Page 1404 not present in the dump file. Type ".hh dbgerr004" for details ........Page 2cf53d 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 1, {7fff4b33a534, 1, 0, fffff3063c3bfb80} Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExitPico+1e5 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* APC_INDEX_MISMATCH (1) This is a kernel internal error. The most common reason to see this bugcheck is when a filesystem or a driver has a mismatched number of calls to disable and re-enable APCs. The key data item is the Thread->CombinedApcDisable field. This consists of two separate 16-bit fields, the SpecialApcDisable and the KernelApcDisable. A negative value of either indicates that a driver has disabled special or normal APCs (respectively) without re-enabling them; a positive value indicates that a driver has enabled special or normal APCs (respectively) too many times. Arguments: Arg1: 00007fff4b33a534, Address of system call function or worker routine Arg2: 0000000000000001, Thread->ApcStateIndex Arg3: 0000000000000000, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable Arg4: fffff3063c3bfb80, Call type (0 - system call, 1 - worker routine) 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: 7fff4b33a534 BUGCHECK_P2: 1 BUGCHECK_P3: 0 BUGCHECK_P4: fffff3063c3bfb80 FAULTING_IP: +0 00007fff`4b33a534 ?? ??? CPU_COUNT: 4 CPU_MHZ: 1004 CPU_VENDOR: AuthenticAMD CPU_FAMILY: 15 CPU_MODEL: 38 CPU_STEPPING: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x1 PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_SESSION_HOST: PCJEROME ANALYSIS_SESSION_TIME: 06-27-2018 17:34:25.0742 ANALYSIS_VERSION: 10.0.15063.468 amd64fre BAD_STACK_POINTER: fffff3063c3bf9b8 LAST_CONTROL_TRANSFER: from fffff8005a9ace69 to fffff8005a99c330 STACK_TEXT: fffff306`3c3bf9b8 fffff800`5a9ace69 : 00000000`00000001 00007fff`4b33a534 00000000`00000001 00000000`00000000 : nt!KeBugCheckEx fffff306`3c3bf9c0 fffff800`5a9acd84 : ffffc58e`5e6bf700 00000000`00000000 ffffffff`fffea070 ffffc58e`5c1283c0 : nt!KiBugCheckDispatch+0x69 fffff306`3c3bfb00 00007fff`4b33a534 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1e5 00000000`00eff5b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`4b33a534 STACK_COMMAND: kb THREAD_SHA1_HASH_MOD_FUNC: 1b1fd012b2a510c586295e696f84a9476c8f91e5 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 23cedde8f16306672a83c8d473517a37e703b476 THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b FOLLOWUP_IP: nt!KiSystemServiceExitPico+1e5 fffff800`5a9acd84 4883ec50 sub rsp,50h FAULT_INSTR_CODE: 50ec8348 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiSystemServiceExitPico+1e5 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 5b1a4590 BUCKET_ID_FUNC_OFFSET: 1e5 FAILURE_BUCKET_ID: 0x1_SysCallNum_0_STACKPTR_ERROR_nt!KiSystemServiceExitPico BUCKET_ID: 0x1_SysCallNum_0_STACKPTR_ERROR_nt!KiSystemServiceExitPico PRIMARY_PROBLEM_CLASS: 0x1_SysCallNum_0_STACKPTR_ERROR_nt!KiSystemServiceExitPico TARGET_TIME: 2018-06-27T15:30:38.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: e47 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x1_syscallnum_0_stackptr_error_nt!kisystemserviceexitpico FAILURE_ID_HASH: {29841e22-ca67-b63d-5b1c-3557be9f186c} Followup: MachineOwner --------- voici la nouvelle page bleu je n'ai pas changé encore mon proc on verra bien si sa marche
  5. jeje86

    Bsod ntoskrnl 0x139

    si vous voulez d'autre info dite le moi je pense remettre mon vieux processeur car les première bsod sont arrivé après que je l'ai installer mais il y en avait une par hasard donc je m'inquiétais pas mais sa commence à être courante, qu'est ce que vous en pensé?
  6. jeje86

    Bsod ntoskrnl 0x139

    Erreur 24/06/2018 08:38:05 SpellChecker 33 Installation - System - Provider [ Name] Microsoft-Windows-SpellChecker [ Guid] {B2FCD41F-9A40-4150-8C92-B224B7D8C8AA} EventID 33 Version 0 Level 2 Task 4 Opcode 0 Keywords 0x2000000000000000 - TimeCreated [ SystemTime] 2018-06-24T06:38:05.536589100Z EventRecordID 9825 Correlation - Execution [ ProcessID] 6428 [ ThreadID] 8104 Channel Application Computer pcjerome - Security [ UserID] S-1-5-21-162900879-1736942234-1805584738-1001 - EventData First http Second http hr -2147467263
  7. jeje86

    Bsod ntoskrnl 0x139

    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
  8. jeje86

    Bsod ntoskrnl 0x139

    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
  9. jeje86

    Bsod ntoskrnl 0x139

    non juste kernel security check faillure c'est tout
  10. jeje86

    Bsod ntoskrnl 0x139

    peu importe en jeu, lecture d'une video, juste sur le bureau, etc... a n'importe quel moment.
  11. jeje86

    Bsod ntoskrnl 0x139

    la vérification est terminé le programme des protections des ressources Windows n'a trouvé aucune violation d'intégrité.
  12. jeje86

    Bsod ntoskrnl 0x139

    il ne se passe rien quand je tape sfc /scannow
  13. jeje86

    Bsod ntoskrnl 0x139

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

    Bsod ntoskrnl 0x139

    J'avais 4 pilotes obsolètes on va voir si ça viens de çà. Encore merci pour votre aide.
  15. jeje86

    Bsod ntoskrnl 0x139

    comment peux t'on le trouver?
×
×
  • Créer...