0x7a and 0xF4 BSOD

[TehEspada]

I've been getting frequent 0x7a and 0xF4 blue screens for a while now and for the past couple days my computer would just freeze up and I would have to force a shutdown with the power button.


Any help is greatly appreciated.

 

[Thedoctor44]

Next time upload the .dmp files directly to Seven Forums not to a file sharing site unless specified otherwise.

0xF4 bugchecks indicate a critical process for Windows to function has been terminated causing the system to crash.

0x7A bugchecks means requested Kernel data cannot be read back into memory from disk.

Both can be caused by disk errors and it looks like your drive is failing.
Especially when this is the error code for the 0x7A bugcheck.

[COLOR="Red"]ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware[/COLOR]

Run SeaTools to see if your HDD or SSD is failing

Post back the test results.

 

[TehEspada]

Next time upload the .dmp files directly to Seven Forums not to a file sharing site unless specified otherwise.

0xF4 bugchecks indicate a critical process for Windows to function has been terminated causing the system to crash.

0x7A bugchecks means requested Kernel data cannot be read back into memory from disk.

Both can be caused by disk errors and it looks like your drive is failing.
Especially when this is the error code for the 0x7A bugcheck.

[COLOR=Red]ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware[/COLOR]

Run SeaTools to see if your HDD or SSD is failing

Post back the test results.

I've ran numerous hard drive test before, windows disk check and western digital data life guard and both came back fine, I'll still run a test with SeaTools to be safe and get back to you.

 

[TehEspada]

Next time upload the .dmp files directly to Seven Forums not to a file sharing site unless specified otherwise.

0xF4 bugchecks indicate a critical process for Windows to function has been terminated causing the system to crash.

0x7A bugchecks means requested Kernel data cannot be read back into memory from disk.

Both can be caused by disk errors and it looks like your drive is failing.
Especially when this is the error code for the 0x7A bugcheck.

[COLOR=Red]ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware[/COLOR]

Run SeaTools to see if your HDD or SSD is failing

Post back the test results.

Firmware Revision: 01.01A01
SMART - Pass 5/27/2014 4:37:02 AM
Short Generic - Started 5/27/2014 4:37:17 AM
Short Generic - Pass 5/27/2014 4:38:51 AM
Long Generic - Started 5/27/2014 4:40:57 AM
Long Generic - Pass 5/27/2014 7:15:15 AM
Short DST - Started 5/27/2014 7:16:03 AM
Short DST - Pass 5/27/2014 7:18:05 AM

All the test passed.

Anything else you think it could be?

 

[Thedoctor44]

Change to Kernel Memory Dumps and post the .dmp file created to a file sharing site like OneDrive as the file is too large to upload directly here.
It's located in C:/Windows/memory.dmp

To change the dump files follow these instructions.

 

[TehEspada]

Change to Kernel Memory Dumps and post the .dmp file created to a file sharing site like OneDrive as the file is too large to upload directly here.
It's located in C:/Windows/memory.dmp

To change the dump files follow these instructions.

I went into my settings and kernel memory dump was already selected but I couldn't find any kernel dumps.

 

[Thedoctor44]

Just wait for another BSOD then upload the dump file.

 

[TehEspada]

Just wait for another BSOD then upload the dump file.

I went to the store a little bit ago and locked my computer and when I came back I had this error message.
View attachment 319574
0x00000000610759EC - 0x00000000610759EC - 0xc00000e Pictures had to be compressed so its hard to see, those are the codes for the first picture.

View attachment 319575
0x0000000075De43cf - 0x0000000075DE43CF - 0xc000000e

And after I logged in all my programs were closed and if I tried to open anything I got this message.

View attachment 319576

After I restarted the computer everything went back to normal, this happen once before but the computer wasn't locked then.

Does this have anything to do with the BSOD?

I ran virus scans, Malwarebytes scans and multiple stress test and memory test and it all looks fine.

 

[Thedoctor44]

When you say you ran a memory test was it Memtest86?
That is the only reliable memory testing software, all others are inferior and can give false reports.

Memtest86 will test your RAM

   Information

Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing

 

[TehEspada]

When you say you ran a memory test was it Memtest86?
That is the only reliable memory testing software, all others are inferior and can give false reports.

Memtest86 will test your RAM

   Information

Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing

It had no errors on memtest, I haven't had another blue screen since I started this thread but my computer has frozen up at random about 3 times.

I reinstalled and updated all of my drivers and I removed on/off charge as someone said might help on a different forum.

 

[Thedoctor44]

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.

 

[TehEspada]

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.

View attachment 320741
View attachment 320742

View attachment 320740

 

[Thedoctor44]

BugCheck [COLOR="Red"]C4[/COLOR], {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 : [COLOR="red"]gdrv.sys[/COLOR] ( 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.

 

[TehEspada]

BugCheck [COLOR=Red]C4[/COLOR], {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 : [COLOR=red]gdrv.sys[/COLOR] ( 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.
View attachment 320809

This is all that I have installed from Gigabyte.

 

[Thedoctor44]

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

 

[TehEspada]

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
View attachment 321236

 

[Thedoctor44]

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.

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

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:

Unloaded modules:
fffff880`0d4a1000 fffff880`0d4c3000   [COLOR="red"]ENG64.SYS[/COLOR]
fffff880`0d29b000 fffff880`0d4a1000   [COLOR="Red"]EX64.SYS[/COLOR]
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/home/current/solutions/kb20080710133834EN_EndUserProfile_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.

 

[TehEspada]

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.

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

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:

Unloaded modules:
fffff880`0d4a1000 fffff880`0d4c3000   [COLOR=red]ENG64.SYS[/COLOR]
fffff880`0d29b000 fffff880`0d4a1000   [COLOR=Red]EX64.SYS[/COLOR]
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/home/current/solutions/kb20080710133834EN_EndUserProfile_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.

The system was already setup to create a kernel memory dump but it was still creating mini dumps instead.
View attachment 321246

Here is the drive screenshot.
View attachment 321247

And another 0xF4 BSOD that happen shortly after the first one.
View attachment 321248

Edit: As I was posting this my programs started to slowly shut down one by one before my computer restarted itself, it did the same thing before the last BSOD happen but this time it just restarted with no BSOD.

Norton has also been uninstalled and MSE put in it place.

 

[Thedoctor44]

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

 

[Arc]

Click on the button below ....



It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Dont edit or alter the zip ... upload it as it is.