yackass

I have indeed not have tried to limit the adapters speed to gen 1. Is it correct that you can limit it only with using diy setup or is there another way? And I am not familiar with TOLUD or with a way to check it. The thing is that I am not actually sure that I do get a bluescreen when I force windows to use the external display. But the psu acts very similarly to the blue screen I got before, so that its fans just stop.

Thanks for the suggestion Haniabaya. Your suggestion indeed kind of worked. I used the software to boot in to safemode and uninstall the nvidia drivers. Afterwards I disabled the 650m lane and successfully installed the 520 drivers. Did a restart after the driver installation and there was no error. In the HWmonitor I can actually see the 520 and even see the voltages and such. But the thing is, nothing is displayed on the external monitor. If I go to screen resolution and force it to display on the second monitor, my laptop screen goes blank and the psu stops spinning. I can't actually see what had happen, but I imagine that it is a blue screen of some sort. So yeah, everything seems to be installed correctly, there are no warnings displayed in the device manager. Could it be that I have currently connected the monitor through vga? I can test a dvi connection on monday. Or could it be intel hd graphics interfearing with it? not sure Cheers!

A quick update. I thought that the problem was that windows automatically keeps reinstalling the 650m driver and the blue screen during windows start up might be the conflict of the 520 and the 650m drivers. So what I did was first connect the beast normally, so in the device manager I would see the intel hd, a microsoft display adapter and the 650m. Then I went ahead and disabled the 650m and proceeded to install the 520 drivers. The installation was completed successfully and in the device manager the 520 was now shown. To prevent the automatic 650m driver installation during windows start-up, I went to gpedit.msc and enabled "Prevent installation of devices not described by other policy settings. I tested this before with just the 650m and it indeed stopped windows from automatically installing its drivers. But still no luck, after the restart I get a blue screen saying video_tdr_failure. So I think, that the problem isn't the 520 and 650m drivers preventing the startup. Since the 650m drivers were in theory atleast not present during this test. Cheers!

Hello! I also ordered the beast. I think that this is a really interesting idea and thought to try it out with a nvidia gt 520. Nothing too special. I had a 450W coolermaster psu lying around and gave it a go. Connected the PSU to the unit, and the mini pcie to the laptop. After powering my laptop on, the psu started working, red light on the beast started working and all good. Could boot up and everything. On the device manager it detected a microsoft display adaptor or something similar. So I went ahead and uninstalled everything from add/remove programs related to nvidia. (the laptop has a 650m). Disabled the 650m and downloaded drivers for the 520. The driver version was 355.98. So I started the driver installation, everything working well, it detected the 520 and finished the installation. Prompted me to restart my computer. Here is a screenshot after the installation. As you can see, it says 520 in the device manager now, this image is taken just before the restart. For some reason, I noticed that the 650m was enabled for some reason again, so I went ahead and disabled it again. Now after the restart, after windows has done loading, the PSU stops and after a short while I get a blue screen, saying video_tdr_failure (nvldd mkm.sys). And the computer wont start. It will start if I remove the beast though. So hopefully someone has any idea about what is going on. I think it might have something to do with the 650m drivers, I am not sure though since I did disable it. Computer specs: clevo w150er windows 8.1 64 bit 8 gb ram (2x4gb) intel i5- 3210m nvidia gt650m 230gb kingfast ssd 700 gb samsung hdd Cheers!