Computer startup problems

mtbeercan · Post by **mtbeercan** » Tue Jul 13, 2004 6:59 pm

Hi, I just recieved a MX4 display. I followed the manual and tried out the display, everything works fine. After testing I mounted the unit into my case and powered up. I get a "Windows Protection Error" screen anytime I boot up with the MX4 module connected. If I disconnect the module and re-boot the computer it starts ok. After that I can plug in the display and all works well. I have tried different com port settings and plugging / unplugging the floppy drive power cable but to no avail. I searched the forums and read the manual but I don't see anything that helps me with this. Has anyone ever heard of this?

mtbeercan · Post by **mtbeercan** » Tue Jul 13, 2004 7:53 pm

After a little more trouble shooting I found that I can boot up ok if I use the internal USB connectors on the motherboard (USB 3-4). If I try to use the USB 1-2 connections on the rear of the board I encounter the "Windows Protection" error. Any ideas on what's going on?

Xtant · Post by **Xtant** » Wed Jul 14, 2004 9:17 am

I had a similar problem with my LCD, I sent it back to Miles and I believe he reflashed the ROM chip. So far no errors whatsoever.

mtbeercan · Post by **mtbeercan** » Wed Jul 14, 2004 9:44 am

Thanks for the reply xtant, I'm still trying to sort this out. I've done a bit of reading about usb problems and have tried different "fixes" but still having problems on bootup. I have done the following...

1 start windows in safe mode and delete all usb entries
2 install latest via chipset drivers
3 allow windows (98se) to reload the correct controller and hub drivers
4 verified that there are no forced hardware issues
5 ran software to check / repair registry
6 disabled bios to set irq for usb
7 disabled bios for system standby (acpi)

I see that my usb is using irq 10, I have read that it should be using irq 9, but this is a system rescource that cannot be changed. I do see that I have other devices sharing irq 10 such as sound card, video card, and tv tuner card, however all these devices are working properly and there are no "!" marks in system properties. what is really puzzeling to me is that the display will allow the computer to boot if it is attached to the internal comport connections (com 3 & 4). I would think if it locks up the computer on usb coms 1 & 2 it should lock up on coms 3 & 4 also. This is a brand new display, so I'm certain it has the latest flash. Hopefully someone with MO can shed some light on this for me. I don't want to format and reload windows, I have quite a bit of work stored on this machine and it would be a major ordeal to have te re-install everything... especially if formatting and installing a clean copy of windows doesn't correct the problem. By the way this is a older mainboard, soyo k7vta, 133 via chipset, usb 1.0, amd athlon xp2100. I have the latest motherboard flash to enable xp2100 compatibility. Running out of things to check for.

mtbeercan · Post by **mtbeercan** » Wed Jul 14, 2004 8:42 pm

Well it seems like formatting and installing a clean build of windows cleared up the problem. Machine boots up correctly and lcdc does it's thing. In a way I'm happy, I'm glad that this fixed it, but now I get to spend the night feeding the computer discs to get back to where it was. Anyways this was a last ditch attempt that I was a little reluctant to do and I'm glad it worked.

mtbeercan · Post by **mtbeercan** » Thu Jul 15, 2004 5:05 pm

Im going to post again on this thread for anyone else that may search this forum for a problem similar to mine. While feeding discs back to the computer the problem reoccured. This time I knew at least where to look for the offending driver. It seems that soundblaster live audio card was loading a soundblaster 16 emulation driver which caused my problem. After disabeling the driver in Device Manager all works ok now. LCD comes on and computer boots through ok. The offending driver was located under Creative Miscellaneous Devices, and is named Creative SB Live! SB 16 Emutation. By disabeling this device the problem was corrected. Sure wish I had known this before spending the time to format and re-install. Oh well, maybe this thread can help someone going through the same problem as I did.