Internet Sharing BSOD

[Niels]

Hi Guys,
hope you can give a lead with the following..

Get a 100% reproducable BSOD when I activate Internet Sharing (ICS) on my system:
- internet connection via NVIDIA nForce on-board controller, shared
- USB-RNDIS device tries to use this connection, using "NDIS-kompatibles Remotegerät" (yeah, my Win7 is german) selected manually from the list (right-click in device manager, etcetera) i.e. windows internal driver.

My system:
ASUS M2N68-AM SE2 mainboard, everything on-board (VGA, Eth, USB2).

Now both devices work perfectly independently, and also simultaneously - so I can do work using both devices - surf the net, do ssh to my USB-RNDIS device, no problem.

As soon as I check 'share this connection' in the nForce controller checkbox I get BSOD in a matter of seconds.

Note that my Vista (SP1 I think) and Ubuntu work perfectly. Yeah, got a Triple-boot system

I attached a minidump, but for ease of use I also have the stack trace here,
which is always (tried 3 times):

nt!KeBugCheckEx
nt!KiBugCheckDispatch+0x69
nt!KiPageFault+0x260
NETIO!NetioCompleteNetBufferAndNetBufferListChain+0x55
NETIO!NetioDereferenceNetBufferListChain+0xf3
tcpip!FlSendNetBufferListChainComplete+0x37
ndis!ndisMSendCompleteNetBufferListsInternal+0x10f
ndis!NdisMSendNetBufferListsComplete+0x6d
RNDISMP6!CompleteSendData+0x292
RNDISMP6!RndisMSendComplete+0x11d
usb80236!WritePipeCompletion+0x3c
nt!IopfCompleteRequest+0x3a6
USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
USBPORT!USBPORT_Xdpc_Worker+0x1d9
nt!KiRetireDpcList+0x1bc
nt!KiIdleLoop+0x5a

What's going on? Help!

 

[usasma]

I'm willing to bet that there's an incompatibility or a corruption with the drivers of the USB device (due to the presence of both Networking and USB drivers in the stack text) - but it doesn't directly appear in the stack text that you've provided. So,
- Please provide the exact make and model of the USB device, and
- Please run Driver Verifier according to these directions (to hopefully force the system to cough up the name of the 3rd party driver that's causing this):

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"
- 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.

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

More to follow after I run the dump files.....

 

[usasma]

AHA!!! Look at what's raised it's ugly head here:

ASACPI.sys Sun Mar 27 22:30:36 2005

This is a known BSOD causing driver in Win7 (and sometimes in Vista also).

Please visit the Asus website here: ASUSTeK Computer Inc.-Support-
and download (in the Utilities section) the ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit

Summary of the BSOD:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun  3 11:47:43.391 2010 (GMT-4)
System Uptime: 0 days 0:00:51.061
BugCheck D1, {0, 2, 0, fffff8800157b565}
Probably caused by : NETIO.SYS ( NETIO!NetioCompleteNetBufferAndNetBufferListChain+55 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System

 

[Niels]

Hi there John,

first of all thanks very much for putting some effort in it.
I tried your first remark and updated my ASACPI.sys,
checked 'Properties' of 'ATK0110 ACPI UTILITY' in the device manager to check it correlated to the .inf contents.
Unfortunately, this did not help - still BSOD.

I rechecked my Vista, and noticed something there - this immediately answers your question too.

The driver I am using is the Microsoft USB RNDIS driver, however, they do not deliver this as build-in so you have to revamp a template .inf, For Win7, I took it from C:\windows\inf\rndiscmp.inf and ajusted the USB to take the VID/PID of my device, which happens to be a linux development running the stock RNDIS 'Gadget' driver. Result is anyway that I am using the default .sys files. (For Vista I used a different approach)

Now, they updated this driver - in Vista it's RNDIS 5.x, and in W7 it's RNDIS 6.x by default. I removed some 6's in the inf, did a reinstall, and hey presto! using 5.x and no BSOD since, problem 'solved'. Maybe, maybe, the 6.x driver is biting the on-board Eth driver, I will get myself a USB-Eth dongle to verify that later when I have time

Thanks again for the reply.

Niels

 

[usasma]

Glad to hear that you got it fixed!
I have no idea about rebuilding inf files like that - so I'll leave it up to you!