Author: coth
Subject: ven_1934&dev_1205 with P67 Fatali1y Pro
Posted: 11 Dec 2016 at 10:48pm
no. just replaced hdd. everything else was same. but something got broken after cloning. all drives were having code 31 and code 43 errors. and lots of different service has unexpectedly stopped errors. it was sector by sector close. so very strange. so i reinstalled windows over the current. ven_1934&dev_1205 popped up. google wasn't much helpful. only something related to asrock z170 series. but mine is p67.
then did a clean install. sadly have to spend few weeks now reinstalling apps.
anyway. deploying windows image into 100% different hardware would actually work in 99%. if you change motherboard/ram/cpu you won't have any problem, unless there are no specific required driver. ahci for example. so you usually switch to ide for a first boot.
but i was doing direct clone this time. something went wrong and didn't copy probably.
Edited by coth - 1 hour 13 minutes ago at 10:53pm
Subject: ven_1934&dev_1205 with P67 Fatali1y Pro
Posted: 11 Dec 2016 at 10:48pm
no. just replaced hdd. everything else was same. but something got broken after cloning. all drives were having code 31 and code 43 errors. and lots of different service has unexpectedly stopped errors. it was sector by sector close. so very strange. so i reinstalled windows over the current. ven_1934&dev_1205 popped up. google wasn't much helpful. only something related to asrock z170 series. but mine is p67.
then did a clean install. sadly have to spend few weeks now reinstalling apps.
anyway. deploying windows image into 100% different hardware would actually work in 99%. if you change motherboard/ram/cpu you won't have any problem, unless there are no specific required driver. ahci for example. so you usually switch to ide for a first boot.
but i was doing direct clone this time. something went wrong and didn't copy probably.
Edited by coth - 1 hour 13 minutes ago at 10:53pm