Forum Jump

Select Group :
Select Forum :
Sorted By :
Sort Order :
From The :
 
Thread Tools  Search this thread 
kroburg
Total Points:
30
Registered User
June 30, 2009 2:37 PM PDT
Amplifier crashes Vista x64 to BSOD on boost::asio profiling

My application creates test loopback connections using boost::asio async functionality (async_accept, async_connect). Dozens of connections works (profiles) fine, but then there are hundreds of connections, it crashes to BSOD.

There is TBB (tbb::concurrent_queue and tb::concurrent_vector) involved also, but i've checked it separately, it works.

Hardware is Core 2 Quad with 8G if it matters.
kroburg
Total Points:
30
Registered User
July 1, 2009 12:31 AM PDT
Rate
 
#1
Looks like this is Kaspersky antivirus fault. It was disabled during tests, but it affects system anyway, even disabled :-/



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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002d34e8e, 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) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!PspGetSetContextInternal+396
fffff800`02d34e8e 488b28 mov rbp,qword ptr [rax]

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002c71080
0000000000000000

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: unitTests.exe

CURRENT_IRQL: 1

TRAP_FRAME: fffffa600b1e69d0 -- (.trap 0xfffffa600b1e69d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d34e8e rsp=fffffa600b1e6b60 rbp=0000000000000000
r8=0000000000000000 r9=fffff80002a48000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!PspGetSetContextInternal+0x396:
fffff800`02d34e8e 488b28 mov rbp,qword ptr [rax] ds:0010:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a76e67 to fffff80002a9c650

STACK_TEXT:
fffffa60`0b1e61e8 fffff800`02a76e67 : 00000000`0000001e ffffffff`c0000005 fffff800`02d34e8e 00000000`00000000 : nt!KeBugCheckEx
fffffa60`0b1e61f0 fffff800`02a9c4a9 : fffffa60`0b1e6928 fffffa60`0ad27570 fffffa60`0b1e69d0 fffffa60`0ad27ac8 : nt! ?? ::FNODOBFM::`string'+0x29317
fffffa60`0b1e67f0 fffff800`02a9b2a5 : 00000000`00000000 00000000`000000ab 00000000`00000000 fffffa60`0ad27570 : nt!KiExceptionDispatch+0xa9
fffffa60`0b1e69d0 fffff800`02d34e8e : 00000000`00000000 fffffa60`0ad27570 00000000`00000000 fffffa60`0ad27ac8 : nt!KiPageFault+0x1e5
fffffa60`0b1e6b60 fffff800`02ab75cd : fffffa80`090101e0 fffffa80`08a2c700 fffffa60`0ad27570 00000000`00000000 : nt!PspGetSetContextInternal+0x396
fffffa60`0b1e70b0 fffff800`02ac6662 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspGetSetContextSpecialApc+0x9d
fffffa60`0b1e71c0 fffff800`02aca393 : fffffa60`0b1e72e0 00000000`00000000 00000000`00000000 fffffa80`08a2c700 : nt!KiDeliverApc+0x1e2
fffffa60`0b1e7260 fffff800`02aa607c : fffffa60`04664889 fffffa60`0b1e7a70 fffffa60`046545d6 00000000`00000010 : nt!KiApcInterrupt+0x103
fffffa60`0b1e73f8 fffffa60`04664889 : fffffa60`0b1e7a70 fffffa60`046545d6 00000000`00000010 00000000`00000206 : nt!KeReleaseSpinLock+0xc
fffffa60`0b1e7400 fffffa60`0b1e7a70 : fffffa60`046545d6 00000000`00000010 00000000`00000206 fffffa60`0b1e7430 : kl1+0x5a889
fffffa60`0b1e7408 fffffa60`046545d6 : 00000000`00000010 00000000`00000206 fffffa60`0b1e7430 fffffa60`046545ec : 0xfffffa60`0b1e7a70
fffffa60`0b1e7410 00000000`00000010 : 00000000`00000206 fffffa60`0b1e7430 fffffa60`046545ec 00000000`00000000 : kl1+0x4a5d6
fffffa60`0b1e7418 00000000`00000206 : fffffa60`0b1e7430 fffffa60`046545ec 00000000`00000000 fffff800`02ae395a : 0x10
fffffa60`0b1e7420 fffffa60`0b1e7430 : fffffa60`046545ec 00000000`00000000 fffff800`02ae395a 00000000`00000010 : 0x206
fffffa60`0b1e7428 fffffa60`046545ec : 00000000`00000000 fffff800`02ae395a 00000000`00000010 fffffa60`0460bf06 : 0xfffffa60`0b1e7430
fffffa60`0b1e7430 00000000`00000000 : fffff800`02ae395a 00000000`00000010 fffffa60`0460bf06 fffa800a`2e48c000 : kl1+0x4a5ec


STACK_COMMAND: kb

FOLLOWUP_IP:
kl1+5a889
fffffa60`04664889 ?? ???

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: kl1+5a889

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: kl1

IMAGE_NAME: kl1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48849e50

FAILURE_BUCKET_ID: X64_0x1E_kl1+5a889

BUCKET_ID: X64_0x1E_kl1+5a889

Followup: MachineOwner
---------
Vladimir Tsymbal (Intel)
Total Points:
8,863
Status Points:
8,363
Brown Belt
July 2, 2009 4:11 AM PDT
Rate
 
#2 Reply to #1
Hi,

Please try to explicitly disable the kl1.sys (Kaspersky Lab) driver in your system and try Amplifier again.
Thanks.


--------
-Vladimir


Intel Software Network Forums Statistics

8445 users have contributed to 31553 threads and 100398 posts to date.
In the past 24 hours, we have 10 new thread(s) 30 new posts(s), and 43 new user(s).

In the past 3 days, the most popular thread for everyone has been Lost in MKL The most posts were made to TBB on linux segfaulting The post with the most views is Hi,if you were using imsl yo

Please welcome our newest member nonamez