- #Logmein mirror driver install drivers
- #Logmein mirror driver install driver
- #Logmein mirror driver install Pc
- #Logmein mirror driver install windows 7
- #Logmein mirror driver install windows
#Logmein mirror driver install driver
Let me know if there are any Event Logs that you think would help find the root cause.Įdit 2: Checking the Event Log again, I have found that LogMeIn is still not uninstalled! Arghgghghghghhh! And, checking under Device Manager, there is still an entry for LogMeIn Mirror Driver under Display Adapters.Įdit 3: Using suggestions from, I tried to weed out the LogMeIn infestation. So, it probably would have worked in this fashion yesterday too. (maybe I should just leave it running.)Įdit: Restarted 4 times with bluescreens during the startup logo each time and then, on the fifth try, it made it all the way through to the desktop where everything seems to be working.
#Logmein mirror driver install Pc
Now I need to restart the PC again to check if it's going to fail. And the camera worked this time too (I arbitrarily made an order of plugging things in this time: camera USB, DK2 USB, DK2 HDMI). Running out of ideas, and recalling an unrelated comment about intermittent bluescreens, I decided to try restarting again (I hadn't tried that yet today.) and on the second time it succeeded. Installing the 0.4.2 runtime again, the computer bluescreened during the restart. So back into Safe Mode (to do the now very familiar "rename, restart, rename, uninstall, restart" routine). Unplugging the hardware (and unplugging other non-essential peripherals) did not work. The DK2 worked in Direct Mode but the camera didn't register for some reason, so I decided to restart - which brought on the bluescreen again.
#Logmein mirror driver install windows
This appeared to work, because the 0.4.2 runtime was successfully installed and Windows restarted without a bluescreen. I went ahead and uninstalled TightVPN and Teamviewer too. I don't have virtual monitors but did find a failed uninstall of LogMeIn (a Google search suggests this is a common problem) which left a few services lying around. Thanks Cybereality - this gave me a few ideas to go on, but was ultimately unsuccessful. I plan to try the 0.4.1 runtime this evening. Using the NVidia config, I rotated it and was able to use the 0.3.2 Oculus config utility (which recognised the DK2, and the config utility demo scene worked with basic head rotation tracking). I plugged it in without the runtime and the screen was recognised straight away as a 1080x1920 monitor (i.e. but still no DK2.Īt this point, it was getting late and I was desperate to finally experience the DK2 (having ordered on April 1st). So I had to repeat the Safe Mode renaming of RiftEnabler.sys, restart, rename, uninstall runtime, restart, all good. Installing the 0.4.2 runtime again and restarting straight away, I arrived straight back at the same bluescreen.
#Logmein mirror driver install drivers
Restarting into Windows, I reinstalled the NVidia drivers and restarted again. I hypothesised that the previous graphics card I had (an AMD HD5850) may have left some conflicting material behind, so using Display Driver Uninstaller (formerly Driver Sweeper from Guru3d) back in Safe Mode I swept all graphics card drivers from my system.
![logmein mirror driver install logmein mirror driver install](https://see-it-3d-webstore.co.uk/WebRoot/Store15/Shops/a4361948-297f-4391-846c-ce0f9585cdad/5E1E/438B/EAD1/11A1/913B/0A48/3535/E289/test.jpg)
![logmein mirror driver install logmein mirror driver install](https://i0.wp.com/amicasto.com/wp-content/uploads/2016/03/Capture1-1.png)
Now everything appeared to be back to normal.
![logmein mirror driver install logmein mirror driver install](https://support.zemax.com/hc/article_attachments/1500007660121/KA-01853_1_black_or_white_screen.png)
So, (now following others' advice, in Safe Mode again) I reinstalled the Oculus Runtime, renamed %windir%\system32\drivers\RiftEnabler.sys to RiftEnabler_bak.sys, restarted normally (now with the graphics card unrecognised), renamed RiftEnabler_bak.sys back to RiftEnabler.sys, ran the Oculus Runtime uninstaller (successfully), and restarted. Safe Mode worked, but the Oculus Runtime uninstaller did not complete successfully (due to missing components in Safe Mode) and the bluescreens still occurred. Windows Startup Repair failed to restore my PC. I have two screens connected to the 2 DVI ports at all times, and had connected the DK2 to the HDMI output (where it was immediately recognised as a 1080x1920 monitor prior to the restart).
#Logmein mirror driver install windows 7
I have an i5-750 with a GTX 760 running Windows 7 64-bit. I believe this is different to other reports because it is *not* a laptop with Optimus (switchable graphics). The bluescreen mentions "IRQL_LESS_THAN_OR_NOT_EQUAL" before quickly disappearing and restarting automatically. The computer then bluescreened early in the startup process and persisted to bluescreen even without the DK2 connected. I just received my DK2 (thanks for bringing Aus/NZ back up to speed!) and installed the 0.4.2 runtime, connected the headset, then restarted the PC (possibly the wrong order of operations in hindsight!).