0x7a and 0xF4 BSOD

Could be a possible driver issue...

Enable driver verifier but only enable the options: Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Requests

Enable Driver Verifier to monitor the drivers.
Driver Verifier -Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

We use Driver Verifier as it puts a stress on the drivers, and so it makes the unstable drivers crash. This should flag the driver responsible in the dump file.
It

Driver Verifier will make the system laggy, this is normal so don't worry.

Before enabling DV, make sure that you have earlier System restore points made in your computer.

If there are no points, make a System Restore Point Manually

Post back the results.

I finally had another BSOD, this one was different too. I got 0xD1 then I did the driver verifier and it would give me 0xC4 every time I'd log into windows.

The computer didn't try to create a dump for the 0xD1 BSOD, it looked like the bsod screen froze up, I did get a picture though.

Attachment 320741
Attachment 320742

Attachment 320740

Code:

BugCheck C4, {f6, 230, fffffa800ef49b30, fffff88009d11809}

*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )

The Gigabyte Easy Saver - mobo power utility driver is causing issues, it's bloatware, remove all bloatware by ASUS as it can cause more problems than good, and in this case it has.

Intel Rapid Storage Technology is known to cause issues

Uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "Disc Drives" by clicking on the triangle in front of it.
5. Select one item under it, right click, uninstall.
6. Continue the process for all items under "Disc Drives"
7. Now restart the computer. At restart, windows will auto configure the appropriate system driver, msahci.sys.

Thedoctor44 said:

Code:

BugCheck C4, {f6, 230, fffffa800ef49b30, fffff88009d11809}

*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1809 )

The Gigabyte Easy Saver - mobo power utility driver is causing issues, it's bloatware, remove all bloatware by ASUS as it can cause more problems than good, and in this case it has.

Intel Rapid Storage Technology is known to cause issues

Uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "Disc Drives" by clicking on the triangle in front of it.
5. Select one item under it, right click, uninstall.
6. Continue the process for all items under "Disc Drives"
7. Now restart the computer. At restart, windows will auto configure the appropriate system driver, msahci.sys.

I uninstalled Intel Rapid Storage but I couldn't find the easy saver.
Attachment 320809

This is all that I have installed from Gigabyte.

I would uninstall Gigabyte OC_GURU II as overclocking should only be done manually in the BIOS.

Thedoctor44 said:

I would uninstall Gigabyte OC_GURU II as overclocking should only be done manually in the BIOS.

Just had another 0xF4 BSOD

Here is the dump
Attachment 321236

0xF4 contain very practical information in minidumps.

Post a screenshot of your drive using CrystalDiskInfo

crystalmark.info/software/CrystalDiskInfo/index-e.html

Switch to Kernel Memory Dumps.

Follow these instructions on how to change to Kernel Memory Dumps.

Dump Files - Configure Windows to Create on BSOD

Once changed wait for another BSOD, then upload the new dump file to a file sharing website like OneDrive.
The new dump file will be located in C:/Windows/memory.dmp.

Don't zip it up as it corrupts the dump file by compressing it.

However being the nosey person I am, I thought I'd take one last look at something.
Looking at your loaded modules I see this:

Code:

Unloaded modules:
fffff880`0d4a1000 fffff880`0d4c3000   ENG64.SYS
fffff880`0d29b000 fffff880`0d4a1000   EX64.SYS
fffff880`0d4c3000 fffff880`0d534000   spsys.sys
fffff880`01600000 fffff880`0160e000   crashdmp.sys
fffff880`019f3000 fffff880`019ff000   dump_pciidex
fffff880`017f4000 fffff880`017ff000   dump_msahci.
fffff880`015e0000 fffff880`015f3000   dump_dumpfve
fffff880`011c5000 fffff880`011ef000   cdrom.sys

Both are Norton 360 drivers which are notorious for causing issues, in fact I've seen Norton directly cause 0xF4 bugchecks in the past.

Uninstall Norton using the removal tool.

https://support.norton.com/sp/en/uk/...rProfile_en_us

Replace it with MSE and Malwarebytes.

Microsoft Security Essentials - Microsoft Windows

Malwarebytes | Free Anti-Malware & Internet Security Software

   Tip

Make sure you don't enable the free trial of malwarebytes pro, deselect the option when prompted.

Did this latest BSOD happen before or after Norton's removal?