Upgraded my PC; frequent BSoDs happen when PC sits

Hi ellison11.

Apparently all your BSODs are caused by Qualcomm Atheros Bandwidth Control
(c:\windows\system32\drivers\bflwfx64.sys).

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000094, fffff880062ead90, 0, 0}

*** WARNING: Unable to verify timestamp for bflwfx64.sys
*** ERROR: Module load completed but symbols could not be loaded for bflwfx64.sys
Probably caused by : bflwfx64.sys ( bflwfx64+8da6 )

Followup: MachineOwner
---------

Try to update the drivers (Killer™ e2200, Wireless-N 1102, 1103 and 1202) from Killer Gaming :: Support :: Driver Download Support. If needed, use the Killer™ Cleaner too.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.

Arc said:

Let us know the results.

I did as you said, but did not restart. I had to get up to grab something and when I came back I was greeted by another BSoD. I will update you and let you know if it happens again, having restarted now.

UPDATE: I didn't initially deselect all items from MSCONFIG, but I am trying that now. Will post results if BSoDs continue.

ellison11 said:

Arc said:

Let us know the results.

I tried all of these and I still receive a BSoD. Is it possible that a VPN service is causing this problem? I recently downloaded a paid VPN service from privateinternetaccess.

VPN services are troublesome, and killer is time consuming to troubleshoot, too.

If you supply the crash dump as per the BSOD posting instructions, we can see what happened there.

In the mean time, if you suspect VPN, uninstall it on a test basis? We have noticed a lot of issues caused by VPN only.