BSOD every morning when I show up to work. - New i7 4770k Custom Build

[shortbus123]

For the past 3 mornings I have come into the office to see a lovely BSOD.
Seems to be fine during the day.
This is a new computer build that I just finished last week.
processor is i7 4770k

Originally I thought it was because I was trying to slightly overclock to 4.0 ghz but I disabled that and it still happens.

and motherboard is
ASRock Fatal1ty Z87 Killer LGA 1150 Intel Z87 HDMI SATA 6Gb/s USB 3.0 ATX Intel Gaming Motherboard

Not sure what else people need but happy to provide any info. Thanks.

 

[shortbus123]

Blah it just happened again and I was not even using the computer for anything.

 

[Arc]

Hi shortbus123.

Download and install The driver to Killer e2200 from Driver Downloads | Qualcomm Atheros, Inc.

http://www.sevenforums.com/tutorials/97061-driver-install-device-manager.html

Let us know the result.

EDIT: Also 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.

_________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000094, fffff88009c55c20, 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+8a16 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000094, The exception code that was not handled
Arg2: fffff88009c55c20, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


OVERLAPPED_MODULE: Address regions for 'spsys' and 'magdrvamd64.' overlap

EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

FAULTING_IP: 
+208d160
fffff880`09c55c20 486bc509        imul    rax,rbp,9

EXCEPTION_PARAMETER2:  fffffa8009db3640

BUGCHECK_STR:  0x1E_c0000094

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  uTorrent.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffffa800a07b2b8 to fffff880040aaa16

CONTEXT:  fffff88009c563a0 -- (.cxr 0xfffff88009c563a0;r)
rax=0000000000024e8a rbx=fffffa800a07b2b8 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa800a07b2b8
rip=fffff880040aaa16 rsp=fffff88009c56d80 rbp=0000000000000000
 r8=fffffa800a07b300  r9=0000000000000000 r10=fffffa8009db3640
r11=00000004aaaa0483 r12=0000000000024e8a r13=fffffa800a119c38
r14=0000000000000000 r15=fffff880018de110
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
bflwfx64+0x8a16:
fffff880`040aaa16 ??              ???
Last set context:
rax=0000000000024e8a rbx=fffffa800a07b2b8 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa800a07b2b8
rip=fffff880040aaa16 rsp=fffff88009c56d80 rbp=0000000000000000
 r8=fffffa800a07b300  r9=0000000000000000 r10=fffffa8009db3640
r11=00000004aaaa0483 r12=0000000000024e8a r13=fffffa800a119c38
r14=0000000000000000 r15=fffff880018de110
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
bflwfx64+0x8a16:
fffff880`040aaa16 ??              ???
Resetting default scope

STACK_TEXT:  
fffff880`09c56d80 fffffa80`0a07b2b8 : fffff880`040aa892 00000000`00000000 fffffa80`0a07b2b8 00000000`00000001 : bflwfx64+0x8a16
fffff880`09c56d88 fffff880`040aa892 : 00000000`00000000 fffffa80`0a07b2b8 00000000`00000001 fffffa80`0a07b3f0 : 0xfffffa80`0a07b2b8
fffff880`09c56d90 00000000`00000000 : fffffa80`0a07b2b8 00000000`00000001 fffffa80`0a07b3f0 00000000`00000000 : bflwfx64+0x8892


FOLLOWUP_IP: 
bflwfx64+8a16
fffff880`040aaa16 ??              ???

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  bflwfx64+8a16

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: bflwfx64

IMAGE_NAME:  bflwfx64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  511bc788

STACK_COMMAND:  .cxr 0xfffff88009c563a0 ; kb

FAILURE_BUCKET_ID:  X64_0x1E_c0000094_bflwfx64+8a16

BUCKET_ID:  X64_0x1E_c0000094_bflwfx64+8a16

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x1e_c0000094_bflwfx64+8a16

FAILURE_ID_HASH:  {2043994a-8f47-1a27-9b57-112cd9ab1f62}

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

2: kd> lmvm bflwfx64
start             end                 module name
fffff880`040a2000 fffff880`041f5000   bflwfx64 T (no symbols)           
    Loaded symbol image file: bflwfx64.sys
    Image path: \SystemRoot\system32\DRIVERS\bflwfx64.sys
    Image name: bflwfx64.sys
    Timestamp:        Wed Feb 13 22:34:08 2013 (511BC788)
    CheckSum:         0001B330
    ImageSize:        00153000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[shortbus123]

I really appreciate the input. I uninstalled Killer e2200 and reinstalled the new driver you listed. Also found a ? unknown device in Device manager and installed my Intel USB 3 drivers. That ? is no longer there. Fingers crossed it fixes the BSOD.

Thanks again.

 

[Arc]

OK, let us know how it goes.

 

[shortbus123]

So far so good. REALLY appreciate the help. I think I have been up x 4 days without any problems.

 

[Arc]

Good news.

Let us know for any further issue.

 

[shortbus123]

New BSOD has just started. Same computer no new hardware. It only happens like once every other day then sometime will happen 2x in the same day. Any help is appreciated. It always amazes me how helpful and smart people on here are. New zip is uploaded

 

[Arc]

In post #3, it is stated to disable startup items. Why? The first intention was to keep Killer Network Manager out of action.

But you havent done it. There are 25 items in startup including two entries of bigfoot/atheros network manager.

It is the same thing that is causing the issue.
____________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000094, fffff880097ed1b0, 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+3810 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000094, The exception code that was not handled
Arg2: fffff880097ed1b0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

FAULTING_IP: 
+32dd5e0
fffff880`097ed1b0 d8e0            fsub    st,st(0)

EXCEPTION_PARAMETER2:  fffffa8008946690

BUGCHECK_STR:  0x1E_c0000094

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  openvpn.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from fffffa8008b7d301 to fffff88004623810

CONTEXT:  fffff880097ed930 -- (.cxr 0xfffff880097ed930;r)
rax=000000000003ed3a rbx=fffffa8008b7d301 rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8008b7d3a0 rdi=fffffa8008b7d2b8
rip=fffff88004623810 rsp=fffff880097ee310 rbp=0000000000000000
 r8=0000000000003500  r9=0000000000000000 r10=fffffa8008946690
r11=0000000000000000 r12=0000000000000001 r13=fffff880047716c0
r14=000000000003ed3a r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
bflwfx64+0x3810:
fffff880`04623810 ??              ???
Last set context:
rax=000000000003ed3a rbx=fffffa8008b7d301 rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa8008b7d3a0 rdi=fffffa8008b7d2b8
rip=fffff88004623810 rsp=fffff880097ee310 rbp=0000000000000000
 r8=0000000000003500  r9=0000000000000000 r10=fffffa8008946690
r11=0000000000000000 r12=0000000000000001 r13=fffff880047716c0
r14=000000000003ed3a r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
bflwfx64+0x3810:
fffff880`04623810 ??              ???
Resetting default scope

STACK_TEXT:  
fffff880`097ee310 fffffa80`08b7d301 : fffff880`046232ef fffffa80`08b7d3a0 fffffa80`08b7d2b8 fffffa80`08c1bc38 : bflwfx64+0x3810
fffff880`097ee318 fffff880`046232ef : fffffa80`08b7d3a0 fffffa80`08b7d2b8 fffffa80`08c1bc38 fffffa80`08b7d2b8 : 0xfffffa80`08b7d301
fffff880`097ee320 fffffa80`08b7d3a0 : fffffa80`08b7d2b8 fffffa80`08c1bc38 fffffa80`08b7d2b8 00000000`00000000 : bflwfx64+0x32ef
fffff880`097ee328 fffffa80`08b7d2b8 : fffffa80`08c1bc38 fffffa80`08b7d2b8 00000000`00000000 fffff880`046234df : 0xfffffa80`08b7d3a0
fffff880`097ee330 fffffa80`08c1bc38 : fffffa80`08b7d2b8 00000000`00000000 fffff880`046234df fffffa80`08b7d3f0 : 0xfffffa80`08b7d2b8
fffff880`097ee338 fffffa80`08b7d2b8 : 00000000`00000000 fffff880`046234df fffffa80`08b7d3f0 00000000`00000000 : 0xfffffa80`08c1bc38
fffff880`097ee340 00000000`00000000 : fffff880`046234df fffffa80`08b7d3f0 00000000`00000000 00000000`000005cf : 0xfffffa80`08b7d2b8


FOLLOWUP_IP: 
bflwfx64+3810
fffff880`04623810 ??              ???

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  bflwfx64+3810

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: bflwfx64

IMAGE_NAME:  bflwfx64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  527d059e

STACK_COMMAND:  .cxr 0xfffff880097ed930 ; kb

FAILURE_BUCKET_ID:  X64_0x1E_c0000094_bflwfx64+3810

BUCKET_ID:  X64_0x1E_c0000094_bflwfx64+3810

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x1e_c0000094_bflwfx64+3810

FAILURE_ID_HASH:  {b337d331-58a5-7079-7577-657f2971ba90}

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

7: kd> lmvm bflwfx64
start             end                 module name
fffff880`04620000 fffff880`04776000   bflwfx64 T (no symbols)           
    Loaded symbol image file: bflwfx64.sys
    Image path: \SystemRoot\system32\DRIVERS\bflwfx64.sys
    Image name: bflwfx64.sys
    Timestamp:        Fri Nov 08 21:09:10 2013 (527D059E)
    CheckSum:         00020472
    ImageSize:        00156000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[shortbus123]

Thanks

Arc,

Appreciate the help. I successfully did the following:

EDIT: Also 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.
Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept then restart.

Do you suggest ever adding them back. ie. one every few day (only the ones that I care about) until I figure what specifically is causing the problem?? or do you just recommend leaving them all unchecked forever?

Happy to do as you suggest. Many thanks. It is working fine so far.

 

[Arc]

Do you suggest ever adding them back. ie. one every few day (only the ones that I care about) until I figure what specifically is causing the problem?? or do you just recommend leaving them all unchecked forever?

Happy to do as you suggest. Many thanks. It is working fine so far.

No.

They all are installed in your computer. You can call them anytime from Start > All Programs.

If they all start with windows, that is not only unnecessary but also bad.

 

[shortbus123]

Its getting worse

Is is possible to have a defective motherboard or ethernet port? Kinfs starting to piss me off.

I have had about 10 BSOD or windows has recovered from unexpected error in the past 24 hours.

I turned off all but like two of the startup programs.

I will attack the most recent BSOD logs. Everyone here has been such a great help.

Thanks in advance for any other advice you may recommend.

 

[shortbus123]

Positive note that the newest Killer Driver suite update allowed my computer to run through the night. That is a big relief.