Ok, sorry for the later response than intended... after rereading the manual and it not being much help as to what precisely the 'Bluetooth Controller' handles in the BIOS, some clarification would be appreciate. I mean, I can bluetooth to/from my phone without issue, so I can only figure what I have disabled pertains to the mPCIe card's BT 4.0? No big deal, but I would then be curious as to why there is no device detected? I had installed and reinstalled drivers from CD/website repeatedly to no avail. I would love to use the BT 4.0, but I won't lose sleep over it. The lack of device recognition bothers me more than anything else - disabled in the BIOS or no.
Also, I just want to throw it out there in case it's related: I have been experiencing infrequent BSOD's - a total of 6 since 07 Apr 2013. They are always related to an inconsistent power state, so drivers are at fault from what I can determine. I have updated the BIOS, vid drivers, sound drivers, firmware where ever necessary, all to no avail. If I need to create a new post in relation to this BSOD, I will. I just figured I would ask here first in the off chance they're related issues. Here's the most recent minidump to hopefully have somebody here confirm if this floating bluetooth device is causing more trouble than it's worth:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Readable dump files\050213-9968-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*
http://msdl.microsoft.com/download/symbolsExecutable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`0304a000 PsLoadedModuleList = 0xfffff800`0328d670
Debug session time: Thu May 2 10:58:22.742 2013 (UTC - 5:00)
System Uptime: 0 days 8:36:06.585
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800d6a3890, fffff80004a243d8, fffffa80128f9010}
Probably caused by : ACPI.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800d6a3890, Physical Device Object of the stack
Arg3: fffff80004a243d8, Functional Device Object of the stack
Arg4: fffffa80128f9010, The blocked IRP
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'hiber_iaStor' and 'hiber_iaStor' overlap
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa80128f9010
DEVICE_OBJECT: fffffa800d60e330
DRIVER_OBJECT: fffffa800d617060
IMAGE_NAME: ACPI.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79294
MODULE_NAME: ACPI
FAULTING_MODULE: fffff88001135000 ACPI
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
fffff800`04a24388 fffff800`0312f8c2 : 00000000`0000009f 00000000`00000003 fffffa80`0d6a3890 fffff800`04a243d8 : nt!KeBugCheckEx
fffff800`04a24390 fffff800`030ca84c : fffff800`04a244c0 fffff800`04a244c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`04a24430 fffff800`030ca6e6 : fffffa80`12ce4b88 fffffa80`12ce4b88 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`04a244a0 fffff800`030ca5ce : 00000048`1985ebba fffff800`04a24b18 00000000`001e4a00 fffff800`0323d288 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04a24af0 fffff800`030ca3b7 : 00000018`b71301c2 00000018`001e4a00 00000018`b713011c 00000000`00000000 : nt!KiTimerExpiration+0x1be
fffff800`04a24b90 fffff800`030b790a : fffff800`0323ae80 fffff800`03248cc0 00000000`00000002 fffff800`00000000 : nt!KiRetireDpcList+0x277
fffff800`04a24c40 00000000`00000000 : fffff800`04a25000 fffff800`04a1f000 fffff800`04a24c00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_ACPI.sys
BUCKET_ID: X64_0x9F_3_IMAGE_ACPI.sys
Followup: MachineOwner
---------