none
Tela Azul windows 7 RRS feed

  • Pergunta

  • Bom dia,

    Foi extraído as logs do Event Viewer de uma máquina com Windows 7 que apresentou tela azul. Por gentileza, poderiam me  reportar o motivo da tela azul?

    Desde já agradeço, segue a log.

    Microsoft (R) Windows Debugger Version 10.0.17712.1000 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\thiago.karas\Desktop\072418-9016-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*
    Symbol search path is: srv*
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.24168.amd64fre.win7sp1_ldr.180608-0600
    Machine Name:
    Kernel base = 0xfffff800`0301d000 PsLoadedModuleList = 0xfffff800`0325cc90
    Debug session time: Tue Jul 24 09:26:05.079 2018 (UTC - 3:00)
    System Uptime: 0 days 22:11:44.697
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ..
    Loading User Symbols
    Loading unloaded module list
    ........................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1, {76f8991a, 0, ffff, fffff8800f6e5b60}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+29d )
    
    Followup:     MachineOwner
    ---------
    
    nt!KeBugCheckEx:
    fffff800`030c18a0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff880`0f6e5930=0000000000000001
    2: 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: 0000000076f8991a, Address of system call function or worker routine
    Arg2: 0000000000000000, Thread->ApcStateIndex
    Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
    Arg4: fffff8800f6e5b60, Call type (0 - system call, 1 - worker routine)
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  7601.24168.amd64fre.win7sp1_ldr.180608-0600
    
    SYSTEM_MANUFACTURER:  Dell Inc.
    
    SYSTEM_PRODUCT_NAME:  Latitude E7270
    
    SYSTEM_SKU:  06DB
    
    BIOS_VENDOR:  Dell Inc.
    
    BIOS_VERSION:  1.18.5
    
    BIOS_DATE:  12/11/2017
    
    BASEBOARD_MANUFACTURER:  Dell Inc.
    
    BASEBOARD_PRODUCT:  0H7Y7K
    
    BASEBOARD_VERSION:  A03
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: 76f8991a
    
    BUGCHECK_P2: 0
    
    BUGCHECK_P3: ffff
    
    BUGCHECK_P4: fffff8800f6e5b60
    
    FAULTING_IP: 
    +0
    00000000`76f8991a ??              ???
    
    CPU_COUNT: 4
    
    CPU_MHZ: 9c0
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 4e
    
    CPU_STEPPING: 3
    
    CPU_MICROCODE: 6,4e,3,0 (F,M,S,R)  SIG: C2'00000000 (cache) C2'00000000 (init)
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1
    
    PROCESS_NAME:  audiodg.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_SESSION_HOST:  RB-NT-022
    
    ANALYSIS_SESSION_TIME:  07-26-2018 10:56:42.0410
    
    ANALYSIS_VERSION: 10.0.17712.1000 amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff800030cfd69 to fffff800030c18a0
    
    STACK_TEXT:  
    fffff880`0f6e5928 fffff800`030cfd69 : 00000000`00000001 00000000`76f8991a 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
    fffff880`0f6e5930 fffff800`030cfc78 : fffffa80`11a87640 00000000`0092e528 fffff880`0f6e5a88 00000000`00000001 : nt!KiBugCheckDispatch+0x69
    fffff880`0f6e5a70 00000000`76f8991a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x29d
    00000000`0092e4f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f8991a
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  713a38487ff3d82058f51d9870e0b3de39cbf964
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  d9da406b771ca61ffe3f9563126f99f31658603a
    
    THREAD_SHA1_HASH_MOD:  2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b
    
    FOLLOWUP_IP: 
    nt!KiSystemServiceExit+29d
    fffff800`030cfc78 4883ec50        sub     rsp,50h
    
    FAULT_INSTR_CODE:  50ec8348
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiSystemServiceExit+29d
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5b1aa20d
    
    IMAGE_VERSION:  6.1.7601.24168
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+29d
    
    BUCKET_ID:  X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+29d
    
    PRIMARY_PROBLEM_CLASS:  X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+29d
    
    TARGET_TIME:  2018-07-24T12:26:05.000Z
    
    OSBUILD:  7601
    
    OSSERVICEPACK:  1000
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  272
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 7
    
    OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  2018-06-08 12:34:37
    
    BUILDDATESTAMP_STR:  180608-0600
    
    BUILDLAB_STR:  win7sp1_ldr
    
    BUILDOSVER_STR:  6.1.7601.24168.amd64fre.win7sp1_ldr.180608-0600
    
    ANALYSIS_SESSION_ELAPSED_TIME:  494
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x1_syscallnum_4_nt!kisystemserviceexit+29d
    
    FAILURE_ID_HASH:  {fb727eba-692d-68a9-1275-128848aa0b58}
    
    Followup:     MachineOwner
    ---------
    
    
    Microsoft (R) Windows Debugger Version 10.0.17712.1000 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\thiago.karas\Desktop\072518-10592-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*
    Symbol search path is: srv*
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.24168.amd64fre.win7sp1_ldr.180608-0600
    Machine Name:
    Kernel base = 0xfffff800`03002000 PsLoadedModuleList = 0xfffff800`03241c90
    Debug session time: Wed Jul 25 08:08:42.882 2018 (UTC - 3:00)
    System Uptime: 0 days 22:41:15.369
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    .
    Loading User Symbols
    Loading unloaded module list
    ..................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1, {772a991a, 0, ffff, fffff88021f12b60}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+29d )
    
    Followup:     MachineOwner
    ---------
    
    nt!KeBugCheckEx:
    fffff800`030a68a0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff880`21f12930=0000000000000001
    0: 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: 00000000772a991a, Address of system call function or worker routine
    Arg2: 0000000000000000, Thread->ApcStateIndex
    Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
    Arg4: fffff88021f12b60, Call type (0 - system call, 1 - worker routine)
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  7601.24168.amd64fre.win7sp1_ldr.180608-0600
    
    SYSTEM_MANUFACTURER:  Dell Inc.
    
    SYSTEM_PRODUCT_NAME:  Latitude E7270
    
    SYSTEM_SKU:  06DB
    
    BIOS_VENDOR:  Dell Inc.
    
    BIOS_VERSION:  1.18.5
    
    BIOS_DATE:  12/11/2017
    
    BASEBOARD_MANUFACTURER:  Dell Inc.
    
    BASEBOARD_PRODUCT:  0H7Y7K
    
    BASEBOARD_VERSION:  A03
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: 772a991a
    
    BUGCHECK_P2: 0
    
    BUGCHECK_P3: ffff
    
    BUGCHECK_P4: fffff88021f12b60
    
    FAULTING_IP: 
    +0
    00000000`772a991a ??              ???
    
    CPU_COUNT: 4
    
    CPU_MHZ: 9c0
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 4e
    
    CPU_STEPPING: 3
    
    CPU_MICROCODE: 6,4e,3,0 (F,M,S,R)  SIG: C2'00000000 (cache) C2'00000000 (init)
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1
    
    PROCESS_NAME:  audiodg.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_SESSION_HOST:  RB-NT-022
    
    ANALYSIS_SESSION_TIME:  07-26-2018 10:57:30.0769
    
    ANALYSIS_VERSION: 10.0.17712.1000 amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff800030b4d69 to fffff800030a68a0
    
    STACK_TEXT:  
    fffff880`21f12928 fffff800`030b4d69 : 00000000`00000001 00000000`772a991a 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
    fffff880`21f12930 fffff800`030b4c78 : fffffa80`168fb640 00000000`00e9e5d8 fffff880`21f12a88 00000000`00000001 : nt!KiBugCheckDispatch+0x69
    fffff880`21f12a70 00000000`772a991a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x29d
    00000000`00e9e5a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772a991a
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  713a38487ff3d82058f51d9870e0b3de39cbf964
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  d9da406b771ca61ffe3f9563126f99f31658603a
    
    THREAD_SHA1_HASH_MOD:  2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b
    
    FOLLOWUP_IP: 
    nt!KiSystemServiceExit+29d
    fffff800`030b4c78 4883ec50        sub     rsp,50h
    
    FAULT_INSTR_CODE:  50ec8348
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiSystemServiceExit+29d
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5b1aa20d
    
    IMAGE_VERSION:  6.1.7601.24168
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+29d
    
    BUCKET_ID:  X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+29d
    
    PRIMARY_PROBLEM_CLASS:  X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+29d
    
    TARGET_TIME:  2018-07-25T11:08:42.000Z
    
    OSBUILD:  7601
    
    OSSERVICEPACK:  1000
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  272
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 7
    
    OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  2018-06-08 12:34:37
    
    BUILDDATESTAMP_STR:  180608-0600
    
    BUILDLAB_STR:  win7sp1_ldr
    
    BUILDOSVER_STR:  6.1.7601.24168.amd64fre.win7sp1_ldr.180608-0600
    
    ANALYSIS_SESSION_ELAPSED_TIME:  478
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x1_syscallnum_4_nt!kisystemserviceexit+29d
    
    FAILURE_ID_HASH:  {fb727eba-692d-68a9-1275-128848aa0b58}
    
    Followup:     MachineOwner
    ---------
    
    

    quinta-feira, 26 de julho de 2018 13:57

Respostas

  • THG InfoSec,

    Olha o Painel de Controle em Sistemas, o seu Windows 7 é versão 32 bits (x86) ou 64bits (x64)?

    No relatório de erros acima mostra que existe drivers 32 bits instalados e drivers 64 bits instalado.

    Se o seu Windows 7 for 64 bits (x64) tem que desinstalar todos os drives 32 bits (x86), terá que procurar a versão 64 bits desses drivers e instalar.

    Se o seu Windows for 32 bits (x86), normalmente não se consegue instalar drivers de 64 bits (x64) nele.

    Quando o sistema operacional é 64 bits (x64) e existe drivers 32 bits (x86) instalados, ou aplicativos 32 bits instalados, o Windows costuma apresentar problemas.


    Ana Mercedes Gauna | IT Consultant | Microsoft Partner: 5126593 | Skype: amgauna@hotmail.com | Site: http://www.anagauna.eti.br | http://www.amgauna.com.br | Blog: http://anagauna.wordpress.com | If you have been able to help, please check the answer as correct.


    • Editado Ana Gauna quarta-feira, 1 de agosto de 2018 23:22
    • Sugerido como Resposta IgorFKModerator quinta-feira, 2 de agosto de 2018 12:25
    • Marcado como Resposta IgorFKModerator terça-feira, 7 de agosto de 2018 12:26
    quarta-feira, 1 de agosto de 2018 23:21
  • Boa tarde,

    Por falta de retorno essa thread está encerrada.

    Se necessário favor abrir uma nova thread.

    Atenciosamente,

    Igor F. Kunrath

    Esse conteúdo é fornecido sem garantias de qualquer tipo, seja expressa ou implícita

    Technet Community Support

    Por favor, lembre-se de Marcar como Resposta as postagens que resolveram o seu problema. Essa é uma maneira comum de reconhecer aqueles que o ajudaram e fazer com que seja mais fácil para os outros visitantes encontrarem a resolução mais tarde.

    • Marcado como Resposta IgorFKModerator terça-feira, 7 de agosto de 2018 12:26
    terça-feira, 7 de agosto de 2018 12:26
    Moderador

Todas as Respostas

  • Boa tarde, tudo bem?

    Dê uma olhada nas respostas destas duas threads abaixo, onde logs bem semelhantes são reportados:

    Blue Screen Error (Probably caused by : ntkrnlmp.exe)https://answers.microsoft.com/en-us/windows/forum/all/blue-screen-error-probably-caused-by-ntkrnlmpexe/d78912a7-f532-474e-bacf-874faf706b24?auth=1

    Bug Crash APC_INDEX_MISMATCHhttps://answers.microsoft.com/en-us/windows/forum/windows_10-performance/bug-crash-apcindexmismatch/c74ea155-4b07-49f3-8aee-bb4c0e69d188

    Espero que ajude. Atenciosamente, 


    Igor F. Kunrath

    Esse conteúdo é fornecido sem garantias de qualquer tipo, seja expressa ou implícita

    Technet Community Support

    Por favor, lembre-se de Marcar como Resposta as postagens que resolveram o seu problema. Essa é uma maneira comum de reconhecer aqueles que o ajudaram e fazer com que seja mais fácil para os outros visitantes encontrarem a resolução mais tarde.

    quarta-feira, 1 de agosto de 2018 17:18
    Moderador
  • THG InfoSec,

    Olha o Painel de Controle em Sistemas, o seu Windows 7 é versão 32 bits (x86) ou 64bits (x64)?

    No relatório de erros acima mostra que existe drivers 32 bits instalados e drivers 64 bits instalado.

    Se o seu Windows 7 for 64 bits (x64) tem que desinstalar todos os drives 32 bits (x86), terá que procurar a versão 64 bits desses drivers e instalar.

    Se o seu Windows for 32 bits (x86), normalmente não se consegue instalar drivers de 64 bits (x64) nele.

    Quando o sistema operacional é 64 bits (x64) e existe drivers 32 bits (x86) instalados, ou aplicativos 32 bits instalados, o Windows costuma apresentar problemas.


    Ana Mercedes Gauna | IT Consultant | Microsoft Partner: 5126593 | Skype: amgauna@hotmail.com | Site: http://www.anagauna.eti.br | http://www.amgauna.com.br | Blog: http://anagauna.wordpress.com | If you have been able to help, please check the answer as correct.


    • Editado Ana Gauna quarta-feira, 1 de agosto de 2018 23:22
    • Sugerido como Resposta IgorFKModerator quinta-feira, 2 de agosto de 2018 12:25
    • Marcado como Resposta IgorFKModerator terça-feira, 7 de agosto de 2018 12:26
    quarta-feira, 1 de agosto de 2018 23:21
  • Boa tarde,

    Por falta de retorno essa thread está encerrada.

    Se necessário favor abrir uma nova thread.

    Atenciosamente,

    Igor F. Kunrath

    Esse conteúdo é fornecido sem garantias de qualquer tipo, seja expressa ou implícita

    Technet Community Support

    Por favor, lembre-se de Marcar como Resposta as postagens que resolveram o seu problema. Essa é uma maneira comum de reconhecer aqueles que o ajudaram e fazer com que seja mais fácil para os outros visitantes encontrarem a resolução mais tarde.

    • Marcado como Resposta IgorFKModerator terça-feira, 7 de agosto de 2018 12:26
    terça-feira, 7 de agosto de 2018 12:26
    Moderador