Post by raucous on Nov 26, 2013 21:10:30 GMT
I just purchased a brand new Dell XPS 15" ultrabook (Haswell) w/Touch, 3K display (NVidia), 512GB SSD, Win8.1 64-bit (Pro).
I installed Reason 6.3.1, and latest Asio4All beta.
I can use Reason to my heart's content, *except* when I connect to Bluetooth, and have Asio4All output to Bluetooth. (I am connecting to Samsung DA-E750 high-end speaker).
Once I start playing to Bluetooth, the system freezes, reboots, and/or blue-screens. So I enabled the driver verifier (std./ALL), and it keeps hitting this stack (below).
I submitted the crash dump to MS but they are only concerned with having me do experiments like remove all third party applications and see if it still reproes using only Windows Bluetooth playback (it doesn't). So they are washing their hands of me, despite my vehemently insisting they have a bug in their Bluetooth stack (which they clearly do).
Any ideas why this only hits in this scenario, or any other suggestions, or things I might try to resolve the issue?
Thanks!
__e
Eric Nelson 206.769.5915
Software Developer
Intel Mobile Platforms
DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (d6) N bytes of memory was allocated and more than N bytes are being referenced.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffcf80394df001, memory referenced
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation
Arg3: fffff80003d2f969, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'mpsdrv' and 'IntcDAud.sys' overlap
WRITE_ADDRESS: ffffcf80394df001 Special pool
FAULTING_IP:
BthA2DP!SBC::build_sbc_frame+29
fffff800`03d2f969 41c6070f mov byte ptr [r15],0Fh
MM_INTERNAL_CODE: 0
IMAGE_NAME: BthA2DP.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5215f836
MODULE_NAME: BthA2DP
FAULTING_MODULE: fffff80003d28000 BthA2DP
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0xD6
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
TRAP_FRAME: ffffd00022bff680 -- (.trap 0xffffd00022bff680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000018 rbx=0000000000000000 rcx=ffffe000050a2000
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003d2f969 rsp=ffffd00022bff810 rbp=ffffcf80394deffe
r8=ffffe000050a20c8 r9=0000000000000002 r10=0000000000000008
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
BthA2DP!SBC::build_sbc_frame+0x29:
fffff800`03d2f969 41c6070f mov byte ptr [r15],0Fh ds:00000000`00000000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff801fcf8595c to fffff801fcf5dca0
STACK_TEXT:
ffffd000`22bff498 fffff801`fcf8595c : 00000000`00000050 ffffcf80`394df001 00000000`00000001 ffffd000`22bff680 : nt!KeBugCheckEx
ffffd000`22bff4a0 fffff801`fce4c5ad : 00000000`00000001 ffffe000`04e50400 ffffd000`22bff680 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x177cc
ffffd000`22bff540 fffff801`fcf67f2f : 00000000`00000001 ffffe000`050a2000 00000000`00000000 ffffd000`22bff680 : nt!MmAccessFault+0x7ed
ffffd000`22bff680 fffff800`03d2f969 : ffffe000`012d9000 00000000`00000002 00000000`00000000 fffff800`03d2f71c : nt!KiPageFault+0x12f
ffffd000`22bff810 fffff800`03d304a4 : ffffe000`050a2000 ffffcf80`394deffe ffffe000`050a2500 ffffe000`050a2036 : BthA2DP!SBC::build_sbc_frame+0x29
ffffd000`22bff890 fffff800`03d34b94 : fffff800`00c0dd43 ffffcf80`394deff1 00000000`00000200 00000000`000004e4 : BthA2DP!SBC::SBC_Encode+0x4f0
ffffd000`22bff9a0 fffff800`03d31fff : ffffd000`00000200 ffffd000`3a285d90 fffff801`00000000 ffffe000`00000000 : BthA2DP!SBC_ProcessDataWithCallback+0x
194
ffffd000`22bffa20 fffff800`03d31b15 : 00000000`00000200 00000000`00000000 ffffcf80`0a836fb0 ffffe000`04e50500 : BthA2DP!CPcmPin::TimerWork+0x4db
ffffd000`22bffac0 fffff801`fceb0a73 : ffffcf80`0a9f6fb0 ffffe000`00152900 00000000`00000000 00000000`00000000 : BthA2DP!CPcmPin::TimerWorker+0x11
ffffd000`22bffaf0 fffff801`fceb11b9 : fffff801`fd23d2c4 fffff801`fceb0998 ffffd000`22bffbd0 ffffcf80`0a836fb0 : nt!IopProcessWorkItem+0xdb
ffffd000`22bffb50 fffff801`fce9d2e4 : ffffd000`20b7b340 ffffe000`04e50400 ffffe000`04e50400 ffffe000`0018e900 : nt!ExpWorkerThread+0x2b5
ffffd000`22bffc00 fffff801`fcf642c6 : ffffd000`20b6f180 ffffe000`04e50400 ffffd000`20b7b340 00000000`00000002 : nt!PspSystemThreadStartup+0x58
ffffd000`22bffc60 00000000`00000000 : ffffd000`22c00000 ffffd000`22bfa000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
BthA2DP!SBC::build_sbc_frame+29
fffff800`03d2f969 41c6070f mov byte ptr [r15],0Fh
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: BthA2DP!SBC::build_sbc_frame+29
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.3.9600.16384
BUCKET_ID_FUNC_OFFSET: 29
FAILURE_BUCKET_ID: 0xD6_VRF_BthA2DP!SBC::build_sbc_frame
BUCKET_ID: 0xD6_VRF_BthA2DP!SBC::build_sbc_frame
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xd6_vrf_btha2dp!sbc::build_sbc_frame
FAILURE_ID_HASH: {156955bd-6c15-e469-29ce-b3b2dac71031}
Followup: MachineOwner
---------