Fixing BSOD within Windows 2008 R2 after installing wrong VIOSTOR driver under Cloudstack

I needed to expand my Windows 2008 R2 server with extra HDD data. I had an ISO available with VIOSTOR drivers (Virtio Storage) and autodetected the drivers. How could I be so stupid.

after reboot: BSOD and BSOD and stupid as I was I was unable to go back to ‘last good known configuration’.

first of all I had to pick the drivers for Windows 2008 from this location: ISO/viostor/2k8/(R2 if you have it)/amd64/viostor.*

To stop the BSOD from happening:

Find the viostor drivers (probably):


Rename Windows/System32/drivers/viostor.sys to System32/drivers/disabled.viostor.sys.disabled;

Similarly renamed both Windows/DriverStore/FileRepository/viostor.inf_amd64_neutral_b5a4b523b42ac3b3/viostor.sysand Windows/DriverStore/FileRepository/viostor.inf_amd64_neutral_e322cb56cfbcc209/viostor.systo disabled.viostor.sys.disabled

Then reboot.

Please be noticed that it can cost you a NEW license if you add this driver. Your hardware can be changed and it could be that Microsoft does not allow your key anymore.

CFULLHDMA: Trying to understand Samba

The Conceptronic CFULLHDMA has an automatical way of finding Samba Shares, to make life easy for customers. The device is using ‘smbtree’ for this purpose. smbtree is a text based network browser.

As I do a lot of testings I suddenly did not get any samba share to see on the CFULLHDMA anymore. Bummer, a bug? let’s find out …

Normally I have 6!! Samba shared devices in my network. Suddenly, after rebooting a PC (XP) and a NAS I lost all Samba shares to bee seen in my CFULLHDMA, reboot, turn off / turn on .. nothing helped.

Analyzing I found out following:

the smbtree was generating an error on the CFULLHDMA.

session request to failed (Called name not present)
Data overflow in cli_receive_trans

the is my printserver, turning off that device only gave totally no output on running smbtree.

Using the same utility ‘smbtree’ on my Centos webserver (where is running at) generated the same error. For me it meant that it was not a bug on my CFULLHDMA but a general ‘error’ within my network. Checking my network neighbourhood at my XP machine revealed only 1 samba share: a rebooted nas device I had to reset to factory defaults and modified on IP level again (fixed) and where I changed its Samba Share name as well. The rest of my shares were even not seen at my XP system, Linux Server or CFULLHDMA.

To solve the issue I did following:

I rebooted my DSL modem (router / dns / dhcp device) &