Announcement

Collapse
No announcement yet.

Oh yay, another driver issue.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #41
    Re: Oh yay, another driver issue.

    it sounds like pentium is trying to rebuild an engine with only a screw driver. look. you may have to re install or use a live cd to test with. you can't have it both ways. it also sounds like a problem with the hardware is still a possibility. did you try a different malware scanner? maybe the first one was no good.

    sorry but 150 bux could get you a lot more than this type of fix. us dollars or Canadian dollars. and clone your drive anyway. good backup habit even if you are not monkeying the drive.
    sigpic

    (Insert witty quote here)

    Comment


      #42
      Re: Oh yay, another driver issue.


      How the hell is this still a hardware issue? If it has failed to work on two different PCI NIC cards and THREE different USB wireless adapters from both D-Link and Linksys, IT IS NOT A HARDWARE PROBLEM.
      Also, someone please tell me how I run a malware check on a system...WHICH HAS NO INTERNET CONNECTION.
      Even Spybot S&D requires an connection for updates, otherwise I'm using an out of date version and I know for a god damn fact, this is NOT a malware issue.
      Why the hell are you people going back to the exact same issues we have covered again and again?
      also: the $150 was a fucking estimate. I don't know what the hell it would really cost so stop fucking complaining! THIS IS SOMETHING I CAN NOT DO! I WANT A GOD DAMN EXPERT TO LOOK AT THIS!


      Jesus christ. Sorry for blowing up like that but you guys are really being stubborn. If you think you know what the problem, just pm me your address and I'll mail the damn system to you. It appears that this forum assistance BS is going nowhere.
      Find Nedry!


      Check the Vending machines!!

      <----Computer says I need more beer.

      Comment


        #43
        Re: Oh yay, another driver issue.

        Dude, chill the fuck out.. The image of the drive before you try anything is the first thing a computer tech does.. Hence why i keep at least 10 spare hard drives of various sizes and interfaces laying around..

        Boot into windows Safe mode (preferable safe mode with networking support), and see what shows up in device manager after you click the "show hidden devices" option in the view menu. Delete all networking interfaces, and do a clean reboot.. Let boot normally, and see if windows picks up the correct network interface card driver.. Let it autoconfigure, then reboot again.. After the system boots again, shell out to a windows command prompt, and issue the ipconfig /all command.. This will show if windows is pulling an IP address.. Then try pinging the network gateway listed in the ipconfig output.. If it passes, that means you have a connection, from an electrical standpoint. If not, bad NIC card, or PCI slot, or windows hasn't configured the interface correctly. Check for yellow explanation points in device manager..

        Booting from a Linux livecd would also give a good test as to if it's a hardware issue, or an issue with your OS.. As long as you don't choose the "install" option, you'll be OK.. In fact, you can even disconnect all of your hard drives, and just leave the optical drive connected.. Hence why i keep a bootable USB jumpdrive with Ubuntu Linux 32 bit on me at all times..

        Comment


          #44
          Re: Oh yay, another driver issue.

          FINE! YOu know what....Fine!
          it seems nobody read ANY of my posts! ANY OF THEM!
          Fuck you too!
          douchebag yanks...

          I'm backjing up whatever the FUCK I can save and reinstalling everything aLLO OVER AGAIN!
          THAT'S MY WHOLE FUCKING WEEKEND I HEAR BEING THROWN AWAY! I GET TWO FUCKING DAYS OFF AND I SPEND IT IN A NON air conditioned room slaving over a fucking computer while I make a half dozen phone calls and reinstall EVERY SINGLE LAST GOD DAMN PIECE OF SOFTWARE I OWN, REGISTER AT LEAST A DOZEN PROGRAMS, IMPORT A MUSIC DATABASE AND SET FUCKING FILE ASSOCIATIONS FOR THE BAJILLIIONTH TIME!
          then there is the fact I have to download and reinstall ALL MY STEAM GAMES.
          Fuck you!
          FUCK YOU
          and most importantly...
          FUCK YOU!!!


          Thread Closed.
          Last edited by pentium; 08-30-2009, 10:18 PM.
          Find Nedry!


          Check the Vending machines!!

          <----Computer says I need more beer.

          Comment


            #45
            Re: Oh yay, another driver issue.

            pentium=



            stop being a troll. we are doing the best we can. if you want help please be more civil. one of my best friends lost my trust/friendship acting like you are. you cant eat your cake and have it too. stop acting so mental. we know you can.
            sigpic

            (Insert witty quote here)

            Comment


              #46
              Re: Oh yay, another driver issue.

              Do you realize how stressful and annoying it is when you follow somebody's steps or you describe all the steps you did to troubleshoot and then the next ten or so posts are other members, telling you to do the exact same steps?

              It feels like I'm being ignored or people tl;dr everything and try to be Mr. Hero by dropping in their two cents, expecting "hey! it worked! Thanks a bunch man!".

              That is essentially what the last page was with the addition of blame redundancy in the form of it's either a malware or a hardware problem.
              Last edited by pentium; 08-30-2009, 11:08 PM.
              Find Nedry!


              Check the Vending machines!!

              <----Computer says I need more beer.

              Comment


                #47
                Re: Oh yay, another driver issue.

                Pentium, spastic much??

                Honestly i don't give a shit if you have to pay $150 to have your computer fixed or not.. Now you've learned what fucking with a perfectly working system can cause.. If the driver update, etc fixes a specific issue, fine, but always make a system restore point before you do. Whether you just use system restore, or make a ghost image.. Whatever... It'll get you back to a working point in time..



                Chances are it's a simple problem. In fact i have a system on my bench right now that had an issue just like yours recently.


                Fine, from what i've read in the thread, you're running a windows XP system, with static ip addressing, but not much relevent information beyond that.



                What ip address range are you using on your network, and what subnet mask are you using? What is the internal ip address of your cable modem/firewall/wireless access point? After DHCP configuration fails, does it fill in a 169.254.x.x address, pop up a network icon with a yellow explanation point, or leave the ip address field empty? What does arp -a at the command prompt give back to you?

                As for you, i'm putting you on ignore until you calm the fuck down..

                Comment


                  #48
                  Re: Oh yay, another driver issue.

                  Originally posted by gg1978
                  Pentium, spastic much??

                  Honestly i don't give a shit if you have to pay $150 to have your computer fixed or not.. Now you've learned what fucking with a perfectly working system can cause.. If the driver update, etc fixes a specific issue, fine, but always make a system restore point before you do. Whether you just use system restore, or make a ghost image.. Whatever... It'll get you back to a working point in time..
                  My system makes a system restore point every morning at 2:30 AM
                  Rolling back to the one made 18 hours or so before networking broke (as I stated three times already) did nothing.

                  Chances are it's a simple problem. In fact i have a system on my bench right now that had an issue just like yours recently.
                  I doubt it.

                  Fine, from what i've read in the thread, you're running a windows XP system, with static ip addressing, but not much relevent information beyond that.
                  did you look at any attachments or links?

                  What ip address range are you using on your network
                  between 192.168.1.1 and 192.168.1.254. System is currently at 192.168.1.45
                  , and what subnet mask are you using?
                  255.255.255.0
                  What is the internal ip address of your cable modem/firewall/wireless access point?
                  192.168.1.254
                  After DHCP configuration fails, does it fill in a 169.254.x.x address, pop up a network icon with a yellow explanation point
                  yes
                  , or leave the ip address field empty?
                  no
                  What does arp -a at the command prompt give back to you?
                  Oooh, a new command to try.
                  Code:
                  No ARP Entries Found
                  As for you, i'm putting you on ignore until you calm the fuck down..
                  Go have a beer.
                  Find Nedry!


                  Check the Vending machines!!

                  <----Computer says I need more beer.

                  Comment


                    #49
                    Re: Oh yay, another driver issue.

                    Alright, you seem to be a bit calmer now.. A note of advice, calling people who are trying to help you "yank douchebags" is not conducive to them wanting to help you..


                    As for the screenshots, they are irrelevent to the network issues you're having.. Although people suggesting that malware might be the culprit do have a point.. You do have processes burning CPU time, that probably shouldn't be.. This may or may not be due to spysware.. Usually they don't intentionally break your networking stack, as they wouldn't be able to use your computer to spam people then, or compel you to buy the "cleanup" over the internet..

                    Do an ipconfig /all and post what you have there..

                    Now, the fact that your computer seems to have an 169.254.x.x address, while your router is at 192.168.1.254 is certainly one issue.. This would seem to suggest that your static ip addresses aren't "sticking"..

                    As for the arp table, that is probably another reason you're having issues.. If you were using DHCP, having windows repair the connection should fix that.. For example, here's what arp-a returns on my box here that is configured to use DHCP..

                    C:\Documents and Settings\Greg>arp -a

                    Interface: 192.168.0.66 --- 0x2
                    Internet Address Physical Address Type
                    192.168.0.254 00-b0-d0-4c-02-e6 dynamic

                    C:\Documents and Settings\Greg>


                    So adding an entry for your gateway would look like

                    arp -s 192.168.1.254 "your gateway mac address"

                    If you look up arp on wikipedia, it should be instructive as to what arp actually does..
                    Last edited by gg1978; 08-30-2009, 11:54 PM. Reason: typo

                    Comment


                      #50
                      Re: Oh yay, another driver issue.

                      Ok, it looks like it's not a network card issue. Something is messed up bad in the Windows network layer.

                      Try running lspfix. It trys to fix the network layer above the drivers. It's worth a shot.
                      http://www.cexx.org/lspfix.htm

                      Run hijackthis and post the log. It has a good chance of showing if you really do have malware or not.

                      Also, run spybot on a working computer and update it. Then copy the directory out of program files onto a USB stick/CD. It works fine that way and will be updated on your broken computer.


                      I know it sounds stupid, but have you checked your cable/port/switch? I've seen broken switches give a link light but still not work.

                      Comment


                        #51
                        Re: Oh yay, another driver issue.

                        I'm just going to skip the hassle and just reinstall. I could try it anyways because something is funky with my sound card driver as well and the Microsoft product activation line IS toll-free. I'll just have to balance out all the installation over a few weeks.
                        Find Nedry!


                        Check the Vending machines!!

                        <----Computer says I need more beer.

                        Comment


                          #52
                          Re: Oh yay, another driver issue.

                          is your cd sp2? if so then it will go faster. if not, install an older lan card or get sp3 on there with no ethernet (whole file on flash drive). sp2 makes most stuff automatically work. then install remaining drivers and software. should take less than 2 days unless you have a stack of cds 5 feet tall to install.
                          sigpic

                          (Insert witty quote here)

                          Comment


                            #53
                            Re: Oh yay, another driver issue.

                            Originally posted by pentium
                            something is funky with my sound card driver as well
                            So you checked for bad caps on your mobo?

                            like I said before, you have the computer in front of you so we can only offer what we perceive is your problem. Whether you take it or not is up to you. No body forces you to do what we suggest. I think you like to have 10, 20 comments/suggestions for you than not a single reply, right?

                            Now, since your Realtek is on board and you "upgraded" the driver, there is the possibility that your registry is hosed and there is not a single thing you can do to fix it except reinstall. I suspect the strange resources being used up by Windows keep trying to "talk" to the Realtek but no one is listening.

                            The next best thing is to disable the Realtek in BIOS. Reboot without any NIC installed. Shutdown system then install another NIC and see if your networking works again. If it does not work in Safe Mode with Networking, then you are looking at reinstall.

                            Finally, if you do have a way to clone your OS drive, do it. Then play around with your cloned drive to resolve the problem w/o worrying about totally screwed up Windows to a point it is totally useless for anything.

                            Comment


                              #54
                              Re: Oh yay, another driver issue.

                              Wow. This was totally unexpected.
                              I was playing music while slightly hung over and it felt like time was suddenly slowing down but no, in fact the system was lagging so god damn hard the music playback was actually slowing down and a few moments the system bluescreened and that was it.
                              I got no idea what caused it but the system won't even reach the desktop anymore before it bluescreens.
                              Yep. I was fighting it before but now it looks like I have no choice but to reinstall windows.
                              Oh well. I guess I'll take this time to move the system over from my old Thermaltake Skull to the Thermaltake Xaser III. It will certainly help me tackle some heating hotspots.
                              Find Nedry!


                              Check the Vending machines!!

                              <----Computer says I need more beer.

                              Comment


                                #55
                                Re: Oh yay, another driver issue.

                                are you oc? if so, then oc to a lower value. or maybe some virus got in there that is so new that nothing can dect it at his time and hieristics missed. maybe ecven a bad sector in the hd or some hd error? is your chipset (if it has fsb) hot? maybe your problem is there?
                                sigpic

                                (Insert witty quote here)

                                Comment


                                  #56
                                  Re: Oh yay, another driver issue.

                                  usb to ethernet, I always keep one in the drawer
                                  ^Learning to walk on rice paper without leaving a trace,

                                  Comment


                                    #57
                                    Re: Oh yay, another driver issue.

                                    Originally posted by Nama
                                    usb to ethernet, I always keep one in the drawer
                                    i have 2. one is a farallon netline wth broken eternet port (i epoxied a cable in and it works great- good for my old laptop (see sig), and the other is a TINY cables unlimited one (low rating due to lack of drivers, but connect it to a linux box and lsusb and i have a realtec chip #, and then you have drivers). it is 10/100, usb1.1. and has 3 leds:



                                    i paid 20 usd at a local shop, i like it because it is compact. also comes in black.

                                    these are handy for testing. i also plan to build a usb- based system (usb hd, sound, optical, networking) as a trial for a computer design i though of. modular box with graphics module, ram/cpu module, power module, usb module. if i owned a co that built pc's id also include some e-sata ports. i think it would be cool. id make it mac mini sized and low cost- no to metion modular so easy to fix.
                                    sigpic

                                    (Insert witty quote here)

                                    Comment


                                      #58
                                      Re: Oh yay, another driver issue.

                                      Blah!
                                      I think it is the network cable.
                                      I backed up, formatted and reinstalled and still got no networking so I plugged the cable into my iBook and it wasn't able to connect either. It did say it was physically connected to a cable but couldn't do anything else.
                                      Damn, I thought I ruled this cable out? now I have to get another length and test with that.
                                      Find Nedry!


                                      Check the Vending machines!!

                                      <----Computer says I need more beer.

                                      Comment


                                        #59
                                        Re: Oh yay, another driver issue.

                                        You should buy a cheap RJ45 tester to rule stuff like this out in a few seconds.

                                        Plug the receiver on one end the transmitter on the other and press the button my 50 dollar tester shows the status of all 8 wires via LEDs (it also tests USB, RJ-11, and BNC connectors) cheaper ones will illuminate a green LED for good.
                                        Last edited by Krankshaft; 09-24-2009, 09:56 AM.
                                        Elements of the past and the future combining to make something not quite as good as either.

                                        Comment


                                          #60
                                          Re: Oh yay, another driver issue.

                                          I should of. The local surplus store sold them for the longest time but the last time I was there they no longer had it.
                                          Find Nedry!


                                          Check the Vending machines!!

                                          <----Computer says I need more beer.

                                          Comment

                                          Working...
                                          X