Compaq presario cq56 black screen on boot up after replacing the fan and keyboard

Hi the cpu fan on my computer died, so we replaced it and i took the opertunity to replace the keyboard at the same time.
Now the fan works just fine the blue/white power button works, initially the caps lock button came on and stayed on but no longer comes on at all.
I am quite the novice in all things computer so think i may have done something stupid, and fried the motherboard, but if anyone could come up with something for me to try before i have to go through replacing that bit i would appreciate it.
Oh i have tried an external monitor and it says recieving no signal on the screen.
Thanks for helping

Hi @carriebevan
Welcome to the HP Community! I saw your post regarding the problem with the notebook going to a black screen after replacing the fan and the keyboard. To be honest with you there isn't a whole lot that I can do for you in this manner. Try seeing if you can get into the operating system using Safe Mode. If you can then we can look at a couple of things.
Please click “Accept as Solution ” if you feel my post solved your issue.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Thank you,
BHK6
I work on behalf of HP

Similar Messages

Compaq presario cq61 black screen

My laptop sometimes has a black screen upon booting up and the white lights blink at the caps lock and page up area. Its running, but won't move from this stage. Please help. Thank you.

HI PiscesJNJ,
Welcome to the HP forum! Thank you for your post. I will do my utmost to aid in this task.
I understand that you are getting a black screen, with a white blinking light on the caps lock. Here are documents on Troubleshooting Black Screen Displays with No Error Messages During Startup or Boot and Computer Does Not Start and the LEDs Blink or the Computer Beeps. I hope these help. Please let me know the outcome.
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

Black screen on boot I can hear the OS boot

Hello,
I am trying to fix my relatives computer it has a black screen that does not go away and I can hear windows 7 load. I suspect that he has dropped it a few times becuase i can see the dents . It had a south american version of windows 7 installed by some else (this PC was purchased in the USA). I was able to log in one night after letting it charge for a long time,removing the battery etc. I also connected a vga monitor and after some trial and error it worked fine and was rebooting ok.
After backing the data and reflashing the BIOS (it already had the latest) I installed a fresh vanilla copy of windows (english) and it seemed to be working fine for the rest of that night. I then purchased a set of recovery discs directly from HP (still waiting for these).
A few days later (tonight) I wanted to work on it to see if i could troubleshoot the battery problem (the battery does not charge before even after the OS was refreshed), but now I am back to having the same isssue with the black screen. I still can't get the screen working.
At this point I am suspecting that I need to replace the LCD screen or the motherboard. The LCD because of the black screen and the motherboard because the motherboard in general becomes very hot quickly and it might be the reason why the battery is having problems (my relative claims he purchased a refurbished battery down there).
I viewed some posts here about a black screen issue that was going on with these G42 models mentioning something about "a black screen with a bliking caps lock LED" but I do not see any lights turn on for the caps lock (ever, perhaps there is not enough power going to the LED?).
If anyone could point me in the right direction on which I should try first I would really appreciate it. I wouldnt mind replacing both and re-pasting the CPU but I don't really have a lot of time and a limited budget.
Thank you

Try cleaning it out. Heat sinks and fans collect dust, which causes them to insulate the CPU rather than disperse heat. I assume that you don't have a dedicated GPU and are using the Intel video built-in.
As for repasting, it may be a good idea. The thermal paste that HP gives you is garbage, and is only there for the sake of having thermal paste. I'd recommend an Arctic Silver compound. It's pretty cheap and very effective.

PT880 Neo LSR - Black screen at boot up after post

Hi all
I've been reading the forum for some time now and unfortunately haven't been able to fix my problem.
Right after post I have a delay of 30 sec. before XP starts loading, the screen being black meantime.
Just changed my PSU for a better quality one (cf. below) but this doesn't solve the issue.
Also desabled the boot rom options, SATA and LAN under bios to no effect.
Please also note that the GPU has a VGA and DVI outputs but the display only a VGA input. Therefore the display is connected to the VGA output of the GPU.
Any idea will be welcome
Thx in advance for your help

Hey SeekerF. I have the same MoBo that you have. I had problems with it also. I really believe that it is your BIOS. When my computer would boot into windows, or sometimes right after you see the window xp logo, it would reboot. I switched out my PSU but that didn't work. I had version 1.2 of the BIOS, and had to upgrade to the latest version which is 1.4. Your best bet is to download the latest version (from someone else's machine of course from the MSI website for you board) and save the files to a floppy. Make sure you read the instructions very carefully when you are flashing the BIOS. When you do this you WILL need a windows 98 or ME startup floppy. If you can't get your hands on one you can go to http://www.bootdisk.com and you can the files from there to make one. Once you boot up your machine with the startup disk, just follow the instructions on how the flash to the latest version. Ever since I upgraded to 1.4 I have not had any problems and my system has been stable. Hope this helps. Later.

Black screen instead of TTYs after Xorg once started and leaved

Hi,
I've installed Arch on my laptop and experience following issue... I log in after boot and run "startx", then openbox starts properly. This is fine, but when I leave X, I can't see anything (TTY expected). I can switch to another TTY, login as root and type "reboot" or type "killall X", then log in as regular user and type "startx" to get openbox again. So there are TTYs obviously but I can't see anything but black screen.
By leaving X (above) I mean...
- typing "sudo killal X" in xterm
- using openbox "Log Out" menu option
- switching to another TTY by hitting Alt+Fn
All of these lead to the same issue.
I assume it's not Xorg problem, but I may be wrong of course. Is that driver related? I have Nvidia card and use proprietary drivers installed via pacman. Can anybody give me an advice where to look? Thanks a lot. I also attach (maybe relevant) outputs. If there is anything else needed to know please tell me and I'll post it.
$ lspci
00:00.0 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a2)
00:01.0 ISA bridge: nVidia Corporation Device 075e (rev a2)
00:01.1 SMBus: nVidia Corporation MCP78S [GeForce 8200] SMBus (rev a1)
00:01.2 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a1)
00:01.3 Co-processor: nVidia Corporation MCP78S [GeForce 8200] Co-Processor (rev a2)
00:01.4 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a1)
00:02.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller (rev a1)
00:04.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller (rev a1)
00:04.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller (rev a1)
00:07.0 Audio device: nVidia Corporation MCP72XE/MCP72P/MCP78U/MCP78S High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:09.0 SATA controller: nVidia Corporation Device 0ad5 (rev a2)
00:0b.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1)
00:12.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1)
00:13.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:14.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:15.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] Mobile K10 [Turion X2, Athlon X2, Sempron] HyperTransport Configuration (rev 40)
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 11h [Turion X2, Athlon X2, Sempron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Mobile K10 [Turion X2, Athlon X2, Sempron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Mobile K10 [Turion X2, Athlon X2, Sempron] Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Mobile K10 [Turion X2, Athlon X2, Sempron] Link Control
02:00.0 VGA compatible controller: nVidia Corporation C77 [GeForce 9100M G] (rev a2)
03:00.0 VGA compatible controller: nVidia Corporation G98 [GeForce 9300M GS] (rev a1)
06:00.0 Network controller: RaLink RT2860
07:00.0 FireWire (IEEE 1394): JMicron Technology Corp. IEEE 1394 Host Controller
07:00.1 System peripheral: JMicron Technology Corp. SD/MMC Host Controller
07:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller
07:00.3 System peripheral: JMicron Technology Corp. MS Host Controller
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
$ pacman -Qs nvidia
local/libvdpau 0.4-1
Nvidia VDPAU library
local/nvidia 256.35-1
NVIDIA drivers for kernel26.
local/nvidia-utils 256.35-4
NVIDIA drivers utilities and libraries.
$ cat /var/log/Xorg.0.log.old
[ 156.095]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 156.097]
X.Org X Server 1.8.1.902 (1.8.2 RC 2)
Release Date: 2010-06-21
[ 156.098] X Protocol Version 11, Revision 0
[ 156.098] Build Operating System: Linux 2.6.34-ARCH x86_64
[ 156.098] Current Operating System: Linux DrZoidberg 2.6.34-ARCH #1 SMP PREEMPT Sat Jun 19 00:07:49 CEST 2010 x86_64
[ 156.098] Kernel command line: root=/dev/sda5 ro
[ 156.098] Build Date: 21 June 2010 12:01:49PM
[ 156.099]
[ 156.099] Current version of pixman: 0.18.2
[ 156.099] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 156.099] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 156.101] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jul 4 15:57:39 2010
[ 156.101] (==) Using config file: "/etc/X11/xorg.conf"
[ 156.101] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 156.102] (==) ServerLayout "Layout0"
[ 156.102] (**) |-->Screen "Screen0" (0)
[ 156.102] (**) | |-->Monitor "Monitor0"
[ 156.102] (**) | |-->Device "Device0"
[ 156.102] (**) |-->Input Device "Keyboard0"
[ 156.102] (**) |-->Input Device "Mouse0"
[ 156.102] (==) Automatically adding devices
[ 156.102] (==) Automatically enabling devices
[ 156.102] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 156.102] Entry deleted from font path.
[ 156.102] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 156.102] Entry deleted from font path.
[ 156.102] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 156.102] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 156.102] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 156.102] (WW) Disabling Keyboard0
[ 156.102] (WW) Disabling Mouse0
[ 156.102] (II) Loader magic: 0x7ce880
[ 156.102] (II) Module ABI versions:
[ 156.102] X.Org ANSI C Emulation: 0.4
[ 156.102] X.Org Video Driver: 7.0
[ 156.102] X.Org XInput driver : 9.0
[ 156.102] X.Org Server Extension : 3.0
[ 156.110] (--) PCI: (0:0:1:3) 10de:0753:1462:6710 nVidia Corporation MCP78S [GeForce 8200] Co-Processor rev 162, Mem @ 0xf8e80000/524288
[ 156.110] (--) PCI:*(0:2:0:0) 10de:0844:1462:6710 nVidia Corporation C77 [GeForce 9100M G] rev 162, Mem @ 0xf9000000/16777216, 0xc8000000/134217728, 0xc6000000/33554432, I/O @ 0x0000bc00/128, BIOS @ 0x????????/131072
[ 156.110] (--) PCI: (0:3:0:0) 10de:06e9:1462:6710 nVidia Corporation G98 [GeForce 9300M GS] rev 161, Mem @ 0xfc000000/16777216, 0xd0000000/268435456, 0xfa000000/33554432, I/O @ 0x0000cc00/128, BIOS @ 0x????????/131072
[ 156.110] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 156.110] (II) LoadModule: "extmod"
[ 156.110] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 156.111] (II) Module extmod: vendor="X.Org Foundation"
[ 156.111] compiled for 1.8.1.902, module version = 1.0.0
[ 156.111] Module class: X.Org Server Extension
[ 156.111] ABI class: X.Org Server Extension, version 3.0
[ 156.111] (II) Loading extension MIT-SCREEN-SAVER
[ 156.111] (II) Loading extension XFree86-VidModeExtension
[ 156.111] (II) Loading extension XFree86-DGA
[ 156.111] (II) Loading extension DPMS
[ 156.111] (II) Loading extension XVideo
[ 156.111] (II) Loading extension XVideo-MotionCompensation
[ 156.111] (II) Loading extension X-Resource
[ 156.111] (II) LoadModule: "dbe"
[ 156.111] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 156.111] (II) Module dbe: vendor="X.Org Foundation"
[ 156.111] compiled for 1.8.1.902, module version = 1.0.0
[ 156.111] Module class: X.Org Server Extension
[ 156.111] ABI class: X.Org Server Extension, version 3.0
[ 156.111] (II) Loading extension DOUBLE-BUFFER
[ 156.111] (II) LoadModule: "glx"
[ 156.111] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 156.127] (II) Module glx: vendor="NVIDIA Corporation"
[ 156.128] compiled for 4.0.2, module version = 1.0.0
[ 156.128] Module class: X.Org Server Extension
[ 156.128] (II) NVIDIA GLX Module 256.35 Wed Jun 16 19:10:31 PDT 2010
[ 156.128] (II) Loading extension GLX
[ 156.128] (II) LoadModule: "record"
[ 156.128] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 156.128] (II) Module record: vendor="X.Org Foundation"
[ 156.128] compiled for 1.8.1.902, module version = 1.13.0
[ 156.128] Module class: X.Org Server Extension
[ 156.128] ABI class: X.Org Server Extension, version 3.0
[ 156.128] (II) Loading extension RECORD
[ 156.128] (II) LoadModule: "dri"
[ 156.128] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 156.129] (II) Module dri: vendor="X.Org Foundation"
[ 156.129] compiled for 1.8.1.902, module version = 1.0.0
[ 156.129] ABI class: X.Org Server Extension, version 3.0
[ 156.129] (II) Loading extension XFree86-DRI
[ 156.129] (II) LoadModule: "dri2"
[ 156.129] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 156.129] (II) Module dri2: vendor="X.Org Foundation"
[ 156.129] compiled for 1.8.1.902, module version = 1.2.0
[ 156.129] ABI class: X.Org Server Extension, version 3.0
[ 156.129] (II) Loading extension DRI2
[ 156.129] (II) LoadModule: "nvidia"
[ 156.129] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 156.130] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 156.130] compiled for 4.0.2, module version = 1.0.0
[ 156.130] Module class: X.Org Video Driver
[ 156.130] (II) NVIDIA dlloader X Driver 256.35 Wed Jun 16 18:45:02 PDT 2010
[ 156.130] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 156.130] (--) using VT number 7
[ 156.134] (II) Primary Device is: PCI 02@00:00:0
[ 156.134] (II) Loading sub module "fb"
[ 156.134] (II) LoadModule: "fb"
[ 156.134] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 156.134] (II) Module fb: vendor="X.Org Foundation"
[ 156.134] compiled for 1.8.1.902, module version = 1.0.0
[ 156.134] ABI class: X.Org ANSI C Emulation, version 0.4
[ 156.134] (II) Loading sub module "wfb"
[ 156.134] (II) LoadModule: "wfb"
[ 156.135] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 156.135] (II) Module wfb: vendor="X.Org Foundation"
[ 156.135] compiled for 1.8.1.902, module version = 1.0.0
[ 156.135] ABI class: X.Org ANSI C Emulation, version 0.4
[ 156.135] (II) Loading sub module "ramdac"
[ 156.135] (II) LoadModule: "ramdac"
[ 156.135] (II) Module "ramdac" already built-in
[ 156.135] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 156.135] (==) NVIDIA(0): RGB weight 888
[ 156.135] (==) NVIDIA(0): Default visual is TrueColor
[ 156.135] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 156.135] (**) NVIDIA(0): Option "NoLogo" "true"
[ 156.135] (**) NVIDIA(0): Enabling RENDER acceleration
[ 156.135] (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
[ 156.135] (II) NVIDIA(0): enabled.
[ 156.360] (II) NVIDIA(0): NVIDIA GPU GeForce 9100M G (C77) at PCI:2:0:0 (GPU-0)
[ 156.360] (--) NVIDIA(0): Memory: 524288 kBytes
[ 156.360] (--) NVIDIA(0): VideoBIOS: 62.77.2c.00.00
[ 156.360] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 156.360] (--) NVIDIA(0): Connected display device(s) on GeForce 9100M G at PCI:2:0:0:
[ 156.360] (--) NVIDIA(0): Seiko/Epson (DFP-0)
[ 156.360] (--) NVIDIA(0): Seiko/Epson (DFP-0): 330.0 MHz maximum pixel clock
[ 156.360] (--) NVIDIA(0): Seiko/Epson (DFP-0): Internal Dual Link LVDS
[ 156.373] (II) NVIDIA(0): Assigned Display Device: DFP-0
[ 156.373] (==) NVIDIA(0):
[ 156.373] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 156.373] (==) NVIDIA(0): will be used as the requested mode.
[ 156.373] (==) NVIDIA(0):
[ 156.374] (II) NVIDIA(0): Validated modes:
[ 156.374] (II) NVIDIA(0): "nvidia-auto-select"
[ 156.374] (II) NVIDIA(0): Virtual screen size determined to be 1366 x 768
[ 156.376] (--) NVIDIA(0): DPI set to (99, 97); computed from "UseEdidDpi" X config
[ 156.376] (--) NVIDIA(0): option
[ 156.376] (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
[ 156.376] (--) Depth 24 pixmap format is 32 bpp
[ 156.376] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
[ 156.865] (II) NVIDIA(GPU-1): NVIDIA GPU GeForce 9300M GS (G98) at PCI:3:0:0 (GPU-1)
[ 156.865] (--) NVIDIA(GPU-1): Memory: 524288 kBytes
[ 156.865] (--) NVIDIA(GPU-1): VideoBIOS: 62.98.3c.00.00
[ 156.865] (II) NVIDIA(GPU-1): Detected PCI Express Link width: 16X
[ 156.865] (--) NVIDIA(GPU-1): Interlaced video modes are supported on this GPU
[ 156.865] (--) NVIDIA(GPU-1): Connected display device(s) on GeForce 9300M GS at PCI:3:0:0:
[ 156.865] (--) NVIDIA(GPU-1): none
[ 156.866] (II) NVIDIA(0): Initialized GPU GART.
[ 156.878] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 156.878] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 156.878] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 156.878] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 156.878] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 156.878] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 156.878] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 156.878] (II) NVIDIA(0): Config Options in the README.
[ 156.879] (II) NVIDIA(0): ACPI display change hotkey events enabled: the X server is new
[ 156.879] (II) NVIDIA(0): enough to receive ACPI hotkey events.
[ 156.879] (II) NVIDIA(0): ACPI brightness change hotkey events enabled.
[ 156.880] (II) NVIDIA(0): Setting mode "nvidia-auto-select"
[ 157.172] (II) Loading extension NV-GLX
[ 157.208] (II) NVIDIA(0): Initialized OpenGL Acceleration
[ 157.216] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 157.216] (II) NVIDIA(0): Initialized X Rendering Acceleration
[ 157.216] (==) NVIDIA(0): Backing store disabled
[ 157.216] (==) NVIDIA(0): Silken mouse enabled
[ 157.232] (**) NVIDIA(0): DPMS enabled
[ 157.232] (II) Loading extension NV-CONTROL
[ 157.233] (II) Loading extension XINERAMA
[ 157.233] (II) Loading sub module "dri2"
[ 157.233] (II) LoadModule: "dri2"
[ 157.233] (II) Reloading /usr/lib/xorg/modules/extensions/libdri2.so
[ 157.233] (II) NVIDIA(0): [DRI2] Setup complete
[ 157.233] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 157.233] (==) RandR enabled
[ 157.233] (II) Initializing built-in extension Generic Event Extension
[ 157.233] (II) Initializing built-in extension SHAPE
[ 157.233] (II) Initializing built-in extension MIT-SHM
[ 157.233] (II) Initializing built-in extension XInputExtension
[ 157.233] (II) Initializing built-in extension XTEST
[ 157.233] (II) Initializing built-in extension BIG-REQUESTS
[ 157.233] (II) Initializing built-in extension SYNC
[ 157.233] (II) Initializing built-in extension XKEYBOARD
[ 157.233] (II) Initializing built-in extension XC-MISC
[ 157.233] (II) Initializing built-in extension SECURITY
[ 157.233] (II) Initializing built-in extension XINERAMA
[ 157.233] (II) Initializing built-in extension XFIXES
[ 157.233] (II) Initializing built-in extension RENDER
[ 157.233] (II) Initializing built-in extension RANDR
[ 157.233] (II) Initializing built-in extension COMPOSITE
[ 157.233] (II) Initializing built-in extension DAMAGE
[ 157.236] (II) Initializing extension GLX
[ 157.423] (II) config/udev: Adding input device Power Button (/dev/input/event5)
[ 157.423] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 157.423] (II) LoadModule: "evdev"
[ 157.423] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 157.423] (II) Module evdev: vendor="X.Org Foundation"
[ 157.423] compiled for 1.8.0, module version = 2.4.0
[ 157.423] Module class: X.Org XInput Driver
[ 157.423] ABI class: X.Org XInput driver, version 9.0
[ 157.423] (**) Power Button: always reports core events
[ 157.423] (**) Power Button: Device: "/dev/input/event5"
[ 157.433] (II) Power Button: Found keys
[ 157.433] (II) Power Button: Configuring as keyboard
[ 157.433] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 157.433] (**) Option "xkb_rules" "evdev"
[ 157.433] (**) Option "xkb_model" "evdev"
[ 157.433] (**) Option "xkb_layout" "cz"
[ 157.433] (**) Option "xkb_variant" "qwerty"
[ 157.433] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 157.469] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[ 157.469] (II) No input driver/identifier specified (ignoring)
[ 157.470] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
[ 157.470] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 157.470] (**) Sleep Button: always reports core events
[ 157.470] (**) Sleep Button: Device: "/dev/input/event3"
[ 157.480] (II) Sleep Button: Found keys
[ 157.480] (II) Sleep Button: Configuring as keyboard
[ 157.480] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD)
[ 157.480] (**) Option "xkb_rules" "evdev"
[ 157.480] (**) Option "xkb_model" "evdev"
[ 157.480] (**) Option "xkb_layout" "cz"
[ 157.480] (**) Option "xkb_variant" "qwerty"
[ 157.480] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 157.481] (II) config/udev: Adding input device Video Bus (/dev/input/event6)
[ 157.481] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 157.481] (**) Video Bus: always reports core events
[ 157.481] (**) Video Bus: Device: "/dev/input/event6"
[ 157.490] (II) Video Bus: Found keys
[ 157.490] (II) Video Bus: Configuring as keyboard
[ 157.490] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
[ 157.490] (**) Option "xkb_rules" "evdev"
[ 157.490] (**) Option "xkb_model" "evdev"
[ 157.490] (**) Option "xkb_layout" "cz"
[ 157.490] (**) Option "xkb_variant" "qwerty"
[ 157.490] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 157.490] (II) config/udev: Adding input device Video Bus (/dev/input/event7)
[ 157.490] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 157.490] (**) Video Bus: always reports core events
[ 157.490] (**) Video Bus: Device: "/dev/input/event7"
[ 157.500] (II) Video Bus: Found keys
[ 157.500] (II) Video Bus: Configuring as keyboard
[ 157.500] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
[ 157.500] (**) Option "xkb_rules" "evdev"
[ 157.500] (**) Option "xkb_model" "evdev"
[ 157.500] (**) Option "xkb_layout" "cz"
[ 157.500] (**) Option "xkb_variant" "qwerty"
[ 157.500] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 157.501] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 157.501] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 157.501] (**) Power Button: always reports core events
[ 157.501] (**) Power Button: Device: "/dev/input/event4"
[ 157.510] (II) Power Button: Found keys
[ 157.510] (II) Power Button: Configuring as keyboard
[ 157.510] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 157.510] (**) Option "xkb_rules" "evdev"
[ 157.510] (**) Option "xkb_model" "evdev"
[ 157.510] (**) Option "xkb_layout" "cz"
[ 157.510] (**) Option "xkb_variant" "qwerty"
[ 157.510] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 157.512] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event9)
[ 157.512] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 157.512] (**) Logitech USB Receiver: always reports core events
[ 157.512] (**) Logitech USB Receiver: Device: "/dev/input/event9"
[ 157.523] (II) Logitech USB Receiver: Found keys
[ 157.523] (II) Logitech USB Receiver: Configuring as keyboard
[ 157.523] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD)
[ 157.523] (**) Option "xkb_rules" "evdev"
[ 157.523] (**) Option "xkb_model" "evdev"
[ 157.523] (**) Option "xkb_layout" "cz"
[ 157.523] (**) Option "xkb_variant" "qwerty"
[ 157.523] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 157.524] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event10)
[ 157.524] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
[ 157.524] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 157.524] (**) Logitech USB Receiver: always reports core events
[ 157.524] (**) Logitech USB Receiver: Device: "/dev/input/event10"
[ 157.536] (II) Logitech USB Receiver: Found 20 mouse buttons
[ 157.536] (II) Logitech USB Receiver: Found scroll wheel(s)
[ 157.536] (II) Logitech USB Receiver: Found relative axes
[ 157.536] (II) Logitech USB Receiver: Found x and y relative axes
[ 157.536] (II) Logitech USB Receiver: Found absolute axes
[ 157.536] (II) Logitech USB Receiver: Found keys
[ 157.536] (II) Logitech USB Receiver: Configuring as mouse
[ 157.536] (II) Logitech USB Receiver: Configuring as keyboard
[ 157.536] (**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[ 157.536] (**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 157.536] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD)
[ 157.536] (**) Option "xkb_rules" "evdev"
[ 157.536] (**) Option "xkb_model" "evdev"
[ 157.536] (**) Option "xkb_layout" "cz"
[ 157.536] (**) Option "xkb_variant" "qwerty"
[ 157.536] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 157.537] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[ 157.537] (**) Logitech USB Receiver: (accel) acceleration profile 0
[ 157.537] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[ 157.537] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[ 157.537] (II) Logitech USB Receiver: initialized for relative axes.
[ 157.537] (WW) Logitech USB Receiver: ignoring absolute axes.
[ 157.537] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse1)
[ 157.537] (II) No input driver/identifier specified (ignoring)
[ 157.538] (II) config/udev: Adding input device MLK EU3C Wireless Office 200 (/dev/input/event11)
[ 157.538] (**) MLK EU3C Wireless Office 200: Applying InputClass "evdev keyboard catchall"
[ 157.538] (**) MLK EU3C Wireless Office 200: always reports core events
[ 157.538] (**) MLK EU3C Wireless Office 200: Device: "/dev/input/event11"
[ 157.553] (II) MLK EU3C Wireless Office 200: Found keys
[ 157.553] (II) MLK EU3C Wireless Office 200: Configuring as keyboard
[ 157.553] (II) XINPUT: Adding extended input device "MLK EU3C Wireless Office 200" (type: KEYBOARD)
[ 157.553] (**) Option "xkb_rules" "evdev"
[ 157.553] (**) Option "xkb_model" "evdev"
[ 157.553] (**) Option "xkb_layout" "cz"
[ 157.553] (**) Option "xkb_variant" "qwerty"
[ 157.553] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 157.554] (II) config/udev: Adding input device MLK EU3C Wireless Office 200 (/dev/input/event12)
[ 157.554] (**) MLK EU3C Wireless Office 200: Applying InputClass "evdev pointer catchall"
[ 157.554] (**) MLK EU3C Wireless Office 200: Applying InputClass "evdev keyboard catchall"
[ 157.554] (**) MLK EU3C Wireless Office 200: always reports core events
[ 157.554] (**) MLK EU3C Wireless Office 200: Device: "/dev/input/event12"
[ 157.566] (II) MLK EU3C Wireless Office 200: Found 9 mouse buttons
[ 157.566] (II) MLK EU3C Wireless Office 200: Found scroll wheel(s)
[ 157.566] (II) MLK EU3C Wireless Office 200: Found relative axes
[ 157.566] (II) MLK EU3C Wireless Office 200: Found x and y relative axes
[ 157.566] (II) MLK EU3C Wireless Office 200: Found absolute axes
[ 157.566] (II) MLK EU3C Wireless Office 200: Found keys
[ 157.566] (II) MLK EU3C Wireless Office 200: Configuring as mouse
[ 157.566] (II) MLK EU3C Wireless Office 200: Configuring as keyboard
[ 157.566] (**) MLK EU3C Wireless Office 200: YAxisMapping: buttons 4 and 5
[ 157.566] (**) MLK EU3C Wireless Office 200: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 157.566] (II) XINPUT: Adding extended input device "MLK EU3C Wireless Office 200" (type: KEYBOARD)
[ 157.566] (**) Option "xkb_rules" "evdev"
[ 157.566] (**) Option "xkb_model" "evdev"
[ 157.566] (**) Option "xkb_layout" "cz"
[ 157.566] (**) Option "xkb_variant" "qwerty"
[ 157.566] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 157.567] (**) MLK EU3C Wireless Office 200: (accel) keeping acceleration scheme 1
[ 157.567] (**) MLK EU3C Wireless Office 200: (accel) acceleration profile 0
[ 157.567] (**) MLK EU3C Wireless Office 200: (accel) acceleration factor: 2.000
[ 157.567] (**) MLK EU3C Wireless Office 200: (accel) acceleration threshold: 4
[ 157.567] (II) MLK EU3C Wireless Office 200: initialized for relative axes.
[ 157.567] (WW) MLK EU3C Wireless Office 200: ignoring absolute axes.
[ 157.567] (II) config/udev: Adding input device MLK EU3C Wireless Office 200 (/dev/input/mouse2)
[ 157.567] (II) No input driver/identifier specified (ignoring)
[ 157.567] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event13)
[ 157.567] (II) No input driver/identifier specified (ignoring)
[ 157.573] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 157.573] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 157.573] (**) AT Translated Set 2 keyboard: always reports core events
[ 157.573] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 157.580] (II) AT Translated Set 2 keyboard: Found keys
[ 157.580] (II) AT Translated Set 2 keyboard: Configuring as keyboard
[ 157.580] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
[ 157.580] (**) Option "xkb_rules" "evdev"
[ 157.580] (**) Option "xkb_model" "evdev"
[ 157.580] (**) Option "xkb_layout" "cz"
[ 157.580] (**) Option "xkb_variant" "qwerty"
[ 157.580] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 157.580] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event8)
[ 157.580] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 157.580] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 157.580] (II) LoadModule: "synaptics"
[ 157.580] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 157.581] (II) Module synaptics: vendor="X.Org Foundation"
[ 157.581] compiled for 1.8.0.902, module version = 1.2.2
[ 157.581] Module class: X.Org XInput Driver
[ 157.581] ABI class: X.Org XInput driver, version 9.0
[ 157.581] (II) Synaptics touchpad driver version 1.2.2
[ 157.581] (**) Option "Device" "/dev/input/event8"
[ 157.620] (II) SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
[ 157.620] (II) SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448
[ 157.620] (II) SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 157.620] (II) SynPS/2 Synaptics TouchPad: finger width range 0 - 0
[ 157.620] (II) SynPS/2 Synaptics TouchPad: buttons: left right
[ 157.620] (**) Option "TapButton1" "1"
[ 157.620] (**) Option "TapButton2" "2"
[ 157.620] (**) Option "TapButton3" "3"
[ 157.646] (--) SynPS/2 Synaptics TouchPad: touchpad found
[ 157.646] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 157.660] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD)
[ 157.660] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 157.660] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 0
[ 157.660] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 157.660] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 157.686] (--) SynPS/2 Synaptics TouchPad: touchpad found
[ 157.686] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 157.686] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 157.686] (II) Synaptics touchpad driver version 1.2.2
[ 158.333] SynPS/2 Synaptics TouchPad no synaptics event device found
[ 158.333] (**) Option "Device" "/dev/input/mouse0"
[ 158.346] (**) Option "TapButton1" "1"
[ 158.346] (**) Option "TapButton2" "2"
[ 158.346] (**) Option "TapButton3" "3"
[ 158.366] Query no Synaptics: 6003C8
[ 158.366] (--) SynPS/2 Synaptics TouchPad: no supported touchpad found
[ 158.367] (EE) SynPS/2 Synaptics TouchPad Unable to query/initialize Synaptics hardware.
[ 158.406] (EE) PreInit failed for input device "SynPS/2 Synaptics TouchPad"
[ 158.406] (II) UnloadModule: "synaptics"
[ 158.406] (II) config/udev: Adding input device PC Speaker (/dev/input/event2)
[ 158.406] (II) No input driver/identifier specified (ignoring)
[ 222.970] (II) Power Button: Close
[ 222.970] (II) UnloadModule: "evdev"
[ 222.990] (II) Sleep Button: Close
[ 222.990] (II) UnloadModule: "evdev"
[ 223.016] (II) Video Bus: Close
[ 223.016] (II) UnloadModule: "evdev"
[ 223.036] (II) Video Bus: Close
[ 223.036] (II) UnloadModule: "evdev"
[ 223.056] (II) Power Button: Close
[ 223.056] (II) UnloadModule: "evdev"
[ 223.076] (II) Logitech USB Receiver: Close
[ 223.076] (II) UnloadModule: "evdev"
[ 223.096] (II) Logitech USB Receiver: Close
[ 223.096] (II) UnloadModule: "evdev"
[ 223.116] (II) MLK EU3C Wireless Office 200: Close
[ 223.116] (II) UnloadModule: "evdev"
[ 223.136] (II) MLK EU3C Wireless Office 200: Close
[ 223.136] (II) UnloadModule: "evdev"
[ 223.156] (II) AT Translated Set 2 keyboard: Close
[ 223.156] (II) UnloadModule: "evdev"
[ 223.190] (II) UnloadModule: "synaptics"
$ cat /etc/X11/xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 256.35 ([email protected]) Wed Jun 16 19:15:05 PDT 2010
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
Option "NoLogo" "true"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection

I was having this exact same problem, then it just stopped. I am using the nouveau driver and I have a tnt2 card.
IIRC, I was having an unrelated problem with xorg or udev or something was having problems detecting my monitor, it claimed I had two monitors connected, I wrote an xorg.conf file and that fixed the problem. IDK if its is related or not because I don't recall exactly when things started working when I would switch ttys.
Try using the nouveau driver and see if it does the same thing, it has a kernel module so it might make difference,
Last edited by RiceKills (2010-07-06 23:39:27)

IPod touch 3rd generation has dim screen and no touch screen response. I've replaced the digitizer and the screen. I've also reset it and did a complete restore still nothing. Is there any way to fix this myself? Does it just need a new memory board?

My 3rd gen iPod touch has a very dim/dark screen and no screen response. I've restored it, still nothing, put a new screen and digitizer and still nothing. I've reset it a 1000 times and nothing works. Is there a way to fix this? It previously had "activation required" on the screen but now it just says "ipod" what do I do now?

Could be due to many things. You could have damaged something during the screen replacement. I would take it to someone with more experience.

Fan issue - Compaq Presario CQ56-106SA

Product : Compaq Presario CQ56-106SA
OS : Windows 7 Home Premium
Issue: Fan error (90b)
Greetings all ,
First off I am very familiar with computer systems and component as I work on them fairly regularly however I am currently unsure to what I should do from this point.
I got the notebook laptop as a present a few years ago and its seen better days however I recenty decided to use it again however when I started the laptop I got the fan error (90b) so I took a look at the fan and it wasnt spining hense the error , so I checked the HP support site and looked at the error and also did a google search to see if anyone else had fixed it.
So I opened the laptop up (since it was out of warranty anyways) and I got to the fan and removed the heatsink and fan component and I opened that up and there was a buildup of dust obviously needless to say i cleaned it up and put the component back together and placed it back in and ensured everything was connected correctly and started up the computer however the fan still isnt spining and I still keep the getting the error.
So my question is , If I took out the component is there a way of testing to see if there is any fault with the fan itself? (eg. putting a small amount of power through it to see if the fan spins?)
Or should I just replace the fan and heatsink component completely and hope that the issue doesnt persist?
Any help would be appreciated , just to have someone elses opinion?

Hi
As you have mentioned that the Fan is not spinning the issue is with Fan & also replacing the heatsink apply terminal paste and that should take care of the issue. I have also seen sometimes issue might be with the Systemboard connector which is bad might cause this issue.
This is very difficult to guess
Let us know how it goes!
"I work for HP."
****Click the (purple thumbs up icon in the lower right corner of a post) to say thanks****
****Please mark Accept As Solution if it solves your problem****
Regards
Manjunath

Recovery Manager could not restore Presario CQ56 & system won't boot, gives error BOOTMGR is missing

1. Product Name and Number
Compaq Presario CQ56
2. Operating System installed (if applicable)
Windows 7
3. Error message (if any)
from error log:
Hard Disk (result-failed) id# UAMBXQ-5H06AK-XD003F-618U03 HARD DISK 1
Start-up (result-failed) id# UAMBXQ-5H60AK-XD003F-40G403 MEMORY MODULE 2
4. Any changes made to your system before the issue occurred
There were no changes made to the computer, prior to the restore the computer would boot up, however, it would freeze after the system was up and running. Restarting the computer did not help and when I tried to restore it to an earlier point it said that it was unable to complete the restore. I then tried to the factory reset, however, it gave me an error message: "Recovery Manager could not restore your computer using the factory image. Please contact HP support. Error code: 0xe0ef0003. When I tried to restart the computer afterwards, it gave an error message: "BOOTMGR is missing, Press Ctrl+Alt+Del to restart". How do I fix this?
This question was solved.
View Solution.

Hello crossurmind.
What sorts of issues led up to the computer originally not booting? Were you getting a lot of blue screen errors?
The two items you posted from the error log seem to indicate that it is having trouble reading the hard drive and possibly the memory. After trying the restore it seems that it failed causing the boot section of the install to "not be found."
I think you should begin by using the built in tests for the hard drive and memory located in the BIOS. Follow this document to perform the hard drive test. All you'll have to do is repeat the process and select "memory" in order to perform the memory test. Make sure to post the result of both of these tests.
I will await the results; have a great day!
Please click the white star under my name to give me Kudos as a way to say "Thanks!"
Click the "Accept as Solution" button if I resolve your issue.

Compaq Presario CQ56-110US will not load up.

So.. the moment I press the power button, my Compaq Presario CQ56-110US notebook, will not load up. It only show the Compaq logo screen flashes black them shut down and restarts the process. It never makes it to the Windows login page.

Hey @rajpodn ,
Welcome to the HP Forums!
I understand you're looking for info on swapping out the CPU in your notebook.
You will find everything you need here: Compaq Presario CQ56 Notebook PC - Maintenance and Service Guide. The instructions you need start on page 75. Keep in mind that the CPU itself may not be the issue, it could be the socket on the motherboard preventing the notebook from reading the CPU, so even replacing the CPU may not work, as you may need a replacement motherboard. I do not suggest replacing the motherboard as doing so requires HP Proprietary software to reinstall the Service-ID necessary for reinstalling Windows.
*Caution - If you do install the new CPU be careful with the thermal paste. A small pea sized amount should be more than enough. Put the paste in the exact center and carefully spread so there is a fine layer almost to the edge of the CPU. Remember that the heatsink will press very firmly onto the CPU and spread the paste more and you don't want any squishing out as this can cause electrical shorts if the paste has a high metal content.
The part you will want is: AMD V140 processor (2.3 GHz, 512-MB, L2 cache, 1066 MHz, 3.2 GT/s)—singlecore 25 W. The part number for this is: 616333-001.
You can order the CPU directly from HP here: HP Part Surfer, but you may be able to find it cheaper on sites like eBay, Amazon, or Newegg.
Hopefully this covers everything you're after!
Please click the "Kudos, Thumbs Up" at the bottom of this post if you want to say "Thanks" for helping!
Please click "Accept as Solution" if you feel my post solved your issue, it will help others find the solution.
The Great Deku Tree
I work on behalf of HP.

Compaq presario v6210US blank screen

I have a "compaq presario v6210US" which worked great for a while then it just shut itself off and restarted and the screen stayed black. Now it keeps restarting itself but the screen stays blakc. I can hear the fan and hard drive and everything else running the way it's supposed to. I heard that this has happened to a bunch of other people so it sounds like a defect to me. How do I get it fixed or do I just pull the hard drive, toss the Presario and get a competitors laptop?
This question was solved.
View Solution.

Hello @Sachmo499 ,
Welcome to the HP Forums!
I understand your notebook keeps restarting and displays a black screen.
Here's a great place to start troubleshooting startup issues on a notebook:
Computer Does Not Start and the LEDs Blink or the Computer Beeps.
Troubleshooting Black Screen Displays with No Error Messages During Startup or Boot.
Testing for Hardware Failures (Windows 7, Vista) or Testing for Hardware Failures (Windows 8).
If you search for any notebook boot issues or black screen, regardless of the brand you will find this issue everywhere. There are currently no recalls for this product.
If you wish to have the notebook repaired I would suggest calling HP Phone Support for service/repair options. You can contact HP Technical Support at 1-800-474-6836 in North America. For all other regions click here.
If you wish to remove the HDD and connect it to another computer to backup your info, you can follow this guide: Compaq Presario V6000 Notebook PC.
Hopefully this helps!
Please click the "Kudos, Thumbs Up" at the bottom of this post if you want to say "Thanks" for helping!
Please click "Accept as Solution" if you feel my post solved your issue, it will help others find the solution.
The Great Deku Tree
I work on behalf of HP.

Presario f700 black screen at start up,

presario f700 black screen at start up, if left to own it flashes hard drive light once fan starts then turns off the starts again can get it to stop this sequence by pressing certain keys but screen always stays black and remote screen does not turn on. Have tried removing memory, hard reset, removed ram, have tested hard drive out of device. Anything else I can try.
Book says 15secs for a hard reset, one post said 30secs, which is correct

Hi, 30 secs is the better of the two options there. I am assuming the Hard drive tested fine? You can try turning the computer on with out the hard drive in it and see if you atleast get some text saying not bootable device or if you are able to boot into BIOS. If this does not happen you can switch out the ram chips. (boot with one chip then take it out and boot with the other) see if these work. If these steps fail its more than likly more of a hardware issue with the systemboard.
While I may work for HP, my posts and replies are my own and should not be mistaken for statments made by HP as a whole.

My Compaq Presario CQ56

My Compaq Presario CQ56 has a blank screen witha little white line in top corner just flashing can not open recovery manager

Hi
You have a couple of options as I see it please run the Hard drive and Memory test check if both off them passes. Then you could order the Recovery disc from HP Technical support or from the web link given below.
If any test Fails you need to replace the part.
How to Run the Test
Order Recovery Discs for Windows 7, Vista, or XP
Let us know how it goes!
*Although I am an HP employee, I am speaking for myself and not for HP.
****Click the White Kudos star to say thanks****
****Please mark Accept As Solution if it solves your problem****
Regards
Manjunath
Let us know how it goes!
"I work for HP."
****Click the (purple thumbs up icon in the lower right corner of a post) to say thanks****
****Please mark Accept As Solution if it solves your problem****
Regards
Manjunath

Compaq presario cq56 115dx will not power on blinking lights, not a disk drive problem

I own two identical Compaq Presario CQ56 115-DX, and the one I use every day stopped powering on. Shows blinking caps lock light and orange WIFI light does not turn blue to turn on. The fan powers on, but the screen doesn't come on at all. I tried hard resetting several times and it didn't work. I swapped the hard drive of the malfunctioning CQ56 to the other one that was working normally, and it works OK normally. No hard disk corruption or problems.
Any idea how to fix this problem laptop?

Hey @rajpodn ,
Welcome to the HP Forums!
I understand you're looking for info on swapping out the CPU in your notebook.
You will find everything you need here: Compaq Presario CQ56 Notebook PC - Maintenance and Service Guide. The instructions you need start on page 75. Keep in mind that the CPU itself may not be the issue, it could be the socket on the motherboard preventing the notebook from reading the CPU, so even replacing the CPU may not work, as you may need a replacement motherboard. I do not suggest replacing the motherboard as doing so requires HP Proprietary software to reinstall the Service-ID necessary for reinstalling Windows.
*Caution - If you do install the new CPU be careful with the thermal paste. A small pea sized amount should be more than enough. Put the paste in the exact center and carefully spread so there is a fine layer almost to the edge of the CPU. Remember that the heatsink will press very firmly onto the CPU and spread the paste more and you don't want any squishing out as this can cause electrical shorts if the paste has a high metal content.
The part you will want is: AMD V140 processor (2.3 GHz, 512-MB, L2 cache, 1066 MHz, 3.2 GT/s)—singlecore 25 W. The part number for this is: 616333-001.
You can order the CPU directly from HP here: HP Part Surfer, but you may be able to find it cheaper on sites like eBay, Amazon, or Newegg.
Hopefully this covers everything you're after!
Please click the "Kudos, Thumbs Up" at the bottom of this post if you want to say "Thanks" for helping!
Please click "Accept as Solution" if you feel my post solved your issue, it will help others find the solution.
The Great Deku Tree
I work on behalf of HP.

[P6N SLI Platinum] black screen NO BOOT after D-bracket replug [RMA-SOLVED]

Quick setup specs;
P6N SLI Platinum
E6600 (box/stock 2400mhz basic)
2x 1Gb DDR2 6400 Gskill HZ
Sapphire ATI X1600Pro (PCI-e basic)
Aerocool Zero DBA 620W
(2 HDs sata, 2 Hds pata, 2 optical pata at first -all OK at first, disconnected after, so irrelevant here ,( )
(XP Pro clean new install from start)
I tried to check the forum old posts before trying to write that new one, but could not find any really related totally adequate posts so far (or i missed them, sorry if so, then -?). I could already find very useful informations on first aid usual 'rebooting' procedures to follow with minimum new boot configurations, d-bracket new LED signals etc. But so far no luck, all same, nothing better, nothing cured here for the stuation here. ,(( Also excuse my english if not perfect, i am not english either. ,(
VERY bad & sad problem here... ,(((( :
All was working perfectly great during 5 days.. the P6N SLI platinum install went GREAT initially (as normal, not a first pc built, all normally happening, so far so good, etc).... all hardwares compatible together at first (dedicated ATX 'full' 8x8 pins connector too for the cpu only for ex -all working perfect at first try. quick tensions 5V/12V under msi dual core control tool perfect too etc), was great easy going/ great strong ultra-stability feeling on the hardware side.. i was just now concentrating on the software side (no special BIOS tweaks even attempted so far, all on basics-normal e6600/ddr2 auto-settings, apart at the end ddr2 quick test -when problem occured- on 450(900?)Mhz at 2.1V, far far easy under its possible specs max anyway.. and had been working perfect for 3 days with that little ddr2 boost try -no time for special bios further tweakings now, etc), reinstalling and transfering/reorganizing slowly my necessary files/hds/softwares from old to new setup, no oc, nothing special tempted (i was planning oc, new cpu more suited fan/silver6 etc only for the end..), LAN file sharing setup done, Realtek audio setup test done, etc ; installation had been so far one of the quickest and problem free ever... explaining maybe also my fatal lack of cautioun for just (too much) 3 sec in the end after 5/- days of perfect working new ring going on.. ,((( :
At first, i also tried to immediately install the D-Bracket too to check possible hardware install problems -very useful feature i of course thought too..and wanted to try too, "in case of"..- (installing it from quick reading of the printed manual..with no colour pic coding inside..and quick error coming from there thereafter with an initial mismatch usb/jbd1 inverted plugs connections.. *both* having the exact same pins numbers and dispositions, beeing side by side on mainboard layout.. and so able to connect both headers indifferently.. so i did not see it immediately (( .. and no way to see it otherwise as such, anyway.. ,( ), just to be sure all was ok. I noticed that LED were of course, never lightning (not normal).. but as EVERYTHING else was working fine (GLAN, sound, etc etc).. i did not bother more than that -- error checking not necessary.
Till that fatal clumsy day i wanted suddenly to.. check the D-bracket too. ((((
All was working well, XP pro opened for hours as usual etc..
i had not yet totally finished to install the motherboard in the pc-case (always on desk, free in sight..)... so i could always see the connections on it. ... and i noticed that ... the colour headers codes were NOT matching (usb=yellow..).. i had just stupidly initially badly connected the D-Bracket jdb1/usb adjacent plugs (inverting them), so... And still, all had ever worked perfect.. except the D-Bracket, of course, was sending back no lights then, obviously.. so i did the fatal error.. confident all was stable enough and strong if even that initial plug error had had no consequences at all.. i did the fatal bad move to try to UNPLUG the D-Bracket connectors and put them back in right orders WITHOUT switching OFF the power supply so... like an hot USB plug, sort of, in a way. fatal error.. :( :( :(
As soon as i began to remove the usb/jdb1 connectors and put them back in normal order... the system suddenly SHUT DOWN ... no special bad noise, no special smell.. just sudden SHUT DOWN.
From there.. impossible ever to boot back again the so far perfectly working machine (((((((((((( , always same till now :
i switch on the power supply.. orange led appears on motherboard (ok)... i switch on the motherboard.. green led on motherboard appears (ok)... CPU fan begins (ok), video fan begins (ok) .... and... NOTHING.. total black video screen. no more even possibility to see the BIOS. :( total dead startup .. and the fans are going on eternally, blocked eternally in that inital startup with leds on too (no sudden shut down after a few seconds.. just.. nothing)... :(
Suprem irony.. the D-bracket LED seems to 'work' now.. "of course". Just the PC no more booting at all ^. Only thing is that only green LEDs are appearing, no red ones... simply the sequence, from start and never changing :
1. GREEN 2. GREEN
3. GREEN 4. (---) (not red, just nothing -?)
If i look in manual, it means "Testing RTC (real time clock)". I don't know exactly what it means *here*, but sounds to me it is the most basic initial first BIOS checking.. and BIOS can't be reached for even that so ; BIOS fried???? :( :(
I tried every 'standard' things recommanded usually here in older posts, for new boots recovery attempts thereafter in such 'boot errors' situations (clear cmos button pushed in every possible ways -quick, long, quick etc..-, removing little by little everything but the very minimal least energy taxing setup; keyboard, cpu, video, motherboard; 1 ddr2 nearest cpu slot.. point).. NOTHING. Worst, i tried to boot with one of those elements missing.. exact same D-Bracket lightning from start to.. eternally (123 GREEN 4-nothing). Even tried to remove the little (cmos?) KTS lithium battery for a few hours -that could work sometimes with the old already ultra-sensitive amd/nforce2 chipset bioses problems, so i tried there too-?-; same 3 green lights and fans running and nothing else happening from there.. ((
Always the same; total dead boot as above. black screen. no possible access to even bios panel. ,(((
So my desperate questions, now: of course, the origin is obvious here; all happened "by my fault" when i tried 'too quickly' to 'hot-plugging' replace correctly the D-BRACKET plugs *without* switching off the power supply... all shut down suddenly when i put back correctly the usb& jdb1 headers... :( ;
- do you think there could be any possible last HOPES to recover the situation that i had missed (a well known situation in such d-bracket handling 'common' (?) connection error, a simple trick to try i had missed ??)
- do you think i FRIED something in the process on the motherboard ?? :( :(
- do you think it is 'only' the BIOS (fried????) ?? :( :(
- do you think i could have fried a specifical external key component in the process (not necessarily motherboard) : ddr2 modules, cpu, video card????? :( :(
- is my only solution is to send the motherboard to RMA (no other ways now) ???
please, don't hesitate to give me any possible hints to try to avoid the RMA process.
can i avoid it, right now?
is that possible to fry an whole board just with such a D-Bracket 'hot plug switch' (on a so far perfectly working -light- setup - no oc, little video card, etc) ???? :( :(
That is the only C2D Intel/ddr2 motherboard i have here around. No possibility to test elements by elements for precise error checking (cpu, ddr2 modules, video card or powersupply).
Only things i could check so far are;
- the power supply (aerocool 620W zeroDBA) ;
i tested it back on my old amd xp-m nforce2 setup.. always working apparently. NOT 'fried' so, apparently. but no way of course to test for exemple the special 8x8 (or 8x4) Intel ATX cpu connector on old xp-m motherboard. But power supply NOt fried at least, apparently -?
- the video card.
no way for me to really test the pci-e card on other motherboard around but.. i tried a very old PCI VGA card.. that one works on old setup.. and on P6N, no effect, doesn't improve the situation. So, not sure the new pci-e video card isn't fried.. but a new video card doesn't correct the dead boot problem.. (
No way for me to test the ddr2 or CPU directly though.
Do you think DDR2 or CPU could have been fried in the process too ???
or just, as i fear anyway, 'simply', the motherboard BIOS fried -??? :-(
Really, thx for any suggestions..
if there could be an 'hidden' trick i did not try yet to try to recover the (initially working perfectly!!! (( ) setup, WITHOUT engaging the motherboard RMA process (at least 2 or 3 weeks lost here to wait the return..online store etc..)....
please, suggest me.. ,((
i am *really* very sad of that stupid clumsy idea to want to 'enable' the D-Bracket.. all was working great so far.. and i lost all with just that stupid idea to try an hot plug bracket reconnection without switching off the power supply it seems.. can it be possible,sigh?? all seemed so stable before that, that i.. just lost my usual cautious just 3 sec too long it seems... :-(
Thanks in advance
hoping post not too long too, but i tried to expose the situation as precisely as possible; first time i ever had such a problem with a motherboard/system install.. that is quiet ironical knowing it was also the best and quickest/easiest easy going new built i ever had so far too.. till then ,( .. and all came from the 'helper' d-bracket 'luxury second hand possible boot helper diagnostic tool' checking in the end too, here.. really hoping i can avoid an RMA process.. and no other hardware elements (apart the motherboard?) could have been damaged in the process ? ,(((

hi, thx a lot for the quick answer. sorry for the length indeed (i did not know exactly how to describe the situation.. without omitting any later possibly important details).
Alas, i already tried that many times in following interesting asnwers on similar problems in old posts here; did NOTHING. ,(
But after your post, i tried it again, and removed for the remaining *hours* (6/8h?) the cmos battery as suggested again *too* so -pushed again the clear cmos button etc when battery out, then when in again, then replugging the powersupply etc; NOTHING better alas too. always same, no boot, black screen, no bios. ,(
Problem always the same, to sum up, for clarity:
power supply on => orange motherboard led is lightning up, motherboard on => green motherboard led is lightning up, cpu/video/case fans are working up as normal and.. that's all. nothing else forever. black screen. no signal. not a single chance to get again the bios setup screen.
another detail i omitted, maybe; keyboard lights are all lightnng up too.. and stay blocked in that state too. tested with 2 different keyboards, same. to shut down the leds, fans etc, only one solution, shut down the power supply button directly, at that stage.
right now, i test on barebone minimal system as recommanded too;
cpu, 1 dimm (closest cpu slot), video, keyboard. all rest disconnected.
i of course tried to reset the cmos with the 'magical red button' many times before, with power supply cable plugged out, pushed the button trying almost every possible way so far (quick, long, long sequences, short sequences etc etc)... changed NOTHING so far -is that thing working?? ,(. and right now, same after hours with cmos battery removed too. ,(
the d-bracket leds are always (now it is correctly plugged..) :
123 GREEN 4 (nothing)
"Testing RTC (real time clock)"
another 'interesting' detail is that; those leds are appearing IMMEDIATELY after the motherboard is switched on, from start (green led appearing on P6N). and it is staying as such till the end. nothing else. i tried to connect also the case speaker ; no bips, no sound signals at all too.
I also remind the system was WORKING like a dream during 5 days *before* i had that sudden TOTAL boot problem.... AND i touched almost nothing in the bios too all along, for initial security reasons too.. (i was concentrating on the software installs anyway right now, NOT on the oc side..). The ddr2 quick little change i did was also the ONLY change i tempted to simply test quickly some setting i already saw working without problem with that P6N and that kind of ram.. and it was working without problem so far too, so.. all the time idem. And it had been perfectly working for 3 days as such untouched from there; no problems at all (those memory modules have been seen on that motherboard largely at those specs, why i did that quick test anyway.. far under their possible max -micron chips). it was even working so well i forgot to put the setting back as default after that quick ram test.. so much it was stable too (even if i had not time to do real memtest test on that one - i did for many hours with the initial automatical default settings too, to check the ram quality, was perfect for many hours, so ok too, no bad ram initially too-; was so stable for all my XP software installs operations etc.. that i forgot it thereafter, to be true..why it stayed like that till that moment (incidently).. but i preferred to mention it 'just in case' though, yes. i also did not push at all the dimm voltages in the process, it was always far inside the specs at 2.05V to be exact -usual for that ram too up to those numbers easy for it. i did not push the ram voltages either so..).
The problem ONLY appears when i wanted to unplug the *initially* badly connected D-bracket headers so (inverted headers.. but that caused NO problems either so far too for the system stability.. only the LEDs were of course not working so far..) : i did the error to NOT switch off the power supply. :(
*then* immediately the system shut down... and above situation appeared. ,(
BUT all was working perfect before.. ram setting included so. ,((
So my simple questions now too ;
- do you know what means *exactly* the d-bracket message 'Testing RTC" (123 GREEN, 4 nothing).. initial bios problem, isn't it?? other ways to recover it now?? ,((
- is it a WELL KNOWN PROBLEM when we try to disconnect and replug too hastily the d-bracket headers without switching off the power supply (*my* main erorr here, it seems :( :( ) ????
... and of course, do you think it could have *fried* another key component (cpu, ram -?? why i reminded the setting, just in case-?-, video card? .. ) with that d-bracket initial disconnection error ... ,(
as i said, i have no secondary c2d/ddr2 motherboard here : no way to test the cpu and ddr2 modules on another motherboard to be sure too here. :( i absolutely can't know if they have been damaged or not, here.. :( :(
any other idea for the motherboard itself though ??? ,(
once again, thx a lot for any suggestions and precisions on that problem (is that a COMMON well known problem with the d-bracket, when we unplug and replug it without extrem care like i did -my main inattention error it seems.. mainly because all was so stable before too.. ((( - without shutting down the power supply/system FIRST ???? can it be possible 'only' that shut down all the system??? (( )
thx in advance again +

Failed win7 installation, black screen on boot

I have an Imac, about 4 years old, 2ghz core 2 duo.
Last night i attempted to install a copy on windows 7 in bootcamp. I created an install DVD, succesfully created a partition and got about 1/3 way through the installation when it failed. I tried twice then shut down the computer. Today i started the imac, boot sound worked, then after white screen for a few seconds, black screen with a flashing white - in the top left, like dos. I'm unable to type anything.
I've tried booting in safe mode, selecting boot device etc, but nothing. the only thing i've been able to do is eject the windows disk by holding f12.
I'm using a logitech wireleskeyboard and mouse if that matters.
I have also tried creating a bootable usb drive with mountain lion,but as i cant get to the boot menu, it's no use.
I've got all my dada backed up externally so i dont mind having to freshly install if that's an issue.
any ideas? thanks

Could be your monitor power supply is going. could also be 10.6.6 so first try to get back to a OSX which did not give you problems.

Compaq presario cq56 black screen on boot up after replacing the fan and keyboard

Similar Messages

Maybe you are looking for