Doomed?
Not after we're done hehe.
Code:
BugCheck 1E, {ffffffffc0000094, 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> !error ffffffffc0000094
Error code: (NTSTATUS) 0xc0000094 (3221225620) - {EXCEPTION} Integer division by zero.
Code:
fffff800`00b9b948 fffff800`03cc15be : fffffa80`099cf000 fffff800`00b9b999 fffff800`00b9c0c0 fffff800`03cf4a90 : nt!KeBugCheck
fffff800`00b9b950 fffff800`03cf475d : fffff800`03ed8380 fffff800`03e15260 fffff800`03c54000 fffff800`00b9c868 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b980 fffff800`03cf3535 : fffff800`03e19038 fffff800`00b9b9f8 fffff800`00b9c868 fffff800`03c54000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b9b0 fffff800`03d044c1 : fffff800`00b9c868 fffff800`00b9c0c0 fffff800`00000000 fffffa80`096f02b8 : nt!RtlDispatchException+0x415
fffff800`00b9c090 fffff800`03cc9242 : fffff800`00b9c868 fffffa80`096f02b8 fffff800`00b9c910 00000000`00000000 : nt!KiDispatchException+0x135
fffff800`00b9c730 fffff800`03cc6a34 : fffff800`00b96002 fffff880`081a5f14 00000000`00000000 fffff880`01e3d8e1 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c910 fffff880`07c2ba16 : fffffa80`096f02b8 fffff880`07c2b892 fffffa80`096f03b0 fffffa80`096f02b8 : nt!KiDivideErrorFault+0xf4 (TrapFrame @ fffff800`00b9c910)
fffff800`00b9caa0 fffffa80`096f02b8 : fffff880`07c2b892 fffffa80`096f03b0 fffffa80`096f02b8 00000000`ffffffff : bflwfx64+0x8a16
fffff800`00b9caa8 fffff880`07c2b892 : fffffa80`096f03b0 fffffa80`096f02b8 00000000`ffffffff fffffa80`0978ec38 : 0xfffffa80`096f02b8
fffff800`00b9cab0 fffffa80`096f03b0 : fffffa80`096f02b8 00000000`ffffffff fffffa80`0978ec38 fffffa80`096f03b0 : bflwfx64+0x8892
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> lm vm bflwfx64
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: Wed Feb 13 17:04:08 2013 (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.
