Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works

HP Pavillion Laptop Fails to Boot

  • Please log in to reply




  • Member
  • PipPip
  • 30 posts
Hey guys, a friend of mine just recently told me about a problem with her laptop computer that it just fails to boot up properly, and she's not very computer 'saavy' so anything I would ask her would go through one ear and out the other, so I took it upon myself to help her figure this out.

The laptop in question is an HP Pavillion dv6000 running on Windows XP. When I turn the computer on it goes in the process of booting the BIOS and everything seems to work properly, it's only after the Windows XP Logo loading screen is over that it hits the blue screen and and very small error(about 6-7 lines) pops up. I was only able to make out the first line, and it looked a little something like 'STOP: [Unable to locate component]' I think there was some numbers and capital letters behind '[Unable to locate component]', but I couldn't make those out correctly as it reboots and goes through the same process continually.

If you can help me out here that'd be great, or any questions that I can possibly relay over to my friend so she can answer and I can keep responding to this thread would be very much appreciated!

Thank you!

*Edit* Okay, so I made an attempt to look what the other lines said, and it looks like it's only 3 lines of text. The second and 3rd text go to say that 'The application failed to start because blah blah 'User32.dll' " It was something like that and the only particular text that caught my attention was that User32.dll file that could be contributing to the error.
  • 0


Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP