Solved Random BSOD while surfing on Chrome

[Xiansations]

Hi people, this is my first time posting here.

For the past 2 days, I been surfing the web and watching Youtube videos and suddenly I get BSOD out of nowhere. It only started 2 days ago and I just got one BSOD of the same issue about 1 hours ago.

I have downloaded BlueScreenView and paste the following text it provided me below. I have also attached the dmp file in this post.

My desktop is custom built and it is fairly new so I think it should not be the issue with the hardware.

The only driver I may have installed the past few day would be my brother's flash drive.

Kindly help me with this issue

==================================================
Dump File : 050315-120869-01.dmp
Crash Time : 5/3/2015 10:21:56 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa80`65f75138
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`02ec3a23
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+72a40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18798 (win7sp1_gdr.150316-1654)
Processor : x64
Crash Address : ntoskrnl.exe+72a40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\050315-120869-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 340,112
Dump File Time : 5/3/2015 10:24:56 PM
==================================================

 

[Arc]

Click on button below ....

​

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.

http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html​

 

[Xiansations]

Hi Arc,

I've already done that and it is attached in my post.

 

[Arc]

That zip does not contain all the necessary information.

OK, you try SF Diag tool and upload the resulting zip with your reply post.

 

[Xiansations]

Okay Arc I have uploaded the file as you request.

 

[Arc]

If further data is required, upload it with your reply post only, dont alter the original post.

The crash dump blames Qualcomm Atheros Bandwidth Control, a component of Killer Network Manager. It is set to auto start with windows.

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.

BTW, you have Daemon Tools there. 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.

Report us for any further BSOD after doing these.
________________________________________________

BugCheck A, {fffffa8065f75138, 2, 1, fffff80002ec3a23}

*** 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+3495 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa8065f75138, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ec3a23, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310a100
GetUlongFromAddress: unable to read from fffff8000310a1c0
 fffffa8065f75138 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeAcquireSpinLockAtDpcLevel+43
fffff800`02ec3a23 f0480fba2900    lock bts qword ptr [rcx],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE:  FFFFF80000BA0FB0

TRAP_FRAME:  fffff80000ba0550 -- (.trap 0xfffff80000ba0550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8008e5d008 rbx=0000000000000000 rcx=fffffa8065f75138
rdx=000000000ba23000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ec3a23 rsp=fffff80000ba06e0 rbp=fffff8800725178e
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000052
r11=fffffa8008e61968 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KeAcquireSpinLockAtDpcLevel+0x43:
fffff800`02ec3a23 f0480fba2900    lock bts qword ptr [rcx],0 ds:fffffa80`65f75138=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002eccfe9 to fffff80002ecda40

STACK_TEXT:  
fffff800`00ba0408 fffff800`02eccfe9 : 00000000`0000000a fffffa80`65f75138 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00ba0410 fffff800`02ecbc60 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`0304de80 : nt!KiBugCheckDispatch+0x69
fffff800`00ba0550 fffff800`02ec3a23 : fffffa80`08e5d278 fffffa80`08ac4db0 00000000`00000002 fffff880`072513c8 : nt!KiPageFault+0x260
fffff800`00ba06e0 fffff880`07251495 : fffffa80`65f75138 fffff880`0725178e 00000000`0ba22fff fffff880`0725159b : nt!KeAcquireSpinLockAtDpcLevel+0x43
fffff800`00ba0730 fffffa80`65f75138 : fffff880`0725178e 00000000`0ba22fff fffff880`0725159b fffff800`0304de80 : bflwfx64+0x3495
fffff800`00ba0738 fffff880`0725178e : 00000000`0ba22fff fffff880`0725159b fffff800`0304de80 fffffa80`0a4b7980 : 0xfffffa80`65f75138
fffff800`00ba0740 00000000`0ba22fff : fffff880`0725159b fffff800`0304de80 fffffa80`0a4b7980 00000000`00000000 : bflwfx64+0x378e
fffff800`00ba0748 fffff880`0725159b : fffff800`0304de80 fffffa80`0a4b7980 00000000`00000000 fffff880`072515f2 : 0xba22fff
fffff800`00ba0750 fffff800`0304de80 : fffffa80`0a4b7980 00000000`00000000 fffff880`072515f2 fffffa80`08e618c0 : bflwfx64+0x359b
fffff800`00ba0758 fffffa80`0a4b7980 : 00000000`00000000 fffff880`072515f2 fffffa80`08e618c0 00000000`00000000 : nt!KiInitialPCR+0x180
fffff800`00ba0760 00000000`00000000 : fffff880`072515f2 fffffa80`08e618c0 00000000`00000000 00000000`00000000 : 0xfffffa80`0a4b7980


STACK_COMMAND:  kb

FOLLOWUP_IP: 
bflwfx64+3495
fffff880`07251495 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  bflwfx64+3495

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: bflwfx64

IMAGE_NAME:  bflwfx64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5346bb7f

FAILURE_BUCKET_ID:  X64_0xA_bflwfx64+3495

BUCKET_ID:  X64_0xA_bflwfx64+3495

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_bflwfx64+3495

FAILURE_ID_HASH:  {49686ff4-420b-9c51-4214-be3ee252a24b}

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

0: kd> lmvm bflwfx64
start             end                 module name
fffff880`0724e000 fffff880`074a5000   bflwfx64 T (no symbols)           
    Loaded symbol image file: bflwfx64.sys
    Image path: \SystemRoot\system32\DRIVERS\bflwfx64.sys
    Image name: bflwfx64.sys
    Timestamp:        Thu Apr 10 21:10:47 2014 (5346BB7F)
    CheckSum:         00021891
    ImageSize:        00257000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Xiansations]

Okay thanks a lot Arc i'll give it a try tomorrrow and let you know the update

 

[Xiansations]

It's been a week and no BSOD since then. Thanks Arc

 

[Arc]

Nice.

Let us know for any further issue.