BSOD booting Windows

[SylverX]

Since this morning, the first BSOD appeared on my computer:

I have this computer for 4 years and 3 months now
I installed this Windows 7 when I bought it, and I never had any BSOD until today (except once because the graphic drivers were way too old, but I fixed it)

This morning, I had this BSOD twice:
- first time, I booted the computer, I always wait a couple minute to let Windows boot properly (while I go grab a coffee) but when I came back it had BSOD:

WhoCrashed:
On Sun 02/06/2019 13:11:00 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060219-26379-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0xC2 (0x60, 0xFFFFF8800CA0F000, 0x0, 0x0)
Error: BAD_POOL_CALLER
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 current thread is making a bad pool request.
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.

The log event also talk about : "amifldrv64.sys" for this BSOD​

- i rebooted, everything working normally (used Nox emulator, started a video, no errors), so I decided to do reboot to be sure, and that's when the second BSOD appeared:

WhoCrashed
On Sun 02/06/2019 14:24:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060219-24991-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x19 (0x22, 0xFFFFFA8012836000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Only ntoskrnl.exe for this BSOD​

The only program I installed recently was Final Fantasy XIV a few days ago.

Any ideas what/where to look ?

[trying to create a "DM Log Collector" but it won't create any files]
[used SF Diagnostic Toll instead]

 

[johnhoh]

1) it could be bad ram or a bad motherboard. After 4 years, it can happen
2) but hopefully its a bad driver. You can use this nirsoft tool to view and sort all your drivers by date. If you are lucky, one of the new ones will stand out and you can replace it with an older version.
DriverView: Loaded Windows Drivers List
3) or try using Driver Verifier, a windows tool built to analyze problems like yours
Check for Bad Drivers in Windows with Driver Verifier - Make Tech Easier

 

[SylverX]

Thx for the quick reply

for 2), I don't understand what you mean by "stand out", I hope you are not talking about red line... cause I seem to have a LOT of them

for 3), the warning saying I could be stuck in a BSOD loop is kinda scaring me, as I have some data I'm gonna need to save in case I need to install Windows from scratch

 

[johnhoh]

By stand out I just meant maybe one driver will show as having been updated 4 days ago or something, right when your problem started.

As it says in the link, if you CANNOT get into safe mode on your machine, then don't use driver verifier unless you have a system backup. But if you CAN get into safe mode, you're fine. You can always disable it in safe mode.

Here's more on how to use it. You will want to read everything on the links I have posted so you can become knowledgeable about the details.
How to Find Out Which Driver Cause Windows to Crash with a Blue Screen using Driver Verifier. - wintips.org - Windows Tips & How-tos

 

[SylverX]

Thx, knowing I can disable it in safe mode is great

Looking at 2), the last driver was modified a month ago (problem only started this morning)

Anyway, I was gonna make a fresh install on the new SSD anyway, so I'll backup my files, try the Verifier way (this SSD/Windows is supposed to stay for my wife) and in worst case I'll have to install not 1 but 2 windows (I keep "my" windows and my wife's separated... in case she kills it and I still want a "game's night)

I'll post updates when it's done