Windows 7 BSOD after upgrade from Vista

[Poppa_Meth]

I recently did an upgrade install from Vista x64 Pro to Win7 x64 Pro. I normally don't try an upgrade but this PC was just built about a month before the upgrade was available.

I'm periodically getting BSOD related to different drivers every time. Here is the latest Memory Dump.

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols;SRV*DownstreamStore*http://msdl.microsoft.c...wnload/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e0a000 PsLoadedModuleList = 0xfffff800`03047e50
Debug session time: Sun Dec 27 09:49:19.981 2009 (GMT-5)
System Uptime: 3 days 0:06:41.468
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8, 2, 0, fffff880016531d9}

PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Probably caused by : NETIO.SYS ( NETIO!CheckEqualConditionEnumMatch+29 )

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

0: 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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880016531d9, address which referenced memory

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

PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details

READ_ADDRESS: 0000000000000008

CURRENT_IRQL: 2

FAULTING_IP:
NETIO!CheckEqualConditionEnumMatch+29
fffff880`016531d9 41817a08ff000000 cmp dword ptr [r10+8],0FFh

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: CNMNSUT.EXE

TRAP_FRAME: fffff880077f59f0 -- (.trap 0xfffff880077f59f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80071701b8
rdx=fffff880077f5fc0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880016531d9 rsp=fffff880077f5b80 rbp=fffffa80071701b8
r8=fffff880077f5c20 r9=fffff880077f5c24 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
NETIO!CheckEqualConditionEnumMatch+0x29:
fffff880`016531d9 41817a08ff000000 cmp dword ptr [r10+8],0FFh ds:00000000`00000008=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002e7b469 to fffff80002e7bf00

STACK_TEXT:
fffff880`077f58a8 fffff800`02e7b469 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`077f58b0 fffff800`02e7a0e0 : 00000000`00000000 fffff880`077f5c20 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`077f59f0 fffff880`016531d9 : fffffa80`06cec190 fffff880`0164b804 fffff880`0196e9a0 fffffa80`04790c60 : nt!KiPageFault+0x260
fffff880`077f5b80 fffff880`01656c15 : fffff880`077f5c20 fffff880`01836b93 fffffa80`04790c60 fffffa80`07315850 : NETIO!CheckEqualConditionEnumMatch+0x29
fffff880`077f5bb0 fffff880`01656b99 : 00000000`00000000 fffff880`077f5fc0 fffff880`077f5d50 00000000`00000000 : NETIO!CheckSpecialCasesConditionEnumMatch+0x35
fffff880`077f5bf0 fffff880`0165367f : 00000000`00000000 00000008`00000011 00000000`00000000 00000000`ffffffff : NETIO!MatchConditionContains+0x79
fffff880`077f5cf0 fffff880`01653824 : 00000000`00000000 00000000`00000000 fffffa80`07175710 00000000`00000000 : NETIO!FilterMatchEnum+0x16f
fffff880`077f5d50 fffff880`0165399a : 00000000`00000001 00000000`00000000 fffff880`00000000 00000000`00000000 : NETIO!IndexListEnum+0x64
fffff880`077f5dc0 fffff880`01654fe6 : 00000000`00000000 fffff880`077f5ee0 fffff880`07020003 00000000`000000b8 : NETIO!FeEnumLayer+0xaa
fffff880`077f5e20 fffff880`0181ed48 : 00000000`00000024 00000000`00000000 fffff880`077f6080 fffff880`077f5ec0 : NETIO!KfdEnumLayer+0x26
fffff880`077f5e60 fffff880`01857b9b : fffffa80`0396a088 fffff800`02fa0024 fffffa80`074455f0 00000000`0000b6ee : tcpip!FindPermittedPorts+0x1d8
fffff880`077f6480 fffff880`0185059b : 00000000`00000b60 00000000`0000eeb6 00000000`0000b6ee fffffa80`0396a000 : tcpip!WfpAleValidateWildcardPortRange+0x10b
fffff880`077f64f0 fffff880`0183319a : fffffa80`0744b840 fffffa80`00000000 fffffa80`0744b8c0 fffffa80`06593500 : tcpip!InetAcquirePort+0x19b
fffff880`077f65c0 fffff880`01833e3f : fffffa80`0744b840 fffff880`00000000 fffffa80`06593550 fffffa80`06593500 : tcpip!UdpBindEndpointRequestInspectComplete+0x21a
fffff880`077f66a0 fffff880`01833b9b : fffffa80`0756cbf0 fffff880`03e74e30 fffffa80`03df86f0 fffffa80`03df86f0 : tcpip!UdpBindEndpointWorkQueueRoutine+0x8f
fffff880`077f66f0 fffff880`01833877 : 00000000`00000000 fffff880`0184f8a0 fffffa80`0744b840 fffffa80`05900060 : tcpip!UdpBindEndpoint+0x8b
fffff880`077f6720 fffff880`03e72977 : 00000000`00000000 fffff800`ec646641 fffffa80`0751d240 00000000`02668ecc : tcpip!UdpIoControlEndpoint+0x87
fffff880`077f6810 fffff880`03e750fd : 00000000`00000010 fffff880`077f6c60 fffffa80`03df86f0 00000000`02668000 : afd!AfdTLIoControl+0x37
fffff880`077f6880 fffff880`03e5e569 : fffffa80`03b16bb0 fffffa80`00000000 00000000`00000001 fffff880`077f6c60 : afd!AfdTLBindSecurity+0xad
fffff880`077f6900 fffff800`031943a7 : fffffa80`03df86f0 fffff880`00000002 fffffa80`00000010 00000000`00000000 : afd!AfdBind+0x399
fffff880`077f69d0 fffff800`03194c06 : fffff880`077f6bb8 00000000`00000188 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`077f6b00 fffff800`02e7b153 : fffff880`077f6c60 fffffa80`05c23060 fffff880`077f6bb8 00000000`004de600 : nt!NtDeviceIoControlFile+0x56
fffff880`077f6b70 00000000`74362dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`004df0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74362dd9


STACK_COMMAND: kb

FOLLOWUP_IP:
NETIO!CheckEqualConditionEnumMatch+29
fffff880`016531d9 41817a08ff000000 cmp dword ptr [r10+8],0FFh

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: NETIO!CheckEqualConditionEnumMatch+29

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18a

FAILURE_BUCKET_ID: X64_0xD1_NETIO!CheckEqualConditionEnumMatch+29

BUCKET_ID: X64_0xD1_NETIO!CheckEqualConditionEnumMatch+29

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

Any input on how to fix this short of a clean install is appreciated.

Thanks.

[Poppa_Meth]

The other two time I've seen this so far were related to a directx driver and an nVidia driver. This started happening a couple weeks after the upgrade instead of immediately.

[Sartori]

The error mentions CNMNSUT.EXE , a quick google gives -->http://www.processlibrary.com/directory/files/cnmnsut/

Its belongs to your Canon IJ Network Scan Utility , I`d go through all startup sequence and note all the added entries - notably not Microsoft , its probably added on programs that are crashing . Locate updated versions and Uninstall all the programs that these entries are from and then reinstall them - virus checkers / firewalls , drivers for printers , scanners etc etc etc . And note down Process names that are in the BSOD and google them .

[Poppa_Meth]

Yes I did update this recently after the problems started. All Canon utilities are at their latest versions. I may have to fully uninstall and try it again. If this happens again I'll check for Cannon services in the log.

[Sartori]

In that case , I`d uninstall everything (that you`ve installed) and reinstall them one at a time and run for a period of time after each is installed until it starts going tits up (ie in this instance it might not be the Canon drivers but something else wiping out the Canon drivers causing it to BSOD - ie as you say , checking the logs) . Obviously Firewall first .

*Ive reflected upon this , see post below first , the random nature of it would suggest to me that its some external factor doing it (ie other than what the log says has crashed) .

[Sartori]

My other thoughts on this - it does seem strange though that it only happened after a couple of weeks , can you check your Microsoft Update logs , was there a patch applied automatically around then ? (the obvious) any programs installed ? CPU running cool enough ? Hard Drive running cool enough ? fans all working / no fluff ? any BIOS settings changed around then - memory timings , overclocking etc , updated ?

All of the above have caused me sweat and a lot of swearing as the causes of BSODs over the years .

My only other suggestion is if you have a System Restore point from before it started happening .

[Poppa_Meth]

No updates since the upgrade. No changes to the BIOS and all temps/fans are good. I built this computer from scratch and had no issues with Vista running on it for several months. This has only started since the Win7 upgrade. Makes me wish I stayed with Vista despite the free upgrade. If worse comes to worse, I have an image of the drive before Upgrade. I just wonder how switching back to Vista will work since Win7 has been activated.

[Sartori]

I did an upgrade on my wifes laptop , it puts all the Vista stuff into a folder called Windows Old (as I recall) and uninstalling W7 should just put everything back as before update , it shouldnt be an issue to backdate (saying that - it shouldnt have been an issue to update either) .
As Vista is a seperate licence , it shouldnt be an issue to backdate to it , I installed , updated , deleted and reinstalled all over the place on my system , even if its an issue , phoning Microsofts automated telephone line provided me with a key to reactivate a Vista licence .
As for the update on my wifes PC , I also wish I`d stayed with Vista on it . W7 has been nothing but a pain in the arse . Vista in all its incarnations (32 and 64 bit) have been rock solid for me , yes , Im not ashamed to say it , I love Vista , on my multiboot system - Vista 32 , Vista 64 , Windows 7 64 and Linux 64 - Ive set it to autoboot to Vista 64 , its dependable for me .

[jman98]

If you built your computer from scratch then why don't you know this - Microsoft's "upgrade" procedure is NOT trustworthy. The ONLY way to safely get a new version of Windows on a PC is to install completely from scratch. Upgrading sounds like a great idea, but it often has problems like yours.

[Poppa_Meth]

Since I did an Upgrade there is no Windows Old folder. This only appears when doing a clean install from an existing installation of Vista.

I know Upgrades seldom ever go right with Windows. The only reason I did it was because I just built it a couple of months prior to the Windows 7 upgrade and thought I'd try to avoid installing everything all over again. If all else fails I'll do a fresh install. I was just hoping that I could figure out for certain what is causing it before putting all the effort into a fresh install and running into the same problem if it's a bad driver issue.

[Bjs]

Similar problem here was resolved by manually setting the memory frequency in bios ... have not had any system problems since making the change a few months back ... might be worth assessing memory setup before you scrape the setup and starting from scratch

[Poppa_Meth]

So far I haven't messed with RAM or clock settings. Most of what I've found on the internet say that the default settings for this board (Gigabyte EP45-UD3P) should be well optimized. I have flashed the latest BIOS now, which knocked out my LAN connections requiring a new driver install in Windows. So far as I can tell all drivers are up to the latest versions now. I did update the Canon IJ Network Tool. It is up to v2.5.5 though the tool still lists as 2.5.0 in the About dialogue so it's hard to confirm. I'll hope for the best now.