Hardware

Ask something
Discussion Locked

HP Pavilion dv5000 Resource Conflict Errors upon Start-up

0 helpful
2 replies

by melsocme 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Unfortunately my issue is quite complicated, and no one appears to know what the problem is.

So here it goes:

I have an HP Pavilion dv5000 (dv5224nr) laptop computer that I purchased in August of 2006. Unfortunately, out of no where in October of 2007, one day when I started up my laptop, all of a sudden my laptop beeped 2 times, and 4 Resource Conflicts presented themselves on the screen. They read as follows:

ERROR
Resource Conflict- PCI Serial Bus Controller in slot 03 (Bus:06, Device:04, Function:02)

ERROR
Resource Conflict- PCI Mass Storage Controller in slot 03 (Bus:06, Device: 04, Function: 03)

ERROR
Resource Conflict- PCI in slot 03 (Bus:06, Device:04, Function:04)

ERROR
Resource Conflict- PCI Network Controller in slot 04 (Bus:06, Device:06, Function: 00)

Now as I said, this occurred out of no where. Therefore, I was able to run into windows by selected Resume at the bottom, and everything else worked besides any means of connecting to the internet. The funny thing was, maybe 2/50 times I would turn on my laptop, it would run fine, no beeping or errors or anything.

I then proceeded to sit at my house computer, attempting to chat with some HP technicans via online, and got a variety of responses from each of them. One was saying it was a memory issue, another was saying it was static electricity, and another was saying it was my motherboard. So I decided to take it into Geek Squad at Best Buy to get it looked at, since my warranty was already up for HP. Upon bringing it into Geek Squad, they ran a diagnostic, and told me that my hard drive didn't pass, and if I replace that, it will be fixed. So I paid overall, about $200 to Geek Squad to supposedly get this issue fixed, but to my surprise, when I turned it on after reinstalling windows xp and all the drivers and applications, it still beeped! Upon bringing it back to Geek Squad, they then told me that it was my Operating System that was causing the issue....

Now correct me if I'm wrong, but I am pretty damn sure that it could not be my OPERATING SYSTEM, considering my internet, and these issues would arise, ANYTIME i lifted my computer up off a desk to reposition it, or even touched it a way it didn't like. Now I'm pretty sure that after uninstalling and reinstalling these (!) drivers, and it still not working, wouldn't mean it is my operating system. I even had someone that knows alot of software installation sitting next to me as i Installed Windows XP on my new harddrive myself, and have it still not work.

Please Help Me!

2 replies

by hal 9000

Side of TR mainly because you get instant Notifications when ever anyone posts an answer & there can be different people who answer questions to those that Haunt the Discussion Forums.

But the give away here is the fact that if you move or touch the NB in a way that it doesn't like you get a problem crop up. Generally speaking Interments are a PAIN to attempt to fix but as you can make it do as you like when you like is much better as it's easier to find the problem. Start off by pulling the RAM and reseating it sometimes a bit of corrosion or muck gets caught between the contacts and can have a detrimental effect.

Depending on where you touch the thing to get the problem it could be a Broken Lead/Cable or socket that is not making a connection. As the unit under test failed the HDD test this doesn't mean that the HDD was damaged or not working just that it needed more testing. So it's possible that the old HDD is OK but either the M'Board or the means of connecting the HDD to the M'Board has a problem. It could be something as simple as a new Data Lead between the M'Board and HDD or it could be the socket on the M'Board isn't correctly soldered to the M'Board. This unfortunately is a job for a professional and to be honest Geek Squad isn't that expert.

Look in your Area for a HP Authorized Repairer and ask then what problems they have had with this Model of NB there even may be a Recall of the product for a Known Issue. Also make sure that the NB isn't allowed to sit on any surface with Table Cloths or other coverings that can get sucked up and block the Air Intake that is used for colling the CPU and also look for a build up of Dust and other rubbish at the Air Intake [the place where the fan/s suck air into the NB.]

Also post this in the Question Forums as there are several people who work with HP Products that may have a much better idea than I of this problem.

Col

by bbengr

Had similar error with PCI Network Controller errors on a V5000 - found I had the main/aux wireless connections reversed on the Wireless LAN mini-pci. blk-main, wht-aux is correct.

This discussion is closed to new replies.