Jump to content


Honorary Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About edshead

  • Rank
    Regular Member
  1. Everything appears to have uninstalled cleanly and I've gone through the rest of the post as well. Additionally, that one popup I was getting on startup returned, and I found it was due to the googletalk plugin registry key in HKCU/Software/Microsoft/Windows/CurrentVersion/Run not enclosing the path in quotes, so Windows wasn't reading the full path. Enclosed it in quotes, and it's all fixed. Thank you again for all of your time and insights. I believe this thread can now be closed.
  2. Bravo. Replaced autochk per your instructions while in Ubuntu. Booted to safe mode just fine. Started a chkdsk and it asked to schedule one for next startup. I said yes, rebooted, autochk ran and came up clean. Windows loaded fine (even without that popup I mentioned earlier). You've taken me from the brink of a reinstall and all the headache that goes with restoring all my programs... to 100% functional. You are truly amazing. Thanks for all of your help. There's no way I could've done this without you. As awesome as you are, no offense, but I hope you don't see me back here again. :-P
  3. I was having problems with chkdsk running on restart, and I believe it would've been autochk that ran at that point so it would make sense that it's not in good health. Here's the combofix logs (quarantine log included). Note, I had a crash when I ran it the first time (froze like previous), so I ran with /nombr. The kicked myself a bit for not doing that the first time. ComboFix-quarantined-files.txt combolog.txt
  4. Sorry. That window that is in the image above pops up on startup. Thank again, so much, for all of your help!!!
  5. Following numbered section is to document your great work. I backed up the registry with ERUNT I started above. Then, I imported i8042prt.reg. Reboot. Keyboard works. Backup registry again with ERUNT. Import usbehci.reg. Reboot. No change in functionality. Backup registry again with ERUNT. Import HDAudBus.reg. Reboot. No change in functionality. Still, I check device manager and I see that the Code 39 errors are gone. Windows thinks that the Audio Codec and Touchpad are running fine. I uninstall the Dell Touchpad. Reboot. It auto-detects Dell Touchpad. It installs it, but it's still not work
  6. Here's the details tab of each device that device manager is giving a Code 39 error on. Additionally, I provided the driver details, which includes the driver file list for each device. As a recap: Built-in keyboard has always used the default Windows driver as far as I know. I can't find a proprietary Dell driver for it anywhere. Touchpad does use a Dell driver, and I've installed the most current one from Dell's support site. That's the driver that gives the details you're looking at there. HD Audio driver: Made by Sigmatel (now IDT). Ever since I got the laptop, if I reinstalled Wind
  7. Didn't see ERDNT\subs. "dir /s" from \ERDNT\ attached. Also, regarding wireless. Wireless adapter itself is fine, loading and showing no error in Device manager. Shows up in network connections as well. The WLAN service isn't starting though due to the ndisuio service not starting. I did try to reinstall the driver, and reached the same result. erdntdir.txt
  8. First off, bad news. Can't uninstall SP1. Not sure if that's because I used a Win7 SP1 DVD to upgrade from Vista, or if it's because the pre-SP1 files got deleted at some point. Bottom line, I don't have the appropriate KB update available in "installed updates" in order to remove SP1. Using wusa at the prompt also doesn't work. Oh well. Reinstalled AVG & Comodo, and the only log for an AVG scan where something turned up is attached.. (AVG is actually semi-colon delimited but it didn't let me upload csv files.) Comodo looks to have taken its log files with it when it uninstalled, or
  9. If this is a problem with the uninstall of Comodo and AVG (so the logs are unintelligible), I could always reinstall them to get a look at the logs if that could point us to the issue. If you want to go the SP1 route, I'll go that route. If it would be helpful to go with the reinstall of the overzealous scanners in order to read logs, I can do that as well. Let me know. I'm guessing SP1 is easier because it does't require diving through any more logs. Worst case, and all of this fails, what next? I realize it's likely still a long way from the root of the problem. But for things like my Wir
  10. I'm going to ignore anything my computer says to the contrary and say yes, everything is perfect. After opening my eyes, unfortunately nothing has changed. Same problems as before in Device Manager (except the McAfee driver is gone). Audio and keyboard still behave the same but I don't know that I'd call completely not working a type of behavior. Although I don't know for certain, I believe the McAfee driver was level over from the Summer of 2010, as that was the last time I had any part of a McAfee suite installed on this computer (that was when the 24-months free with the laptop ran out).
  11. FSS: Farbar Service Scanner Version: 13-02-2012 Ran by edshead (administrator) on 19-02-2012 at 09:56:39 Running from "C:\Users\edshead\Desktop\fixes" Microsoft Windows 7 Home Premium Service Pack 1 (X86) Boot Mode: Normal **************************************************************** Internet Services: ============ Connection Status: ============== Localhost is accessible. LAN connected. Google IP is accessible. Yahoo IP is accessible. Windows Firewall: ============= Firewall Disabled Policy: ================== System Restore: ============ System Restore Disabled Policy: ==============
  12. And again with the forgetting to click attach. dvmg.zip
  13. Couldn't find those on the tree. Here's screenshots of the tree, plus hopefully detailed enough screenshots of the three 'devices' error'd out in the tree. (Screenshots for each device showing General tab, Driver tab + error when clicking Start service msgbox, and Driver Details.)
Back to top
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.