Solved BSOD with Qualcomm WLAN(?) - BCCode d1, 4a

[YoYo155]

Ok it's failing on athrx.sys and afd.sys.
athrx.sys being your wireless adapter and afd.sys being Windows winsock which is to be attributed to your
adapter as well.

You currently have the latest version, so for now we will try to run the release prior to last if it will crash
on the the same driver again we will have to switch to a wired connection and removing the adapter
that way we can eliminate possibly faulty hardware.

Scroll down the page and download the prior to last version.

[LEFT][COLOR=black]Version:[/COLOR] [B]10.0.0.242
[/B][COLOR=black]Release: [/COLOR][B]2013-03-27[/B]
[/LEFT]

• Drivers for Atheros AR946x and Windows 7

 

[asura8]

Looks like a new error. I'll attach the logs.

I called a shop in the area, intending to see if they handled custom builds so that this might get solved by an expert (since I am now turning to desperation), and they suggested that it could be an unstable SSD. Would it be worth reinstalling on the mechanical drive, if the log shows that the error is not in the WLAN?

 

[asura8]

Didn't reinstall on the mechanical drive yet, since I thought of something less intensive to test.

You mentioned that the memtest86+ should not give an accurate result on the Z87 chipset. As such, and since I do not have another computer to test the RAM on, I decided to carry out the redneck RAM test of remove a stick of RAM, test for stability, and repeat with.

I've removed one stick of RAM so far, and the computer SEEMS to be stable. I'll give it a day or two to see if it crashes... but cross my fingers?

 

[YoYo155]

Hi sorry for the late reply.
The last bugcheck is a bit fishy so I was consulting with other members about it.
Do you still have the TDSSkiller log files? , if you do please zip and upload them.
They are saved in the same directory where you launched the software from.

 

[asura8]

I'll give a check on that once I return home and upload them if they are available. Personally, I'm holding hope that it is bad RAM. It is a far easier solution, I imagine!

 

[YoYo155]

It is .

 

[asura8]

Just an update, but TDSS does not appear to be making logs - perhaps it only does so if it detects something?

If I tell it to "Verify Digital Signatures" it fines two unsigned files that the default option is set to skip: IntcDAd, and Intel Capability Licensing Service Interface. I copy and pasted the Report into the text document below.

Edit: One more thing that it NOW occurs to me might have been a symptom that I didn't notice.

Previously, it was taking multiple attempts to boot up - the fan would start whriling up, it would stop, and then the power on cycle would begin again. I had previously associated this with a lower limit on fan speed, as I had seen something similar on the forums. I believed this was the case, because it would only do this when booting cold.

However, now that one (apparently) offending stick of RAM was removed, this effect is gone and it is starting cleanly every time. I'm heavily leaning towards the RAM being bad now. If the computer remains stable by the time I return from work, I'll likely reinstall the video card and see if it works without that stick of RAM too.

 

[YoYo155]

Thank you for the files and update .
It was suggested to be the culprit back in post #12 >.< , But it better late than never I always say.
How are things going now that the, presumably, bad module is no longer installed?

 

[asura8]

So. It appears to be stable with the video card now. I'm going to give it two days on that just to test this fact, and then attempt to test to see if switching the "bad" RAM to the good slot causes any problems. That should determine if it is bad RAM or a bad RAM slot.