Windows 10: Random BSOD on various actions - amifldrv64.sys and ntkrnlmp.exe

Hello, I'm Leon

Well, my problem is this:
Randomly, my computer (desktop) deadlocks or gets a Blue Screen and restarts. This happens randomly, while I'm playing, watching videos, doing nothing. My computer is 1 month old, has a GTX 970, i5-6500 and has been working properly until the last 2 weeks.

This (from what I've read) can be either an 1) energy problem, 2) memory problem, 3) temperature problem or 4) driver problems.

1) Since my computer needs around 400W of power and my current PSU is of 600W, I can rule out the energy problem.

2) I have run the windows memory check test and has reported 0 errors.

3) Usually the temperature of the computer won't go past 45ºC, even when I'm running Fallout 4, DOOM, ARK. So I can rule out also the temperature problem.

4) A program that came with my PC named MSI Live Update 6, usually updates my drivers. And everything goes fine. However, today, I have gotten a Blue Screen after trying to update the BIOS 2 times. Edit: Disabled Driver Verifier, updated BIOS with no problems.

The error messages presented are:
Driver_verifier_detected_violation (Driver Verifier has already been deactivated - was toggled for deadlocks)
Critical_Structure_Corruption
Page_Fault_In_Nonpaged_Area

The read I have on the Windows Event Viewer before this BIOS update was a Kernel-Power ID:41 error. And after the bios update BSOD, the error presented was still the same. So the BIOS problem has to be connected to the other BSOD (?)

This one can be found in only 1 minidump
FAILURE_BUCKET_ID: X64_AV_nt!KiPageFault+17f
BUCKET_ID: X64_AV_nt!KiPageFault+17f
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe


This one can be found in 2 minidumps
FAILURE_BUCKET_ID: X64_0xc4_81_VRF_amifldrv64+1681
BUCKET_ID: X64_0xc4_81_VRF_amifldrv64+1681MODULE_NAME: amifldrv64
IMAGE_NAME: amifldrv64.sys
MODULE_NAME: amifldrv64
IMAGE_NAME: amifldrv64.sys

EDIT v2.0: I found the file (supposedly causing the error) - amifldrv64.sys inside of LiveUpdate (the program used to update BIOS).



Leon

:)

 

Bad_Pool_Header BSOD once login to windows.

The driver that appears to be causing the crash is the amifldrv64.sys, which appears to be a component of a MSI Bios update utility:

BugCheck 19, {22, ffff8f81bff0c000, 0, 0}

*** WARNING: Unable to verify timestamp for amifldrv64.sys

*** ERROR: Module load completed but symbols could not be loaded for
amifldrv64.sys

Probably caused by : memory_corruption

The process that crashed was the SCEWIN_64.exe which appears to be a component of MSI Control Center.

PROCESS_NAME: SCEWIN_64.exe

That appears to be the similar to what was reported in the following topic:

Random Crashes / BSODs during boot (and during boot ONLY) - MiniDump files included

Try uninstalling, at least temporarily, the MSI software.

 

Another Bad Pool Header Question

*** WARNING: Unable to verify timestamp for amifldrv64.sys

*** ERROR: Module load completed but symbols could not be loaded for amifldrv64.sys<==
MSI Control center driver

Probably caused by : amifldrv64.sys ( amifldrv64+188c )

Followup: MachineOwner

---------

1: kd> !thread

THREAD ffffc00e6fc11080 Cid 0ca0.0c88 Teb: 000000000035a000 Win32Thread: ffffc00e6f9f7520 RUNNING on processor 1

IRP List:

ffffc00e6f9fac90: (0006,0118) Flags: 00060070 Mdl: 00000000

Not impersonating

GetUlongFromAddress: unable to read from fffff802176f9924

Owning Process ffffc00e6fba8800 Image: SCEWIN_64.exe

Attached Process N/A Image: N/A

fffff78000000000: Unable to get shared data

Loaded symbol image file: amifldrv64.sys

Image path: \??\C:\MSI\Smart Utilities\amifldrv64.sys

Image name: amifldrv64.sys

Browse all global symbols functions data

Timestamp: Wed Oct 07 12:50:32 2009 (4ACCC6D8)

Please update the driver above or remove MSI Control center.

 

This site does not support counterfeit installation which yours appears to be

Forum rules

Troubleshooting a counterfeit installation is useless as it is not known what has been modified on your system. A counterfeit installation may contain modified code which causes the system to behave in unexpected ways. For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.

Please install a genuine copy of Windows and activate it.

If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you once this install is confirmed .

We fully realize that everyone with an illegal installation is not always aware of this. Some have shops who work on their computer or who reinstall windows for them only to find out when they come here that it is illegal. They paid for a legal copy, but wound up with a counterfeit one. The ones who bought from eBay, (or other online sources or were ripped off).

We are always prepared to work with users once they are fully legal

You may also report this type of thing to Microsoft who have been known to assist victims in the past