ASRock.com Homepage
Forum Home Forum Home > Technical Support > HTPC&Gaming Barebone&Others
  New Posts New Posts RSS Feed - Vision 3D (Sandy Bridge) vs Windows 10
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

Vision 3D (Sandy Bridge) vs Windows 10

 Post Reply Post Reply Page  12>
Author
Message Reverse Sort Order
Worfje View Drop Down
Newbie
Newbie


Joined: 10 Jan 2021
Status: Offline
Points: 4
Post Options Post Options   Thanks (0) Thanks(0)   Quote Worfje Quote  Post ReplyReply Direct Link To This Post Topic: Vision 3D (Sandy Bridge) vs Windows 10
    Posted: 12 Jan 2021 at 2:29am
Connecting to the internet and getting the windows updates worked out fine. So, an Asrock Vision 3D 137B is Win10 compatible.
Back to Top
Worfje View Drop Down
Newbie
Newbie


Joined: 10 Jan 2021
Status: Offline
Points: 4
Post Options Post Options   Thanks (0) Thanks(0)   Quote Worfje Quote  Post ReplyReply Direct Link To This Post Posted: 10 Jan 2021 at 10:19pm
On another laptop I downloaded the NVidia windows 10 driver which supports the GT425M graphics card (352.84 from 2015.5.15) and via a USB stick I could use it on the Asrock Vision 3D. It installed fine.

The only thing left is connection to the internet and hoping Windows Update doesn't screw it up. ;-)
Back to Top
Worfje View Drop Down
Newbie
Newbie


Joined: 10 Jan 2021
Status: Offline
Points: 4
Post Options Post Options   Thanks (0) Thanks(0)   Quote Worfje Quote  Post ReplyReply Direct Link To This Post Posted: 10 Jan 2021 at 10:13pm
Sorry for bumping such an old thread, but I also wanted to install Windows 10 on a Asrock Vision 3D 137B and I might have made some progress (using your tips also, thanks!).

I can confirm that even the latest beta bios from Asrock (L1.52a from 2011-Apr-14) doesn't give you the possibility to disable Intel HD Graphics. There is no way to disable 'Quick Sync' in the BIOS.

When installing Windows 10 it would crash with BSOD. Safe mode with networking was not possible.

Installing without an internet connection was successful.
Back to Top
jj7879 View Drop Down
Newbie
Newbie


Joined: 03 Aug 2015
Status: Offline
Points: 6
Post Options Post Options   Thanks (0) Thanks(0)   Quote jj7879 Quote  Post ReplyReply Direct Link To This Post Posted: 25 Jan 2017 at 3:14am
Thanks parsec and wardog for explanations and suggestions!
 
@philk - Good to hear you got it working!
Back to Top
philk View Drop Down
Newbie
Newbie


Joined: 25 Jan 2017
Status: Offline
Points: 2
Post Options Post Options   Thanks (1) Thanks(1)   Quote philk Quote  Post ReplyReply Direct Link To This Post Posted: 25 Jan 2017 at 1:28am
Thank you!  After months of searching, and almost switching to Linux (to be fair, may still switch), disabling the QuickSync in the BIOS solved my problem.  Win10 worked on my ASRock Vision 3D HTPC (after doing a fix similar to what wardog suggested) at first, but after the anniversary update, even that fix (and many, many others) didn't work.  No matter what, Win10 tried to access the Intel graphics (even disabling it in the Device Manager didn't work).  Win10 would always try to load the Intel graphics, and the system would BSOD within a minute of loading.

The fix described above (disabling QuickSync in the BIOS, under the North Bridge settings) solved this. 

Thank you all!


Back to Top
wardog View Drop Down
Moderator Group
Moderator Group


Joined: 15 Jul 2015
Status: Offline
Points: 6447
Post Options Post Options   Thanks (1) Thanks(1)   Quote wardog Quote  Post ReplyReply Direct Link To This Post Posted: 24 Jan 2017 at 11:51am
Control Panel > System and Security > System > Advanced system settings > Hardware tab >
Device Installation Settings > No, let me choose what to do > and then check Never install driver software from Windows Update > then click on Save Changes

Simple as that.


Edited by wardog - 24 Jan 2017 at 11:52am
Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 4996
Post Options Post Options   Thanks (1) Thanks(1)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 24 Jan 2017 at 10:26am
You can also configure Windows 10 to not install every driver during the post installation configuration process, just don't choose the Win 10 Express settings.

Another easy workaround for Windows 10 installations, which I always do, is simply do not connect the PC to your network during the installation, or immediately afterwards. I always install my own drivers first on any Windows installation, I don't trust or want at least most of the drivers that MSoft will send my way.

Of course the problem with this PC is, since Lucid Virtu is one of its basic features, and is only supported in Windows 7, you don't have driver listings for other Windows versions. You could find most of the drivers and software on your own, but not all of them, more on that below.

Disable the IGP? Can you tell me how you enable it in your board's BIOS?

To this day, after all the years of Intel's integrated graphics, on all the desktop boards I've used and seen, there has never been an option that directly "disables" the IGP. The closest thing is the Share Memory option, but your BIOS does not have that option.

For the board in this PC, which only uses the IGP with Lucid, in the North Bridge Configuration screen in the BIOS, find the Quick Sync option, which is enabled by default. Set Quick Sync to Disabled to disable the IGP.

So, an option to disable the IGP is already in the BIOS.

As your PC's manual explains, the Quick Sync option (and Lucid Virtu) are only for use with Windows 7. This option must be disabled for any other OS (page 54.)

Apparently any problems caused by Win 10 installing a graphics driver for the Intel 3000 graphics in the three i5-2xxxM processors used in this PC, is because Intel does not have a Win 10 compatible driver for their 3000 graphics. For example, click on the Download Drivers link on this page, the specs for one of the processors used in the Vision 3D series:

https://ark.intel.com/products/53452/Intel-Core-i5-2450M-Processor-3M-Cache-up-to-3_10-GHz#@specifications

Back to Top
jj7879 View Drop Down
Newbie
Newbie


Joined: 03 Aug 2015
Status: Offline
Points: 6
Post Options Post Options   Thanks (0) Thanks(0)   Quote jj7879 Quote  Post ReplyReply Direct Link To This Post Posted: 24 Jan 2017 at 6:56am
For those interested, a workaround which seems to work..
 
You will have to be quick, before the igdkmd64.sys crashes though..
 
1. Install "Display Driver Uninstaller".
Start and select "Intel" and uninstall those.
 
2. To prevent Windows Update from reinstalling the Intel drivers, download ""Show or hide updates" troubleshooter package" (wushowhide.diagcab).
Start it and hide the Intel graphics driver.
 
I don't know for how long Windows will remember to not try to reinstall the Intel driver though..
 
So, again..Asrock please provide a bios update, where you can disable the igp.
Back to Top
jj7879 View Drop Down
Newbie
Newbie


Joined: 03 Aug 2015
Status: Offline
Points: 6
Post Options Post Options   Thanks (0) Thanks(0)   Quote jj7879 Quote  Post ReplyReply Direct Link To This Post Posted: 04 Aug 2016 at 11:23pm
Now also tested on Windows 10 "Anniversary Update" (v1607):
- Crashes after a few minutes.
 
That Bios option mentioned in the first post would be useful..
Back to Top
jgarner View Drop Down
Newbie
Newbie


Joined: 26 Dec 2015
Status: Offline
Points: 1
Post Options Post Options   Thanks (0) Thanks(0)   Quote jgarner Quote  Post ReplyReply Direct Link To This Post Posted: 26 Dec 2015 at 10:48pm
Hi,

I'd like to second this and ask for a Bios that at least addresses the issue of the Lucid Virtu crashing the whole system on Windows 10. Even if it isn't perfect and/or reduces some functionalities, at least you can use the computer...

Not impressed with how this top of the range expensive computer has just been completely disregarded...

Thanks,
Back to Top
 Post Reply Post Reply Page  12>
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.219 seconds.