New
#31
Hi Timo,
A quick update while I read what you have written above. I disabled the two vmnetadapters listed in my device manager. The computer still gives rapid BSOD on wireless networking but not wired LAN.
Various crash, BSOD scenarios
-
-
New #32
Here is the Wireless network adapter
Intel Centrino Advanced-N 6200 AGN
File version 13.2.1.5 (installed today) driver files:
NETw5s64.sys
vwifibus.sys
NETw5c64.dll
NETw5r64.dll
-
New #33
OK, this is strange. There is another wireless adapter. I didn't recognize it as one in device manager, but when I look at the network connections (as in your last pic) it shows a wireless signal icon. This is called Microsoft virual WiFi miniport adapter. It is enabled but not connected on IPv4 or IPv6. It shows 131,330 packets sent and 0 received.
-
New #34
Timo,
I spent awhile sifting through the event viewer looking for something about the drivers I have installed for Realtek LAN and Intel wireless. I am not seeing anything, but I probably don't know how to navigate through the viewer effectively.
There is a new event starting this morning that is happening constantly (550 times).
Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
I have attached a new version of the event log. I have to go to lab and perform an experiment. Actually should have started it earlier this morning. Oh well.
Ben
-
New #35
Just before I duck off
- It'll take a fair while to go through those event logs (although the info is great). Could you please post the event numbers of the problematic ones, so I can find them fast.
In regards to the Failed extract of third-party root list, at a quick guess your Certificate Revocation List (CRL) has an expired certificate or the database is out of date. Here's the official Microsoft Fix for those two scenarios'. The CRL may have become corrupt during a BSOD.
The good thing is that we know that the VMware driver being blocked by Microsoft causes the BSOD, we now have proven that it occurs only when it interacts with the wireless adapter interaction, however we don't know (yet) why the dump file gets it wrong (as I'm now sure it does) and says the LAN adapter. With the new information, I will need to compare the Wireless driver details to the DUMP log to see if I can find any new info. Thanks for confirming that the wireless adapter is the one we thought it was.
The problem is that there are 'no' new wireless drivers, you have the latest. Therefore the only choice left for us (with the wireless adapter is to find older drivers) that may not be affected by this new problem that you've discovered. See if you can locate those and install them.
I will get back to you tomorrow with any new info from the dump and logs.
At this stage, I would seriously consider:
- Looking for older Wireless Drivers (check your installation disk if you have one)
- Opening a support call with VMware, they may have to re-write their drivers and/or may be aware of the issue already.
- Reinstalling VMware
-
New #36
Hi Timo,
I had said the wireless associated rapid BSODs occurred even when the VMware network adapters were disabled.
I haven't yet tried disabling the Microsoft virual WiFi miniport adapter. In terms of the wireless adapter, I can first try and install the version on my HP system recovery disks.
What kind of event's numbers would you like me to look for on my event viewer?
Thanks,
Ben
-
New #37
Hello,
Great suggestions Timo !! I one small thing i would recommend to uninstall Zone Alarm since its notorious for BSOD. Saw in your thread that you had Zone Alarm installed i have seen lot of causes where Zone Alarm used to cause BSOD. Use the Removal Tool to clear the left over entries check this link for more information on removal BSOD vs. Internet Security !! « Captain Debugger
Good Luck,
Captain
-
New #38
@benjis78 - I must have missed th bit about the adapters mate, so much to read.
- RE: The event errors, the list you gave me has every event in it. If you could just take a quick look and jot down any event numbers that are errors.
- Also I'll wait the results of my last suggestions.
@Capt - I thought this too, so I asked benjis78 to disable it and it and the BSOD's still occurred.
A mini synopsis of where we're at. What we've managed to prove is that the 'most likely' culprit in the dump (the lan adapter) is incorrect. Also we are finding that updating the drivers is not getting us there, so I've asked benjis78 to try previous drivers and contact vendors and consider a vmware re-install to cover corruption there. benjis78 may very well be the first person with this error/bug.
-
New #39
Hi Timo,
Yes, my mother always said I was special. This must apply to computer bugs too.
Attached are text files of event IDs corresponding to error messages for EventSys and EventApp from 7-9-2010 onwards located in the system event files I attached to post #34. I have filtered out event IDs for the constant CAPl2 error in EventApp and listed it only once.
Ben
-
New #40
Hi Timo,
Today I installed an older wireless adapter (2 versions before mine). Like before, the install hanged. I think this is because they are not the HP authorized drivers. Strangely enough, on my HP software page list, it doesn't even list drivers for my intel wireless adapter. But, the pre-installed HP monitoring software recognizes I have an intel adapter and showed it was updated on 7-7-10. I have been using my wireless connection without a crash for more than half an hour. I am getting ready to re-enable my vmware wireless adapters and see if the system goes haywire.
I also updated skype and zone alarm because I saw they were associated with the "Failed extract of "third-party root list from auto update cab" error message. This comes from a source called CAPI2. I read the link you gave me, but the download (meant for XP) was dead. I spent some time reading posts on a microsoft technet forum about the error. It seems like a mess which ultimately microsoft should be responsible for dealing with. In my event viewer, I enabled a new log of applications and service logs -> Microsoft -> Windows -> CAPI2 -- Operational. There are CAPI2 errors being generated every couple of seconds.
Ben
Quote
Related Discussions