Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

PCI bus conflict apparently causing Win95 lockup

Posted on 1998-07-04
8
Medium Priority
?
335 Views
Last Modified: 2013-12-16
How do I detect a correct an apparent PCI bus conflict which causes Win95 to hang during bootup? I recently added a Creative Labs 3D Blaster Voodoo2 to my system, precipitating this problem. The Diamond Video VRAM card has a know conflict with the 3D Blaster which was supposedly fixed by running a utility (S3fixv2.exe) which apparently changes the values in address registers on one of the cards. After accomplishing the remap operation, the utiltity then spit a message to the effect that the 3D Blaster/Diamond conflict was fixed but that it had detected another PCI bus conflict that is unrelated to the 3D Blaster card. Win95 now hangs with a gray screen after the Windows 95 flag screen disappears! Arrrrrgggggggg!

The only approach that I know of is to tear down the machine and install one board at a time, letting Win95 detect and install it to see where it fails. Bummer!
0
Comment
Question by:rgallaway
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
8 Comments
 
LVL 4

Expert Comment

by:swwelsh
ID: 1756765
Do you have any other pci cards installed? I would go into device manager and check the memory resources of the all the pci cards to see if you can find a conflict. I would also bitch at Creative Labs since their card and/or utility have apparently rendered your system unusable. That is not a good recommendation for their product - if they didn't help I would return the card.
0
 
LVL 1

Expert Comment

by:jrbuck
ID: 1756766
take a look in the CMOS setup utility.  There is a way to assign interrupts and change other values for the PCI setup.  It is possible that you can do a rebuild or refresh, or even to set the cards up manually.
0
 
LVL 17

Expert Comment

by:mikecr
ID: 1756767
Have you tried starting in Safe Mode and going into the device manager in control panel and setting the resources manually? You can set a known conflicting device to another address and IRQ and then set your sound card up afterwards.


Mike
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Expert Comment

by:Brentman
ID: 1756768
I think jrbuck is probably on the right track. Look for a "Reset Configuration" option under PNP or PCI in your CMOS.
0
 
LVL 2

Expert Comment

by:harley47
ID: 1756769
i too agree with jrbuck but also you can try going into safe mode and removing all entries for the Voodoo 2 card and the regular video card this will make windows find them again and should set the IRQ's differently.  One other strange thing is normaly the PCI Bus can share IRQ's. (though it is not common for two video cards to share one)
0
 
LVL 1

Expert Comment

by:cmw
ID: 1756770
You might try to swap PCI boards around. PCI slots get a IRQ assigned during bootup by the BIOS. I was lucky, my BIOS allows me to specify which slot should use which IRQ. Other BIOS don't allow this. Allthough PCI slots allow IRQ sharing, some boards do not. I have a Adaptec 2930, Matrox Millenium and a NE2000 PCI clone. By default the BIOS set the Adaptec and Nic to share an IRQ. Seemed ok, but windows kept shutting down one of the two (Adaptec seemed to win more).

Set up system so that Nic and video shared IRQ and all problems went away. Most video drivers do not use an IRQ. I had no IRQ's left so this was the only option for me.

Also be sure to exclude any ISA resources in the BIOS. This will prevent the BIOS from assigning these to the PCI slots. You don't need to reserve them in W95, as long as W95 detect the device properly.
0
 

Expert Comment

by:itbruce
ID: 1756772
Try to see if there is any conflict for memory or irq in device manager. If it is. try to remove or unload the conflicted device. If it is IRQ conflict, try to look for any free IRQ available.
Then, disable (if possible, any setup program) the PNP feature of the device and manually assign the free resources for the devices. If it still doesn't work, try to refresh the BISO setup (use default)  or upgrade BISO. Or try to disble BISO PNP feature if it has. And install the device manually. Lastly, get all the latest drivers for all devices and remove them form device manager, and windows detects them and assign the resources for them.
0
 
LVL 14

Accepted Solution

by:
smeebud earned 200 total points
ID: 1756773
CAUSE

This problem is caused by a Plug and Play BIOS that is not supported by Windows 95 on computers that
have a PCI BIOS but not a PCI bus.

On PCI computers, it is the PCI driver that starts the Plug and Play ISA driver. If the PCI driver fails, the ISA
driver is not loaded, and Plug and Play ISA adapters are not automatically recognized or configured.

RESOLUTION

To add a Plug and Play adapter so that Windows 95 automatically recognizes it, enable the ISA Plug and
Play bus using the following steps:

1.In Control Panel, double-click the Add New Hardware icon, and then click Next.

2.Click No, and then click Next.

3.Click System Devices, and then click Next.

4.Click ISA Plug And Play Bus, and then click Next.

5.Click Finish.

6.When you are prompted to restart your computer, do so.

You may also want to contact your computer manufacturer to inquire about obtaining an updated Plug and
Play BIOS that is supported by Windows 95.

http://support.microsoft.com/support/kb/articles/q132/7/66.asp

Please tell us all about you system, hardware and software.

Bud
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is a collection of issues that people face from time to time and possible solutions to those issues. I hope you enjoy reading it.
Windows Server 2003 introduced persistent Volume Shadow Copies and made 2003 a must-do upgrade.  Since then, it's been a must-implement feature for all servers doing any kind of file sharing.
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question