Windows 7 32bit on iMac 21"5 (late2009) Wireless Keyboard issue

Hello,
I'm using Windows 7 on my iMac since 2011 and I've never had a problem with my bluetooth Apple Magic Keyboard, until three days ago.
While I was browsing the web, the iMac suddenly rebooted and the classic Windows screen showing the loading of new files (with the progress percentage, which normally appears after reeboting the computer after an OS update) appeared. As soon as the computer became operative, my keyboard stopped working.
I tried to install again the drivers supplied by Apple, but it still doesn't work. What should I do ? This sudden reboot certainly deleted or modified some files... (I use a wired mouse so the problem concerns only with my keyboard)

Do you have windows setup to auto install updates? Or recent updates? See if you can roll back your Broadcom driver or use system restore to an earlier time

Similar Messages

My iMac is looking for wireless keyboard but I have a usb and it is plugged in.

my iMac is looking for wireless keyboard but I have a usb and it is plugged in. Right now I am using the one from my old computer. This happened once before and I unplugged/plugged in, restarted. Didn't work. Repeated several times, it finally worked. This time not so much. Any one else have this problem and know how to solve it?

Try turning off Blue Tooth in its respective preference panel. Do not try using the USB keyboard in a USB extender. Connect directly to the computer.

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

Windows XP laptop doesn't connect to Apple wireless keyboard

I'm trying to pair my Apple wireless keyboard to my Samsung N110 netbook using Bluetooth. When go to the Add Bluetooth device, the laptop sees my iMac desktop, but not the wireless keyboard. BTW-the keyboard is NOT paired to the iMac. Samsung support suggested re-installing the Widcomm Bluetooth driver on the laptop, then restarting the laptop. Driver was re-installed successfully, but the keyboard is still not visible. Samsung had no other suggestions except to look for an Apple wireless keyboard driver, but I haven't located that yet nor do I know if that's the solution. Every time I search for Bluetooth devices within range, only the iMac is seen. I've tried pressing the power button on the keyboard while the laptop is searching, but that doesn't help either.
Any suggestions would be appreciated. I'm running Windows XP Home Edition, SP 3. Thanks.

Well try upgrading the firmware of the router & keep on holding tightly
the reset button in such a way that power light is blinking on the
router & then do a complete network power cycle i.e., unplug the power
cables from the modem & from the router & then plug in the power cable
to the modem first once all the lights are solid green you could plug
in the power cable to the router & check out it will definately work!!

Can my early 2008 iMac (intel) take a wireless keyboard?

Sorry for the ignorance, here, but my iMac's keyboard has just gone up the spout. I like the idea of a wireless one, but I don't know whether this iMac can take one

Thanks for your quick reply, Kappy.
However, I don't understand why a wireless keyboard can't replace the original USB keyboard.

New iMac 27 with the Wireless Keyboard and Magic Mouse

Is it just my keyboard or does the wireless keyboards that come with the iMac 27inch just SUCK? ALWAYS and I mean ALWAYS losing its connection. The keyboard is ALWAYS losing its connection. The mouse, barely, but sometimes, maybe once every 2 days. The keyboard. Several times an feffin day. What gives? Should I have them exchanged or are others experiencing this BS?
Did Apple just RUSH out the new iMacs without properly QAing????? WT*?

I thought I read that with two batteries there is no problem-only with three.
I can only provide a sample of one but the new keyboard which came with my i7 is still at 100%. Regarding the Magic Mouse, I am on my second set of batteries. The i7 is on day 40 of use. I also have a Magic Mouse paired with my 24" 2.8 Intel iMac which has a wired keyboard. The 24" sits idle much of the time and the original batteries show 91%.
Message was edited by: ScotMij

Does the imac come with a wireless keyboard and a wireless mouse?

I am buying an imac tomorrow and I was wondering if I have to pay extra for a wireless keyboard and a wireless mouse.

iMac's come with a wireless keyboard and magic mouse, as the standard fare. So you don't need to pay extra for them. I would recommend purchasing rechargable batteries and a charger, as the mouse does chew through batteries.

Windows 8.1 Ent. Helix - UltraNav, TouchPad and Keyboard issues

System:
Helix 3701XXX
Windows 8.1 Enterprise 64-bit
Third Apps installed
Latest Lenovo Drivers installed
Problem:
Latest versions of ThinkPad Synaptic UltraNav Drivers (versions 18.0.7.39 to .57) causing keyboard to act sporadically. This would cause programs to automatically open and key inputs to continuously active (repeating the enter key). Other behaviors include ignoring touchpad input and ignoring certain keys on keyboard. The problem has been reported by 5+ systems.
When it occurs:
The problem is intermittent; it often occurs after waking the system up from sleep or from a locked state (Windows lockscreen). As a workaround, the user has to press the ESC key, CTRL+ALT+Delete or restart the system in order to regain functionality. Uninstalling the driver application also resolves the issue.
Anyone else experiencing this issue? Any advice from Lenovo staff would help.

Yes, I get similar issues. Although in my case it is mainly:
i) the mouse point does not respond after resuming from sleep - CTRL-ALT-Delete or ESC normal resolves this
ii) windows or programs open on resume from sleep as if the mouse button was depressed (could be enter key however). Again CTRL-ALT-DEL or ESC can resolve this
I'm pretty sure that this is a driver issue as it has only been the last 6 or so months I've experienced this
I'm running Windows 8.1 Pro

Did your imac come with a wireless keyboard that has dead batteries inside?

I bought my new imac yesterday but the pre-packed batteries inside the keyboard are dead already...I had to replace them with new ones.
Does it happen often? and why? I thought the keyboard should be off and in sleep mode when its new.

Is this a comedy central or what...
The inference is that if it is unusual to have dead batteries in a keyboard, then -
• the machine may have been in a storeroom for a long, long time. With batteries sitting long enough to go dead, there may have been some leakage from the batteries.
• some enterprising clerk may have swapped keyboards with a defective one brought in.
• more likely, it may have been put into use at one time, perhaps even as a floor demo, then repackaged and sold as 'new' rather than as a demo unit.
None of those instances is funny.

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

Using the A1016 Wireless Keyboard with Windows

So, this isn't a question, it's more like a 'For What It's Worth'. I found some bad information in some archived posts here, and it seems I'm not allowed to resurrect them lol. Anyway, the rumor on the forum is that this old keyboard won't work with Windows 7, 8, etc., but that is just wrong!
http://www.silly-science.co.uk/2012/06/05/pairing-apple-1st-gen-keyboard-a1016-w ith-windows-7/
1) First, have another functioning keyboard hooked up to your PC, in such a way that it is fully operational as an input device for said PC.
2) Batteries in your wireless keyboard are good, right?
3) Slide the switch on the keyboard to 'on'.
4) Go into the Bluetooth control panel in Windows and if the keyboard shows up as a device, hit the connect button.
5) ** Here's the new part ** on your wireless keyboard, type 1 2 3 4 [return].
6) Now Windows will prompt you for a code. Type 1 2 3 4 [return].
Yay! I typed this on a homemade Windows 8.1 PC using my antique Apple Wireless Keyboard A1016. Serenity.

Success! I finally got the older, plastic, white Apple A1016 Bluetooth Keyboard to work on Windows7. I have tried several attempts and multiple days and dont remember the exact steps but I wanted to let folks know the general steps and patience in making it work. You will likely have to try many many times to get it working.
-First, stabilize your Windows BT device drivers i.e., make sure your bluetooth driver works with another device such as a BT mouse. This way, you know your BT driver is working correctly in Windows 7
-Turn on the A1016 power switch until it starts to blink. On your BT menu, click "Add Device" or something equivalent.
-Once it detects the A1016, you can right click on the BT KB icon. I noticed that the first tab did not display the "HID Device" check box option but the 2nd tab, allowed me to change the name of the KB. It is fine if you do not see the "HID Device" check box, as suggested by other sites.
-Click to Connect --- this is where I spent multiple days to get it right.
-It may or may not display a page where it asks you for a pairing code and sometimes, a screen just disappears in a flash. I got multiple pages where I was asked to enter a code (and then failed to connect), got to a page where it asked if I wanted to enter my Code or System generated (also failed to connect) but finally I got to a point, when I hit Connect or Next, it just stayed on the same page (as though nothing is happening), except that is says "Connecting"
At this point, enter "0000" or "1234" or any series of #s on an existing/usb or wired keyboard. Immediately enter the same "0000" or your choice of #s on the A1016 and hit return. Success!
I have spent countless days googling suggested steps and have seen all the problems that others have described but entering on the wired keyboard and then entering the same code on the A1016 was the step that made it work. I liked the look and feel of the A1016 hence I spent an enormous amount of time to make it work but I am glad I did.

IMac Bluetooth not connecting to keyboard

Hello All, I have a new 2013 iMac with an Apple Wireless keyboard and Magic trackpad and for some reason the bluetooth stopped working the other day. I have tried deleting the bluetooth.pst as well as resetting the PRAM and doing a softwear update. I updated to Mavericks and that still didn't fix it. Neither the Trackpad or the Keyboard are paired with anything else and the light is flashing on both meaning they are in discovery mode

yes i have changed the batteries twice just to make sure and tried connecting it to my friends imac and it worked perfectly.Tried my old one which has a damaged key and it automatically connected

Windows 8 USB wireless keyboard and mouse?

I have a MacBook Pro 13.3" late 2011 base model running Mac OS X 10.7.4 (Lion). I am planning on installing the Windows 8 Release Preview (64-bit). The requirements state that I need to use a USB keyboard and mouse to get the drivers going once I am in Windows. My question is whether my Microsoft wireless keyboard and mouse, which connect via a USB to my MacBook, will work in Windows 8 with the same functionality so I can run the executable file to download the drivers. Also, as a follow-up question, is Windows 8 Release Preview (64-bit) a safe install for me through Boot Camp?
Thanks in advance,
Rith=Apple4Life

Really? Have you installed Windows 8 onto your Mac because in some videos I have watched, I have seen people not being able to use the built-in keyboard and trackpad until the drivers are installed by using the .exe file. Anyway, for backup, I have secured a wired keyboard and mouse just in case and will be installing Windows 8 soon. It would be nice to download the RTM version, but I wouldn't trust any source other than Microsoft itself.
Thanks,
Rith=Apple4Life

Will the ex emulator work in windows 7(32bit) on a bootcamp iMac?

I have an intel iMac (Snow Leapard) running Windows 7 (32bit) using the bootcamp partition.
Microsoft has an XP emulator that will run on Windows 7.
My concern are the drivers for the emulator.
Bootcamp has translation drivers that allow a Windows OS to run using Mac drivers.
Has anyone done this?
Run the xp emulator on a Windows 7 (32bit) iMac using bootcamp?

of you by emulator mean virtual machine then virtual machines are virtual so they don't have direct hardware access and therefore does not require drivers provided by the user

My Windows XP 32bit Wireless quit working on my 2008 iMac, works great in Apple mode.

Hello all,
My 2008 iMac in Windows XP 32bit mode (for work programs) stopped working. The crazy thing is that its AWESOME in Apple mode, but in Windows mode, it fails totally. I cant communicate with the modem. I have tried reloading the drivers for the Broadcom from the OSX CD/Bootcamp Drivers, but that did nothing.
Any idea how to fix this?
Please help me. I have spent a week on this, and its been malfunctioning for several months now. I must get it working right.
lh

A couple of things, first there is a Boot Camp forum so if you want support I'd think that would be the best venue.
As you have discovered Boot Camp only supports Windows 7 on the current machines so you are in a box if you must run on Boot Camp. However instead of using Boot Camp you can use virtualization software such as Parallels or VMWare Fusion which perform very well. The are many advantages of virtualization one primary one is you can still run XP. Others include being able to run MS Windows within OS X so you can use both OS's simultaneously. The only downside to virtualization is if you run graphics intensive apps (3D Game, CAD/CAM, 3D rendering) then performance will not be as good as with Boot Camp. However for almost all other apps performance is really good and most cases users don't complain.
While it will cost a few dollars (I believe about $79) virtualization is a very solid alternative.

Windows 7 32bit on iMac 21"5 (late2009) Wireless Keyboard issue

Similar Messages

Maybe you are looking for