BSoD - Fresh install

realbass1 said:

Hello All,
Thank you in advance for your assistance. I've been helping a friend with his machine and he just recently started getting BSoDs. He thinks it may have been caused by a World of Warcraft update, but he's continuing to get BSoDs with a fresh install of Win7 Home Premium x64.

The machine is a home-built machine with all components purchased from Newegg or Amazon (Amazon itself and not any sub-retailers that sell on amazon).

Specs:
Motherboard EVGA P55 LE
Graphics: EVGA GTX465
Processor: Core i7-870
Ram: 8GB of Crucial
OS: Full Retail
Age of system: 6 months
OS Age: fresh install for 30 minutes prior to BSoD

Memtest86 was clean for several hours.
Things that were installed prior to the crash:
- Norton 360
- MS office
- Google Chrome
-Nero
-Razer drivers
-EVGA Drivers

Well this one points directly to your Norton 360. Remove and replace with Microsoft Security Essentials

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

http://www.microsoft.com/security_essentials/

Code:

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\042011-38921-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*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 Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e09000 PsLoadedModuleList = 0xfffff800`03046e50
Debug session time: Wed Apr 20 16:43:23.029 2011 (GMT-4)
System Uptime: 0 days 0:17:57.091
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8800313a5b0, 0, 0}

Unable to load image \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\N360_4.0.0.127\Definitions\IPSDefs\20091105.001\IDSVia64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for IDSVia64.sys
*** ERROR: Module load completed but symbols could not be loaded for IDSVia64.sys
Probably caused by : IDSVia64.sys ( IDSVia64+45187 )

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

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800313a5b0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


OVERLAPPED_MODULE: Address regions for 'ENG64' and 'ENG64.SYS' overlap

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
+5dc2952f03c4db5c
fffff880`0313a5b0 d8b4130380f8ff  fdiv    dword ptr [rbx+rdx-77FFDh]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b10e0
 0000000000000000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff8800313b4d8 -- (.exr 0xfffff8800313b4d8)
ExceptionAddress: fffff88008e59187 (IDSVia64+0x0000000000045187)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff8800313b580 -- (.trap 0xfffff8800313b580)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=09d5ed10fffffb01 rbx=0000000000000000 rcx=0000000000000027
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88008e59187 rsp=fffff8800313b710 rbp=ffffffffffffffff
 r8=fffff88008e14000  r9=0000000000000004 r10=fffffa800b61275c
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
IDSVia64+0x45187:
fffff880`08e59187 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f0bb2b to fffff80002e7af00

STACK_TEXT:  
fffff880`0313a4f8 fffff800`02f0bb2b : 00000000`0000001e ffffffff`c0000005 fffff880`0313a5b0 00000000`00000000 : nt!KeBugCheckEx
fffff880`0313a500 fffff800`02ece390 : 0000b384`0fed8445 0f013cc0`200f4400 84c74800`0000a787 fdb61000`00014024 : nt!KipFatalFilter+0x1b
fffff880`0313a540 fffff800`02ea94dc : 33451057`8d48fffb 15ff0000`0101b9c9 74c08548`fffb6d04 fffe0193`0583f063 : nt! ?? ::FNODOBFM::`string'+0x95d
fffff880`0313a580 fffff800`02ea0bed : fffff800`02fc1470 fffff880`0313d440 00000000`00000000 fffff800`02e09000 : nt!_C_specific_handler+0x8c
fffff880`0313a5f0 fffff800`02ea8250 : fffff800`02fc1470 fffff880`0313a668 fffff880`0313b4d8 fffff800`02e09000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0313a620 fffff800`02eb51b5 : fffff880`0313b4d8 fffff880`0313ad30 fffff880`00000000 fffffa80`00000005 : nt!RtlDispatchException+0x410
fffff880`0313ad00 fffff800`02e7a542 : fffff880`0313b4d8 fffffa80`0a0e2730 fffff880`0313b580 fffff880`0313b8c0 : nt!KiDispatchException+0x135
fffff880`0313b3a0 fffff800`02e78e4a : 00000000`00000001 00000000`00000001 fffffa80`0b612434 fffffa80`06f72264 : nt!KiExceptionDispatch+0xc2
fffff880`0313b580 fffff880`08e59187 : fffff880`0313b8a0 fffff880`0313b8c0 fffffa80`0b09ffb4 fffffa80`0a67e004 : nt!KiGeneralProtectionFault+0x10a
fffff880`0313b710 fffff880`0313b8a0 : fffff880`0313b8c0 fffffa80`0b09ffb4 fffffa80`0a67e004 fffffa80`40000000 : IDSVia64+0x45187
fffff880`0313b718 fffff880`0313b8c0 : fffffa80`0b09ffb4 fffffa80`0a67e004 fffffa80`40000000 fffffa80`0a3ea754 : 0xfffff880`0313b8a0
fffff880`0313b720 fffffa80`0b09ffb4 : fffffa80`0a67e004 fffffa80`40000000 fffffa80`0a3ea754 00000000`00000004 : 0xfffff880`0313b8c0
fffff880`0313b728 fffffa80`0a67e004 : fffffa80`40000000 fffffa80`0a3ea754 00000000`00000004 fffff880`01865767 : 0xfffffa80`0b09ffb4
fffff880`0313b730 fffffa80`40000000 : fffffa80`0a3ea754 00000000`00000004 fffff880`01865767 00000000`00000000 : 0xfffffa80`0a67e004
fffff880`0313b738 fffffa80`0a3ea754 : 00000000`00000004 fffff880`01865767 00000000`00000000 fffffa80`0b09ffbc : 0xfffffa80`40000000
fffff880`0313b740 00000000`00000004 : fffff880`01865767 00000000`00000000 fffffa80`0b09ffbc fffffa80`0b612434 : 0xfffffa80`0a3ea754
fffff880`0313b748 fffff880`01865767 : 00000000`00000000 fffffa80`0b09ffbc fffffa80`0b612434 fffffa80`00000000 : 0x4
fffff880`0313b750 00000000`00000000 : fffff880`0313b870 fffffa80`0b5aea40 00000000`00000006 00000000`00000000 : tcpip!IppDispatchSendPacketHelper+0x87


STACK_COMMAND:  kb

FOLLOWUP_IP: 
IDSVia64+45187
fffff880`08e59187 ??              ???

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  IDSVia64+45187

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: IDSVia64

IMAGE_NAME:  IDSVia64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ae76706

FAILURE_BUCKET_ID:  X64_0x1E_IDSVia64+45187

BUCKET_ID:  X64_0x1E_IDSVia64+45187

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

6: kd> lmvm IDSVia64
start             end                 module name
fffff880`08e14000 fffff880`08e8b000   IDSVia64 T (no symbols)           
    Loaded symbol image file: IDSVia64.sys
    Image path: \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\N360_4.0.0.127\Definitions\IPSDefs\20091105.001\IDSVia64.sys
    Image name: IDSVia64.sys
    Timestamp:        Tue Oct 27 17:32:54 2009 (4AE76706)
    CheckSum:         00072557
    ImageSize:        00077000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4