FAQ

Windows instance faced bluescreen or freeze. What should I do?

(:Last updated)

 Note
The following procedures are for instances which are created from Windows 2012 R2 Official Image before 
“WindowsServer-2012R2_Standard_64_include-license_virtual-server_42” (Released on July 19 2018).
Cusotmer does not need to do the procedure to the instances which are created from Windows 2012 R2 Official image 
since “WindowsServer-2012R2_Standard_64_include-license_virtual-server_42”.

Windows instance which was created from official image may face bluescreen or freeze suddenly.
This event can be avoided by updating VirtIO/viostor/memory balloon driver if customer wants to keep existing instance.
There are 2 workarounds about VirtIO update. One is to required internet connectivity, and the other is not to require internet connectivity. Procedures are as below;

Workaround 1: VirtIO update to Instance which has internet connectivity

*) CAUTION: This workaround requires target instance has internet connection.

 

1. Download virtio-win-0.1.141 image to target instance

Download virtio-win-0.1.141 image to target instance from here.

 

2. Mount ISO file

Mount downloaded ISO file on DVD Drive

iso-file-mount-to-dvddrive

 

 

3. Update virtio driver

3-1. Click “Tool” on Server Manager, and click “Computer Management”

computer-management2

 

 

3-2. Click “Device Manager “on the left side of Computer Management

devicemanager

 

 

3-3. Expand “Network adapters” on the center of Computer Management. Confirm Red Hat VirtIO Ethernet Adapter is displayed. (it is displayed accordance with the number of logical network)

virtupdate-test

 

 

3-4. Right-click displayed Red Hat VirtIO Ethernet Adapter (first adapter if more than one), and click “Properties”.

red-hat-virtio-ethernet-adapter2

 

 

3-5. Click Driver tab on Properties

driver-tab

 

 

3-6. Confirm Driver version is not “63.74.104.14100”, and click “Update Driver...”

update-driver

 

 

3-7. Click “Browse my computer for driver software “

windows-update-wizard

 

 

3-8. Click “Browse...”, select DVD drive which ISO file mounts on, click “OK” and click “Next”

browserforfolder

 

 

3-9. Pop up “Would you like to install this device software?”, and click “Install”.

would-you-like-to-install-this-device-software

 

 

3-10. Close window after “Windows has successfully updated your device software” was displayed, confirm virtio version is updated to63.74.104.14100 and close window.

 

If driver version is not updated, please reboot instance and try updating again after update all Network Adapter and conduct [4. Eject mounted ISO(DVD drive)].

 

3-11. Update other un-updated Red Hat VirtIO Ethernet Adapter to “63.73.104.14100” version as well when a number of logical network are connected.

 

4.Update viostor driver
4-1.Click “Tool” on Server Manager, and click “Computer Management”.
virtioドライバのアップデート

 

4-2.Click “Device Manager “on the left side of Computer Management.

device-manager2

 

4-3.Expand “Storage controllers” on the center of Computer Management. Confirm Red Hat VirtIO SCSI Controller is displayed. (it is displayed accordance with the number of mounted disk).

 

 

4-4.Right-click displayed Red Hat VirtIO SCSI Controller (first adapter if more than one), and click “Properties”.

 

 

4-5.Update Red Hat VirtIO SCSI Controller by repeating the workaround 3-5~3-10 for Red Hat VirtIO SCSI Contoller.

 

 

4-6.Update other un-updated Red Hat VirtIO SCSI Controller to “63.73.104.14100” version as well when a number of disks are connected.

 

 

5.Update memory balloon driver

※Please inform us when you are using the official image "WindowsServer-2012R2_Standard_64_include-license_virtual-server_20".

5-1.Click “Tool” on Server Manager, and click “Computer Management”.
virtioドライバのアップデート

 

5-2.Click “Device Manager “on the left side of Computer Management.

device-manager2

 

5-3.Expand “System devices” on the center of Computer Management. Confirm VirtIO Balloon Driver is displayed.

 

 

5-4.Right-click displayed VirtIO Balloon Driver, and click “Properties”.

 

5-5.Update VirtIO Balloon Driver by repeating the workaround 3-5~3-10 for VirtIO Balloon Driver.

 

6. Eject mounted ISO(DVD drive)

Eject mounted ISO(DVD drive).

eject-mounted-iso

 

 

7. Reboot instance

Reboot target WindowsServer instance.

 

 

Workaround 2 : VirtIO update to Instance which doesn’t have internet connectivity

*) CAUTION: This workaround doesn’t need target instance has internet connection, however, charge of  Image Storage and Volume are occurred in accordance with these usage because the workaround requires to use Image Storage and Volume.

 

1. Download virtio-win-0.1.141 image to target instance

Download virtio-win-0.1.141 image to any computer which has internet connectivity from here

*) Customer should use the above linked image in Workaround 2 because the image is customized for using as Workaround 2 by referring the following virtio-win-0.1.141 image.

Reference: virtio-win-0.1.141 image

https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.141-1/virtio-win-0.1.141.iso

 

2. Upload virtio-win-0.1.141 image to Image Storage

Upload virtio-win-0.1.141 image to Image Storage in customer’s tenant from the computer which has internet connectivity.

 

3.Create volume from virtio-win-0.1.141 image
Select “Create Volume“ on Actions list of virtio-win-0.1.141 image, and create volume from virtio-win-0.1.141 image.

 

Name:Anything

Description:Anything(Option)

Use image as a source:virtio-win-0.1.141 (352MB) is selected automatically

Size(GB):15

Zone/Group:Same Zone/Group as target insntace which need to be updated virtio driver.

 

4. Attach the volume to target instance
Open Portal>Virtual Server>Volume, and select “Manage Attachments“ on Actions list.

“Attach to Instance“ is poped up, selecet target instance which need to be updated virtio driver and click "Attach Volume“.

 

5. Log in to target instance
Launch target Windows instance, and log in to the instance via VNC console etc.

 

6. Make the attached volume online

Make the volume attached on the instance available on Windows by configuring on OS.

Open Server Manager>Dashboard, click “Tool“ on upper right and click “ Computer Management“. Click “Disk Management“ on the left side of Computer Management.

Confrim 15GB disk with Offline is displayed on disk list on the lower center of Computer Management, right click around “ Disk X (X is number such as 1 and 2) Basic Offline“ and click “Online“.

Confrim disk named as “ virtio-0.1.141“ is displayed on disk list on the upper center of Computer Management.

computer-management_wo2

 

 

7. Update virtio driver

7-1. Click “Tool” on Server Manager, and click “Computer Management”

computer-management2

 

 

7-2. Click “Device Manager “on the left side of Computer Management

devicemanager

 

 

7-3. Expand “Network adapters” on the center of Computer Management. Confirm Red Hat VirtIO Ethernet Adapter is displayed. (it is displayed accordance with the number of logical network)

virtupdate-test

 

 

7-4. Right-click displayed Red Hat VirtIO Ethernet Adapter(first adapter if more than one), and click “Properties”.

red-hat-virtio-ethernet-adapter2

 

 

7-5. Click Driver tab on Properties

driver-tab

 

 

7-6.Confirm Driver version is not “63.74.104.14100”, and click “Update Driver...”

update-driver

 

 

7-7. Click “Browse my computer for driver software “

windows-update-wizard

 

 

7-8. Click “Browse...”, select mounted virtio-0.1.141 disk, click “OK” and click “Next”
7-9.  Pop up “Would you like to install this device software?”, and click “Install”.

would-you-like-to-install-this-device-software

 

 

7-10.  Close window after “Windows has successfully updated your device software” was displayed, confirm virtio version is updated to 63.73.104.14100 and close window.

 

If driver version is not updated, please reboot instance and try updating again after update all Network Adapter.

 

7-11. Update other un-updated Red Hat VirtIO Ethernet Adapter to “63.73.104.14100” version as well when a number of logical network are connected.

 

8.Update viostor driver
8-1.Click “Tool” on Server Manager, and click “Computer Management”.
virtioドライバのアップデート

 

8-2.Click “Device Manager “on the left side of Computer Management.

device-manager2

 

8-3.Expand “Storage controllers” on the center of Computer Management. Confirm Red Hat VirtIO SCSI Controller is displayed. (it is displayed accordance with the number of mounted disk).

 

 

8-4.Right-click displayed Red Hat VirtIO SCSI Controller (first adapter if more than one), and click “Properties”.

 

 

8-5.Update Red Hat VirtIO SCSI Controller by repeating the workaround 3-5~3-10 for Red Hat VirtIO SCSI Contoller.

 

 

8-6.Update other un-updated Red Hat VirtIO SCSI Controller to “63.73.104.14100” version as well when a number of disks are connected.

 

 

9.update memory balloon driver

※Please inform us when you are using the official image "WindowsServer-2012R2_Standard_64_include-license_virtual-server_20".

9-1.Click “Tool” on Server Manager, and click “Computer Management”.
virtioドライバのアップデート

 

9-2.Click “Device Manager “on the left side of Computer Management.

device-manager2

 

9-3.Expand “System devices” on the center of Computer Management. Confirm VirtIO Balloon Driver is displayed.

 

 

9-4.Right-click displayed VirtIO Balloon Driver, and click “Properties”.

 

9-5.Update VirtIO Balloon Driver by repeating the workaround 7-5~7-10 for VirtIO Balloon Driver.

 

10. Shut off Instance and detach Volume
Offline virtio-0.1.141 disk on Computer Management>Disk Management of display which was used in “6. Make the attached volume online”, and shut off Windows Server instance.

Select “Manage Attachments” on Actions list of virtio-win-0.1.141 volume.

“Manage Atttachments“ is poped up, and click “Detach volume“.

 

11. Reboot instance

Reboot target Windows Server instance.

 

 

Is this page helpful?

Yes No

We appreciate your cooperation in improving the site

Did this FAQ be helpful? If you have any comments, please let us know.

Thank you

Your feedback has been received.