zer0point 0.7184 messed my pc up.

Discussion in 'NVIDIA Graphics Cards' started by EvilKnivel, Apr 12, 2005.

  1. EvilKnivel

    EvilKnivel New Member

    Joined:
    Apr 12, 2005
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    0
    Hi there.

    Looking for optimized drivers, i downloaded yesterday the DH zer0point 71.84 release. After a clean install using Drivercleaner i recieved severeal Bluescreens in CSS. So i decided to switch back to the usual 71.84 drivers ( drivercleaner used again).

    No more bluescreens for me, but now i get an error "memory cout not be written" (not sure if its the correct translation) this happens like every 10 Minutes of playing, i once in a while rezieved the same error when changing s.th in graphics options while playing css, but never in regular playing.

    Now im asking myself what i should do. Its pretty clear to me that those drivers are/were part of the problem, sure it could be totally driver independent but i doubt that.


    My system is as followed:

    Barton Xp 2500@3200
    1 gig ddr400 Ram (Corsair)
    6600GT Gainward
    NF7 Mobo



    Any Ideas? ​
     
    Last edited: Apr 12, 2005
  2. PoopyTheJ

    PoopyTheJ New Member

    Joined:
    Jan 15, 2003
    Messages:
    1,584
    Likes Received:
    1
    Trophy Points:
    0
    did you run DC pro in safemode after uninstalling the drivers? IE uninstall drivers, reboot into safemode and run DC Pro, then reboot and install drivers followed by a reboot after the install? I would also check for spyware/adware and or viruses possibly hanging around your system, as I can honestly say that none of our beta testers or authors have had those kinds of problems. I'm not saying it doesn't exist just that I haven't seen it. So that said I'd run a virus scan and a spyware scan and see if anything shows up....
     
    Last edited: Apr 12, 2005
  3. EvilKnivel

    EvilKnivel New Member

    Joined:
    Apr 12, 2005
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    0
    Aint no Virus nor Spyware on my machine.


    But no i didnt run Drivercleaner in safemode
     
  4. PoopyTheJ

    PoopyTheJ New Member

    Joined:
    Jan 15, 2003
    Messages:
    1,584
    Likes Received:
    1
    Trophy Points:
    0
    [​IMG]

    Usage for Windows 2000 and Higher
    -----------------------------------------------------------------

    ATI:
    1. Unplug nic card or modem from net or disconnect
    2. Remove ATI driver from add/remove programs then remove the control panel from add/remove programs
    3. Reboot into safe mode (F8 during boot up)
    4. On reboot into safe mode WinXP SP1/SP2 will auto detect and install drivers. Just let it do its thing. If you can cancel out of the auto install hardware wizard then skip the rest and run Driver Cleaner! If you can NOT cancel out of auto detect wizard then...
    5. Navigate to device mgr->display adapter->uninstall and/or remove ATI display adapter but do not reboot
    6. Disable any AntiVirus Software (If you don't disable is than it could give trouble)
    7. Run Cab Cleaner (not needed, but recommended)
    8. Run Driver Cleaner
    9. Empty recycle bin and reboot
    10. Install the new drivers and control panel

    nVidia:
    1. Unplug nic card or modem from net or disconnect
    2. Remove nvidia from add/remove programs
    3. Reboot into safe mode (F8 during boot up)
    4. On reboot into safe mode WinXP SP1/SP2 will auto detect and install drivers. Just let it do its thing. If you can cancel out of the auto install hardware wizard then skip the rest and run Driver Cleaner! If you can NOT cancel out of auto detect wizard then...
    5. Navigate to device mgr->display adapters->highlight nVidia and click uninstall or remove but don't reboot
    6. Disable any AntiVirus Software (If you don't disable is than it could give trouble)
    7. Run Cab Cleaner (not needed, but recommended)
    8. Run Driver Cleaner
    9. Empty recycle bin and reboot
    10. Install the new drivers

    Other:
    1. Unplug nic card or modem from net or disconnect
    2. Remove driver from add/remove programs
    3. Reboot into safe mode (F8 during boot up)
    4. On reboot into safe mode WinXP SP1/SP2 will auto detect and install drivers. Just let it do its thing. If you can cancel out of the auto install hardware wizard then skip the rest and run Driver Cleaner! If you can NOT cancel out of auto detect wizard then...
    5. Navigate to device mgr->select the category->uninstall and/or remove but do not reboot
    6. Disable any AntiVirus Software (If you don't disable is than it could give trouble)
    7. Run Driver Cleaner
    8. Empty recycle bin and reboot
    9. Install the new driver
     
  5. pr0digal jenius

    pr0digal jenius Delete Me

    Joined:
    Mar 15, 2004
    Messages:
    14,526
    Likes Received:
    28
    Trophy Points:
    0
    yes, be sure you properly unisntall the drivers, and if you used the autoexec.cfg file, try deleting that too.
     
  6. EvilKnivel

    EvilKnivel New Member

    Joined:
    Apr 12, 2005
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    0
    alright i followed your instructions, thx for the help :)


    Lets hope it helped.


    But i dont see any sence in deleting my autoexec since it just stores my binds
     
  7. pr0digal jenius

    pr0digal jenius Delete Me

    Joined:
    Mar 15, 2004
    Messages:
    14,526
    Likes Received:
    28
    Trophy Points:
    0
    I'm saying that if you used the autoexec.cfg included with our drivers, try deleting that as well.

    Also,if it still doesn't work, try deleting it anyways, as sometimes it can go corrupt(it stores more then just binds)
     
    Last edited: Apr 13, 2005
  8. EvilKnivel

    EvilKnivel New Member

    Joined:
    Apr 12, 2005
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    0
    k problem is still there, its surely a memory problem, so maybe it got nothing to do with your drivers, still its kind of strange that it occured right after installing em. ill try to run the cpu at normal speed for a while, maybe this will fix it
     
  9. pr0digal jenius

    pr0digal jenius Delete Me

    Joined:
    Mar 15, 2004
    Messages:
    14,526
    Likes Received:
    28
    Trophy Points:
    0
    perhaps....and my guess is that it is just a coincidence, but keep us posted, so that if it is our drivers we can fix it for ya :D
     
  10. rico01

    rico01 Audio Junkie

    Joined:
    May 26, 2004
    Messages:
    126
    Likes Received:
    0
    Trophy Points:
    0
    Why should he sue the drivers??? =P
     
  11. mike2h

    mike2h New Member

    Joined:
    Nov 11, 2002
    Messages:
    6,359
    Likes Received:
    69
    Trophy Points:
    0
    'cause they were bad & have to be fiscally punished;)
     
  12. sc3000

    sc3000 New Member

    Joined:
    Jan 23, 2005
    Messages:
    222
    Likes Received:
    0
    Trophy Points:
    0
    you can't sue modded drivers because you said I agree to the terms. Modded drivers are at your own risk!!!!
     
  13. mike2h

    mike2h New Member

    Joined:
    Nov 11, 2002
    Messages:
    6,359
    Likes Received:
    69
    Trophy Points:
    0
    i never said anything of the kind.;)
     
    Last edited: Apr 13, 2005
  14. Soldja

    Soldja New Member

    Joined:
    Feb 1, 2005
    Messages:
    29
    Likes Received:
    0
    Trophy Points:
    0
    gay..
    now you guys have put the DHZero Guys at ease :(
    if we had them on the toes, they probably wouldve released a better driver :drool:
    with COOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOL features :drool:
    and
    SUPERRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR performance in css :eek:[​IMG]
    but oo well, nevermind
    go DHZero :cool:
     
  15. pr0digal jenius

    pr0digal jenius Delete Me

    Joined:
    Mar 15, 2004
    Messages:
    14,526
    Likes Received:
    28
    Trophy Points:
    0
    heh, typo fixed :oops:

    any news on the CSS bug?
     
  16. Blackboost

    Blackboost -=[DHzer0point Author]=-

    Joined:
    Sep 28, 2004
    Messages:
    0
    Likes Received:
    0
    Trophy Points:
    0
    I beleive its the same classic memory reference error bug from Valve. If that's what he's seen, then its not the drivers.
     
  17. zenkmander

    zenkmander New Member

    Joined:
    Feb 26, 2005
    Messages:
    136
    Likes Received:
    0
    Trophy Points:
    0
    It's very possible that your RAM fried/got corrupted. I've seen this happen with a friend of mine; I don't know what he did, but his memory got permanently screwed. He needs to replace it now, just as you might have to.
     
  18. pr0digal jenius

    pr0digal jenius Delete Me

    Joined:
    Mar 15, 2004
    Messages:
    14,526
    Likes Received:
    28
    Trophy Points:
    0
    run memtest and check
     
  19. EvilKnivel

    EvilKnivel New Member

    Joined:
    Apr 12, 2005
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    0
    Alright, running now at 2500+ and no more errors so far. My guess is that i should clean my case from dust once again.

    So sorry for blaming your drivers:uhoh::rofl:
     
  20. pr0digal jenius

    pr0digal jenius Delete Me

    Joined:
    Mar 15, 2004
    Messages:
    14,526
    Likes Received:
    28
    Trophy Points:
    0
    Long as yer still using them, all is forgiven :p
     

Share This Page

visited