LCDC Error, hardware or software?

Xtant · Post by **Xtant** » Mon May 03, 2004 3:09 pm

Well I finally have things running at home but now I"ve run into this bit of crap. I programmed all my screens got it running, installed a fresh copy of WinXP on my system etc etc. But even with my system idling and doing nothing I get a fault error in LCDC and it locks up the screen. I can click ok and it goes away however I get errors all over the place if I try to access LCDC again and the program locks. If I just logoff and back on instead of rebooting I get the same errors. If I warm boot the screen stays locked during reboot and the screen has to be manually started when the system reboots fully. Here is a screenshot of the error message I receive when it crashes.

Xtant · Post by **Xtant** » Tue May 04, 2004 8:46 am

Well did more testing and still can't get rid of this issue. Other USB devices on my system are working fine and a fresh install of LCDC didn't help either. It appears to my untrained in things LCD eye that it is a USB communication error possibly a bad controller on the LCD? Anyone? Anyone? Bueller?

Xtant · Post by **Xtant** » Tue May 04, 2004 11:59 am

Spoke with Matt-D-Rat over at the LCDC forums and he seems to think it's a hardware based issue. I'm tending to agree with him at this poiint. I've reset the screen, reloaded LCDC, have a fresh OS install and still this error will crop up randomly. Sometimes after 2 min, sometimes after 2 hours. What do I need to do for possible repacement/RMA?

Miles · Post by **Miles** » Tue May 04, 2004 12:50 pm

I got your email!! Thanks!

Xtant · Post by **Xtant** » Thu May 06, 2004 8:45 am

Hey Miles just as a note to this issue. I totally uninstalled/reinstalled LCDC that seemed to help a little, it only errored every 5-6 hours. Then I replaced the internal USB cable with an external one. Now I haven't errored in a day. So now I'm guessing it's either a bad internal cable or a bad connection of the cable to the system board. Can't see any cracked solderes or anything by the int. USB cable connector but thought you should know what I found out playing with it.

Miles · Post by **Miles** » Thu May 06, 2004 9:50 am

Let me know how you make out with that...! In the meantime, check your email about the MX4!

Xtant · Post by **Xtant** » Thu May 06, 2004 10:48 am

Miles wrote:Let me know how you make out with that...! In the meantime, check your email about the MX4!

I sent ya some mail back about that, you let ME know about the MX4 *grin*

WinoOutWest · Post by **WinoOutWest** » Thu May 13, 2004 12:58 am

o my...this is exactly the same problem I am having! Same error code and almost the same setup.

How is yours running now? All Fixed and stable?

One other thing I can add:

I had the same problem as you - then for other reasons had to reinstall everything from scratch (Clean XP/LCDC etc) I left it for a few weeks stock and the errors were gone. Never got the error once. Then yesterday I started to "personalize" my config and now I am back to this same error message. Some times after 2 minutes sometime two hours. I have to uninstall and re-install the MO Drivers to get it working again. Yesterday I added 2 new plugins to my setup: Speedfan and Zoomplayer. I also added my2 temp probes back in. I have since uninstalled the ZP and speedfan dlls but the errors are still coming fast and furious. (did I mention this is annoying)

Miles · Post by **Miles** » Thu May 13, 2004 1:54 pm

Are you using an internal or an external USB cable?

WinoOutWest · Post by **WinoOutWest** » Fri May 14, 2004 3:15 pm

Miles wrote:Are you using an internal or an external USB cable?

I was using internal - but decided to try external, which I just did but it errored out as well after about 20 minutes connected externally.

Any other ideas?

-Wino

WinoOutWest · Post by **WinoOutWest** » Sun May 30, 2004 1:42 am

Bump for a new week.
This is the week I solve my problem.
Matrix: Do I need log a formal issue with you?

WinoOutWest wrote:
Miles wrote:Are you using an internal or an external USB cable?
I was using internal - but decided to try external, which I just did but it errored out as well after about 20 minutes connected externally.

Any other ideas?

-Wino

Post by **Mat-Moo** » Sun May 30, 2004 5:19 am

Is this happeneing after a "Sleep" or "Hibernate" etc. or just any time.

WinoOutWest · Post by **WinoOutWest** » Sun May 30, 2004 11:11 pm

mat-d-rat wrote:Is this happeneing after a "Sleep" or "Hibernate" etc. or just any time.

Definitely anytime... usually within the first hour after starting LCDC. The machine never shuts down or hibernates. If I boot and don't run LCDC (and just run with the startup screen) then it will run for days with no errors.

Miles · Post by **Miles** » Mon May 31, 2004 12:51 pm

So, basically whenever you are communicating with the module, errors occurr?? When using LCDC, can you autodetect??

WinoOutWest · Post by **WinoOutWest** » Mon May 31, 2004 1:03 pm

Miles wrote:So, basically whenever you are communicating with the module, errors occurr?? When using LCDC, can you autodetect??

Yes that's probably safe to say. If I am not communicating with the module it doesn't error.

I can autodetect after I (cold) reboot. Once I get that error the backlighting goes off LCDC won't recognize it until I (cold) reboot. Not sure if this helps troubleshoot or not but if I don't want to shut down I can get the LCD working again by going into Control Panel->Hardware - removing the Matrix orbital and then reinstall the drivers.

LCDC Error, hardware or software?

LCDC Error, hardware or software?

EXACTLY the same problem!!