The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    TCP/IP Fix causing consistent BSOD's

    Discussion in 'Networking and Wireless' started by Nocturnal310, Sep 30, 2008.

  1. Nocturnal310

    Nocturnal310 Notebook Virtuoso

    Reputations:
    792
    Messages:
    2,708
    Likes Received:
    0
    Trophy Points:
    0
    Hi guys,

    i am in college so if anyone can suggest a solution ..


    i was having poor net speeds...so i downloaded TCP/IP fix from Softpedia HERE

    I was very doubtful but i ran the Fix.


    it asked for System restart so i press yes.

    but after that whenever the OS tries to load i get BSOD's.

    I tried all modes... Safe mode, Debugging mode etc.

    none worked.

    So what can i do?
     
    Nocturnal310, Sep 30, 2008
    #1
  2. Nocturnal310

    Nocturnal310 Notebook Virtuoso

    Reputations:
    792
    Messages:
    2,708
    Likes Received:
    0
    Trophy Points:
    0
    the TCP Patch doesnt have Driver signature and hence causes BSOD as a stupid Vista Security feature to prevent damage.

    the real damage on a laptop is Vista itself with its stupid UAC + useless security features
     
    Nocturnal310, Sep 30, 2008
    #2
  3. Nocturnal310

    Nocturnal310 Notebook Virtuoso

    Reputations:
    792
    Messages:
    2,708
    Likes Received:
    0
    Trophy Points:
    0
    I Fixed the Problem.


    I am a Genius!

    I did a surgery on my laptop.

    Took out the Hardrive, used SATA to USB on Dad's laptop... edited the path of the .Bat file for the TCP/IP UNDO patch.

    Copied the Sony vaio's TCPIP.SYS in Patch folder and using the bat moved it to my Windows/system32/drivers/tcpip.sys.

    and ya i fixed it ...

    little bit of programming + some hardware stuff.

    As usual i ignored the usual reply that 'Reinstall OS'.

    Thanks for not replying.

    couldnt have done with Replies
     
    Nocturnal310, Sep 30, 2008
    #3
  4. Shyster1

    Shyster1 Notebook Nobel Laureate

    Reputations:
    6,926
    Messages:
    8,178
    Likes Received:
    0
    Trophy Points:
    205
    Well, maybe you should just reinstall the OS? :D
     
    Shyster1, Sep 30, 2008
    #4
  5. Nocturnal310

    Nocturnal310 Notebook Virtuoso

    Reputations:
    792
    Messages:
    2,708
    Likes Received:
    0
    Trophy Points:
    0
    Nah, it would have wasted my entire day.


    all it took me was 1 hour including research and computer was back to normal.
     
    Nocturnal310, Sep 30, 2008
    #5