[/QUOTE][FONT="Lucida Console"]
Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\YUSRA\Downloads\debug-SalDesktop1\debug-SalDesktop1\SALDESKTOP1-Tue_02_17_2015_192310_90\021715-17316-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
Machine Name:
Kernel base = 0xfffff800`03218000 PsLoadedModuleList = 0xfffff800`0345c890
Debug session time: Wed Feb 18 05:59:05.650 2015 (UTC + 6:00)
System Uptime: 0 days 7:55:43.462
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000094, fffff8800b2d00d0, 0, 0}
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: fffff8800b2d00d0, 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:
+26ea6473f49359
fffff880`0b2d00d0 f8 clc
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.16384 (debuggers(dbg).130821-1623) x86fre
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88004824a16
CONTEXT: fffff8800b2d0850 -- (.cxr 0xfffff8800b2d0850;r)
rax=00000000000006af rbx=fffffa8010b5d2b8 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa8010b5d2b8
rip=fffff88004824a16 rsp=fffff8800b2d1230 rbp=0000000000000000
r8=0000000000000600 r9=0000000000000000 r10=fffffa8010934c00
r11=00000016a9bb7f02 r12=00000000000006af r13=fffffa8010bfbc38
r14=0000000000000000 r15=fffff88001904110
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`04824a16 ?? ???
Last set context:
rax=00000000000006af rbx=fffffa8010b5d2b8 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa8010b5d2b8
rip=fffff88004824a16 rsp=fffff8800b2d1230 rbp=0000000000000000
r8=0000000000000600 r9=0000000000000000 r10=fffffa8010934c00
r11=00000016a9bb7f02 r12=00000000000006af r13=fffffa8010bfbc38
r14=0000000000000000 r15=fffff88001904110
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`04824a16 ?? ???
Resetting default scope
STACK_TEXT:
fffff880`0b2d1230 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : bflwfx64+0x8a16
FOLLOWUP_IP:
bflwfx64+8a16
fffff880`04824a16 ?? ???
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 0xfffff8800b2d0850 ; 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`0481c000 fffff880`0496f000 bflwfx64 T (no symbols)
Loaded symbol image file: bflwfx64.sys
Image path: \SystemRoot\system32\DRIVERS\bflwfx64.sys
Image name: bflwfx64.sys
[COLOR="Blue"]Timestamp: Wed Feb 13 23:04:08 2013 (511BC788)[/COLOR]
CheckSum: 0001B330
ImageSize: 00153000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
[/FONT]
from a certain well known application. I received the following info:
