Topic: BSOD when closing client (Read 485 times)
Get rid of Norton, stop avast Network Shield and avast Firewall, then try again.
It happened today again... this time with yet another client. I typed "stop" and the whole computer BSOD'd.
More details in the OP.
More details in the OP.
bump... anyone else have this issue?
In the past few days, I have experienced BSODs multiple times related to ndis.sys when closing clients. After searching, I believe that this issue is related to my network card (Qualcomm Atheros AR9565 802.11b/g/n Wi-Fi Adapter). I have tried two driver versions (10.0.0.212 and 222), and both have experienced BSODs.
The three clients which I have had BSODs on are Offerings From Ctlhulu, SIF and Kingcoin. This issue occurs intermittently and is preceded by me entering "stop" into the debug console and the window freezing.
Does anyone have information regarding this issue?
I am running Windows 8 on a HP laptop. On the computer I have Avast and an expired copy of Norton (which I couldn't be bothered to uninstall).
Every time it crashes, quite a few processes are running. Chrome, Notepad are the two that I remember I always had open when I typed "stop" and the BSOD happened.
The three clients which I have had BSODs on are Offerings From Ctlhulu, SIF and Kingcoin. This issue occurs intermittently and is preceded by me entering "stop" into the debug console and the window freezing.
Does anyone have information regarding this issue?
I am running Windows 8 on a HP laptop. On the computer I have Avast and an expired copy of Norton (which I couldn't be bothered to uninstall).
Every time it crashes, quite a few processes are running. Chrome, Notepad are the two that I remember I always had open when I typed "stop" and the BSOD happened.
Jump to: