BSOD - random ndis.sys error

I have 2 options that we could do, option one is a trial and error where you download the LAN drivers of the different rev versions and see which ones work and which one don't. Option two is opening the computer to check the rev version and download the right LAN drivers immediately, I would not recommend doing option two if you're inexperienced for reasons described below.


What you, or someone else, will need to do is the following with option two.
- Unplug the power supply (PSU)
- Turn off the PSU
- Start the pc, this removes most of the power inside the computer that was left
- Unplug any cables if needed to open the case
- Ground yourself
- Open the case
- Look at the motherboard, specifically the corner of the motherboard where the graphics card slots are located, to see the rev version and note it down or remember it.
- Close the case
- Plugin all cables
- Turn on the PSU
- Connect the PSU

This is a lot for just opening the case to go inside the computer, but there are risks involved here. When you start the pc whilst the PSU is turned off, a lot of power will be removed. Unfortunately, some power will still be present, particularly in the PSU and if you touch a wrong spot in the PSU you can hurt yourself and damage the PSU along with other components as well, with this I do not mean touching the case of the PSU but actually inside the PSU. On top of that, there's a risk that you may touch something that's quite vulnerable, particularly when you're inexperienced. Because everyone generates electricity and a low amount of it could already damage components, it is important that you are grounding yourself so the electricity flows into the earth at least minimizing the risk of damaging something.

The reason I am bringing it up is, with every different version of the rev. there's a change in the motherboard which is not significant enough for a whole new motherboard. I do not know if this somehow has any effect on the LAN, but you could download the LAN of any of the rev. versions for your motherboard and see how it goes. I doubt the wrong one will cause crashes, but there may be hiccups so it remains a trial and error.

If I was in your place, I would download them all and add 'rev x' where x is the rev number to the file name. Then I would install the latest rev first, 1.2, and work my way down if necessary.

As far as I know the Qualcomm driver is the current suspect.

You're welcome.

Let me know how things go.