Please assist.
I am experiencing BSOD after installing NAV 2010 on Windows 7 RTM. System experienced same BSOD during the public beta and now same issue with the NAV 2010 final release retail version.
Note, the BETA version was uninstalled entirely, all traces removed from the registry, all folders removed, and even ran the Norton Uninstall Tool to get anything left behind.
System has been running w/ no AV for SEVERAL days 24/7 w/o any issues. Once the retail release came out I decided to give it another chance and purchased it online w/ a 2 year subscription. It has been running for 2 days straight w/o any problems until last night when the system crashed on me.
---------------------------------------
System Specs:
---------------------------------------
Motherboard: ASUS P6T7 WS Supercomputer LGA 1366 Intel X58
Processor: Intel Core i7-975 Extreme Edition Bloomfield 3.33GHz LGA 1366 130W Quad-Core Processor
Memory Bank 1: CORSAIR DOMINATOR-GT 6GB (3 x 2GB) 240-Pin DDR3 SDRAM DDR3 1866 (PC3 15000)
Memory Bank 2: CORSAIR DOMINATOR-GT 6GB (3 x 2GB) 240-Pin DDR3 SDRAM DDR3 1866 (PC3 15000)
Above Memory Total: 12GB
Video Card: ASUS ENGTX295/2DI/1792MD3/A GeForce GTX 295 1792MB
HDD 1 & 2 in RAID 1 Config for C Drive: WD VelociRaptor 150GB SATA Hard Drive 10000rpm
HDD 3 & 4 in RAID 1 Config for D Drive: WD RE3 Enterprise 1 TB SATA Hard Drive 7200rpm
Note: Processor is not overclocked and memory is running at the XMP profile spec of 1.65v & 1866mhz.
Note 2: Memory test performed several times, no issues with memory detected.
Note 3: Windows 7 RTM is a clean install.
---------------------------------------
MEMORY.DMP
---------------------------------------
WARNING: Whitespace at start of path element
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Kevin\Desktop\MEMORY DUMP\20090912_1248\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
WARNING: Whitespace at start of path element
Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c61000 PsLoadedModuleList = 0xfffff800`02e9ee50
Debug session time: Sat Sep 12 12:46:34.954 2009 (GMT-4)
System Uptime: 0 days 0:48:30.844
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050033, 6f8, fffff80002cd88b6}
*** ERROR: Module load completed but symbols could not be loaded for SYMTDIV.SYS
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000006f8
Arg4: fffff80002cd88b6
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002cd2469 to fffff80002cd2f00
STACK_TEXT:
<<Note, I removed Stacked Text to fit character limit on this post. I can post it seperately if needed>>
STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO!CompareSecurityContexts+6a
fffff880`0198bc5a 448b442470 mov r8d,dword ptr [rsp+70h]
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: NETIO!CompareSecurityContexts+6a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETIO
IMAGE_NAME: NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18a
FAILURE_BUCKET_ID: X64_0x7f_8_NETIO!CompareSecurityContexts+6a
BUCKET_ID: X64_0x7f_8_NETIO!CompareSecurityContexts+6a
Followup: MachineOwner
---------
3: kd> lmvm NETIO
start end module name
fffff880`01985000 fffff880`019e5000 NETIO (pdb symbols) C:\Program Files\Debugging Tools for Windows (x64)\sym\netio.pdb\4ACD68B3A9824AAAB3C53C0077FC611F2\netio.pdb
Loaded symbol image file: NETIO.SYS
Image path: \SystemRoot\system32\drivers\NETIO.SYS
Image name: NETIO.SYS
Timestamp: Mon Jul 13 19:21:46 2009 (4A5BC18A)
CheckSum: 0005F36C
ImageSize: 00060000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4