Random BSOD & Lock Ups, code 0x000000f4

I just re-seated everything except my cpu, but could it be my mobo that's giving the BSOD/ lockups?

Yesteday I re-seated everything, today I managed to play for 3 hours but unfortunately without success.. It crashed 10min ago

Here you go!

Bump!
I recently found out when I get an incoming call on my mobile phone and it's near my desktop it just freezes instantly.. could it be my phone thats causing those crashes? Maybe it's sending out signals that messes up my pc.. really weird but it happened 3 times when I get a phone call next to my desktop, it just freezes..

If your phone isn't plugged in when you get the phone call then it's probably a coincidence.
I think it's a faulty SATA port but there's a possibility I'm wrong so lets try something else first.

also you said you've had quite a few bugchecks but you've not uploaded them. Check in C:/Windows/minidump for .dmp files, if there are any copy them to the desktop, compress them in a .zip folder then upload that.

Can you also 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

Why Driver Verifier:
It puts a stress on the drivers, and so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there are no points, make a System Restore Point Manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results.

andrew129260 said:

Do you have the phone plugged into your pc when it happens?

Nope it's not plugged in when it happens

Thedoctor44 said:

If your phone isn't plugged in when you get the phone call then it's probably a coincidence.
I think it's a faulty SATA port but there's a possibility I'm wrong so lets try something else first.

also you said you've had quite a few bugchecks but you've not uploaded them. Check in C:/Windows/minidump for .dmp files, if there are any copy them to the desktop, compress them in a .zip folder then upload that.

Can you also 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

Why Driver Verifier:
It puts a stress on the drivers, and so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there are no points, make a System Restore Point Manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results.

Did the Verifier and here are some dumpfiles