virtualbox.org

MD wrote:Qualcomm Atheros AR8161 PCI-E Gigabit Ethernet Contro.

That would be a cabled connection, Mistake in getting the name?

Yes that was a mistake in sending wrong name by my colleague, sorry for the wrong information.

The adapter name is RealTek RTL8723AE Wireless LAN 802.11n PCI-E NIC

Looks more & more like a driver issue. Do you have the latest version installed in the end?
You could also try to downgrade to 4.2.12 like your colleague and see it improves anything.

you could try uninstalling VirtualBox and install 4.2.12 like you colleague has, which would isolate that as the cause

I have installed version similar to that of my colleague, but this too doesn't seem to work as I again got a BSoD with ndis.sys (NDIS 6.30 Driver) as the driver that caused the problem. Although this time I did not try using internet in Vbox but rather kept on working for some time normally on Fedora and ended up with crash! Later also tried to see whether I get BSoD upon using internet and yes I got another crash and this time problem was due to nwifi.sys (Native WIFI Miniport Driver). For both of the crashes am attaching the log file.

Might sound not so logical, can it be due to "802.11bgn" and "802.11n" adapter difference between my and my colleague's system respectively?

From all the things you've said so far, it seems like the Access Point of your company is not playing nice and causing an issue with your drivers.
Since the drivers are the only thing you have a control on, you should try that way first.

noteirak wrote:Looks more & more like a driver issue. Do you have the latest version installed in the end?

Well I had latest version of drivers earlier, after that I had refreshed my PC so I am back to older versions. I am now updating the drivers and will try to see the occurence of crash with downgraded version of Vbox and updated drivers! Will very soon get back on this.

noteirak wrote:Looks more & more like a driver issue. Do you have the latest version installed in the end?
You could also try to downgrade to 4.2.12 like your colleague and see it improves anything.

Well nothing seems to work for now atleast!!

Following is the summary of trials:
VBox version Drivers
4.2.16 updated
4.2.16 downgraded
4.2.12 downgraded
4.2.12 updated

All of which end up with a BSoD!!!!

Any suggestions??

MD wrote:VBox version Drivers

You mean Ralink NIC drviers, yes?

Yes.

For the drivers I mean that of my laptop.

Well I'm personally out of idea here...

Thanks for time buddy.

I hope somebody might have some idea about this particular issue.

It would be interesting to find somebody using Ralink NIC on windows Host, then we might get some idea about the issue.