Apple Wireless Keyboard under Windows 7 pairing but not responding
Hi all,
I'm having a strange issue getting my Apple Wireless Keyboard to run on my new HTPC under Windows 7 (64 bit). I can get Windows' bluetooth manager to detect the keyboard, and I can input the pairing code, following which Windows seems to install a bunch of drivers, but then I get no response from the keyboard at all.
The thing I find strange is that the keyboard works when I punch in the code numbers, but never before or after.
I also have a Magic Mouse which works perfectly.
Once paired and installed, the keyboard is displayed in Windows' driver manager as a "Bluetooth Peripheral Device", so I'm wondering if the issue is that Windows isn't recognising the device as a keyboard.
Does anyone have any suggestions? Thanks heaps, in advance.
After 3 frustrating hours of trying every tip on the net, I found the answer: Try this.
"This finally fixed it for me: Device Manager - Open System Devices, you will find a Bluetooth HID Device. Double Click it, open Driver tab and click "Update Driver" Select Browse my Computer, then "Let me Pick". It should now show TWO compatible drivers with exactly the same name. One of them is the Microsoft one, one is the non-working Chinese ****. Install one of them and see if the driver properties changed to the right (Microsoft) driver. If not, try again with the other one. For me, the Microsoft driver was the first one in the list, but this may be different for you. Wow, an annoying and intense hour of trouble shooting finally over..."
Source: http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/window s-update-yi-ruan-bluetooth-hid-device-driver/5bfd0c92-1771-e011-8dfc-68b599b31bf 5?page=2&tm=1304484508563
The issue is related to the Chinese version of the driver that the latest windows update applies that stops the keyboard from working.
I'm typing this on the Apple Wireless Keyboard on Windows 7 64 bit on my PC. Finallly!
Similar Messages
-
I installed windows 8 Pro to my Mac 27', however am having a hard time to pair apple wireless keyboard with windows 8 pro. Can anyone help?
one have to go to osx and to it's bootcamp app
and make an usb stick with the apple drivers for windows
then one have to install them in windows to get the hardware working ok -
Apple Wireless Keyboard with Windows 7 on non Apple Hardware
Good Day,
I love the Apple Wireless Keyboard and it's the on I use when using my Thinkpad laptop as a desktop, meaning connected to an external Monitor and with an external keyboard and mouse. The Keyboard I use is an Apple Wireless Keyboard.
On my MBA 13 I use Windows 7 as my OS and the Apple lyouted keyboard works actually quite well with windows: The function keys perform very much like in Mac OSX with the volume, screen brightness, the fn+left or right for "home" or "end" etc.
Not I bought an Apple Wireless Keyboard to use in conjuction with my Thinkpad but all does features are missing. I guess that this has to to that on the MBA 13 the appropriate drivers where installed when the whole Bootcamp Software package was installed.
Since I obviously cant install the whole Bootcamp CD on non Apple Hardware, is there any way to just download somewhere the drivers for Apple KEyboards so the behave the same way as they would on a Mac running Windows?
Or is there any other way I could use my Apple Wireless Keyboard with non Apple Hardware the same way it behaves on my MBA 13 running Windows 7? Can somwhere lolely the Apple Keyboard drivers be downloaded?
I want to thank anyone who is kind enough to help mme with this mather in advance and please leave out comments of the kind that I it's my fault, I should have bought an Apple machine from the beginning. I have my reasons and If anyone can't handle that I kindly ask you to just ignore this post unless it's constructive and helpful contribution
Message was edited by: ApollossAfter 3 frustrating hours of trying every tip on the net, I found the answer: Try this.
"This finally fixed it for me: Device Manager - Open System Devices, you will find a Bluetooth HID Device. Double Click it, open Driver tab and click "Update Driver" Select Browse my Computer, then "Let me Pick". It should now show TWO compatible drivers with exactly the same name. One of them is the Microsoft one, one is the non-working Chinese ****. Install one of them and see if the driver properties changed to the right (Microsoft) driver. If not, try again with the other one. For me, the Microsoft driver was the first one in the list, but this may be different for you. Wow, an annoying and intense hour of trouble shooting finally over..."
Source: http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/window s-update-yi-ruan-bluetooth-hid-device-driver/5bfd0c92-1771-e011-8dfc-68b599b31bf 5?page=2&tm=1304484508563
The issue is related to the Chinese version of the driver that the latest windows update applies that stops the keyboard from working.
I'm typing this on the Apple Wireless Keyboard on Windows 7 64 bit on my PC. Finallly! -
Configure the Apple numeric keyboard under Windows in iMac
I have an iMac with Windows 7. How can I configure the Apple numeric keyboard under Windows?
From Apple:
Are there any Macintosh features that I should not expect to work when running Windows XP on an Intel-based Macintosh computer?
Even after installling the Macintosh Drivers CD, the Apple Remote Control (IR), Apple Wireless (Bluetooth) keyboard or mouse, Apple USB Modem, MacBook Pro's sudden motion sensor, MacBook Pro's ambient light sensor, and built-in iSight camera will not function correctly when running Windows. -
Why does a specific site open with Firefox 3.6 running under Windows 7 Ulimate but not under Windows 7 professional?
== URL of affected sites ==
http://www.bmw.co.ukWhy does a specific site open with Firefox 3.6 running under Windows 7 Ulimate but not under Windows 7 professional?
== URL of affected sites ==
http://www.bmw.co.uk -
Can't pair apple wireless keyboard in Windows
Hi
I have just purchased the new June 2009 Macbook Pro. I've used bootcamp to install Windows XP and i'm trying to pair my apple wireless keyboard.
Its the brand new apple wireless keyboard but when i search for the device in the Bluetooth control panel, its displayed but when it attempts to pair it says completed ok, but the keyboard still doesn't work.
Any ideas?
Cheers
Andy' Peter, I'm sorry to say this, but it sounds like you specifically either have a genuine hardware problem, or your Windows installation is sicker than most. You should never see the sort of symptoms you're talking about in a normal, healthy system!!!
' However, the bad / sad fact of the matter is that, even were you not in the position you're in, you couldn't use either keyboard or mouse when in Windows!
' I am able to (and have done - my Vista system is still configured successfully with 'em - I haven't removed them despite them being useless!) propperly pair both devices on Vista without much of a challenge - pretty standard fair actually... But that's all a smokescreen. Despite this - and despite being able to actually query each device over bluetooth for the services they provide and so on - they still cannot be actually used!!! No matter what, there is never any response from the OS to input or actions on either keyboard or mouse.
' <Shrugs> What can I tell ya. It does sound like Peter needs to move onto solving his bluetooth problem though anyways - in case this causes trouble for him (you) at some later date with devices that actually would be useful!
' Later!
~Menageryl
-Jack of All Trades, Master of Some!-
Message was edited by: Menageryl -
Blue Screen of Death from Apple Wireless Keyboard in Windows 7
Hi all,
Situation: I have Windows 7 Professional 64 bit installed (boot camp) on my late 2008 MBP. Oftentimes, I'm plugged in to an LED Cinema display and work off of the Apple Wireless Keyboard & Magic Mouse. The Boot Camp partition / Drivers were originally installed from a Snow Leopard DVD. My Apple Software update reports that all my Apple Windows Software is up-to-date.
Problem: Since installing Windows 7 back in May, I've experienced the Blue Screen of Death (BSOD) 5 times. Each time has resulted from a key press on my bluetooth keyboard after it had been sitting idle for some time and presumably gone into power save mode. Any key press causes an instantaneous BSOD. It only occurs when I'm running windows and I'm working off my bluetooth keyboard so it's hard to replicate and likewise hard to troubleshoot and determine if a fix has worked.
*Error Details:* Here's some information I've extracted from the BSOD dump files.
IRQLNOT_LESS_OREQUAL
+The problem seems to be caused by the following file: ntoskrnl.exe+
+Technical Information:+
+* STOP: 0x0000000a (0xfffff80003032f00, 0x0000000000000002, 0x0000000000000008,+
0xfffff80003032f00)
+* ntoskrnl.exe - Address 0xfffff80002cbf600 base at 0xfffff80002c4f000 DateStamp+
0x4b88cfeb
Thanks for the help!
PaulI'm experiencing the same problem with the BSODs while using my Apple wireless keyboard (latest model).
I'm running Windows 7 x64 and admit that I bypassed the BootCamp software/driver installation wizard after it complained that my model didn't support installation of the x64 drivers. Its a bit of a gray area, as my system is 64-bit capable and many services and applications run in 64-bit mode without my intervention.
Just curious if Windows 7 x86 users are experiencing these BSODs or is it a coincidence that you all are installing the drivers creatively. -
How to disable "special" f-key function on Apple Wireless Keyboard in Windows 7
Hi. I dual-boot my iMac using an Apple Wireless Keyboard. In Mac OS's "Keyboard" system preference pane, I've chosen to treat the F-keys as actual F-keys, and not the "special" function keys, such as volume control and screen brightness. This however does not carry over to the Windows environment.
I cannot find an option to do this on the Windows 7 side. I've tried SharpKeys (popular Windows freeware key-mapping registry editor), however the program doesn't recognize the key being pushed (unless I hold the "Fn" key, at which point, it sees it as the F# key).
To reiterate, I'd like to know how to use the F1 through F12 keys as F1-F12 in Windows 7, without having to use the "Fn" key.Hi alexia416,
If you would like to use your Apple keyboard in Boot Camp with the standard function keys as the default, you may find the following article helpful:
Boot Camp: Use the function keys on an Apple keyboard
For other keyboard-related Boot Camp issues, this article is also useful:
Boot Camp: About keyboards and key assignment for Microsoft Windows - Apple Support
Regards,
- Brenden -
Apple Wireless Keyboard on Windows 7
Hi all--
I recently bought an Apple Wireless Keyboard for my pc at home, specifically inquiring at the Apple Store if it would be compatible with Windows.
I'm using a Dell Inspiron 1545 laptop-- and when I navigate to Control Panel > Hardware and Sound > Add device -- Windows is completely unable to find the keyboard.
My Macbook Pro has no trouble finding the keyboard, and from what I've read: there shouldn't be any trouble finding this device on Windows. What's going on here?Hi alexia416,
If you would like to use your Apple keyboard in Boot Camp with the standard function keys as the default, you may find the following article helpful:
Boot Camp: Use the function keys on an Apple keyboard
For other keyboard-related Boot Camp issues, this article is also useful:
Boot Camp: About keyboards and key assignment for Microsoft Windows - Apple Support
Regards,
- Brenden -
Apple Wireless Keyboard for Windows Vista
I recently bought an Apple Wireless Keyboard and a Kensington micro USB Bluetooth adapter for my Windows Vista laptop. The initial steps to configure the keyboard were straightforward and I did not run into any problems. Within a few hours after setting things up, I ran into the following problems:
a) The Apple Wireless Keyboard would disconnect randomly, sometimes mid-typing.
b) After functioning normally, a key (usually 'f') kept repeating.
The only way to solve both problems was to hold the power button on the side of the keyboard for a few seconds until the power light turned off. Then I had to hold down the power button again to turn it back on and it would automatically reconnect. The keyboard would work fine for a few minutes, only to have the same problems return later. The problems seemed to occur more frequently when I left the keyboard alone and did not use it for a few minutes.
The Solution
I become quite frustrated and was on the verge of returning the keyboard. As a final effort to fix things, I removed the Bluetooth drivers and reinstalled newer drivers. Here's how I did this:
1) Go to Start > Control Panel (Classic View) > Keyboard.
2) In the keyboard menu, select the 'Hardware' tab and select 'HID Keyboard Device'.
3) Click 'Properties' and then select 'Change Settings' and click 'Continue' at the security prompt.
4) Select uninstall.
5) Go back to the Control Panel and go to 'Programs and Features'. Locate the program you installed with your Bluetooth adapter. (Mine was Toshiba Bluetooth Stack. If your computer has built-in Bluetooth, you can probably skip this step.)
6) Uninstall the Bluetooth program.
7) Restart the computer.
Hopefully by this point, Windows will prompt you by saying that it has discovered new hardware and is installing the software for it. It should then display a Bluetooth icon in the notification area (bottom-right by clock). Right-click it and select add new device or view connected devices. Then simply run through the steps to connect your keyboard. Make sure you turn on the keyboard before you run through the setup.
After going through this procedure, I have not had any problems. The repeatings keys and disconnections have both subsided. Before playing around with the drivers, I suggest copying the drivers to a safe location or creating a Restore Point so you can always revert your changes.
Hope everything works out!Hello,
I am having the exact problem you were having. Is it possible to apply Apple's new firmware update to the keyboard and have it function with the PC? I called the Applestore, and the sales rep told me that the keyboard did not save the firmware on the keyboard itself. Is this true?
Any and all help would be greatly appreciated.
Thanks! -
Apple Bluetooth Keyboard under Windows
Guys I can't get the Apple Bluetooth Keyboard to work under windows when I start my MBP in XP...I can discover it and then it pairs with it, but in the end no key will work :/
From Apple:
Are there any Macintosh features that I should not expect to work when running Windows XP on an Intel-based Macintosh computer?
Even after installling the Macintosh Drivers CD, the Apple Remote Control (IR), Apple Wireless (Bluetooth) keyboard or mouse, Apple USB Modem, MacBook Pro's sudden motion sensor, MacBook Pro's ambient light sensor, and built-in iSight camera will not function correctly when running Windows. -
A u disk would be recognized as Apple Internel Keyboard under Windows
Hi All,
I've encounted a strange problem when running Windows 8.1 under bootcamp support. The u disk would be recognized as "Apple Internel Keyboard" when pluging it in, and it was not able to eject it safely. The OSX is the latest 10.10.2 and Windows is 8.1 with update, could someone help me to fix this? Thanks in advance.Yes, please refer to the attacked picture below.
-
Application Runs Under Windows 8.1 But Not Under Windows XP (I Know XP Is Deprecated)
The problem is with the obtuse error message put out by Windows's program loader. It reads, in part, "..is not a valid Win32 application." The application runs everywhere except on Windows XP. Looking for root cause of the problem. It's a very
simple application. Only a few lines of code.
C:\Packaged-Software\32-BIT\Reboot.exe is not a valid Win32 application.
Proposed nature of the problem:
1. The file was downloaded from a website but the download was incomplete.
2. The full file system filename path contains bad characters such blank space.
3. Visual Studio constructed an application that won't run anywhere much less on XP.
4. The supporting libraries are not properly installed (e.g. .NET Framework4, and VCREDIST).
Retorts:
1. The file wasn't downloaded from a website and is intact.
2. The filename path doesn't contain any spaces.
3. The application runs under Windows 8.1. Also on Windows 7.
4. The supporting libraries are properly installed.
So, what's the problem? One surely will not discover the root cause from "not a valid application."
Body must be 4 to 60000 characters long. I had put the code here. It isn't 60000 character long. But it validated as if there are more than 60000 characters. Sorry for the incomplete submission due to website construction error.
MARK D ROCKMANHi F7H2fw,
How did you develop the application ?
Here is a similar symptom and this may explain the issue somehow:
Setup.exe is not a valid Win32 application
http://blogs.msdn.com/b/vsnetsetup/archive/2012/10/16/setup-exe-is-not-a-valid-win32-application.aspx
I suspect there is a compatibility issue here .
Considering this is more likely a developing issue .It is recommended to ask for help from our MSDN Forum .They are more familiar with the developing issue .If it is possible ,please attach the code in that thread .Thanks for your understanding and cooperation.
MSDN Forum
https://social.msdn.microsoft.com/Forums/en-US/home
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
I bought a new wireless keyboard 3 days ago and the number "1" key is not responding. My old wireless keyboard did the same. What am I doing wrong with the setup or installation.
I bought a new wireless keyboard 3 days ago and the number "1" key is not responding. My old wireless keyboard did the same. What am I doing wrong with the setup or installation.
-
Windows 7 Blue Screen of Death from Apple Wireless Keyboard?
I've installed Windows 7 with Boot Camp 3.0 drivers on my Mac mini, and I suppose overall, I'm enjoying it. However, I'm getting a blue screen that seems almost random. Keyword is almost.
I've got my Apple Wireless Keyboard and Mighty Mouse paired, and they're both working well, however, I do believe I am getting some blue screens from my wireless keyboard.
It seems, at random intervals (usually when I haven't touched the keyboard and mouse for awhile) I get an IRQL blue screen and no information about what's exactly causing it. For example, if I'm sitting in the other room listening to music for awhile, and I come back and press the "next" media button on my keyboard, it'll crash and give me the blue screen. However, I've also tried pressing another random button (shift) to "wake" the keyboard if it had fallen asleep, which also results in a blue screen. The blue screens ONLY show up when I give input via the wireless keyboard. Or, if I leave the computer on overnight to download a file or something, the screen will sleep (which it should) then I'll press a button on the keyboard, the screen will stay asleep, and the computer will restart. Which is just a hidden blue screen I'm assuming.
I've tried reinstalling Windows (Clean/fresh install of course), installing/uninstalling drivers, pairing and re-pairing. I've also removed unnecessary/non-Windows 7 drivers that were installed with Boot Camp.
Outside of this blue screen, I am quite impressed with Windows 7. I just can't figure out what's going on. Is there any place I can get a description of what's causing this crash? Does anyone know what's happening or know a solution to this?
Thanks in advance, if you need more details, please ask.Experiencing exactly the same symptoms, bugcheck/bluescreen only when touching the Apple wireless keyboard after a period of inactivity.
I have an 20" iMac, just upgraded Leopard -> Snow Leopard latest minor version and updated to Boot Camp 3.1 hoping they provided a fix, but the driver at fault (keymagic.sys) doesn't look updated and the issue is still there
Hopefully someone from Apple dev support is reading this, here's all the info I could squeeze from the crash dump:
=============================================
* Bugcheck Analysis *
IRQLNOT_LESS_OREQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff80002e33440, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e33440, address which referenced memory
Debugging Details:
READ_ADDRESS: fffff80002e33440
CURRENT_IRQL: 2
FAULTING_IP:
nt!IoIsWdmVersionAvailable+0
fffff800`02e33440 80f906 cmp cl,6
CUSTOMERCRASHCOUNT: 1
DEFAULTBUCKETID: VISTADRIVERFAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88002f2f0c0 -- (.trap 0xfffff88002f2f0c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002f2f100 rbx=0000000000000000 rcx=0000000000000006
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e33440 rsp=fffff88002f2f258 rbp=fffff88002f2f2b0
r8=fffff80002a4f000 r9=0000000000000000 r10=fffffa80027f3010
r11=fffff88002f2f208 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!IoIsWdmVersionAvailable:
fffff800`02e33440 80f906 cmp cl,6
Resetting default scope
LASTCONTROLTRANSFER: from fffff80002ac0469 to fffff80002ac0f00
FAILEDINSTRUCTIONADDRESS:
nt!IoIsWdmVersionAvailable+0
fffff800`02e33440 80f906 cmp cl,6
STACK_TEXT:
fffff880`02f2ef78 fffff800`02ac0469 : 00000000`0000000a fffff800`02e33440 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`02f2ef80 fffff800`02abf0e0 : 00000000`00000000 fffffa80`03375d90 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f2f0c0 fffff800`02e33440 : fffff880`04a02e5d fffffa80`02a3add0 fffffa80`027e8b40 fffffa80`02a3add0 : nt!KiPageFault+0x260
fffff880`02f2f258 fffff880`04a02e5d : fffffa80`02a3add0 fffffa80`027e8b40 fffffa80`02a3add0 0000057f`fd5c5228 : nt!IoIsWdmVersionAvailable
fffff880`02f2f260 fffffa80`02a3add0 : fffffa80`027e8b40 fffffa80`02a3add0 0000057f`fd5c5228 fffff880`04a02dfc : KeyMagic+0x2e5d
fffff880`02f2f268 fffffa80`027e8b40 : fffffa80`02a3add0 0000057f`fd5c5228 fffff880`04a02dfc fffff880`00e5a2a7 : 0xfffffa80`02a3add0
fffff880`02f2f270 fffffa80`02a3add0 : 0000057f`fd5c5228 fffff880`04a02dfc fffff880`00e5a2a7 fffffa80`02a3add0 : 0xfffffa80`027e8b40
fffff880`02f2f278 0000057f`fd5c5228 : fffff880`04a02dfc fffff880`00e5a2a7 fffffa80`02a3add0 00000000`00000000 : 0xfffffa80`02a3add0
fffff880`02f2f280 fffff880`04a02dfc : fffff880`00e5a2a7 fffffa80`02a3add0 00000000`00000000 fffffa80`027fd9d0 : 0x57f`fd5c5228
fffff880`02f2f288 fffff880`00e5a2a7 : fffffa80`02a3add0 00000000`00000000 fffffa80`027fd9d0 00000000`00000010 : KeyMagic+0x2dfc
fffff880`02f2f290 fffff880`00e30c9b : fffffa80`027fd9d0 fffffa80`027fd9d0 fffffa80`027fd9e0 fffffa80`027fdc01 : Wdf01000!FxRequestBase::CompleteSubmitted+0x1f3
fffff880`02f2f310 fffff880`00e30dc4 : 00000000`00000002 fffff880`04bbcff7 00000000`00000000 fffff880`04bbcff7 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff880`02f2f380 fffff800`02aab935 : 0d780da4`0da40dd4 fffff880`02f2f420 0d440d78`0d780da4 fffff880`04bbeb52 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff880`02f2f3b0 fffff800`02ac3516 : fffffa80`027e8f2b 00000000`00000000 fffffa80`027fdc70 fffffa80`027e8b40 : nt!IopUnloadSafeCompletion+0x55
fffff880`02f2f3e0 fffff880`04b62323 : fffffa80`027e8b40 00000000`00000000 fffffa80`02655c10 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02f2f4c0 fffff880`04ba24be : fffff880`02f2f590 fffffa80`027e8b40 00000000`00000000 fffffa80`0294f600 : bthport!BthCompleteRequestEx+0x5b
fffff880`02f2f4f0 fffff880`04b9c8d4 : 00000000`00000000 00000000`00000001 fffffa80`02a50c40 fffff880`02f2f6e0 : bthport!L2Cap_CompleteReadIrpList+0xc2
fffff880`02f2f540 fffff880`04b70732 : fffffa80`03349530 fffffa80`0294f5f0 fffff880`00410001 00000005`00000002 : bthport!L2CapInt_ProcessReadBip+0x430
fffff880`02f2f6d0 fffff880`04b70078 : fffffa80`0267f230 00000000`00000000 fffffa80`029b5402 fffffa80`02670000 : bthport!HCI_ProcessAclReadBip+0x642
fffff880`02f2f7a0 fffff880`04b988d9 : fffffa80`0267f230 fffffa80`03036702 fffffa80`026c0ab0 00000000`00000000 : bthport!HCI_ProcessAclRead+0x214
fffff880`02f2f810 fffff880`04b66201 : 00000000`00000000 00000000`00000000 00000000`00000056 fffffa80`026c0ab0 : bthport!HCI_ProcessMpBip+0x61
fffff880`02f2f880 fffff880`04b4d327 : fffffa80`0294f4f0 fffffa80`026c0ab0 00000000`00000000 fffff800`02ac59fa : bthport!BTHPORT_RecvMpBip+0x41
fffff880`02f2f8d0 fffff880`04b5399f : 00000000`00000000 fffffa80`00cd3910 fffff880`04b56388 fffffa80`00cda820 : BTHUSB!BthUsb_ReadTransferComplete+0xf7
fffff880`02f2f930 fffff880`04b53c31 : 00000000`00000003 fffff880`02f2f9f0 fffffa80`00ca2d00 fffffa80`00000012 : BTHUSB!UsbWrapWorkRoutine+0x17b
fffff880`02f2f9b0 fffff800`02ac3516 : fffffa80`00cd3bdb 00000000`00000000 00000000`00000000 00000000`00000000 : BTHUSB!UsbWrapInterruptReadComplete+0x1dd
fffff880`02f2fa40 fffff880`044135d9 : fffffa80`01e81050 fffffa80`00cda700 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02f2fb20 fffff880`04413ab7 : fffffa80`028ef502 fffffa80`00cd3910 00000000`ffffffff fffffa80`01e81ea8 : USBPORT!USBPORTCoreiCompleteDoneTransfer+0xa15
fffff880`02f2fc00 fffff880`0441164f : fffffa80`01e81ea8 fffffa80`01e811a0 fffffa80`01e82040 00000000`00000000 : USBPORT!USBPORTCoreiIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02f2fc60 fffff880`04402f89 : fffffa80`01e81050 00000000`00000000 fffffa80`01e81e02 fffffa80`01e81ea8 : USBPORT!USBPORTCore_UsbIocDpcWorker+0xf3
fffff880`02f2fca0 fffff800`02acc5dc : fffff880`02f07180 fffffa80`01e81ea8 fffffa80`01e81ec0 00000000`00000000 : USBPORT!USBPORTXdpcWorker+0x1d9
fffff880`02f2fcd0 fffff800`02ac96fa : fffff880`02f07180 fffff880`02f11f40 00000000`00000000 fffff880`04402db0 : nt!KiRetireDpcList+0x1bc
fffff880`02f2fd80 00000000`00000000 : fffff880`02f30000 fffff880`02f2a000 fffff880`02f2fd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
KeyMagic+2e5d
fffff880`04a02e5d ?? ???
SYMBOLSTACKINDEX: 4
SYMBOL_NAME: KeyMagic+2e5d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: KeyMagic
IMAGE_NAME: KeyMagic.sys
DEBUGFLR_IMAGETIMESTAMP: 49c160ec
FAILUREBUCKETID: X640xA_CODE_AV_BAD_IPKeyMagic+2e5d
BUCKET_ID: X640xA_CODE_AV_BAD_IPKeyMagic+2e5d
Followup: MachineOwner
---------
Maybe you are looking for
-
IMovie HD keeps quiting unexpectedly?
Hi, I have an MAC OS X 10.4.8 and I use iMovie HD. Everytime I try to record on iMovie it quits unexpectedly, it lets me open it but it gets to about 6milliseconds then it quits. I have a 55.57GB harddrive but there is 27.07 free, is that enough spac
-
How to test restore in another server?
Hi, I want to test full backup (hot backup using RMAN) of my DB (11.2 SE) on another server (I didn't install DB on yet). Saad,
-
When watching a video, it will only play the beginning part of the video and not the entire thing.
I've made sure i've updated my plugins and made sure my graphics drivers are all up to date. I'm running windows 7, & firefox 24. I've noticed ever since firefox came out with a new version of the browser, i'm not able to watch an entire video online
-
Calling the smartform based on checkbox selection in ALV
Hi i displayed the report output in ALV using 'REUSE_ALV_GRID_DISPLAY'. I maintained checkboxes as first column of data. and i also added three user defined buttons like check,uncheck,print form. Now my problem is when user selecting the records in A
-
When I click on the icon at the top left of the page all I ever get is refresh or close. never the Mozilla Firefox page. I have downloaded Firefox , but never get any further. What can I do about this problem?