Hi there
I'm new here and just brought a laptop about 2 months back.
Had been getting this blue screen with a lots of wordings and then it restart, this happen about 4 times a day.
This is my PC details
Windows edition - Windows 7 Professional
Sysytem
Manufacter : Dell
Model : Precision M4500
Processor : Intel(R) Core(TM) i7 CPU M620 @ 2.67GHz
Installed memory (RAM) : 8.00GB (7.86 GB usable)
System Type : 64-bit Operating System
Here the dump file details from WinDbg
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
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*DownstreamStore*Symbol information
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`02c5d000 PsLoadedModuleList = 0xfffff800`02e9ae50
Debug session time: Sun Nov 7 07:37:50.493 2010 (GMT+8)
System Uptime: 0 days 7:46:11.038
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {68, 2, 1, fffff8800461b2e0}
*** ERROR: Module load completed but symbols could not be loaded for e1k62x64.sys
Probably caused by : e1k62x64.sys ( e1k62x64+1b2e0 )
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: 0000000000000068, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800461b2e0, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 0000000000000068
CURRENT_IRQL: 2
FAULTING_IP:
e1k62x64+1b2e0
fffff880`0461b2e0 f00fc14168 lock xadd dword ptr [rcx+68h],eax
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff8800757c850 -- (.trap 0xfffff8800757c850)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa800c988320 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800461b2e0 rsp=fffff8800757c9e0 rbp=000000000000011f
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`0461b2e0 f00fc14168 lock xadd dword ptr [rcx+68h],eax ds:00000000`00000068=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002cccca9 to fffff80002ccd740
STACK_TEXT:
fffff880`0757c708 fffff800`02cccca9 : 00000000`0000000a 00000000`00000068 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0757c710 fffff800`02ccb920 : fffffa80`0a0f0000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0757c850 fffff880`0461b2e0 : fffffa80`09cbb630 fffffa80`0a13d610 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0757c9e0 fffff880`04615c98 : fffffa80`09cb6610 00000000`00000000 00000000`00000000 00000000`00000000 : e1k62x64+0x1b2e0
fffff880`0757ca80 fffff880`04616092 : 00000000`00000000 00000000`00000000 fffffa80`09d0b1a0 fffff800`02cd4992 : e1k62x64+0x15c98
fffff880`0757cb60 fffff880`016ace4b : fffff880`01683110 00000000`00000000 fffffa80`09d0b1a0 fffffa80`09d0bf68 : e1k62x64+0x16092
fffff880`0757cba0 fffff880`01632bfd : fffffa80`0a0ebb58 00000000`0000000a 00000000`00000001 00000000`00000001 : ndis! ?? :
KGKHJNI::`string'+0x1597
fffff880`0757cc10 fffff880`01659b0c : 00000000`00000000 fffffa80`0a0ebb58 00000000`00000080 fffffa80`09597580 : ndis!ndisQueuedMiniportDpcWorkItem+0xcd
fffff880`0757ccb0 fffff800`02f71c06 : 00000000`00000000 fffffa80`0db27b60 00000000`00000080 00000000`00000000 : ndis!ndisReceiveWorkerThread+0x12c
fffff880`0757cd40 fffff800`02cabc26 : fffff880`033e9180 fffffa80`0db27b60 fffff880`033f3fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0757cd80 00000000`00000000 : fffff880`0757d000 fffff880`07577000 fffff880`0757ca00 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
e1k62x64+1b2e0
fffff880`0461b2e0 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
---------
Don't really understand all these, could someone please tell me what should I do?
(By the way, I not really good with PC knowledge, please type in a word to word help if you can)
Thank you
I'm new here and just brought a laptop about 2 months back.
Had been getting this blue screen with a lots of wordings and then it restart, this happen about 4 times a day.
This is my PC details
Windows edition - Windows 7 Professional
Sysytem
Manufacter : Dell
Model : Precision M4500
Processor : Intel(R) Core(TM) i7 CPU M620 @ 2.67GHz
Installed memory (RAM) : 8.00GB (7.86 GB usable)
System Type : 64-bit Operating System
Here the dump file details from WinDbg
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
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*DownstreamStore*Symbol information
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`02c5d000 PsLoadedModuleList = 0xfffff800`02e9ae50
Debug session time: Sun Nov 7 07:37:50.493 2010 (GMT+8)
System Uptime: 0 days 7:46:11.038
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {68, 2, 1, fffff8800461b2e0}
*** ERROR: Module load completed but symbols could not be loaded for e1k62x64.sys
Probably caused by : e1k62x64.sys ( e1k62x64+1b2e0 )
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: 0000000000000068, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800461b2e0, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 0000000000000068
CURRENT_IRQL: 2
FAULTING_IP:
e1k62x64+1b2e0
fffff880`0461b2e0 f00fc14168 lock xadd dword ptr [rcx+68h],eax
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff8800757c850 -- (.trap 0xfffff8800757c850)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa800c988320 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800461b2e0 rsp=fffff8800757c9e0 rbp=000000000000011f
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`0461b2e0 f00fc14168 lock xadd dword ptr [rcx+68h],eax ds:00000000`00000068=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002cccca9 to fffff80002ccd740
STACK_TEXT:
fffff880`0757c708 fffff800`02cccca9 : 00000000`0000000a 00000000`00000068 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0757c710 fffff800`02ccb920 : fffffa80`0a0f0000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0757c850 fffff880`0461b2e0 : fffffa80`09cbb630 fffffa80`0a13d610 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0757c9e0 fffff880`04615c98 : fffffa80`09cb6610 00000000`00000000 00000000`00000000 00000000`00000000 : e1k62x64+0x1b2e0
fffff880`0757ca80 fffff880`04616092 : 00000000`00000000 00000000`00000000 fffffa80`09d0b1a0 fffff800`02cd4992 : e1k62x64+0x15c98
fffff880`0757cb60 fffff880`016ace4b : fffff880`01683110 00000000`00000000 fffffa80`09d0b1a0 fffffa80`09d0bf68 : e1k62x64+0x16092
fffff880`0757cba0 fffff880`01632bfd : fffffa80`0a0ebb58 00000000`0000000a 00000000`00000001 00000000`00000001 : ndis! ?? :
fffff880`0757cc10 fffff880`01659b0c : 00000000`00000000 fffffa80`0a0ebb58 00000000`00000080 fffffa80`09597580 : ndis!ndisQueuedMiniportDpcWorkItem+0xcd
fffff880`0757ccb0 fffff800`02f71c06 : 00000000`00000000 fffffa80`0db27b60 00000000`00000080 00000000`00000000 : ndis!ndisReceiveWorkerThread+0x12c
fffff880`0757cd40 fffff800`02cabc26 : fffff880`033e9180 fffffa80`0db27b60 fffff880`033f3fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0757cd80 00000000`00000000 : fffff880`0757d000 fffff880`07577000 fffff880`0757ca00 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
e1k62x64+1b2e0
fffff880`0461b2e0 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
---------
Don't really understand all these, could someone please tell me what should I do?
(By the way, I not really good with PC knowledge, please type in a word to word help if you can)
Thank you
My Computer
- OS
- Windows 7 Profesasional 64