Random BSOD & Lock Ups, code 0x000000f4

I think Kernel Memory Dumps will help more as I can't seem to find any lead.
Follow these instructions on how to change your dump files to Kernel Memory Dumps.

Dump Files - Configure Windows to Create on BSOD

Once your dump file creation has changed, reboot the computer and wait for another BSOD.
When a new BSOD has occurred go to this directory:
C:/Windows/memory.dmp

Copy that dump file to the desktop, then upload it to a program like OneDrive, once uploaded post the link in your next reply and I'll take a look.

Thedoctor44 said:

I think Kernel Memory Dumps will help more as I can't seem to find any lead.
Follow these instructions on how to change your dump files to Kernel Memory Dumps.

Dump Files - Configure Windows to Create on BSOD

Once your dump file creation has changed, reboot the computer and wait for another BSOD.
When a new BSOD has occurred go to this directory:
C:/Windows/memory.dmp

Copy that dump file to the desktop, then upload it to a program like OneDrive, once uploaded post the link in your next reply and I'll take a look.

I zipped it because it was 500MB's or something
https://onedrive.live.com/redir?resi...nt=file%2c.zip

You can't .zip it, the .dmp gets corrupt when you compress it.
Upload it unzipped.

Thedoctor44 said:

You can't .zip it, the .dmp gets corrupt when you compress it.
Upload it unzipped.

https://www.dropbox.com/s/mn1dhryxadew9nf/MEMORY.DMP
I hope you don't mind that I used dropbox for this very large file.

   Warning

Make sure you create a restore point.

System Restore Point - Create

What is your network card?

The dump files indicate a Xenos card but in your msinfo file it just says Killer e2200 PCI-E Gigabit Ethernet Controller.

You should be able to get an updated version here.

Driver Downloads | Qualcomm Atheros, Inc.

Thedoctor44 said:

   Warning

Make sure you create a restore point.

System Restore Point - Create

What is your network card?

The dump files indicate a Xenos card but in your msinfo file it just says Killer e2200 PCI-E Gigabit Ethernet Controller.

You should be able to get an updated version here.

Driver Downloads | Qualcomm Atheros, Inc.

I do got the Killer E2200 and I updated it just now.

Ok good, let me know how it goes.
I'm hoping that has fixed it.

Thedoctor44 said:

Ok good, let me know how it goes.
I'm hoping that has fixed it.

It didn't fix it
I just had a bluescreen after gaming for 2 weeks without having a blue screen, I also thought it fixed it but it didn't.. I received a text message from a friend and all of a sudden my pc closed all programs and it went into a blue screen, it's weird but I'm starting to think my iphone has something to do with it (sending out signals to my pc that makes it crash).
Here is another MEMORY.DMP file right after the latest BSOD
https://www.dropbox.com/s/mn1dhryxadew9nf/MEMORY.DMP

Well, it depends, is your phone plugged in?

Code:

BugCheck F4, {3, fffffa800eaad120, fffffa800eaad400, fffff80002b94270}

Probably caused by : csrss.exe

This bugcheck indicates that a critical process has been terminated or exited. The first parameter which I have marked in blue indicates a process has terminated, the process is marked in green.
csrss.exe is the Windows Subsystem that provides callable routines to the other subsystems to perform things like Display I/Os where needed etc.

It's very difficult to track down the cause of this, sometimes, not always it can be caused by memory leakages causing the memory resource pools to run dry.
Lets take a look.

Code:

	NonPagedPool Usage:    15192 (     60768 Kb)
	NonPagedPool Max:    3116636 (  12466544 Kb)

Nope, everything looks fine here.

It may well be another faulty HDD but given that you've already replaced it, it would look more like a faulty motherboard.
That being said, with nothing appearing for 2 weeks I have my doubts.

Can you upload all new files using the DM Log Collector.

Strangely enough, I had one last idea by dumping the raw stack, I found your Nvidia driver being blamed...

Code:

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for nvlddmkm.sys - 
 nvlddmkm+0xd7599

Lets take a look at the timestamp.

Code:

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f055000 fffff880`0fcb9000   nvlddmkm   (export symbols)       nvlddmkm.sys
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue May 20 00:08:44 2014 (537A8EFC)
    CheckSum:         00C1EA41
    ImageSize:        00C64000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

These latest versions have caused quite a few issues.
I recommend rolling back to an earlier version (Late last year).
These instructions are useful.

NVIDIA Drivers - Avoid Problems

Run a Disk Check to scan for errors

   Note

Afterwards go into an Elevated Command Prompt (Run as administrator) and type in sfc /scannow
If it finds errors reboot and run the scan two more times

Run SeaTools to see if your HDD or SSD is failing

Post back the results.

I used the SeaTools for Windows on my SSD and everything passed!
I will do a Disk Check when I reboot my pc and I'll let you know if there are some issues.
Here is the file I get using the DM Log Collector.