Multiple times every other day or so, my new Win 7 desktop crashes and restarts on me. Earlier today it totally froze, had to hard boot. Then, while watching YouTube, it crashed. Please help. Am setting up SkyDrive link for the Memory.dmp file now

Here they are https://cid-52e3e150613def40.skydrive.live.com/self.aspx/.SharedFavorites/2009-12-04-2.part1.rar and https://cid-52e3e150613def40.skydrive.live.com/self.aspx/.SharedFavorites/2009-12-04-2.part2.rar

Can you try providing the dump files again as theydo not appear to be available.Also, what network adapter and drivers are installed?

http://cid-52e3e150613def40.skydrive.live.com/self.aspx/.Public/2009-12-05.r00 http://cid-52e3e150613def40.skydrive.live.com/self.aspx/.Public/2009-12-05.rar http://cid-52e3e150613def40.skydrive.live.com/self.aspx/.Public/device%20manager.jpg http://cid-52e3e150613def40.skydrive.live.com/self.aspx/.Public/driver.jpg I have an Acer desktop with NVIDIA nForce network adapter

Analysis of the full memory dumpimplicated the nvmf6264.sys, which is the NVIDIA network adapter driver.This driver appeared to access, and perhaps corrupt, memory aheadof other drivers such as the vsdatant.sys (ZoneAlarm), avgtdia.sys (AVG),and the NETIO.SYS amongst other drivers.Since youare running an older version of thenvmf6264.sys, try updating this driver by going to the Device Manager andright-click the network adapter > Update driver software > Search automatically for updated driver softwareBTW, did you intentionally disable the Microsoft Teredo Tunneling Adapter?

No. Ever since I started the desktop there has been a problem with Teredo. It says that it cannot start, however using windows troubleshooting only calls for it to reinstall the driver.

I searched for an update tot he nForce ethernet driver and I am told I have the latest one.

If you double-clickthe Microsoft Teredo Tunneling Adapter in the Device Manager, under the "General" tabwhat is the " Device status"?Also, in the Device Managercan you double-click the NVIDIA network adapter > Details, then, under "Property"select"Hardware Ids" from the drop-down list.What is listed under "Value"

For Teredo, its Device not started. It would ask at startup to fix the problem, but each time I clicked on Find Solution, it only said to reinstall the driver. The Hardware Ids for the Nvidia are: PCI\VEN_10DE&DEV_0760&SUBSYS_01531025&REV_A2 PCI\VEN_10DE&DEV_0760&SUBSYS_01531025 PCI\VEN_10DE&DEV_0760&CC_020000 PCI\VEN_10DE&DEV_0760&CC_0200

Can you provide some more info on the computer?:Start > type msinfo32 in the "Search programs and files" box and press "Enter" > File > Save > then save as an .nfo fileThen make the resulting .nfo fileavailable viaWindows Live SkyDrive.

http://cid-52e3e150613def40.skydrive.live.com/self.aspx/.Public/matthias.nfo

There appears to be a program installed that may be causingproblems with your network connectivity andmay becontributing to the BSOD with the netio.sys.That program is the NVIDIA NetworkAccess Manager program.The NVIDIA NetworkAccess Manageris an optional program thatmay beofferedduring the installation ofNVIDIA network adapter drivers.You can decline the invitation to install the NVIDIA NetworkAccess Managerduring any installation of NVIDIA adapter drivers, if it isoffered.The NVIDIA NetworkAccess Manager software is not necessary and has been known to cause issues.For now I would suggestto uninstall the NVIDIA NetworkAccess Manager program using "Uninstall a program".Then restart the computer and check the situation in the Device Manager concerning the Microsoft Teredo Tunneling Adapter which is presently disabled.

One point of clarification: Everyone naturally assumes that the latest drivers are the best drivers.Don't make that assumption. Windows 7 is still very new and the one thing you can be absolutely sure of is that the latest drivers have the least amount of testing.-Noel

Thank you I uninstalled the Nvidia ForceWare Network Management software and restarted my desktop. First thing was to check the Devices and Printers and there was no longer a yellowexclamationmark on Matthias. Device Manager also is clear of any conflicts. Teredo seems to be functioning and time will tell if Netio.sys will cause another BSOD. Again, thank you.

It happened again. At first I thought there was a problem with the files I was copying across the network, but this dump happened today well after that task was done and the computer was practically idle. From what I can tell, Netio.sys is again the culprit. The NVidia Network Manager was removed and Teredo is currently working with no issues. http://cid-52e3e150613def40.skydrive.live.com/self.aspx/.Public/2009-12-12.rar and http://cid-52e3e150613def40.skydrive.live.com/self.aspx/.Public/2009-12-12.r00

Can you try uploading the last dump file again as the one youlinked appears "corrupted".Try also uploading the minidump file from the C:\Windows\Minidump folder.

Ok. Here is the Memory.dmp from the latest crash and the minidumps from this week. http://cid-52e3e150613def40.skydrive.live.com/self.aspx/.Public/2009-12-10.rar and http://cid-52e3e150613def40.skydrive.live.com/self.aspx/.Public/2009-12-10.r00

The minidump files did not implicate any third party driver so at this point you may want to turn on the Driver Verifier against all non-Microsoft drivers to stress test them:Start > type verifierin the Search programs and files box and press "Enter" > Create standard settings > Next > Select driver names from a list > then select all non-Microsoft drivers > FinishRestart the computer.Continue to use the computer normally but if you experience any BSODs make available theminidump files.If after enabling the Driver Verifier and restarting the computer you receive a BSOD on startup and cannot start Windows, restart the computer in "Safe Mode" and do the following:Start > type verifierin the Search programs and files box and press "Enter"> Delete existing settings > FinishRestart the computer, log into Normal Mode, and make available any resulting minidump file.

I did as you asked and BSOD at start up, right after the pretty flying lights. http://cid-52e3e150613def40.skydrive.live.com/self.aspx/.Public/12122009.rar

OK, the Driver Verifier caught the vsdatant.sys "attempting to corrupt the system".The vsdatant.sys, a ZoneAlarm driver, ismostlikely to be the cause of the BSODs you have been experiencing.In the following link the same BSODs as you have been having, BugCheck 7Fprobably caused bythe ntkrnlmp.exe and NETIO.SYS, were traced to ZoneAlarm:http://www.sevenforums.com/crashes-debugging/37399-bluescreen-after-connecting-company-network.htmlTo resolve the BSODs ZoneAlarmhad to becompletely uninstalled.

I have removed zonealarm. It was the first thing I installed since I had a licese and used it on my XP machine. Something familiar. I thought the 64 bit version would be compatible, but from what I read and what you say, it really isn't. Thank you