BSOD's when watching movies or playing games - Windows 7 x64

T

Timmeh

New member
Joined
Aug 15, 2014
Posts
3
Good day everyone,

I have a problem with my PC which has been annoying me for quite a while now. I am usually quite good with fixing problems and have really no clue where to go from here any longer.
I have purchased a new PC and it gives me BSOD's when I play games or watch movies. I already RMA'd all off my hardware and received replacements. I re installed windows several times and am beginning to wonder if this PC is doomed before it even starts.

OS : Windows 7 64 Bit
OS : was purchased by me and also re-installed several times.
Age of system (hardware) 4 months old as I purchased a new PC and then left for Japan I never really got the chance to fix it until now even though I tried for several weeks before I went to Japan.
Age of OS installation : I am gonna say 4 months as well.

CPU : Intel(R) Core(TM) i7-3770 CPU @3.40GHz 3.40 Ghz
Video Card : Nvidia GeForce GTX 660
MotherBoard: Z77A-G43 Gaming
Power Supply : CS750M Corsair

System manufacturer : self
Desktop

I figured the blue screens were pointing to a faulty driver but I can't seem to figure out how to fix it and have attached the necessary files to the post and also added 3 mini dumps.
I already checked my RAM and ran HDD Diagnostics and it came out clean. I would use Driver Verifier but last time I used it I got an instant BSOD.
 

Attachments

Doomed?
Not after we're done hehe.

Code: 
BugCheck 1E, {[COLOR="#FF0000"]ffffffffc0000094[/COLOR], fffff8800d8100d0, 0, 0}

We're getting 0x1E bugchecks which indicate a kernel mode exception wasn't handled, now the 2 latets dump files are caused by the same thing but some information isn't saved in either of them so I'm mixing them up to help you understand.
Notice how I've highlighted the first parameter?
That's the exception code that caused the error.

It's a divide by zero fault which always results in a crash.

Code: 
4: kd> [COLOR="#008000"]!error ffffffffc0000094[/COLOR]
[COLOR="#FF0000"]Error code: (NTSTATUS) 0xc0000094 (3221225620) - {EXCEPTION}  Integer division by zero.[/COLOR]

Code: 
fffff800`00b9b948 fffff800`03cc15be : fffffa80`099cf000 fffff800`00b9b999 fffff800`00b9c0c0 fffff800`03cf4a90 : [COLOR="#0000FF"]nt!KeBugCheck[/COLOR]
fffff800`00b9b950 fffff800`03cf475d : fffff800`03ed8380 fffff800`03e15260 fffff800`03c54000 fffff800`00b9c868 : [COLOR="#00FFFF"]nt!KiKernelCalloutExceptionHandler+0xe[/COLOR]
fffff800`00b9b980 fffff800`03cf3535 : fffff800`03e19038 fffff800`00b9b9f8 fffff800`00b9c868 fffff800`03c54000 : [COLOR="#00FFFF"]nt!RtlpExecuteHandlerForException+0xd[/COLOR]
fffff800`00b9b9b0 fffff800`03d044c1 : fffff800`00b9c868 fffff800`00b9c0c0 fffff800`00000000 fffffa80`096f02b8 : [COLOR="#00FFFF"]nt!RtlDispatchException+0x415[/COLOR]
fffff800`00b9c090 fffff800`03cc9242 : fffff800`00b9c868 fffffa80`096f02b8 fffff800`00b9c910 00000000`00000000 : [COLOR="#00FFFF"]nt!KiDispatchException+0x135[/COLOR]
fffff800`00b9c730 fffff800`03cc6a34 : fffff800`00b96002 fffff880`081a5f14 00000000`00000000 fffff880`01e3d8e1 : [COLOR="#00FFFF"]nt!KiExceptionDispatch+0xc2[/COLOR]
fffff800`00b9c910 fffff880`07c2ba16 : fffffa80`096f02b8 fffff880`07c2b892 fffffa80`096f03b0 fffffa80`096f02b8 : [COLOR="#FF0000"]nt!KiDivideErrorFault+0xf4[/COLOR] (TrapFrame @ [COLOR="#008000"]fffff800`00b9c910[/COLOR])
fffff800`00b9caa0 fffffa80`096f02b8 : fffff880`07c2b892 fffffa80`096f03b0 fffffa80`096f02b8 00000000`ffffffff : [COLOR="#FF0000"]bflwfx64+0x8a16[/COLOR]
fffff800`00b9caa8 fffff880`07c2b892 : fffffa80`096f03b0 fffffa80`096f02b8 00000000`ffffffff fffffa80`0978ec38 : [COLOR="#800080"]0xfffffa80`096f02b8[/COLOR]
fffff800`00b9cab0 fffffa80`096f03b0 : fffffa80`096f02b8 00000000`ffffffff fffffa80`0978ec38 fffffa80`096f03b0 : [COLOR="#FF0000"]bflwfx64+0x8892[/COLOR]

Well this callstack shows that your bflwfx64.sys driver has used an illegal mathematical calculation which isn't allowed, a division by zero.
If you divide something by zero what do you get? Zero... It won't work and never will.

The driver itself is buggy and must be updated or the network card must be replaced as a last alternative.

Code: 
0: kd> [COLOR="#008000"]lm vm bflwfx64[/COLOR]
start             end                 module name
fffff880`07c23000 fffff880`07d76000   bflwfx64 T (no symbols)           
    Loaded symbol image file: bflwfx64.sys
    Image path: \SystemRoot\system32\DRIVERS\bflwfx64.sys
    Image name: bflwfx64.sys
    Timestamp:        [COLOR="#FF0000"]Wed Feb 13 17:04:08 2013[/COLOR] (511BC788)
    CheckSum:         0001B330
    ImageSize:        00153000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Never thought I'd say this but...
Lucky for you its outdated so an update should fix it, run Windows Update on your wireless network card or try and find an update from your network card manufacturer.

Looking at your programs installed I have a few recommendations for removing some problematic software, however I don't really like taking the caveman approach and uninstalling all software on the computer so we have two options.

You can either update your network driver which should fix the problem, most likely will and you can be on your way.
or
We can remove some software which might be contributing.

It's entirely up to you, a lot of softwrae you have installed has caused numerous problems but whether you want to keep it or not is up to you.
 
Last edited:
I have a question as I deleted my wifi driver all together since I don't have a wifi card in my PC anymore so I just have my MSI Killer Network Drivers running. I will try and find an update for this if there are any. as I am not sure if these are the cause of the crash now

MSI USA - Computer, Laptop, Notebook, Desktop, Mainboard, Graphics and more 64

I figured I would use the latest drivers from the MSI website as these seem to be a newer version and hope this will help me
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top