Corrupted UI in XP

Discussion in 'other software & services' started by TimaN, Mar 4, 2012.

Thread Status:
Not open for further replies.
  1. TimaN

    TimaN Registered Member

    Joined:
    Aug 22, 2005
    Posts:
    125
    Location:
    Tulsa, OK
    Okay, I fought this issue for a few weeks now, and I'm running out of ideas. I woke up one morning to find my GUI all corrupted as shown on screenshots. I restart and all is well for several days. After that time period the problem repeats. I wanted to use a screen capturing software to capture this, but PC is unusable in that state. The computer is virus free, I updated graphic drivers, ran chkdsk and system file check. Anyone knows what might be causing this?

    IMG_5426 (Small).JPG

    IMG_5427 (Small).JPG
     
  2. Kerodo

    Kerodo Registered Member

    Joined:
    Oct 5, 2004
    Posts:
    7,786
    Just curious... is this the same machine that wouldn't post on reboot?
     
  3. TimaN

    TimaN Registered Member

    Joined:
    Aug 22, 2005
    Posts:
    125
    Location:
    Tulsa, OK
    Yes, I wanted to start a separate thread. I have a few issues going on at the same time.
     
  4. Kerodo

    Kerodo Registered Member

    Joined:
    Oct 5, 2004
    Posts:
    7,786
    Ok, just wondering if they are related....
     
  5. blacknight

    blacknight Registered Member

    Joined:
    Sep 25, 2007
    Posts:
    2,434
    Location:
    Europe
    It sounds like Explorer was corrupted.
     
  6. Keyboard_Commando

    Keyboard_Commando Registered Member

    Joined:
    Mar 6, 2009
    Posts:
    690
    Are those swirly lined patterns in the first pic what you saw on the screen at the time ... or just poor pic quality?

    Going by that screenshot, and the problems with booting up, you've got to do some detective work by swapping hardware to see which is faulty. Those swirling and lines look like either ram or graphic artifacts, which can be a result of faulty cooling, too much overclocking of the GPU; CPU; Ram; or any of these components + motherboard failing. There are a whole heap of potential scenarios. If you are not really able to do the detective work then save yourself the time and potential cost by taking it into be repaired.

    Here is a pretty good website.

    Ideally get your hands on some hardware to try in place of yours. Beg, steal, or borrow if you haven't got them. That is rather than spending money on one component and it not being the problem.
     
  7. Cudni

    Cudni Global Moderator

    Joined:
    May 24, 2009
    Posts:
    6,956
    Location:
    Somethingshire
    Did you check with several tools that the machine is malware free?
     
  8. TimaN

    TimaN Registered Member

    Joined:
    Aug 22, 2005
    Posts:
    125
    Location:
    Tulsa, OK
    The swirly lines are just a moire pattern that happens when taking pictures of the monitor. The computer was checked with various anti-malware tools and I have an active antivirus running. I suspect some sort of software corruption, like an explorer. What I don't understand is why all is well for a couple of days and the next day same thing happens.
     
    Last edited: Mar 4, 2012
  9. guest

    guest Guest

    I had this same problem or close to the same
    and just finally brought a new motherboard
    and basically built a new computer, reinstalling
    windows would only work temporary, never did
    find out if it was software or hardware related
    sometimes it seemed to be both or either:thumbd:
     
  10. The Shadow

    The Shadow Registered Member

    Joined:
    Jan 24, 2012
    Posts:
    814
    Location:
    USA
    If you have a backup image that was taken when all was well, restore it...

    ...otherwise I would suggest backing up all personal files and then doing a WinXP Repair-Install.
     
    Last edited: Mar 4, 2012
  11. TimaN

    TimaN Registered Member

    Joined:
    Aug 22, 2005
    Posts:
    125
    Location:
    Tulsa, OK
    I found this entry in the event log: Event ID: 4609 "The COM+ Event System detected a bad return code during its internal processing. HRESULT was 800705AA from line 44 of d:\comxp_sp3\com\com1x\src\events\tier1\eventsystemobj.cpp." Could this be related to my problem?
     
Loading...
Similar Threads
  1. Overkill
    Replies:
    69
    Views:
    3,393
Thread Status:
Not open for further replies.