BSOD: L1C62X64.sys, and ndis.sys. Tried updating, no luck!

[Coldkilla]

Greetings all.

My system:
1. Windows 7 64-bit.
2. 16GB Ram/770GTX @Stock/4670 @ Stock 3.4
3. Motherboard: ASRock H87M

I have gotten two BSOD's recently: L1C62X64.sys, and ndis.sys. The first (L1C62X64.sys) occurred, I did a little research and people had stated that it was a Atheros problem associated with my LAN drivers: http://www.asrock.com/mb/Intel/H87M/?cat=Download&os=Win764. I uninstalled my current version that came with the disc, restarted, and downloaded the latest version from their website (2.1.0.21). Installed, restarted - and a new BSOD occured: ndis.sys. As luck would have it, this too apparently is a network driver issue. After searching more on this, it says that I already have the latest driver installed.

What can I do to fix this? It's really preventing me from doing any gaming on this system. Thanks!

 

[Burpo]

Could possibly be a fault in the motherboard. Maybe try a network card or USB WiFi dongle & disable the on-board NIC..

 

[Coldkilla]

So something like this http://www.newegg.com/Product/Produc...-005-_-Product would fix it since it wouldn't be the motherboard connecting anymore?

 

[Ketchup]

High percentage of bad boards on Newegg. Strange. I have generally heard good things about Asrock.

From the sound of things, yes, a replacement LAN card should do the trick.

As a test, disable the Atheros chip and uninstall the software and see what happens.

Had you made any software changes around the time the issue started?

 

[Coldkilla]

Strangely this issue only occurs when flying a helicopter in the game ARMA3 in multiplayer. The game's terrain is 240km2 and I assume traveling at a higher rate of speed results in additional packets of information being sent to a server somewhere to keep my position constantly in check. When I'm running around on-foot in the game and the terrain isn't changing much, it's never BSOD'd. It's never done this outside of the game ether.

As far as software changes, a Java update was recently done but that's about it.

By disabling the chip, I disable my ability to do the only test in which has proven to cause the issue. I did pick up the network card though so I will be sure to report back once it arrives!

 

[Ketchup]

That is interesting indeed. Let us know how the new card goes.