Solved BSOD system_service_exception on startup

So after packing with me my MSI GP70 2PF laptop running Win 8.1 it has suddenly stopped working, I used it the night before travelling without any issues and now I get BSOD system_service_exception after the BIOS loads but before I see any signs of Windows. I am able to boot into safe mode, but nothing else. I've tried most solutions I could find online like running sfc and chkdsk without any success, chkdsk even gave me BSOD while running it. I've also updated any and all drivers which weren't updated but I've been unable to update Killer ethernet e2200 drivers since it tells me to uninstall the old version first and when I try to uninstall it through the control panel it says that it has been uninstalled but it's still on the list and I still can't install the latest version.

Attached is the result of running dm_log_collector, hoping that I don't have to format everything.
View attachment 65679

Hi Josch,

Welcome to the 8forums.

The crashes are caused by a driver from Oculus VR Drift Display Mgr.
Please remove this driver as you likely do not have it anymore?
Or update it from here

axe0 said:

Hi Josch,

Welcome to the 8forums.

The crashes are caused by a driver from Oculus VR Drift Display Mgr.
Please remove this driver as you likely do not have it anymore?
Or update it from here

Code:

Oculus VR Rift Display Mgr    c:\windows\system32\drivers\riftenabler.sys

Code:

*** WARNING: Unable to verify timestamp for RiftEnabler.sys
*** ERROR: Module load completed but symbols could not be loaded for RiftEnabler.sys


2: kd> lmvm RiftEnabler
start             end                 module name
fffff800`8f3b1000 fffff800`8f3c1000   RiftEnabler T (no symbols)           
    Loaded symbol image file: RiftEnabler.sys
    Image path: \SystemRoot\system32\DRIVERS\RiftEnabler.sys
    Image name: [U]RiftEnabler.sys[/U]
    Timestamp:        [COLOR=#ff0000][U]Wed Dec 03 22:09:25 2014[/U][/COLOR] (547F7C05)
    CheckSum:         00018AEE
    ImageSize:        00010000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Click to expand...

Oh wow, thanks a lot for the quick response! Had uninstalled everything rift related since I read somewhere that someone else had problems with it, but after a quick search I found out I also had to manually delete riftenabler.sys which now has fixed my problems!

You're welcome