0x7a and 0xF4 BSOD

When the BSOD will occur next time, upload the entire DM logs, not the dump only. I want to take another close look.

From the event logs, MSE failed to get updates. Then it tried to load, which kept pending for 44 seconds and the stop 0xF4 occurred.

Can you uninstall it and then download a fresh copy of MSE to install it?

Arc said:

From the event logs, MSE failed to get updates. Then it tried to load, which kept pending for 44 seconds and the stop 0xF4 occurred.

Can you uninstall it and then download a fresh copy of MSE to install it?

Got multiple 0xF4 and 1 0x7E, it's only happening while the gpu is plugged in, I removed the gpu and was able to log on fine. I also haven't had my computer freeze up on me yet with the gpu removed. Attachment 323658

Not sure if its driver related or its the motherboard, gpu or power supply...

TehEspada said:

Got multiple 0xF4 and 1 0x7E, it's only happening while the gpu is plugged in,

The 0x7E blames the disc.

Code:

BugCheck 1000007E, {ffffffffc0000006, fffff80002e5095f, fffff880072cb7e8, fffff880072cb050}

Probably caused by : hardware_disk

Followup: MachineOwner
---------

And so the 0xF4 is.

Code:

BugCheck F4, {3, fffffa8009014b30, fffffa8009014e10, fffff800021c5260}

----- ETW minidump data unavailable-----
Probably caused by : hardware_disk

Followup: MachineOwner
---------

Previously your 0x7A BSODs reported the same.

• You applied another disc.
• You changed the SATA cables.
• You tried different motherboard ports.
• Even you have done a clean reinstall.

Nothing changed the situation.

Either you have got both the HDDs bad (hard to believe) or the motherboard is corrupt.

We cannot test the mobo; but test the replacement HDD using WinDFT.

If the disk is tested to be good, and still the BSODs continue to occur, unfortunately we will have nothing left to blame but the motherboard.

Arc said:

TehEspada said:

Got multiple 0xF4 and 1 0x7E, it's only happening while the gpu is plugged in,

The 0x7E blames the disc.

Code:

BugCheck 1000007E, {ffffffffc0000006, fffff80002e5095f, fffff880072cb7e8, fffff880072cb050}

Probably caused by : hardware_disk

Followup: MachineOwner
---------

And so the 0xF4 is.

Code:

BugCheck F4, {3, fffffa8009014b30, fffffa8009014e10, fffff800021c5260}

----- ETW minidump data unavailable-----
Probably caused by : hardware_disk

Followup: MachineOwner
---------

Previously your 0x7A BSODs reported the same.

• You applied another disc.
• You changed the SATA cables.
• You tried different motherboard ports.
• Even you have done a clean reinstall.

Nothing changed the situation.

Either you have got both the HDDs bad (hard to believe) or the motherboard is corrupt.

We cannot test the mobo; but test the replacement HDD using WinDFT.

If the disk is tested to be good, and still the BSODs continue to occur, unfortunately we will have nothing left to blame but the motherboard.

The drive wouldn't show up in WinDFT but I did run a dskchk last night and it had no errors and I also ran a couple test with SeaTools and it had no errors, here is another 0xF4 Attachment 323760.

I'm gonna fill out a repair request with Gigabye now and we'll see what happens in a couple weeks when I have a working motherboard.

Edit:: I got my new SATA cable and installed it along with reinstalling my GPU, I've been able to log in no problem but I had a few more 0xF4 but I'm pretty sure they're from the wireless card I tried installing, Attachment 323792 I took out the card and went back to using my USB wireless stick and everything is running fine again, I'm gonna use the computer like normal and see if I encounter any problems.

If what you said is true then it is something unforeseen to me.

Frankly speaking, I have never seen stop 0xF4s causing for anything other than the storage environment (your BSOD dumps also reported in the same line). But you are talking about a PCI network card I think.

If the computer works stable without that card, definitely it will add something new to my debugging knowledge.