New
#61
I think it is 9 AM. Arc will be on later.
I don't have a doubt that you guys are correct at all and I greatly appreciate your help! It says the driver you listed is already installed when I tried to install it. from the screen shot I posted can you tell that it is the best version installed? or is not specific enough?
Not specific enough for me, at lease.
Device manager Shows ....
Windbg finds it as Fri Mar 16 09:27:28 2012.
So the dates are confusing there.
Well thats no good! Well what should I do now?
Do as stated in post #60 of the previous page .... can you install any of the drivers, even after getting the NVM Update Utility for Intel 82579V Gigabit Ethernet PHY Network Connection?
Two more things after checking the entire thread and all the uploaded data ......
First, Remove this startup item:
Here is how to remove them....Code:GoogleChromeAutoLaunch_721577D41E77D440C916E2687EBA0267 "c:\program files (x86)\google\chrome\application\chrome.exe" --no-startup-window Owner-PC\Owner HKU\S-1-5-21-513764542-151033864-1713244246-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Second, if removing this startup item does not stop the network related BSODs (a lot are there, and all are indicating to the same thing), uninstall Google Chrome, at least as a test, and use any other internet browser. There are a lot of other good browsers.Arc said:
Report us back at this point.
alright i got it the updated to the newest version of my network connector driver. I just restarted and saw you updated post with the Google chrome startup issue. If i BSOD again I will try that immediately.
now my computer is just going crazy. I cant update my driver further, even though it has one more update that it needs to be fully up to date. I uninstalled chrome and now I cant reinstall it at all. intel's update utility application wont run anymore. (even after I uninstalled then re-installed it) and my system restore will not restore to a previous restore point. even though I made the restore point 2 days ago. help!
I will read replys tomorrow because I am frustrated with this machine (as of late) and am very tired!
Thank you for your help,
Clay
This post reveals your sheer frustration. Keep some facts in mind:
Almost all the BSODs of the initial time somehow links to Google Chrome, irrespective of the bugcheck code. Later on it tends to reveal some more corruptions.
We have already noticed it over last couple of months that Google Chrome causes Stop 0x12, and uninstalling it resolves the issue. Here is one example for you: Recently BSOD on a new Windows // ntoskrnl.exe
So no need to get Chrome back, at least at this point, it is not any must.
Some other things you mentioned, I am thinking your frustration played in when you written the post down, but if not, and the situation is really that bad, better you backup your user data somewhere else and perform a clean reinstall minus google chrome.