Problema no Windows/HD ou VGA mesmo?

[Eolaz]

PC:
ECS A890GXM-A

AMD Phenom II X4 965 @3.4GHz
1050TI GALAX EXOC (estou ciente do gargalo, vou fazer um upgrade na CPU em breve)
8GB Ram
Corsair CX500
WD10EZEX 1TB
W7 Pro x64

 

Pessoal, pela manhã eu fui ligar meu computador e pra minha surpresa ele não estava passando imagem para o monitor. Tirei minha 1050TI e botei o PC na oboard e ligou normal. Pesquisando o erro no Eventviewer vi que ele não conseguiu gerar o arquivo dump de memória, então fiz o memtest e como não acusou nada tentei por a VGA de novo. Ligou, logo de cara tentei fazer um stress test com o Furmark, não aguentou 2min e deu BSOD. Fui atrás e como
indicava algo relacionado a drive eu decidi atualizar o driver de vídeo. Atualizei e durou umas boas 12h... mas aí tive outra BSOD. De novo indicando "problema de drive", ativei o Driver Verifier do windows reiniciei máquina e logo tive outra BSOD, dessa vez indicando o driver "ntfs.sys". No total fiz esses testes descritos abaixo.

 

Testes já feitos:
MemTest - Tudo normal.
CHKDSK - Disse que corrigiu alguns erros, mas não resolveu o problema.
DLGDIAG Extended Test (software da WD) - Não apontou nenhum problema com o HD.
CCleaner e Malwarebytes - Só por desencarno de consciência.
Desinstalei e instalei todo o driver de vídeo.

Furmark - Após 2 minutos de stress test o PC reiniciou.

 

A questão é: Segundo tudo que pude testar aqui parece que é problema físico da GPU - ou seja, a solução seria fazer o RMA. Mas segundo TODOS os logs do WhoCrashed o problema não parece ser de hardware, mas sim de "driver". Mas problema de driver poderia deixar minha VGA não passar imagem pro monitor depois do PC ser reiniciado? Nem BIOS? Enfim, segue o log do WhoCrashed das BSOD que tive ao longo do dia. Há alguma chance de o problema não ser a VGA?

 

 

Citação

On Tue 03/07/2018 21:53:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070318-19094-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0xBE (0xFFFFF8A0011C2A38, 0x80000001D5127820, 0xFFFFF880089FE540, 0xE)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 03/07/2018 21:53:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0x9C332)
Bugcheck code: 0xBE (0xFFFFF8A0011C2A38, 0x80000001D5127820, 0xFFFFF880089FE540, 0xE)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver do Sistema de Arquivos NT
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Tue 03/07/2018 21:11:39 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070318-16848-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x18 (0x0, 0xFFFFFA800A2F2060, 0x2, 0xFFFFFA800A2F2FF7)
Error: REFERENCE_BY_POINTER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 03/07/2018 10:58:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070318-16738-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF7, 0x0, 0xFFFFF80002EC9CB6, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 25/05/2018 10:30:58 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052518-17238-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70DD0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.