The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    dv6 IEEE1394/ Bluetooth Mouse issues

    Discussion in 'HP' started by katsura, Jul 25, 2010.

  1. katsura

    katsura Notebook Enthusiast

    Reputations:
    0
    Messages:
    15
    Likes Received:
    0
    Trophy Points:
    5
    Hi Folks,

    I got a dv6-2120TX about 3 weeks ago (on discount for AU$897) to replace an old VAIO.

    I have re-installed Win7 Pro 64 bit on it and so far I'm quite happy with the performance.

    I've paired the laptop with a Microsoft Wireless Laser Mouse 8000 on bluetoooth. There seem to be a problem, the mouse will stop working randomly all of a sudden - I've not be able to pinpoint any sequence that leads to this - it does seem to be purely random.

    I tested it with another Laser 8000 and the same happens.

    When it happen, the mouse cursor just stops moving and buttons also do not respond (the Synaptics pad still works at this stage).

    Now if I go into Device manager and go a Scan for Hardware Changes the mouse will be back again. Wonder what's causing this?

    Also, I found I often get a code 43 (Windows has stopped this device sue to a reported error) on my IEEE 1394 OHCI Compliant Host Controller. If I remove the device then do the Scan Hardware it will be back working.

    Does anyone else experience these random issues?
     
  2. Power2Go

    Power2Go Notebook Enthusiast

    Reputations:
    0
    Messages:
    35
    Likes Received:
    0
    Trophy Points:
    15
    Totally random, but go into device properties and right click on the bluetooth chip, then go to the last page and uncheck "allow pc to turn off to save power" or something to that effect.

    Perhaps the pc is shutting down the Bluetooth chip to conserve power which disables your mouse. Give it a shot.
     
  3. katsura

    katsura Notebook Enthusiast

    Reputations:
    0
    Messages:
    15
    Likes Received:
    0
    Trophy Points:
    5
    Cheers for the suggestion!

    Funny thing is, just when I was reading your post and about to write a reply the BT mouse went dead again.

    I have already unticked allow sleep on the BT device. So the issue is somewhere else. If this carries on I'm going to have to do a re-install :(
     
  4. katsura

    katsura Notebook Enthusiast

    Reputations:
    0
    Messages:
    15
    Likes Received:
    0
    Trophy Points:
    5
    Oh - and just when I finished posting that last post, the BT mouse came back again. This is weird...
     
  5. katsura

    katsura Notebook Enthusiast

    Reputations:
    0
    Messages:
    15
    Likes Received:
    0
    Trophy Points:
    5
    LOL! The issue has been resolved - the Allow Windows to Turn Power off option WAS ticked/ enabled for the BT radio.

    I THOUGHT I had disabled that Power Management option as usually it's one of the things to do on my list after an OS install, but this time I missed it.

    So thanks Power2Go for the suggestion.

    Now I need to figure out the Firewire host controller issue, gah.
     
  6. Power2Go

    Power2Go Notebook Enthusiast

    Reputations:
    0
    Messages:
    35
    Likes Received:
    0
    Trophy Points:
    15
    Your welcome, glad I could be a help.
     
  7. katsura

    katsura Notebook Enthusiast

    Reputations:
    0
    Messages:
    15
    Likes Received:
    0
    Trophy Points:
    5
    I found the reason for the Code 43 and Yellow exclamation mark error or the Firewire (and sometimes, card reader) in Device Manager.

    Again it's caused by power management feature - these 2 devices don't offer a power save option in the control panel, HOWEVER, if you go tot he BIOS you can see they can be enabled for power management.

    Turn the power management off in BIOS for these devices will cure the code 43 error.

    Any one with a similar problem can try this out.