Apple Wireless keyboard (aluminium) on G4 Cube

Having just spotted that there have been two different aluminium Wireless keyboards release by Apple over the last 2/3 years, I have also noticed that the minimum MacOS has risen from 10.4.10 for the original to 10.5.x for the current one.
...but what -exactly- is the issue with running the new one on an older Mac? Is it a partial functionality issue or plain old 'just wont work' issue?
As the G4 Cube maxes out at running MacOS 10.4.11, I'll need to get the older A1255 model but finding these is getting difficult now..;-(

My experience with the current Bluetooth KB and Leopard might or might not be helpful, but what happened, I started trying to use it with my G5 running Leopard and everything worked except that the function keys (F1-F12) only worked as function keys. I solved that with the aluminum KB update, but I know there isn't such an update for Tiger, so my assumption is that you would just be stuck with it like mine was pre-update. I may be wrong though.

Similar Messages

Unable to pair Apple Wireless Keyboard in OS X 10.5.8

Hello everyone,
This is my first post here so if I mess it up, pls don't dog me too much...
I'm currently running OS X Tiger on a Dual PowerMac G5 2GHz with 3GB of RAM and all is well with the world. However, in an attempt to upgrade and become familar (more so) with OS X10.5 I've found that I am unable to pair with my wireless keyboard. I'm running 10.5 on a seperate drive. It sees the dongle, just won't pair with it. The Bluetooth dongle I'm using works fine in OS X 10.4.11, has for years. Any clues, is there something I'm missing?
I've read about Bluetooth issues with Leopard so I thought I would see if i could find an answer here. The keyboard is the original Apple wireless keyboard that came out a few years ago, Model M9270LL/A.
Hardware Overview:
Machine Name:    Power Mac G5
Machine Model:    PowerMac7,3
CPU Type:    PowerPC G5 (2.2)
Number Of CPUs:    2
CPU Speed:    2 GHz
L2 Cache (per CPU):    512 KB
Memory:    3 GB
Bus Speed:    1 GHz
Boot ROM Version:    5.1.8f7
Apple Bluetooth Software Version:    1.9.5f4
Hardware Settings:
PowerMac G5:
Address:    00-02-72-08-1e-0c
Manufacturer:    Broadcom
Firmware Version:    3.16389 (3.17166)
Bluetooth Power:    On
Discoverable:    Yes
HCI Version:    3 ($3)
HCI Revision:    16389 ($4005)
LMP Version:    3 ($3)
LMP Subversion:    17166 ($430e)
Device Type (Major):    Computer
Device Type (Complete):    Desktop Computer
Composite Class Of Device:    1057028 ($102104)
Device Class (Major):    1 ($1)
Device Class (Minor):    1 ($1)
Service Class:    129 ($81)
Requires Authentication:    No
Thanks for any help you folks might wish to provide me in advance.
Message was edited by: Onatopa

I don't think you're following me very well Mr Williams. I appreciate your attempt to assist and hopefully I won't come across as an **** here but, you're not helping. I will agree you, it seems to be a software issue...and it's called Leopard!
Let me explain something. I have not migrated this system, as per se, and for obvious reasons. The system has 2 HDD's. One has 10.4.11 on it and the other HDD has 10.5.8 installed. I can go from one to the other and it's the way I will continue to work until this problem has been resoved, if ever. I can NOT be productive without the Mac running, regardless of which OS. I'm attempting this because I have apps that must have Leopard, so I'm trying to make it work.
Just to be clear, I gave-up running OS X 10.3 several years ago but did not do so without kicking and screaming the entire way. Now, I'm comfortable with Tiger and I'm very glad I upgraded, as it's a much more stable OS but at this rate I'm about ready to give-up. I don't need Leopard and I don't want it, nor do I like the look and feel of it, I just wanted to try and attempt to upgrade and see if I could run some newer apps that won't run on Tiger. I will probably NEVER upgrade to an Intel Mac, even if I could afford to do so. And I will NEVER run Micro$oft Windoze on a Macintosh...period - EVER! That to me is just sacrilege...so just call me a purist, I care not. If I want to run that OS I'll do it on a PeeCee.
Back to the dicussion.
I'm typing this reply on the PowerMac running 10.4.11 using the keyboard in question and my Bluetooth dongle. And YES, the keyboard is the older, white keyboard. Did I not share the model # in the original post, Apple Keyboard model M9270LL/A ? Did you not Google that if you're not familiar with these Model numbers?
You said, "...Another thought: did you "unpair" the keyboard from the old system before trying to pair it with the new one?..." What exactly does that mean? That's makes no sense at all. "Can you "see" the keyboard in the bluetooth setup window when trying to set it up or not?" What does my original post say?? YES, I can see the keyboard in OS X 10.5.8, I just can not pair with it.
As a last resort I have installed the Apple Aluminum Keyboard Update, as per your suggestion, even though I don't have an aluminium keyboard and this 'update' installed successfully but my keyboard, although seen will still not pair with the dongle. I will NOT go buy a Al Keyboard just to test this issue. The only thing I've thought about purchasing is the Bluetooth module so that I don't need to use a dongle, but those are expensive and often hard to find. I have also removed the prefs file from /user/Library with no effect.
I almost forgot. I also have another BT dingle from Kensington and although the system sees it as does the other, it does not pair with the keyboard either. That dongle works fine on my PeeCee laptop without any problems, so both dongles are functioning correctly. Do you have any other suggestions you would like to share?
Thank you for your time.
< Edited By Host >

Apple Wireless Keyboard on iMac 20

Good morning everybody, two months ago i have installed an apple wireless keyboard model M9270T/A (not aluminium), model with numeric pad.
It runs properly since yesterday, when it stops to run.
I have tried to reinstall, it is discovered, but it doesn't linked and the led continue to lamp. So the system tells me that this bluetooth configuration is not supported by this Os X (but until yesterday it runs properly!?!?)
I have:
1) replaced the batteries
2) followed strictly what reported on support (turn off the keyboard, follo guidelines, update the latest version of software)...
No way...does anyone can help me?
Thanks in advance

Did you manage to get around your issue without resorting to a wired keyboard? My brother has the same issue.

Powering Apple Wireless Keyboard

I know this is a keyboard issue, but there's no keyboard Discussion area, and I'm using it with a MacBook Pro... thanks in advance for any help.
Using a new Apple Wireless Keyboard (the latest tiny aluminium one), it seems unclear how to use something as simple as the power button!
Apple say "The keyboard automatically powers down when you're not using it and turns on instantly as soon as you start typing. This intelligent power management means you'll get up to nine months of battery life based on average usage patterns." I get all that - sounds great! But, they go on to say "It also has an on/off switch for when you're away from your computer for a long time." But there's nothing to explain how that works. If I stop working, turn it off and walk away, there's nothing to indicate that it's turned off. When I come back to work, do I need to turn it on again or does it just power up automatically from the 'turned off' state? If so, What did the turning off actually do? Or this a 'fridge light' situation??
Point is, I see no point in the power button if the unit turns off automatically when I stop using it, and there's nothing on the device to indicate whether it's been switched off or on. And it has used the new set of batteries far too quickly for my liking (less than a week), especially considering that Apple suggest a long (up to nine months) battery life. Mind you, as is always the case, the "up to" terminology also means "down to" (zero) I guess.
Any help or advice much appreciated. Thanks.

I had the same questions after installing my keyboard. When I powered it up the first time, the power light came on and then went off. My power light seems to be off even when I'm using the keyboard to type. So that's not a valid indication of "sleep mode". However, I found to turn it off completely I pushed the power button, and the power light came back on. Then I pushed and held the power button for a few seconds. The power light went out and I saw a keyboard icon on my display with "connection lost" below it. Powered it back on by pushing the power button and was back in business immediately.
The manual is skimpy and confusing. It reads, "Note: When the Power On light is off, the keyboard is off." That's on page 3. Well it's working well right now, with the light off. If the manual is correct (it's not, but if it were) then my batteries would last a very, very long time.
Nice keyboard though, and very portable for a ModBook - if I ever get one.

Trouble with keys on apple wireless keyboard and MBP

I have attached my Apple wireless keyboard to my MBP and I want to use it with the onboard screen. It properly synced, and I know it reads the keyboard because the F keys work, and the delete button works, and it even can wake the computer from sleep mode. However the problem is quite simple, the alpha keys do not work. I can turn up my brightness, or volume cycle through my "spaces" on leopard but am still unable to type. I have looked all over for other cases of this and can not find it. Is it possible that the apple wireless MUST be used with an external monitor only? I have not attempted that yet because I have been away from my studio for a few weeks.
If anyone could shed some light on this situation it would be greatly appreciated.
Thank You.

The "wireless mouse/keyboard firmware update 1.1" is for the old white plastic wireless mice and keyboards , Sean. Is the one you are trying to use one of these, or is it one of the aluminium ones?
If it is the aluminium one, then the update you might need is Aluminum Keyboard Firmware Update 1.0 - http://www.apple.com/support/downloads/aluminumkeyboardfirmwareupdate10.html
None of the updates should be needed to prevent the sort of problem you report though.
Is this keyboard newly purchased, or one that you have had for a while and that ahs worked in the past? It may simply be defective.
The only other thing I can think of, apart from conflict with a third party keyboard driver or the like, is a corrupted system file of some kind, in which case an "archive and install" of the OS might be needed to fix it I'm afraid.
Cheers
Rod

I have an Apple wireless keyboard that I use with my iPad 2. Does it work with the iPad 3?

I have an Apple wireless keyboard synced to my iPad 2. Can sync this same keyboard be used with my iPad 3? If so, what are the syncing instructions?

Assuming you are talking about the aluminium keyboard the answer is yes. I had some problems trying to get my iPad 2/keyboard combo to 'forget' their connection but one complete the keyboard connected to my iPad 3.

Trouble pairing Apple Wireless Keyboard with N95. Please help.

I bought the new aluminium Apple Wireless Keyboard today and tried pairing it with my N95 (firmware v20.0.015) using the 'Wireless Keyboard" application but it refuses to connect!
Would anyone be kind enough as to shed some light on this issue I'm experiencing?

The process is quite simple:
- Turn Bluetooth 'on' in your N95 - Settings\Connection\Bluetooth\On.
- if your wireless keyboard is on, turn it off then on again. This will make it discoverable for 3 min.
- go to 'Wlss.keybd' app on your N95....Menu\Office\Wlss.keybd and open it.
- go to Option menu and select 'Find keyboard'. This will search for available bluetooth devices. Your keyboard name should show up here. When it does, you can press 'stop' so that the phone stops looking for additional devices.
- select the keyboard from the list of found bluetooth devices. You will then go through a sequence of code inputs on both your phone and keyboard (just follow the prompts on the phone) which will 'pair' your keyboard to your phone.
Hey presto, your phone should now be connected to your keyboard! Hope this works for you.
killkenny

Wacom Tablet causes Apple wireless keyboard to stop working.

My Wacom tablet/pen causes my Apple wireless keyboard to stop working. While working on a photo in Photoshop using my Apple (usb) mouse to make selections the keyboard works fine. When I use the Wacom Pen to make selections, not immediately but anywhere from five to ten minutes into it, I hear what sounds like a chirp from my computer (Mac Pro) and my keyboard stops working. The command, option, control and direction keys still work but not the number and letter keys. I have to connect a spare Logitech keyboard via USB in order to continue and not loose my work. After awhile I will hear the chirp again and the Apple keyboard will start working. This will continue to occur at irregular intervals. Without the spare keyboard I've had to reboot my computer (loosing all the work on the photo) to get the keyboard working again, but only for it to reoccur. Any suggestions to fix this would be appreciated.

The Mac inherently keeps all input methods active, such that you could type alternate keys on alternate keyboards.
If you have third party add-ons that might change the way Bluetooth works, those would be the primary suspects.
Be sure all your Drivers are completely up-to-date, and batteries in battery-powered devices are still strong.
Bluetooth uses the same part of the frequency spectrum (but a different modulation technique) as cheap WiFi Routers, baby monitors, and microwave ovens. if you live in a busy apartment building, there may be very high levels of interference.

HT201178 how do you unpair an apple wireless keyboard?

I have an apple wireless keyboard, but I recently just purchased and apple keyboard with numeric keypad and I am wondering if I need to unpair the apple wireless keyboard from bluetooth or I dont know but, my new keyboard is wired so it should work already, correct?????

Hello,
I believe that when you plug in the USB keyboard, that one should control the device.
However, why not either unpaid or turn the Bluetooth device off?
Barry

How do you get the Apple Wireless Keyboard to accept function keys?

I use the Apple Wireless Keyboard with my iPad2 and I use the VPN to connect to my work-related software which requires that I use some of the function keys as actual F1, F2, F3,...etc. When I hit F2, the iPad2 responds with the Screen Brighter action. How do I get the keyboard input to just be F2? Thanks!
Jeff Lehmer

Thanks. But I tried that and nothing happens. I've looked though all the System Preferences sections and can't find anything on this.

How do I pair my new Mac mini (mid 2011) and white Apple Wireless Keyboard (2003)?

I just bought a new Mac mini (mid 2011) and can not set it up via my Apple Wireless Keyboard (2003). I'm disheartened but not surprised that my Bluetooth 4.0 Mac isn't backwards-compatible with my Bluetooth 1.0 keyboard. But I can't find any documentation confirming the fact that my non-paired, but tested & perfectly functioning keyboard will not work with current Macs.
I was however, able to locate a tech support doc (http://support.apple.com/kb/HT4112) that mentions my Apple Wireless Keyboard (2003) is not compatible with iOS devices. (Which is not critical because iOS provides a non-physical keyboard. Aside, it would be lovely were Apple to add a non-physical keyboard to Mac OS X, if only so new desktop owners can continue to set up their Macs in a pinch.)

I just bought a new mini mac (lion 2011) with a wireless keyboard. I could not get the mac to recognise the keyboard. Spent several hours back with the Genius team who replaced keyboard and mac but did not get anywhere. They gave me a wired keyboard, was able to configure the mac and then it recognised the wireless keyboard.
Seems this is a problem with the new mac/OS

New apple wireless keyboard & iPad 3 pairing question

Bought a new Apple wireless keyboard this week. Had some trouble pairing with iPad 3. Took me 4-5 attempts but it finally paired successfully after 10-15 minutes. Question for all you gurus... When the wireless keyboard arrived on Friday, I first paired it with my MacBook Pro. Could that have caused issues when I re-paired the wireless keyboard (today) with my iPad 3. And further, this will sound like a silly question, can the wireless keyboard be paired with two devices? I don't mean simultaneously. Does it screw up any settings to use the key board with separate devices/computers? Wondering -- if I keep my wireless keyboard at my office -- can I go to work with either my MBP or my iPad and simply use this one wireless keyboard? Or should each device have its own dedicated wireless keyboard? That seems redundant but I kind of love this keyboard already and would be willing to buy a second, if need be. Obviously, I don't want to spend extra money if it isn't necessary. Am I going to have to re-pair the keyboard and device each time I switch between the iPad and the MBP? Thanks all. You are always helpful and I appreciate it.

Thanks for the quick reply Skydiver! So...I really should buy a second wireless keyboard so that I don't have to go through the hassle of re-pairing the keyboard when i switch devices, yes? Yes, I believe I've answered my own question as I now sit here with my MBP attempting to pair it to the keyboard. Oy. Taking forever. I don't mind buying a second -- for $69, it seems to be the most efficient thing to do. Now I just need to figure out a way to designate which wireless keyboard goes with which device. Time to buy a little sticker! Thanks again.

Apple wireless keyboard, mouse and trackpad battery management is SO MESSED UP! HELP!

I have like 2 dozen batteries that I have swapped in the days since 10.8.4. The **** thing just drains in like 4 days. I am using apple wireless keyboard and mouse/trackpad (either at a time) with my macbook pro that is in closed lide clamshell mode less than a feet away from these devices. the batteries are draining like crazy! 3-4 days! they used to work for like weeks! i have heard in another thread that there is some bluetooth driver issue.
i know many of you would come up with things to check for like other wireless devices, etc. but like I said i have been using this since 2011 and only now since 10.8.4 they have gone crazy!
whats even more weird is that i dont think the batteries are really draining. its something to do with the battery management hardware/software that fails to see the power inside. when i remove the currently dead battery and put in one that was indicated having 0% charger i get a magically 50+ % sometimes event 80! a reboot and the figure is something else! since this is happening with all the three input devices i think its something to do with macbook pro.
any fix?
Neerav

SOLUTION:
Put the devices in "Manual paring mode"
1. Turn device off.
2. Push and hold in power button until the LED starts flashing on and off.
3. Try the paring procedure.
4. It should work.
I went to the apple store and this is what they did. They got the trackpad paired no problem, but the keyboard would refuse to make connection. At first they blamed windows and didn't want to replace the keyboard because it worked fine under OSX. However I made them try one of their keyboards and it paired fine. So they ended up swapping out my keyboard for one of the newer ones and now it pairs with both windows and OSX with no problem!

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!
Paul

I'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.

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
---------

Apple Wireless keyboard (aluminium) on G4 Cube

Similar Messages

Maybe you are looking for