HP ProBook 6540b won't boot and caps lock "blinking" continuously.

[matsja59]

Hi,

I'm trying to help a friend with his laptop a Probook 6540b.

It won't boot and caps lock "blinking" continuously.

When I got it caps lock and num lock was "blinking" tre times... indicated memory problems, reseated the memory modules

and the the "tre time blinking" disappeared, but caps lock now blinking continuously and the only way to shot down the computer

is to disconnect the power.

Anyone with some ideas???

Janson 

[SSDdrive]

Hello,

  Have you tried a hard reset? Where you disconnect the battery and anything else, unplug the notebook and then press down on the Power Button for 45 seconds before plugging it back in, but not the battery, and restarting. Hope this helps. Also fyi, an Hp Probook notebook is not considered a laptop.

                                                  'I am a volunteer!

If it were a rattler. . . . Rattle Snake, that is. . . .

[matsja59]

---

@SSDdrive wrote:

Hello,

  Have you tried a hard reset? Where you disconnect the battery and anything else, unplug the notebook and then press down on the Power Button for 45 seconds before plugging it back in, but not the battery, and restarting. Hope this helps. Also fyi, an Hp Probook notebook is not considered a laptop.

                                                  'I am a volunteer!

If it were a rattler. . . . Rattle Snake, that is. . . .

---

Yes I have tried that... 

Thanks anyway.... and for Your information about Notebook 🙂

[SSDdrive]

Hello again,

               Please try this link to restoring the bios:

          http://support.hp.com/us-en/document/c02693833

Hope this helps!

                                                  'I am a volunteer!

If it were a rattler. . . .

[matsja59]

---

@SSDdrive wrote:

Hello again,

               Please try this link to restoring the bios:

          http://support.hp.com/us-en/document/c02693833

Hope this helps!

                                                  'I am a volunteer!

If it were a rattler. . . .

---

Thanks, but I have tried that to,  and from USB key.

Tried to reset "RTC" by removing battery, then when starts caps lock and num lock blink tvice, for BIOS error, then reboot and stop with black screen and caps lock "blinking...

Keepin on trying...  almost everything..

Janson

[Volunteer]

A neighbor had the same problem and asked for my assistance.  I created a rescue disk using my HP desktop running Windows 7 64-bit.  Even though her HP laptop was running Windows 7 32-bit, the disk allowed me to boot into windows on her computer.  I then went to the HP web site and downloaded the latest BIOS and then flashed it to the BIOS chip following the instructions that came with the download.  Everything is working fine now.  Hope this helps.

[Maxfe]

Had the same problem, solved with the following steps:
1) remove the battery
2) press power button
3) vacuum clean the ventilation window for about 1 min
Possibly the last step is the decisive one, since the air flow also cooled down the computer

[3vilrabbit]

My HP 360x had the same problem. When I unplugged the power cord, problem solved...

[truthizwizdom]

For me it was a memory problem. Before the PC wouldn't boot and the power LED was on and the caps lock was continuously blinking and the only way to turn it off was to take out the battery.

I replaced the RAM and set it into a different slot and it booted. I hope this helps you.

Thanks!

Update: The PC booted and once it rebooted the problem occurred again. Still troublehooting..

😞

[Isscander]

Hi All,

I have the exact same problem as truthizwizdom.

It boots once, then when rebooted the same problem occurs. It's like I have to change the hardware to let it boot.

I tried another harddrive, formatted the old one, updated the BIOS, did a hard reset but nothing works.

Did someone resolve this yet?

Cheers

Update [SOLVED]: I removed half of the RAM so the notebook could boot (no clue why this worked). Then I ran the 'SFC /scannow' command in the commandprompt (as administrator). It found and fixed an corrupted .cfg file. Now it works like a charm. Hope this helps.