Tip: Run a free scan for common Windows errors ad

re: Resource conflict PCI display controller Saturday, March 25, 2006 at 7:18 pm Posted by Tim (101 messages posted) One more thing. I am unable to get into safe mode to investigate further. I tap the F8 key, no luck. I hold down the F8 key, no luck. I have read that the ctrl key may work but I have not tried it as I am trying to get some ideas before I drive over there again. Thanks again. Tim On Saturday, March 25, 2006 at 6:30 pm, Tim wrote: >Good evening; I am attempting to fix a computer for a friend. The problem is, upon >bootup the computer beeps twice instead of the normal once when the OS takes over. > The DOS startup screen comes up and it seems the boot process is stopped by the >following error. "Resource conflict PCI Display Controller in slot 01 Bus:01, Device:OE, >Function:00." When I continue, it takes me to the BIOS setup screen. My friend's >husband is deployed to Iraq and this is her only means of communication with him. > Any help would be greatly appreciated. The case has not been opened, and no changes >have been made to the system before this error occured. > >Tim [Reply or follow-up to this message] re: Resource conflict PCI display controller Saturday, March 25, 2006 at 7:38 pm Posted by bob wells (1590 messages posted) Tim, Without knowing which, of many, Bios is in your friends computer, it's difficult to know what the problem is. If you can determine who produced the bios in her system, this link may have the answer. http://www.pchell.com/hardware/beepcodes.shtml The most common ones indicate Memory problem with 2 beeps. Could be something else. google search by Manufacturer and Model# could supply which Bios is installed. If yu can get back to the Bios setup screen, you could try restoring default values. Instructions for this shoulb be on setup screen, maybe even Bios mfg. and version #. BW. On Saturday, March 25, 2006 at 6:30 pm, Tim wrote: >Good evening; I am attempting to fix a computer for a friend. The problem is, upon >bootup the computer beeps twice instead of the normal once when the OS takes over. > The DOS startup screen comes up and it seems the boot process is stopped by the >following error. "Resource conflict PCI Display Controller in slot 01 Bus:01, Device:OE, >Function:00." When I continue, it takes me to the BIOS setup screen. My friend's >husband is deployed to Iraq and this is her only means of communication with him. > Any help would be greatly appreciated. The case has not been opened, and no changes >have been made to the system before this error occured. > >Tim [Reply or follow-up to this message] re: Resource conflict PCI display controller Saturday, March 25, 2006 at 8:10 pm Posted by Tim (101 messages posted) Thanks for the reply Bob. She has Phoenix Bios. I looked around their site and could not find a code for 2 short beeps. I did see something that stated any number of beeps after the 2 beeps indicated a memory problem. This is not the case. There is simply 2 short beeps. Any suggestions for getting into the safe mode? I cannot even access a DOS prompt. Thanks again Tim On Saturday, March 25, 2006 at 7:38 pm, bob wells wrote: >Tim, > >Without knowing which, of many, Bios is in your friends computer, it's difficult >to know what the problem is. > >If you can determine who produced the bios in her system, this link may have the >answer. > >http://www.pchell.com/hardware/beepcodes.shtml > >The most common ones indicate Memory problem with 2 beeps. Could be something else. >google search by Manufacturer and Model# could supply which Bios is installed. If >yu can get back to the Bios setup screen, you could try restoring default values. >Instructions for this shoulb be on setup screen, maybe even Bios mfg. and version >#. > >BW. > > > [Reply or follow-up to this message] re: Resource conflict PCI display controller Saturday, March 25, 2006 at 8:39 pm Posted by bob wells (1590 messages posted) Tim, Reboot holding the F8 key, (some say to tap it repeatedly but I've never gotten that to work). You should get to the boot menu. If so, select command prompt only, hit enter, at the C:\> type Scanreg_/restore hit enter. (Underscore indicates a space). You should see a list of registry backups, Select one that predates this problem and that has "started", preceeding it. Once selected, hit Enter. should see a message Rgistry Checker is Restoring System.dat user.dat. Next message, Windows has successfully restored"... At the C:\> type Win >Enter, or power down and restart. Control/alt/delete also works. If none of this is possible, it could be CMOS Battery on Motherboard, or it just could be Memory. Good luck. Bob On Saturday, March 25, 2006 at 8:10 pm, Tim wrote: >Thanks for the reply Bob. She has Phoenix Bios. I looked around their site and >could not find a code for 2 short beeps. I did see something that stated any number >of beeps after the 2 beeps indicated a memory problem. This is not the case. There >is simply 2 short beeps. Any suggestions for getting into the safe mode? I cannot >even access a DOS prompt. > >Thanks again > >Tim > > > [Reply or follow-up to this message] re: Resource conflict PCI display controller Saturday, March 25, 2006 at 9:58 pm Posted by Tim (101 messages posted) Thanks anyway Bob. As I put in my first post, I have tried tapping and holding the F8 key. I am still not able to get into the boot menu. The system just procedes to the error I discussed. I am frustrated because I cannot get to a place to troubleshoot the problem such as the boot menu (for DOS or safe mode). I am completely stuck. Thanks again. Tim On Saturday, March 25, 2006 at 8:39 pm, bob wells wrote: >Tim, > >Reboot holding the F8 key, (some say to tap it repeatedly but I've never gotten that >to work). You should get to the boot menu. If so, select command prompt only, hit >enter, at the C:\> type Scanreg_/restore hit enter. (Underscore indicates a space). > >You should see a list of registry backups, Select one that predates this problem >and that has "started", preceeding it. Once selected, hit Enter. should see a message >Rgistry Checker is Restoring System.dat user.dat. Next message, Windows has successfully >restored"... At the C:\> type Win >Enter, or power down and restart. Control/alt/delete >also works. > >If none of this is possible, it could be CMOS Battery on Motherboard, or it just >could be Memory. > >Good luck. > >Bob > > > [Reply or follow-up to this message] re: Resource conflict PCI display controller Saturday, March 25, 2006 at 11:06 pm Posted by bob wells (1590 messages posted) Tim, If you have a win98 boot floppy, startup with the disk in the drive. If you get to the A:\> type sys_C: hit enter. (underscore=space). you should see "system transfered". power down and restart. If she doesn't have a boot floppy, one can be made on any win98 system from Control Panel Add/remove programs> create disk tab. Can also download from www.bootdisk.com. Save the file to desk top, put new floppy in drive and doubleclick on file. boot disk will be created. file you want is win98se OEM. Try opening the case and reseating the Ram modules, check all connections outside computer. also the Display connections inside and out. Got any Geek friends? Hope something helps. Memory problem could be video memory. bw Y Did you try restoring Bios defaults? On Saturday, March 25, 2006 at 6:30 pm, Tim wrote: >Good evening; I am attempting to fix a computer for a friend. The problem is, upon >bootup the computer beeps twice instead of the normal once when the OS takes over. > The DOS startup screen comes up and it seems the boot process is stopped by the >following error. "Resource conflict PCI Display Controller in slot 01 Bus:01, Device:OE, >Function:00." When I continue, it takes me to the BIOS setup screen. My friend's >husband is deployed to Iraq and this is her only means of communication with him. > Any help would be greatly appreciated. The case has not been opened, and no changes >have been made to the system before this error occured. > >Tim [Reply or follow-up to this message] re: Resource conflict PCI display controller Sunday, March 26, 2006 at 12:13 am Posted by Tim (101 messages posted) Thanks Bob. I'll try a 98 boot disk tomorrow as it is midnight here. Also, I did try setting the bios to defaults. No luck. Thanks again. Tim On Saturday, March 25, 2006 at 11:06 pm, bob wells wrote: >Tim, > >If you have a win98 boot floppy, startup with the disk in the drive. If you get to >the A:\> type sys_C: hit enter. (underscore=space). you should see "system transfered". >power down and restart. > >If she doesn't have a boot floppy, one can be made on any win98 system from Control >Panel Add/remove programs> create disk tab. Can also download from www.bootdisk.com. >Save the file to desk top, put new floppy in drive and doubleclick on file. boot >disk will be created. file you want is win98se OEM. > >Try opening the case and reseating the Ram modules, check all connections outside >computer. also the Display connections inside and out. > >Got any Geek friends? > >Hope something helps. Memory problem could be video memory. > >bw > >Y > >Did you try restoring Bios defaults? > > > [Reply or follow-up to this message] re: Resource conflict PCI display controller Sunday, March 26, 2006 at 12:18 am Posted by gewg_ (3923 messages posted) |If you have a win98 boot floppy... | bob wells As I understand it, he's not getting thru POST. "Boot" means that a computer pulls itself up by its bootstraps. It is a series of BIOS routines that checks and initializes the hardware. It happens even if there is no operating system on the machine. The next to the last thing that happens during boot is that the speaker beeps. One beep means all the hardware checked out OK; any other beep code means there is a hardware problem. The last thing that happens in the boot process is that the computer goes looking for an OS. If an error code is encountered before the single-beep thing, the BIOS routines branch to a place in the BIOS from which it will NOT try to acces ANY disk. The hardware problem has to be cleared before BIOS will complete POST. The usual way to do this is to strip the machine to "bare bones". After removing all non-essential plug-in stuff, you are left with 1 stick of RAM and a video card. If it still won't pass POST, you pull the video card (and will get a video failure beep code). If it does pass POST, you start putting stuff back, beginning with memory modules. ||The DOS startup screen comes up || Tim || Do you see a DOS prompt that identifies the disk or is it just a black screen that you assumed to be DOS? I'm betting that the message is from the BIOS, not from an OS. [Reply or follow-up to this message] re: Resource conflict PCI display controller Sunday, March 26, 2006 at 12:33 am Posted by bob wells (1590 messages posted) Hi gewg_, What ya doin up so late? Where were You earlier. LOL So if I'm understanding your Post, any Bios code, Beeps, whatever, that is not the single, Post beep, occurs earlier in the Bios routine, and interrupts the Boot process? The Os will not load. I was thinking that the Display Pci conflict message came from the OS, indicating passing Post with Problems that could be resolved from safe mode/device manager. Guess I should have known from PCHell's comments concerning 2 or more Beeps. It's a good day when you learn something new. See ya. BW On Sunday, March 26, 2006 at 12:18 am, gewg_ wrote: >|If you have a win98 boot floppy... >| bob wells > >As I understand it, he's not getting thru POST. > >"Boot" means that a computer pulls itself up by its bootstraps. >It is a series of BIOS routines that checks and initializes the hardware. >It happens even if there is no operating system on the machine. > >The next to the last thing that happens during boot >is that the speaker beeps. >One beep means all the hardware checked out OK; >any other beep code means there is a hardware problem. > >The last thing that happens in the boot process >is that the computer goes looking for an OS. >If an error code is encountered before the single-beep thing, >the BIOS routines branch to a place in the BIOS >from which it will NOT try to acces ANY disk. > >The hardware problem has to be cleared before BIOS will complete POST. >The usual way to do this is to strip the machine to "bare bones". >After removing all non-essential plug-in stuff, >you are left with 1 stick of RAM and a video card. > >If it still won't pass POST, you pull the video card >(and will get a video failure beep code). > >If it does pass POST, you start putting stuff back, beginning with memory modules. > > >||The DOS startup screen comes up >|| Tim >|| >Do you see a DOS prompt that identifies the disk >or is it just a black screen that you assumed to be DOS? > >I'm betting that the message is from the BIOS, not from an OS. [Reply or follow-up to this message] re: Resource conflict PCI display controller Sunday, March 26, 2006 at 12:55 am Posted by bob wells (1590 messages posted) Tim, Guess I was way off base. Had you going in the wrong direction. These ----- Experts are never here when ya need em. Ehh. al least they finally show up. Sorry I wasn't more real help. BW On Sunday, March 26, 2006 at 12:13 am, Tim wrote: >Thanks Bob. I'll try a 98 boot disk tomorrow as it is midnight here. Also, I did >try setting the bios to defaults. No luck. > >Thanks again. >Tim > > > [Reply or follow-up to this message] re: Resource conflict PCI display controller Sunday, March 26, 2006 at 1:09 am Posted by J.R. (2349 messages posted) BIOS beep codes (AMI, Award, Phoenix etc.) including those from major computer manufactures (Dell, IBM, Compaq etc.) BIOS Central [Reply or follow-up to this message] re: Resource conflict PCI display controller Sunday, March 26, 2006 at 9:43 am Posted by gewg_ (3923 messages posted) |Hi gewg_, |What ya doin up so late? | bob wells | Look who's talking, young man. 8-) |Where were You earlier. LOL |...I was thinking that the Display Pci conflict message came from the OS... | After I let it rattle around in my head for a while, I realized that was the part that was the red herring --the piece of the puzzle that didn't fit. (If you haven't see how Ann-Margret's character in "The Cinncinatti Kid puts together jigsaw puzzles, make an effort to see that. It's priceless.) [Reply or follow-up to this message] re: Resource conflict PCI display controller Sunday, March 26, 2006 at 10:20 am Posted by Tim (101 messages posted) Thank you all for your replies. Just to clarify, it is not a DOS screen that pop's up with the error. There error occurs with the initialization of setup. I'm sorry, but I can't come up with a better way to explain it. I am totally unable to get into DOS or the boot screen that gives the option to start in safe mode. I am going to attempt to start the machine with a 98 boot disk and see if I can locate light at the end of the tunnel. Thanks again. Tim On Sunday, March 26, 2006 at 9:43 am, gewg_ wrote: >|Hi gewg_, >|What ya doin up so late? >| bob wells >| >Look who's talking, young man. 8-) > >|Where were You earlier. LOL >|...I was thinking that the Display Pci conflict message came from the OS... >| >After I let it rattle around in my head for a while, >I realized that was the part that was the red herring >--the piece of the puzzle that didn't fit. >(If you haven't see how Ann-Margret's character in "The Cinncinatti Kid >puts together jigsaw puzzles, make an effort to see that. >It's priceless.) [Reply or follow-up to this message] re: Resource conflict PCI display controller Sunday, March 26, 2006 at 10:48 am Posted by gewg_ (3923 messages posted) |Just to clarify, it is not a DOS screen that [pops] up with the error. | Tim | Now we're getting somewhere. |I am totally unable to get into DOS | Now we're back-sliding. |I am going to attempt to start the machine with a 98 boot disk | and we're spinning our wheels again. As I said, you're not getting that far. You have a HARDWARE problem that needs to be cleared. Find where I said bare bones. [Reply or follow-up to this message] re: Resource conflict PCI display controller Tuesday, September 5, 2006 at 1:50 am Posted by Kobe (1 messages posted) Hey people i had the same problem Gweg is right i stripped it down to bare bones started it up took the error that came turned it off put everything back in and TADA works like magic it took me about ten minutes to solve this problem if you listen to his advice and follow it step by steppy step it should take you the same thanks gweg On Sunday, March 26, 2006 at 10:48 am, gewg_ wrote: >|Just to clarify, it is not a DOS screen that [pops] up with the error. >| Tim >| >Now we're getting somewhere. > >|I am totally unable to get into DOS >| >Now we're back-sliding. > >|I am going to attempt to start the machine with a 98 boot disk >| >and we're spinning our wheels again. >As I said, you're not getting that far. >You have a HARDWARE problem that needs to be cleared. >Find where I said bare bones. [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows 98 Discussion Forum