Win7 Obtendo tela azul Crash, como verificar se o seu software ou hardware. (Log do WinDbg incluído)

Question

de repente minha antiga vitória de 7 64 bits começou a travar com a tela azul. Eu quero saber qual é o problema. analizei o arquivo mini dmp. e aqui está o resultado, infelizmente tenho problema para entender qual é o problema. aqui está o log:

ADDITIONAL_DEBUG_TEXT:  
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: nt

    FAULTING_MODULE: fffff80003651000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

    BUGCHECK_STR:  0x1a_41790

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff80003737d50 to fffff800036c6bc0

    STACK_TEXT:  
    fffff880'0ac34818 fffff800'03737d50 : 00000000'0000001a 00000000'00041790 fffffa80'01bbd6c0 00000000'0000ffff : nt+0x75bc0
    fffff880'0ac34820 00000000'0000001a : 00000000'00041790 fffffa80'01bbd6c0 00000000'0000ffff 00000000'00000000 : nt+0xe6d50
    fffff880'0ac34828 00000000'00041790 : fffffa80'01bbd6c0 00000000'0000ffff 00000000'00000000 00000000'00d11000 : 0x1a
    fffff880'0ac34830 fffffa80'01bbd6c0 : 00000000'0000ffff 00000000'00000000 00000000'00d11000 fffffa80'09e0a060 : 0x41790
    fffff880'0ac34838 00000000'0000ffff : 00000000'00000000 00000000'00d11000 fffffa80'09e0a060 00000000'00000000 : 0xfffffa80'01bbd6c0
    fffff880'0ac34840 00000000'00000000 : 00000000'00d11000 fffffa80'09e0a060 00000000'00000000 fffff680'00069ff8 : 0xffff


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    nt+75bc0
    fffff800'036c6bc0 48894c2408      mov     qword ptr [rsp+8],rcx

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt+75bc0

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  ntoskrnl.exe

    BUCKET_ID:  WRONG_SYMBOLS

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

Eu também tenho log sysdata.xml, mas é longo e eu não encontrei nenhuma informação de falha Como posso verificar se é problema de hardware ou driver?

link para o minidmp e o código xml: link

Por favor, dê uma olhada no resultado do memtest86 +:

    

Answer 1

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffffa83017b348b, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8000367d8b5, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

STACK_TEXT:
00 nt!KeBugCheckEx
01 nt! ?? ::FNODOBFM::'string'
02 nt!KiPageFault
03 nt!MiAgeWorkingSet
04 nt! ?? ::FNODOBFM::'string'
05 nt!MmWorkingSetManager
06 nt!KeBalanceSetManager
07 nt!PspSystemThreadStartup
08 nt!KxStartSystemThread

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+52b

BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+52b

PRIMARY_PROBLEM_CLASS:  X64_0x50_nt!MiAgeWorkingSet+52b

O memory_corruption at nt!MiAgeWorkingSet+52b parece uma falha relacionada à memória / RAM.

Você usa o F1 BIOS / UEFI:

BiosVersion = F1
BiosReleaseDate = 08/19/2014
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H81M-S2H

atualize para F2 e veja o que acontece. Se você ainda tiver travamentos, teste o RAM do EHC com o memtest86 + . Se ambos estiverem bem sozinhos, a mistura de um módulo RAM Transcend e Team-Elite pode causar o travamento.