New
#1
Blue Screen issue with ek162x64.sys
Is Windows 7 X64 Pro
Installed From Disk
Overwrote installed Windows to remove onreader
attaching docs.
Is Windows 7 X64 Pro
Installed From Disk
Overwrote installed Windows to remove onreader
attaching docs.
These were caused by your e1k62x64,sys. Intel(R) Gigabit Adapter NDIS 6.x driver, C:\Windows\system32\DRIVERS\e1k62x64.sys
I would re-install it and all the other drivers listed below. You should also remove Norton and replace it with Microsoft Scurity Essentials
Let us know if you need assistance with any of this
'Ken
Code:PBADRV.sys fffff880`0163a000 fffff880`01646000 0x0000c000 0x4782798d 1/7/2008 15:12:13 SYMEVENT64x86.SYS fffff880`039c5000 fffff880`039fb000 0x00036000 0x478bf103 1/14/2008 19:32:19 SRTSP64.SYS fffff880`02e00000 fffff880`02e73000 0x00073000 0x49a366f8 2/23/2009 23:18:16 SRTSPX64.SYS fffff880`013e2000 fffff880`013f6000 0x00014000 0x49a36795 2/23/2009 23:20:53 dsNcAdpt.sys fffff880`04411000 fffff880`0441e000 0x0000d000 0x49d180fd 3/30/2009 22:33:33 dump_iaStorV.sys fffff880`02e93000 fffff880`02fb1000 0x0011e000 0x49dcd76d 4/8/2009 12:57:17 iaStorV.sys fffff880`010ad000 fffff880`011cb000 0x0011e000 0x49dcd76d 4/8/2009 12:57:17 spldr.sys fffff880`017dc000 fffff880`017e4000 0x00008000 0x4a0858bb 5/11/2009 12:56:27 amdxata.sys fffff880`011cb000 fffff880`011d6000 0x0000b000 0x4a12f2eb 5/19/2009 13:56:59
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\090810-36020-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Whitespace at end of path element 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 (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02e57000 PsLoadedModuleList = 0xfffff800`03094e50 Debug session time: Wed Sep 8 12:06:30.237 2010 (GMT-4) System Uptime: 0 days 0:20:10.405 Loading Kernel Symbols ............................................................... ................................................................ ....................................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {90, 2, 1, fffff880045cc353} Unable to load image \SystemRoot\system32\DRIVERS\e1k62x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for e1k62x64.sys *** ERROR: Module load completed but symbols could not be loaded for e1k62x64.sys Probably caused by : e1k62x64.sys ( e1k62x64+1b353 ) 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: 0000000000000090, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff880045cc353, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ff0e0 0000000000000090 CURRENT_IRQL: 2 FAULTING_IP: e1k62x64+1b353 fffff880`045cc353 48899090000000 mov qword ptr [rax+90h],rdx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff880098ef850 -- (.trap 0xfffff880098ef850) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800626aca0 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880045cc353 rsp=fffff880098ef9e0 rbp=00000000000001cb r8=0000000000000001 r9=0000000000000000 r10=0000000000000000 r11=000000000000fffb r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc e1k62x64+0x1b353: fffff880`045cc353 48899090000000 mov qword ptr [rax+90h],rdx ds:00000000`00000090=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ec6ca9 to fffff80002ec7740 STACK_TEXT: fffff880`098ef708 fffff800`02ec6ca9 : 00000000`0000000a 00000000`00000090 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`098ef710 fffff800`02ec5920 : fffffa80`03d803d0 00000000`00000000 fffffa80`03d800b0 fffffa80`03d80560 : nt!KiBugCheckDispatch+0x69 fffff880`098ef850 fffff880`045cc353 : fffffa80`05e0c6c0 fffffa80`05d166b0 00000000`00000000 00000000`00000009 : nt!KiPageFault+0x260 fffff880`098ef9e0 fffffa80`05e0c6c0 : fffffa80`05d166b0 00000000`00000000 00000000`00000009 00000000`00000000 : e1k62x64+0x1b353 fffff880`098ef9e8 fffffa80`05d166b0 : 00000000`00000000 00000000`00000009 00000000`00000000 fffff880`045d44f4 : 0xfffffa80`05e0c6c0 fffff880`098ef9f0 00000000`00000000 : 00000000`00000009 00000000`00000000 fffff880`045d44f4 fffffa80`00000000 : 0xfffffa80`05d166b0 STACK_COMMAND: kb FOLLOWUP_IP: e1k62x64+1b353 fffff880`045cc353 48899090000000 mov qword ptr [rax+90h],rdx SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: e1k62x64+1b353 FOLLOWUP_NAME: MachineOwner MODULE_NAME: e1k62x64 IMAGE_NAME: e1k62x64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4bbae4c3 FAILURE_BUCKET_ID: X64_0xD1_e1k62x64+1b353 BUCKET_ID: X64_0xD1_e1k62x64+1b353 Followup: MachineOwner ---------
Hello and Welcome !
The crash dump points to your Intel networking driver - e1k62x64.sys. Please visit the Intel website and download the latest Windows 7 drivers for your network card.
Uninstall Symantec End Point Protection and use the Tool to clean the left over files Endpoint Removal Tool | Symantec Connect and install Microsoft Security Essentials.
Bugcheck:
Hope this helps,Code:******************************************************************************* * * * 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: 0000000000000068, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff880046852e0, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ba0e0 0000000000000068 CURRENT_IRQL: 2 FAULTING_IP: e1k62x64+1b2e0 fffff880`046852e0 f00fc14168 lock xadd dword ptr [rcx+68h],eax CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff8800a02c850 -- (.trap 0xfffff8800a02c850) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000ffffffff rbx=0000000000000000 rcx=0000000000000000 rdx=fffffa8003a8dcd0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880046852e0 rsp=fffff8800a02c9e0 rbp=0000000000000012 r8=0000000000000001 r9=0000000000000000 r10=0000000000000000 r11=000000000000fffb r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc e1k62x64+0x1b2e0: fffff880`046852e0 f00fc14168 lock xadd dword ptr [rcx+68h],eax ds:00000000`00000068=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002e81ca9 to fffff80002e82740 STACK_TEXT: fffff880`0a02c708 fffff800`02e81ca9 : 00000000`0000000a 00000000`00000068 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`0a02c710 fffff800`02e80920 : fffffa80`0738f560 00000000`00000000 fffffa80`0738fec0 fffffa80`0738f240 : nt!KiBugCheckDispatch+0x69 fffff880`0a02c850 fffff880`046852e0 : fffffa80`05fd2cc0 fffffa80`05ee97f8 00000000`00000000 00000000`00000009 : nt!KiPageFault+0x260 fffff880`0a02c9e0 fffffa80`05fd2cc0 : fffffa80`05ee97f8 00000000`00000000 00000000`00000009 00000000`00000000 : e1k62x64+0x1b2e0 fffff880`0a02c9e8 fffffa80`05ee97f8 : 00000000`00000000 00000000`00000009 00000000`00000000 fffff880`0468d4f4 : 0xfffffa80`05fd2cc0 fffff880`0a02c9f0 00000000`00000000 : 00000000`00000009 00000000`00000000 fffff880`0468d4f4 fffffa80`00000000 : 0xfffffa80`05ee97f8 STACK_COMMAND: kb FOLLOWUP_IP: e1k62x64+1b2e0 fffff880`046852e0 f00fc14168 lock xadd dword ptr [rcx+68h],eax SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: e1k62x64+1b2e0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: e1k62x64 IMAGE_NAME: e1k62x64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4bbae4c3 FAILURE_BUCKET_ID: X64_0xD1_e1k62x64+1b2e0 BUCKET_ID: X64_0xD1_e1k62x64+1b2e0 Followup: MachineOwner
Captain
Edit: Sorry Ken i dodn't see your replay seems like we both said the same thing