I looked at the other dumps that I had not seen yesterday and found 2 dumps that named the Windows 2000-era driver
as the probable cause. The bugchecks of the two - 0xa
= invalid memory referenced 0xd1
= improper access of paged memory
For these 2 dumps, the stack text shows the driver lne100v4.sys -
807dcb64 88a6b38e nt!KiTrap0E+0x2cf
807dcbe4 8ec0194d ndis!NdisMCompleteBufferPhysicalMapping+0x27
WARNING: Stack unwind information not available. Following frames may be wrong.
807dcc2c 88a6d18d lne100v4+0x194d
807dcc58 88a3d54c ndis!ndisMDpc+0x173
807dcc78 828783b5 ndis!ndis5InterruptDpc+0x99
807dccd4 82878218 nt!KiExecuteAllDpcs+0xf9
807dcd20 82878038 nt!KiRetireDpcList+0xd5
807dcd24 00000000 nt!KiIdleLoop+0x38
I do believe the driver is involved in the BSODs, but is not necessarily completely to blame. Several other dumps indicate the presence of OS corruption - that may be hardware failure or software. If it was just the driver alone, I would expect the same bugcheck each time (or similar ones).
It is the Asian characters in the screenshot below that I am concerned
The following is a screenshot from a 0x101 dump file and contains what appear to be Asian characters. Cut/paste caused the charachters to change to ???????, hence the reason for the screenshot - Attachment 30047
The above are supposed to be the names of drivers
I would advise ditching that driver and see how things go, although I believe that you will probably run into trouble. You really should re-install Windows 7. Since you are running RTM, go to TechNet or MSDN and refresh the install copy. It may have been corrupted during the download process.
Finally, to try and answer some of your questions and to leave you with additional ones -
Windows 7, like Vista, employs a legacy driver to connect to the Internet during installation. What surprises me is that Windows 7 permitted the installation of the 9 year old Ethernet driver. Was there no indication in the Device manager?
Regardless of how the driver got into the Windows 7 system, the fact is the driver was loaded into RAM at the time of the BSODs. I honestly don't understand how you ran Windows 7 Beta for months with that driver and no crashes. 4 & 6 month old NIC drivers are causing BSODs -- this past week. I am surprised that you were not here earlier seeking BSOD help.
Please... seriously consider re-installing Windows 7 RTM.
Regards. . .