[SOLVED] RiftEnabled BSOD - Windows 8.1 x64

[Mindputty]

Hi! This is my first post, and was hoping someone could help. This one might be tricky, though I'm not sure. About a month ago, I had a failed hard drive. Had it replaced and recovered my old data off it. Everything was working peachy keen. Today, was attempting to run an Oculus Rift demo in Direct Mode when my screen went black. I couldn't get it back, so was forced to do a hard reboot. This brought up the BSOD and I haven't been able to do anything but work in Safe Mode since.

Some things I have tried:

- uninstalling the oculus device drivers from the CLI
- Ran sfc /scannow which seemed to indicate a corruption on Amd64\CNBJ2530.DPB
- ran SFCFix to attempt to fix this, but didn't seem to work
- ran chkdsk /f but wouldn't fix - scheduled to fix on restart. Restarted and the scheduled "scan and repair" hanged at 10% each time.

Here is the zip file:
View attachment SysnativeFileCollectionApp.zip

Any help would be greatly appreciated!

Thank you!

EDIT:

The SFCFix said that there was 1 corruption, and that it fixed it, but the following screen said there were no errors found, producing this output:

SFCFix version 2.4.2.1 by niemiro.
Start time: 2015-02-07 02:35:58.824
Microsoft Windows 8.1 FAILED - amd64
Not using a script file.








AutoAnalysis::
FIXED: Performed DISM repair on file Amd64\CNBJ2530.DPB of version 6.3.9600.16384.
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-02-07 02:51:06.271
----------------------EOF-----------------------

 

[jcgriff2]

Hi -

Uninstall RiftEnabled - Driver Reference Table - RiftEnabler.sys

Uninstall Glary Utilities Startup Manager - Driver Reference Table - GUBootStartup.sys

Both were named probable cause in the dumps.

Use SysInternals AutoRuns from Microsoft TechNet if you wish to disable start-up items - https://technet.microsoft.com/en-us/sysinternals/bb963902

Also, I renamed the thread title for easier readability.

Regards. . .

jcgriff2

`

 

[Mindputty]

Hi jcgriff2,

I have fixed the problem - albeit temporarily, I believe. I didn't want to go ahead and delete the *.sys files - I was trying to find a way to uninstall instead, since they weren't coming up in the windows uninstaller. In searching for a way to do that, I did find a fix for my problem though - by changing the value of Start in the registry editor for riftenabler, from 1 (auto start) to 3 (disabled / only on request), I was able to boot up without any BSOD for the first time in 2 days. I found the solution here, at the bottom of the page.

Thanks for all of your help! I really appreciate it!

 

[jcgriff2]

Hi -

You are quite welcome, but you did all of the work! That's a great work-around you found!

For future info, if you need to disable a driver, you may want to use SysInternals AutoRuns from Microsoft TechNet -

https://technet.microsoft.com/en-us/sysinternals/bb963902

Un-checking the box next to the driver name ("drivers" tab) will disable it - same as changing startup in Regedit to a 3.

Thank you very much for posting back with the outcome - greatly appreciated.

Regards. . .

John

EDIT: Apologies for repeating myself about AutoRuns. I just noticed that I posted about it earlier in the thread.

JC

 

[Mindputty]

I am keeping Autoruns around as it seems like a very useful tool, although for me the RiftEnabler did not show up in Autoruns (the reason I needed to go directly to the registry was because of this). Thanks again!