BSOD after rendering in Sony Vegas Pro 12, starting pro 13

I rendered a video no less than 4 days ago without any problems, yet today when I try to render a video using Sony Vegas Pro 12, the windows on my screen will stop responding (I can still move my mouse around by this point) and the computer will crash (BSOD). This came as a complete surprise to me, since I've been using this program to render projects for quite some time now. I tried turning off GPU acceleration, but my computer would still come to a grinding halt before blue-screening. I even went to the lengths of installing Sony Vegas Pro 13, which turned out actually BSOD'ing my computer when starting the program up.

Any help would be greatly appreciated.

Code:

BugCheck F4, {3, fffffa800bb94b30, fffffa800bb94e10, fffff800035e3270}

This bugcheck indicates a critical process has terminated for some reason which causes the system to crash as this process is critical for the system's operations.

Code:

2: kd> !process fffffa800bb94b30
GetPointerFromAddress: unable to read from fffff80003515000
PROCESS fffffa800bb94b30
    SessionId: none  Cid: 0174    Peb: 7fffffda000  ParentCid: 0154
    DirBase: 321389000  ObjectTable: fffff8a00b4f9840  HandleCount: <Data Not Accessible>
    Image: csrss.exe

The process that crashed is csrss.exe (Client/Server Runtime Subsystem) which is the Windows Subsystem, although Windows was designed to support multiple subsystems, calling each subsystem to perform functions such as display I/O would result in duplicate functions which would inevitably reduce performance, therefore designers put a lot of basic functions within this primary subsystem to improve performance. This results in the Windows Subsystem (implemented within csrss.exe) is marked as a critical process even on servers where display I/O isn't needed so if its exited for any reason the system must bugcheck.

Now is mainly caused by disk I/O errors, so what is a disk I/O error?
Well when drive cannot perform basic operations such as read and write Windows cannot perform basic routines so the system fails resulting in a crash, this is usually the cause of a failing disk.

Code:

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

Code:

X64_0xF4_IOERR_IMAGE_csrss.exe

Code:

The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800b29f420, 0xfffffa800b29f700, 0xfffff8000357f270). A dump was saved in: C:\Windows\MEMORY.DMP

Later on if we struggle to find anything this dump will be useful.

Secondly, severe memory leakage can cause this problem as it can drain all the systems resources, normally non paged memory pools so the system cannot function and crashes.
It's caused by programs not freeing there pages of memory after they've finished using them so the pages are no longer in use by the application but they can't be used by anything else as they haven't been freed.

With all this said I suggest the best option is to test your drive.


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.

Seagate Results:
C: and D: Gyazo - 9c6588164e1adf59da984a58d95d215e.png

Chkdsk Results:
C: Gyazo - e5116d3f32c3f115eb022f5e33cfdcb4.png
D: Gyazo - d04c31399f1fad4d0b5b2fc99959f519.png

Daemon Tools was not installed and was not found on my computer.

Important note:

I was going to share the results of the sfc /scannow results, but at the scan stopped at 16% for around a minute, before a notification from Security Essentials popped up telling me that the shield was disabled (I can't remember the exact wording). The Command Prompt then stopped with the words, ""Windows Resource Protection could not perform the requested operations."

At that point, skype stopped responding, as did explorer.exe, and even Ctrl+Alt+Delete. I was forced at that point to manually shut down the computer (holding the power button down) and restarting.

Can you also run a long generic test as well please, I have my doubts.

I've updated my previous post with the results. I'll start the long generic test now.

Is your SSD firmware up to date?

Thedoctor44 said:

Is your SSD firmware up to date?

I haven't updated anything with regards to my SSD firmware, but then again I'm not sure how I'd go about checking to be sure.

I'll post the results of the long generic test when it's done.

Thanks for the very speedy replies gents

Whelp.

I just tried the long generic test, and two minutes in I got a BSOD. I was then prompted with a black screen saying, "Reboot and select proper boot device or insert media in selected boot device." I manually turned off the computer and then turned it on without experiencing the same message.

The minidump file has been attached for those interested.