Os dumps mostram problemas de RAM (falha no nt! NtFreeVirtualMemory e nt! MiResolveDemandZeroFault):
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa86017ecff0, 2, 1, fffff80002ce835f}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa86017ecff0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ce835f, address which referenced memory
Debugging Details:
------------------
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiReplenishPageSlist+100
fffff800'02ce835f f00fba6b1000 lock bts dword ptr [rbx+10h],0
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: firefox.exe
STACK_TEXT:
nt!KeBugCheckEx
nt!KiBugCheckDispatch
nt!KiPageFault
nt!MiReplenishPageSlist
nt!MiRemoveAnyPage
nt!MiResolveDemandZeroFault
nt!MmAccessFault
nt!KiPageFault
0x0
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MiReplenishPageSlist+100
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
contains the address of the PFN for the corrupted page table page.
On a 32 bit OS, parameter 2 contains a pointer to the number of used
PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80047ebe10
Arg3: 000000000000ffff
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41790
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: dllhost.exe
STACK_TEXT:
nt!KeBugCheckEx
nt! ?? ::FNODOBFM::'string'
nt!NtFreeVirtualMemory
nt!KiSystemServiceCopyEnd
nt!KiServiceLinkage
nt!PspExitThread
nt!PspTerminateThreadByPointer
nt!NtTerminateThread
nt!KiSystemServiceCopyEnd
0x0
FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6
Faça o download do memtest86 + , grave um novo CD inicializável (use um CD-RW, se possível) da ISO ( baixar e usar ImgBurn para fazer isso ou clique duas vezes no ISO no Windows 7), reinicie o seu PC e escaneie sua RAM 4-5 horas para erros. Se o memtest86 + detectar erros, teste cada módulo individualmente e substitua a RAM defeituosa.
Se o memtest não informar nenhum erro, faça o download CPU-Z , procure na memória e no SPD e verifique se a velocidade atual da RAM e as temporizações correspondem aos valores que você vê na guia SPD. Se a sua RAM for executada em CR (Command Rate) 1T, mude o valor para 2T no BIOS.