+ Reply to Thread
Results 2,971 to 2,980 of 11677
Thread: DIY eGPU experiences
-
26th February 2011, 06:53 AM #2971Newbie
- Join Date
- Feb 2011
- Posts
- 3
- Rep Power
- 0
Re: DIY ViDock Experiences
Can anybody tell me if a DIY ViDock will work on a Asus 5735z laptop.
-
26th February 2011, 07:09 AM #2972Banned
- Join Date
- Dec 2008
- Location
- YellowBrickRd.AU
- Posts
- 7,931
- Rep Power
- 0
Re: DIY ViDock Experiences
The Acer 5735Z guide/specs shows it has an expresscard slot AND 4500MHD graphics. Means you could do a Optimus setup for best performance with an internal LCD function by using a NVidia Fermi card. eg: GTS450 or GTX460 (recommended). There's a US$110AR GTX460-768MB.
-
26th February 2011, 07:27 PM #2973Notebook Enthusiast
- Join Date
- Jan 2009
- Location
- Calgary, AB
- Posts
- 14
- Rep Power
- 11
Re: DIY ViDock Experiences
Ok, pretty much at my wits end. I went out and bought a third video card today, an HD5770 to replace my NVidia card as it seems more people have been having trouble with NVidia cards.
On connecting after sleep my system tries to switch displays for a while then suddenly restarts.
On connecting prior to restart, dos recognizes my displays but prior to starting windows I get a blue screen.
(Below all done with intel card disabled in device manager)
Using bridged setup I get code 12.
36-bit on both or 36-bit dedicated 32-bit imp I get 8-bit colour, device manager doesn't show an error but display settings only sees my laptop screen.
32-bit everything or 36-bit dedicated, ignore imp shows 32-bit colour but otherwise the same as previous.
There was another user here that was also having trouble with a toshiba satellite, any chance these laptops are incompatible? Any chance that my P34H is faulty? Any other direction I should take before I just give up and return what I can?
Thanks.
-
26th February 2011, 08:00 PM #2974Banned
- Join Date
- Dec 2008
- Location
- YellowBrickRd.AU
- Posts
- 7,931
- Rep Power
- 0
Re: DIY ViDock Experiences
Win7 must have the primary video card enabled in Device Manager so do not disable it. If you have an error 12 then boot Setup 1.x, performing the following PCI compaction:
32-bit on HD5770, then chainload
36-bit on HD5770, then chainload.
32-bit on ALL, then chainload.
If you still see error 12 with the above, then "Save Diagnostics" on Setup 1.x, archive the \diag directory, upload and link here.
A faulty mini HDMI cable could be the cause of your problem. It would still allow the video card to be seen on the PCI BUS but it would BSOD when trying to use it due to the heftier data transmission.
-
26th February 2011, 08:54 PM #2975Notebook Enthusiast
- Join Date
- Jan 2009
- Location
- Calgary, AB
- Posts
- 14
- Rep Power
- 11
Re: DIY ViDock Experiences
Alright, I'm not getting code 12 on these, device manager seems to think my card is working but when I try to turn on the screen using display settings I get a blue screen. I have tried another hdmi cable with my last card (came with the card) with no changes but if the diagnostics don't point anything out I'll see if I can pick up another tomorrow as a last resort.
-
26th February 2011, 09:00 PM #2976Banned
- Join Date
- Dec 2008
- Location
- YellowBrickRd.AU
- Posts
- 7,931
- Rep Power
- 0
Re: DIY ViDock Experiences
I'm referring to the mini HDMI cable that connects your PE4L/PE4H and EC2C. If that is faulty then you'll have the symptoms as described. It's quite frustrating as it will allow the card to be detected but fail to allow it's use.
Your diags show you have plenty of space to accomodate your HD5770 so should see no error 12.
-
26th February 2011, 09:04 PM #2977Notebook Enthusiast
- Join Date
- Jan 2009
- Location
- Calgary, AB
- Posts
- 14
- Rep Power
- 11
-
27th February 2011, 02:58 AM #2978
Re: DIY ViDock Experiences
bad news guys
after i reinstall my OS and updated my BIOS to 1.35 dual IDA, no matter what i do, i am greeted by Code 43 error
i tried
-reinstalling my os without updates and with updated(SP1)
-reverted to Official 1.29 and 1.35 BIOS
-save dump using RW-Everything 1.4.7 and 1.4.9
-32bit compaction, 36bit compaction
-ignore onboard video card
-do the devcon.txt
-use 258.96, optimus 266.35, official 266.58, driver cd
-boot with vidock unplug and power off then sleep, power on, plug and resume
-remove the PCI BUS on devcon.txt
-unplug, replug, reseat the video card, hdmi cable and power connectors
-hotplug the videocard while on vidocksetup and in windows
-swap the end of the hdmi cable
i did everything i previously did before i had success and now the Code 43 error wont go away
i tested my vidock on a Toshiba A665 Core i3 to check if everything is working and so far it is working perfectly.
i am not sure if i saw this before but i suspect this has something to do why i am receiving Code 43 error

right now i am running 1.35 dual ida BIOS and i enabled some stuff on the BIOS to see if it will make any difference but so far it is not making any
i also did a save diagnose on DIYSetup just incase someone can decypher it
devcon.txt
10DE0E22.BIN
save diagnostic "before compaction"
save diagnostic "after compaction"
-
27th February 2011, 03:17 AM #2979Banned
- Join Date
- Dec 2008
- Location
- YellowBrickRd.AU
- Posts
- 7,931
- Rep Power
- 0
Re: DIY ViDock Experiences
Edit your startup.bat in Setup 1.x to contain the following so when you select "Automated startup via startup.bat" all the right steps are done in the correct order. ie:
If you get an error 43 when you chainload, then power off your DIY ViDock, do a Device Manager rescan so that the GTX460 will go away, sleep system, poweron DIY ViDock, resume and do a Device Manager scan.Code::: PCI ID of GTX460 is 10de:0e22. Countdown 60secs for user to attach a GTX460. :: Power on DIY ViDock then plug in mini HDMI in EC2C when prompted call waitvid 60 10de:0e22 :: Ensure have done a video cards->PCI Dump->Save (Win) to 'configure' the :: GTX460 so it doesn't hang Win7 startup or cause error 43. call pcicap load -d 10de:0e22 :: Ensure have done a 32-bit PCI compaction on the GTX460. This is saved :: to pci.bat. This ensures no error 12 occurs. call pci :: Chainload into Win7 call grub4dos w7
Failing that, use Driver Sweeper to remove all traces of previous NVidia video drivers and install the standard desktop driver. Your system has x3100 graphics so can't get the Optimus driver benefits anyway.
-
27th February 2011, 06:55 AM #2980Notebook Enthusiast
- Join Date
- Feb 2011
- Posts
- 25
- Rep Power
- 6
Re: DIY ViDock Experiences
Nando, what do you think about this PSU for my project (PE4H kit and a GTX 580)?
Thank you
Last edited by NewNet; 27th February 2011 at 06:57 AM. Reason: some modify



19Likes
LinkBack URL




Reply With Quote


2013 Alienware Notebooks revealed
11th June 2013, 12:46 PM in Alienware