What the hell does this error mean?

Discussion in 'Windows Desktop Systems' started by fantasi, Jun 9, 2005.

  1. fantasi

    fantasi My Yngy is My HoneY! Folding Team

    Messages:
    307
    Location:
    Perth
    well my computer has been acting up a while now. Firstly it freezes my screen, then it just reboots by itself. that is just hell annoying. Anyone know what it means or if it helps where the logs are kept so i can give to u guys for a look read? if it helps....Arrrh annoying error..
     

    Attached Files:

  2. zeke_mo

    zeke_mo (value not set) Staff Member Political User Folding Team

    Messages:
    1,984
    Location:
    Placerville, CA
    looks kinda like a virus(or viri in parris language), Try a virus scan with any scanner you have, and if you dont have one try avg free edition.
     
  3. unknownsoul

    unknownsoul Moderator

    Messages:
    601
    Location:
    Fort Worth, Texas
    Have you tried a virus scan yet? if not, try here
     
  4. gonaads

    gonaads Beware the G-Man Political User Folding Team

    It's the infinite loop error. Has to do with Video Drivers.

    Update your BIOS Video driver (AGP) and then also update your Video Card drivers. Or reinstall the Video Card drivers.

    I had this happen to me. It's a real pain. It was a different senario but it all tends to do with the AGP driver of the MoBo and the Vid Card drivers.

    Yours could be a variant of this error. Are you using any Symantec/Norton AntiVirus software? If so disable it, turn it off and reboot to see if it stops. There is a problem with the virtual video adapter driver that is used by Symantec. It's used by Symantec's PCAnywhere but I had the problem with the AV proggy. Anyway...



    I posted this:

    http://www.osnn.net/forum/showpost.php?p=629631&postcount=211
     
  5. gonaads

    gonaads Beware the G-Man Political User Folding Team


    Damn zeke, you forget already what happened to me? :eek: :speechless:
     
    fantasi likes this.
  6. Blue Jack

    Blue Jack OSNN Addict

    Messages:
    103
    Oh yeah, the old 256_1 error. Had the same thing, all the documentation I found points towards videocard drivers.

    When I had that error, the only way I could get rid of it was to move my sound card down a PCI slot. I guess with my motherboard my pci 1 slot was sharing resources with my agp slot, and creative and nvidia were not sharing nicely.

    Since I moved my soundcard, never had it happen again. YMMV.
     
  7. zeke_mo

    zeke_mo (value not set) Staff Member Political User Folding Team

    Messages:
    1,984
    Location:
    Placerville, CA

    :rolleyes: tehehe
     
  8. gonaads

    gonaads Beware the G-Man Political User Folding Team


    Yep... There was a thing, a weird thing with Sound Blaster cards and the first PCI slot. Something to do with the first slot being a master slot and having some sort of conflict with the video card slot. I remember that SB actually had a update sheet in their retail boxes pointing this out.



    @ zeke... :mad: Smart ass... I want a refund! :rolleyes:






    :laugh:
     
    zeke_mo likes this.
  9. Johnny

    Johnny .. Commodore .. Political User

    Messages:
    5,015
    Location:
    Happy Valley
    Mostly what that means is that you should clean out your temp files ..
     
  10. fantasi

    fantasi My Yngy is My HoneY! Folding Team

    Messages:
    307
    Location:
    Perth
    ill give it a try guys...see if it still comes up. thx gonaads.
     
  11. fantasi

    fantasi My Yngy is My HoneY! Folding Team

    Messages:
    307
    Location:
    Perth
    ok error still there...which agp thingo is it? is it the gart drivers or smbus driver? or am i barking up wrong tree. and yes i have downloaded the latest nvidia drivers as well. my mobo is on my sig..which one should i install? the drivers from msi.com or the nforce3 drivers from nvidia? cuz i think one is version 5 and the other is 5.10.
     
  12. fantasi

    fantasi My Yngy is My HoneY! Folding Team

    Messages:
    307
    Location:
    Perth
    ok i found the culprit. well im just giving info so that incase some one else gets that error they know how to fix it. Ive fixed with forceware, gart, smbus u name it. norton, sblive. well the reason i have give: forceware, agp drivers, norton, sblive is because those are the top 4 reasons of that error. I have done them all. yet another 5th one is: ram. yup2 thats right. thats the one that fixed for me. just take out ram, start machine, let it beep, put back ram and whambam thankyoumaam...it works fine now guys...
     
  13. gonaads

    gonaads Beware the G-Man Political User Folding Team

    So the Ram wasn't seated correctly. It lost it's connection in the slot. What a pill. Glad ya fixed it.