Computer Gurus - Help me fix the random BSODs please.

Discussion in 'OT Technology' started by Kirlain, Mar 8, 2006.

  1. Kirlain

    Kirlain First world problems

    Joined:
    Sep 16, 2002
    Messages:
    8,054
    Likes Received:
    0
    Location:
    Charlotte, NC
    So, recently upgraded to 2GB of ram from 1GB. Its OCZ, good quality stuff.

    Timing settings are good, ran several burns and overnight mem tests, memory tests OK.

    Random BSOD's are happening. Can't replicate, randomly happen.

    Sometimes they reference tcpip.sys, other times nothing but an address number.

    SO I did a full uninstall of all nvidia drivers, a driver clean, then a clean reinstall of drivers straight from nvidias site.

    Still having BSOD's, but so far only referencing an address.

    This is the latest error message from the event viewer:

    Error code 1000007f, parameter1 00000008, parameter2 80042000, parameter3 00000000, parameter4 00000000.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Please help, I beg you.:hsd:
     
  2. DAN513

    DAN513 OT Supporter

    Joined:
    Mar 10, 2003
    Messages:
    10,089
    Likes Received:
    2
    Location:
    204
    Try going back one revision of the nvidia drivers. I had troubles with my last system and my current system using the current revision of drivers. Problem free with the older ones.
     
  3. Kirlain

    Kirlain First world problems

    Joined:
    Sep 16, 2002
    Messages:
    8,054
    Likes Received:
    0
    Location:
    Charlotte, NC
    The nforce drivers or the forceware/display?
     
  4. DAN513

    DAN513 OT Supporter

    Joined:
    Mar 10, 2003
    Messages:
    10,089
    Likes Received:
    2
    Location:
    204
    nforce.
     
  5. grkgus

    grkgus New Member

    Joined:
    Aug 28, 2004
    Messages:
    8,155
    Likes Received:
    0
    what video card do you have?
     
  6. Wolf68k

    Wolf68k OT Supporter

    Joined:
    Dec 18, 2003
    Messages:
    4,861
    Likes Received:
    2
    Location:
    Houston, Texas
    With the tcpip.sys
    Go to C:\Windows\System32
    Find that file and rename it tcpip.bak
    Wait about 4 seconds and refresh the folder and you should see a new tcpip.sys along with the tcpip.bak file. Windows just replaced the "missing" file.
    I've done the same to the same file and another.

    However if nv4_disp.dll shows up in the BSOD as the problem file, DO NOT try to do this same trick because the usually the backup file that Windows will replace it with is a very old version.
    If this comes up just restart and go back to an older set of Forceware drivers.


    If you keep getting random BSOD you might want to look into backing up what you can, format the drive and reinstall the OS.
     

Share This Page