BSOD Netio.sys Network/Veetle Issue

perfmon reports issues with your Teredo adapters. Please open up Device Manager and right click on the Teredo adpaters to uninstall them. Do the same thing with any 6to4 adapters and any ISATAP adapters that are installed. The adapters will automagically reinstall themselves at the next reboot if they are needed (but most times they aren't needed).

There are some issues with Catalyst Control Center and Daemon Tools in some Win7 systems. Please uninstall these programs. Feel free to reinstall them (if needed) once we're done troubleshooting.

There are no memory dumps later than Sep 6 uploaded. Have you had more BSOD crashes since then?
The dump files show issues with networking and the Windows firewall - so it's possible that the ZoneAlarm program was causing it.

I'd suggest running Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 12:41:34.211 2010 (UTC - 4:00)
System Uptime: 0 days 0:12:47.446
*** WARNING: Unable to verify timestamp for vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
Probably caused by : NETIO.SYS ( NETIO!CalloutStreamDataInit+1d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  vsmon.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`015a658d fffff880`052341a0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 12:22:14.399 2010 (UTC - 4:00)
System Uptime: 0 days 2:03:54.649
*** WARNING: Unable to verify timestamp for vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
Probably caused by : NETIO.SYS ( NETIO!CalloutStreamDataInit+1d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  vsmon.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0177658d fffff880`050261a0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 10:17:21.562 2010 (UTC - 4:00)
System Uptime: 0 days 0:26:25.812
Probably caused by : NETIO.SYS ( NETIO!CalloutStreamDataInit+1d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  vsmon.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`015a958d fffff880`046111a0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 07:36:11.986 2010 (UTC - 4:00)
System Uptime: 0 days 6:09:00.236
BugCheck D1, {8, 2, 0, fffff880017c3050}
*** WARNING: Unable to verify timestamp for epfwwfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for epfwwfpr.sys
Probably caused by : NETIO.SYS ( NETIO!StreamDatapTruncateAfterOffset+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  ekrn.exe
Bugcheck code 000000D1
Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff880`017c3050
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep  5 22:22:02.418 2010 (UTC - 4:00)
System Uptime: 1 days 11:11:01.618
BugCheck D1, {8, 2, 0, fffff88001796050}
*** WARNING: Unable to verify timestamp for epfwwfpr.sys
*** ERROR: Module load completed but symbols could not be loaded for epfwwfpr.sys
Probably caused by : NETIO.SYS ( NETIO!StreamDatapTruncateAfterOffset+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  ekrn.exe
Bugcheck code 000000D1
Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff880`01796050
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  

Hmm, bit strange that there are no memory dumps after Sep 6 cause I had a BSOD just two days ago.

I have uninstalled the Teredo adapters, Catalyst Control Center and Daemon Tools and streams using Veetle running smooth and slick now....but only with one that had an old black and whte picture. As soon as I started a coloured one I had a BSOD again :-(

So I uninstalled Zonealarm and it looks like that does the trick. No more BSOD's so far !!! I have no idea with Zonealarm has probs with this sort of (coloured) streams. Probably to much data through Zonealarm's security filter I guess.

Anyway usasma - you're my hero !! I have resolved most BSODs on my old XP-system on my own, but this one was a to hard nut to crack for me and I wouldn't have expected that Zonealarm is the reason for my problem.

Once again....thank you for your expert analysis and the time and effort you have put in there.

Kind regards

Hauke from Bremen, Germany


Love your sig (pass the dynamite ) and yes....you have the knack ! ;-)