Everything always worked fine in Vista RC1, I hope this issue is brought to
someones attention so that it can be corrected. I have an Asus M2n-SLi Deluxe
motherboard, with two nvidia nforce network adapters. The drivers for these
network adapters come with Vista, and used to always work fine.

In RC2, they still work fine to connect to the internet. However, if I try
and make a shared folder available on my network, and anyone tries to
download a file from my share, my network adapter craps out, I can't get back
onto the internet until I restart my computer.

In network properties, it shows no errors. However, if I try to disable and
reenable the problem adapter, the O/S freezes to a halt.

To test my theory that the network driver is bad, I messed around for about
40 minutes and finally got Vista to use an old driver that Nvidia designed
for Xp x64 for my network drivers, instead of the default one. Using this
driver, everything works perfectly. However when I restart my computer the
driver defaults back to the pre-installed driver and my problem comes back,
it happens on both adapaters.

To be sure of this problem I did a clean format of my computer, and
reinstalled vista RC2. I installed nothing else and tested the problem, it
repeated itself identically, leaving me 100% convinced this driver has some
sort of a problem in RC2. I tried two different hard drives, that didn't make
any difference either.

Any workarounds would be much appreciated.

I have been having similar problems both in RC1 32bit and 64bit and RC2 32bit
and 64bit versions. I have not been able to get this working at all. It has
drove me insane and now i just dont care. I just restart. My problem seems
to be when a lot of bandwith comes through my system the nic will just fail.
What i have tried doing is connect the network cable to the next nic and it
works perfectly. I do have MAC addressing on my router where one MAC gets
this IP and this MAC gets this IP. So everytime i switch NICS i have a diff
local IP. I have been working on this off and on lately as i have a lot of
free time now. If i find any way to resolve ill make another post. Just
wanted to let you know your not a lone. Some one else feels your frustration.

"Andy" wrote:

Everything always worked fine in Vista RC1, I hope this issue is brought to
someones attention so that it can be corrected. I have an Asus M2n-SLi Deluxe
motherboard, with two nvidia nforce network adapters. The drivers for these
network adapters come with Vista, and used to always work fine.

In RC2, they still work fine to connect to the internet. However, if I try
and make a shared folder available on my network, and anyone tries to
download a file from my share, my network adapter craps out, I can't get back
onto the internet until I restart my computer.

In network properties, it shows no errors. However, if I try to disable and
reenable the problem adapter, the O/S freezes to a halt.

To test my theory that the network driver is bad, I messed around for about
40 minutes and finally got Vista to use an old driver that Nvidia designed
for Xp x64 for my network drivers, instead of the default one. Using this
driver, everything works perfectly. However when I restart my computer the
driver defaults back to the pre-installed driver and my problem comes back,
it happens on both adapaters.

To be sure of this problem I did a clean format of my computer, and
reinstalled vista RC2. I installed nothing else and tested the problem, it
repeated itself identically, leaving me 100% convinced this driver has some
sort of a problem in RC2. I tried two different hard drives, that didn't make
any difference either.

Any workarounds would be much appreciated.

I have a very similar problem. My nvidia nic craps out during high bandwith
usage seems more likely to occur when high uploads are going on. I have a
quick fix on mine is switching cat5 cable to the next nic slot. At the same
time i also have MAC addressing setup in my router so 1 MAC gets this
reserved ip and the other MAC this reserved IP, so when i switch nic ports i
get a diff ip. I kinda figured i might be my router or my switch but i guess
it narrows down to vista and nvidia.

I havnt had any other luck in getting it to work. I have been having this
problem since the first vista beta release. I have the epox mf570sli.
Just wanted to let you know your not alone i share the hair pulling
frustration.

"Andy" wrote:

Everything always worked fine in Vista RC1, I hope this issue is brought to
someones attention so that it can be corrected. I have an Asus M2n-SLi Deluxe
motherboard, with two nvidia nforce network adapters. The drivers for these
network adapters come with Vista, and used to always work fine.

In RC2, they still work fine to connect to the internet. However, if I try
and make a shared folder available on my network, and anyone tries to
download a file from my share, my network adapter craps out, I can't get back
onto the internet until I restart my computer.

In network properties, it shows no errors. However, if I try to disable and
reenable the problem adapter, the O/S freezes to a halt.

To test my theory that the network driver is bad, I messed around for about
40 minutes and finally got Vista to use an old driver that Nvidia designed
for Xp x64 for my network drivers, instead of the default one. Using this
driver, everything works perfectly. However when I restart my computer the
driver defaults back to the pre-installed driver and my problem comes back,
it happens on both adapaters.

To be sure of this problem I did a clean format of my computer, and
reinstalled vista RC2. I installed nothing else and tested the problem, it
repeated itself identically, leaving me 100% convinced this driver has some
sort of a problem in RC2. I tried two different hard drives, that didn't make
any difference either.

Any workarounds would be much appreciated.

I have a very similar problem. My nvidia nic craps out during high bandwith
usage seems more likely to occur when high uploads are going on. I have a
quick fix on mine is switching cat5 cable to the next nic slot. At the same
time i also have MAC addressing setup in my router so 1 MAC gets this
reserved ip and the other MAC this reserved IP, so when i switch nic ports i
get a diff ip. I kinda figured i might be my router or my switch but i guess
it narrows down to vista and nvidia.

I havnt had any other luck in getting it to work. I have been having this
problem since the first vista beta release. I have the epox mf570sli.
Just wanted to let you know your not alone i share the hair pulling
frustration.

I have a very similar problem. My nvidia nic craps out during high bandwith
usage seems more likely to occur when high uploads are going on. I have a
quick fix on mine is switching cat5 cable to the next nic slot. At the same
time i also have MAC addressing setup in my router so 1 MAC gets this
reserved ip and the other MAC this reserved IP, so when i switch nic ports i
get a diff ip. I kinda figured i might be my router or my switch but i guess
it narrows down to vista and nvidia.

I havnt had any other luck in getting it to work. I have been having this
problem since the first vista beta release. I have the epox mf570sli.
Just wanted to let you know your not alone i share the hair pulling
frustration.

Thanks for the reply, yea it sounds like we are having the same issue here.
You should try what I did that made it work (though not a permanent fix, this
can you tell you without a shadow of a doubt that its the driver causing the
error). I

went on nvidias site, and downloaded the nforce drivers for my chipset and
selected the windows xp x64 edition of the drivers. I extracted the setup
files to a folder, and in this folder there is an ethernet folder. In here
you will find an older, 64 bit driver for our network cards.

Next took a lot of fighting with vista to get it to recognize this "new" old
driver. It always said the version I was trying to install wasn't better than
the one already installed. Eventually I uninstalled both of my network cards,
removed the default driver from the windows/system32/drivers folder, and
finally got it to recognize the old driver on ONE of the network cards. I
tested the heck out of this network card for hours and could not break it
under any circumstance. Obviously as soon as I had to restart it "fixed"
(read: broke) itself again. But at least this made me 100% certain its that
driver causing all my problems.

"PS851112" wrote:

I have a very similar problem. My nvidia nic craps out during high bandwith
usage seems more likely to occur when high uploads are going on. I have a
quick fix on mine is switching cat5 cable to the next nic slot. At the same
time i also have MAC addressing setup in my router so 1 MAC gets this
reserved ip and the other MAC this reserved IP, so when i switch nic ports i
get a diff ip. I kinda figured i might be my router or my switch but i guess
it narrows down to vista and nvidia.

I havnt had any other luck in getting it to work. I have been having this
problem since the first vista beta release. I have the epox mf570sli.
Just wanted to let you know your not alone i share the hair pulling
frustration.

Hey, i was checking out in device manager and saw under "power management"
there is a "allow the computer to turn off this device to save power" that
was checked. try unchecking that and see what happens. i just did it my
self and doing a lot of uploading, no problems yet, well see later on tonight
though.

"Andy" wrote:

Thanks for the reply, yea it sounds like we are having the same issue here.
You should try what I did that made it work (though not a permanent fix, this
can you tell you without a shadow of a doubt that its the driver causing the
error). I

went on nvidias site, and downloaded the nforce drivers for my chipset and
selected the windows xp x64 edition of the drivers. I extracted the setup
files to a folder, and in this folder there is an ethernet folder. In here
you will find an older, 64 bit driver for our network cards.

Next took a lot of fighting with vista to get it to recognize this "new" old
driver. It always said the version I was trying to install wasn't better than
the one already installed. Eventually I uninstalled both of my network cards,
removed the default driver from the windows/system32/drivers folder, and
finally got it to recognize the old driver on ONE of the network cards. I
tested the heck out of this network card for hours and could not break it
under any circumstance. Obviously as soon as I had to restart it "fixed"
(read: broke) itself again. But at least this made me 100% certain its that
driver causing all my problems.

"PS851112" wrote:

I have a very similar problem. My nvidia nic craps out during high bandwith
usage seems more likely to occur when high uploads are going on. I have a
quick fix on mine is switching cat5 cable to the next nic slot. At the same
time i also have MAC addressing setup in my router so 1 MAC gets this
reserved ip and the other MAC this reserved IP, so when i switch nic ports i
get a diff ip. I kinda figured i might be my router or my switch but i guess
it narrows down to vista and nvidia.

I havnt had any other luck in getting it to work. I have been having this
problem since the first vista beta release. I have the epox mf570sli.
Just wanted to let you know your not alone i share the hair pulling
frustration.

Well I posted this in the nvidia forums, but I thought it may be more
useful here...I've been having the same problem and got some debugging
reports from the BSOD's caused by the network driver.

Basically, whenever I leave DC++ or a torrent program running for a few
hours to a day, the network switches from internet to local only
(despite the fact that I can't see local computers either) and the only
way to resolve this is via a hard reset, as the computer fails to
restart via shutdown or restart commands in the start menu. Despite the
fact that this happens after a few hours running DC++ or utorrent (and
it does eventually happen everytime if I don't restart my computer
earlier), it takes only a matter of seconds if I'm getting a file off
mIRC. I decided to try playing around with some of the settings for the
ethernet controller (i.e. turning off power management in properties,
enabling flow control, turning off large send overflow, etc.) to see if
this had any effect. I then tested out these settings my trying to
download a file off mIRC and each time, it appears that I get a BSOD. I
tried getting some old drivers from the nvidia website, but
unfortunately any driver I get it says is not better than the current
one and vista quickly resets it. I also attempted to disable windows
firewall and windows defender to no avail. Here are the crash dumps from
the BSOD's analyzed in Debugging Tools for Windows x64:


Microsoft ® Windows Debugger Version 6.6.0007.5
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini101106-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Windows\Symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Windows Vista Kernel Version 5744 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff800`01800000 PsLoadedModuleList = 0xfffff800`01998030
Debug session time: Wed Oct 11 00:03:22.939 2006 (GMT-4)
System Uptime: 0 days 0:07:07.690
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Loading Kernel Symbols
.................................................. .................................................. ........................................
Loading User Symbols
Loading unloaded module list
..................
************************************************** **********
*******************
* *
* Bugcheck Analysis *
* *
************************************************** **********
*******************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {18, 2, 1, fffff9800420425a}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Unable to load image \SystemRoot\system32\DRIVERS\nvm60x64.sys, Win32
error 2
*** WARNING: Unable to verify timestamp for nvm60x64.sys
************************************************** **********
*************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** **********
*************
Probably caused by : nvm60x64.sys ( nvm60x64!OS_PacketWasReceived+1b6 )

Followup: MachineOwner
---------

1: kd !analyze -v
************************************************** **********
*******************
* *
* Bugcheck Analysis *
* *
************************************************** **********
*******************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address
at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000018, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff9800420425a, address which referenced memory

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** **********
*************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** **********
*************

FAULTING_MODULE: fffff80001800000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 44f88258

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
0000000000000018

CURRENT_IRQL: 2

FAULTING_IP:
nvm60x64!OS_PacketWasReceived+1b6
fffff980`0420425a ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from fffff8000184e273 to fffff8000184e4d0

STACK_TEXT:
fffff980`00ce3a68 fffff800`0184e273 : 00000000`0000000a
00000000`00000018 00000000`00000002 00000000`00000001 : nt+0x4e4d0
fffff980`00ce3a70 00000000`0000000a : 00000000`00000018
00000000`00000002 00000000`00000001 fffff980`0420425a : nt+0x4e273
fffff980`00ce3a78 00000000`00000018 : 00000000`00000002
00000000`00000001 fffff980`0420425a fffffa80`04ce7010 : 0xa
fffff980`00ce3a80 00000000`00000002 : 00000000`00000001
fffff980`0420425a fffffa80`04ce7010 00000000`00000000 : 0x18
fffff980`00ce3a88 00000000`00000001 : fffff980`0420425a
fffffa80`04ce7010 00000000`00000000 00000000`00000000 : 0x2
fffff980`00ce3a90 fffff980`0420425a : fffffa80`04ce7010
00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff980`00ce3a98 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 :
nvm60x64!OS_PacketWasReceived+0x1b6


STACK_COMMAND: kb

FOLLOWUP_IP:
nvm60x64!OS_PacketWasReceived+1b6
fffff980`0420425a ?? ???

SYMBOL_STACK_INDEX: 6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvm60x64

IMAGE_NAME: nvm60x64.sys

SYMBOL_NAME: nvm60x64!OS_PacketWasReceived+1b6

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

Second one:


Microsoft ® Windows Debugger Version 6.6.0007.5
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini101306-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Windows\Symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Windows Vista Kernel Version 5744 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff800`01800000 PsLoadedModuleList = 0xfffff800`01998030
Debug session time: Fri Oct 13 16:51:20.456 2006 (GMT-4)
System Uptime: 0 days 0:13:44.267
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Loading Kernel Symbols
.................................................. .................................................. .............................................
Loading User Symbols
Loading unloaded module list
..........
************************************************** **********
*******************
* *
* Bugcheck Analysis *
* *
************************************************** **********
*******************

Use !analyze -v to get detailed debugging information.

BugCheck C5, {8, 2, 1, fffff8000193bd83}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** **********
*************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** **********
*************
Unable to load image \SystemRoot\System32\drivers\tcpip.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for tcpip.sys
Probably caused by : ntoskrnl.exe ( nt+13bd83 )

Followup: MachineOwner
---------

1: kd !analyze -v
************************************************** **********
*******************
* *
* Bugcheck Analysis *
* *
************************************************** **********
*******************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address
at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8000193bd83, address which referenced memory

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** **********
*************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** **********
*************

MODULE_NAME: nt

FAULTING_MODULE: fffff80001800000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 45234f33

BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:
nt+13bd83
fffff800`0193bd83 ?? ???

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

LAST_CONTROL_TRANSFER: from fffff8000184e273 to fffff8000184e4d0

STACK_TEXT:
fffff980`00a65398 fffff800`0184e273 : 00000000`0000000a
00000000`00000008 00000000`00000002 00000000`00000001 : nt+0x4e4d0
fffff980`00a653a0 00000000`0000000a : 00000000`00000008
00000000`00000002 00000000`00000001 fffff800`0193bd83 : nt+0x4e273
fffff980`00a653a8 00000000`00000008 : 00000000`00000002
00000000`00000001 fffff800`0193bd83 00000000`00000000 : 0xa
fffff980`00a653b0 00000000`00000002 : 00000000`00000001
fffff800`0193bd83 00000000`00000000 00000000`00000000 : 0x8
fffff980`00a653b8 00000000`00000001 : fffff800`0193bd83
00000000`00000000 00000000`00000000 00000000`00000000 : 0x2
fffff980`00a653c0 fffff800`0193bd83 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff980`00a653c8 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x13bd83
fffff980`00a653d0 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a653d8 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a653e0 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a653e8 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a653f0 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a653f8 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a65400 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a65408 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a65410 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a65418 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a65420 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a65428 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a65430 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a65438 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a65440 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a65448 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a65450 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 fffff6fb`7da00000 : 0x0
fffff980`00a65458 00000000`00000000 : 00000000`00000000
00000000`00000000 fffff6fb`7da00000 00000000`00000000 : 0x0
fffff980`00a65460 00000000`00000000 : 00000000`00000000
fffff6fb`7da00000 00000000`00000000 00000000`00000000 : 0x0
fffff980`00a65468 00000000`00000000 : fffff6fb`7da00000
00000000`00000000 00000000`00000000 00000980`00000000 : 0x0
fffff980`00a65470 fffff6fb`7da00000 : 00000000`00000000
00000000`00000000 00000980`00000000 0000007f`fffffff8 : 0x0
fffff980`00a65478 00000000`00000000 : 00000000`00000000
00000980`00000000 0000007f`fffffff8 fffffa80`0200a090 : 0xfffff6fb`7da00000
fffff980`00a65480 00000000`00000000 : 00000980`00000000
0000007f`fffffff8 fffffa80`0200a090 00000000`00000000 : 0x0
fffff980`00a65488 00000980`00000000 : 0000007f`fffffff8
fffffa80`0200a090 00000000`00000000 fffff800`01966498 : 0x0
fffff980`00a65490 0000007f`fffffff8 : fffffa80`0200a090
00000000`00000000 fffff800`01966498 00000000`6264444e : 0x980`00000000
fffff980`00a65498 fffffa80`0200a090 : 00000000`00000000
fffff800`01966498 00000000`6264444e 00000000`00000001 : 0x7f`fffffff8
fffff980`00a654a0 00000000`00000000 : fffff800`01966498
00000000`6264444e 00000000`00000001 fffff800`01800000 : 0xfffffa80`0200a090
fffff980`00a654a8 fffff800`01966498 : 00000000`6264444e
00000000`00000001 fffff800`01800000 fffff800`019662c0 : 0x0
fffff980`00a654b0 00000000`6264444e : 00000000`00000001
fffff800`01800000 fffff800`019662c0 00000000`00000000 : nt+0x166498
fffff980`00a654b8 00000000`00000001 : fffff800`01800000
fffff800`019662c0 00000000`00000000 fffff800`0184d14b : 0x6264444e
fffff980`00a654c0 fffff800`01800000 : fffff800`019662c0
00000000`00000000 fffff800`0184d14b 00000000`00000001 : 0x1
fffff980`00a654c8 fffff800`019662c0 : 00000000`00000000
fffff800`0184d14b 00000000`00000001 00000000`6264444e : nt
fffff980`00a654d0 00000000`00000000 : fffff800`0184d14b
00000000`00000001 00000000`6264444e ffffffff`00000000 : nt+0x1662c0
fffff980`00a654d8 fffff800`0184d14b : 00000000`00000001
00000000`6264444e ffffffff`00000000 fffff980`052bd05f : 0x0
fffff980`00a654e0 00000000`00000001 : 00000000`6264444e
ffffffff`00000000 fffff980`052bd05f 6264444e`00000000 : nt+0x4d14b
fffff980`00a654e8 00000000`6264444e : ffffffff`00000000
fffff980`052bd05f 6264444e`00000000 00001f80`01016498 : 0x1
fffff980`00a654f0 ffffffff`00000000 : fffff980`052bd05f
6264444e`00000000 00001f80`01016498 00000000`00000000 : 0x6264444e
fffff980`00a654f8 fffff980`052bd05f : 6264444e`00000000
00001f80`01016498 00000000`00000000 fffffa80`00000004 : 0xffffffff`00000000
fffff980`00a65500 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 :
tcpip!IppFillPacketInfoCmsg+0x5f


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+13bd83
fffff800`0193bd83 ?? ???

SYMBOL_STACK_INDEX: 6

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

SYMBOL_NAME: nt+13bd83

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------



The last one was after I reconfigured some settings for the driver but
the first one was before that. Any help would be appreciated.