Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: ntoskrnl.exe Problem

18 Apr 2010   #1

ntoskrnl.exe Problem

X64 Windows 7 often crashes with blue screen, and error
minidump attached

My System SpecsSystem Spec
18 Apr 2010   #2
Capt.Jack Sparrow

Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit

Quote   Quote: Originally Posted by ector View Post
X64 Windows 7 often crashes with blue screen, and error
minidump attached

Hello !! Welcome to SF !!

I guess the problem is with L1E62x64.sys Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller. Remove the existing driver completely. Then disable automatic Driver installation Turn off Windows 7 Automatic Driver Installation | then download the latest driver from Atheros Communications then install it.

*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

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 a kernel debugger is available get the stack backtrace.
Arg1: 0000100000010329, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c22977, address which referenced memory

Debugging Details:

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0f0e0


fffff800`02c22977 448b6f2c        mov     r13d,dword ptr [rdi+2Ch]




PROCESS_NAME:  emule.exe

TRAP_FRAME:  fffff880095236c0 -- (.trap 0xfffff880095236c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000002c rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c22977 rsp=fffff88009523850 rbp=fffffa8008b94998
 r8=0000000000000000  r9=0000000000000008 r10=fffffa800859c870
r11=fffff880095237e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fffff800`02c22977 448b6f2c        mov     r13d,dword ptr [rdi+2Ch] ds:f003:00000000`0000002c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cd6b69 to fffff80002cd7600

fffff880`09523578 fffff800`02cd6b69 : 00000000`0000000a 00001000`00010329 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`09523580 fffff800`02cd57e0 : 00000000`00000000 fffffa80`08b94988 00000000`00000003 00000000`970f1fd4 : nt!KiBugCheckDispatch+0x69
fffff880`095236c0 fffff800`02c22977 : 00000000`00000000 fffff800`02c1ffb9 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x260
fffff880`09523850 fffff800`02c2313d : fffffa80`081d0050 fffffa80`0859c870 fffffa80`0859c801 00000000`00000000 : hal!HalpAllocateAdapterCallback+0xef
fffff880`095238f0 fffff800`02c2271f : fffffa80`08b94940 00000000`0000002c fffffa80`0859c870 fffffa80`0a0192c0 : hal!HalAllocateAdapterChannel+0x101
fffff880`09523930 fffff880`0169a831 : fffffa80`0a917920 fffffa80`06c477d0 00000000`000000a0 fffff880`01791bb1 : hal!HalBuildScatterGatherList+0x2f3
fffff880`095239a0 fffff880`03deaa10 : fffffa80`081d01a0 00000000`00000000 fffffa80`08b8a320 fffffa80`06c477d0 : ndis!NdisMAllocateNetBufferSGList+0x181
fffff880`09523a40 fffffa80`081d01a0 : 00000000`00000000 fffffa80`08b8a320 fffffa80`06c477d0 fffffa80`08b94940 : L1E62x64+0x6a10
fffff880`09523a48 00000000`00000000 : fffffa80`08b8a320 fffffa80`06c477d0 fffffa80`08b94940 fffffa80`000001c0 : 0xfffffa80`081d01a0


fffff880`03deaa10 ??              ???


SYMBOL_NAME:  L1E62x64+6a10

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  L1E62x64.sys


FAILURE_BUCKET_ID:  X64_0xA_L1E62x64+6a10

BUCKET_ID:  X64_0xA_L1E62x64+6a10

Followup: MachineOwner
Hope this helps,
My System SpecsSystem Spec

 ntoskrnl.exe Problem

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Similar help and support threads
Thread Forum
ntoskrnl.exe problem
my laptop Is showing bluescreen and I guess there is some problem with this file ntoskrnl.exe please help
BSOD Help and Support
DRIVER_POWER_STATE_FAILURE ntoskrnl.exe problem?
My laptop has been experiencing blue screen of death shutdowns frequently when I leave it by itself for a while, I checked my drivers and they are all up to date, I also scanned it using antivirus and there was no virus found. What could be the problem? I've attached the dump file can you please...
BSOD Help and Support
HIDCLASS.SYS & ntoskrnl.exe Problem's
Hi, i'm using Windows 7 Ultimate x64 and updated Service Pack 1 its like to crash when i'm playing game or just to listen music by winamp application ( sometimes it also happen when i just browsing with google chrome ) i've already re-install the OS, but i got the same thing:cry: this is my...
BSOD Help and Support
ntoskrnl.exe problem?
My computer always need start over twice that can enter the OS. sometime will show the ERROR like "dump of physical memory" or "memory crash". I don't know how to solve this problem. Help plz.
BSOD Help and Support
Problem ntoskrnl.exe
Windows 7 x 64 frequently reboots with blue screen and gives me error This Was Likely Caused By The Following module: ntoskrnl.exe Bugcheck code: 0xA (0xFFFFF88112BFFA80, 0x2, 0x0, 0xFFFFF80002C7F640) Error: IRQL_NOT_LESS_OR_EQUAL Dump File: C: \ Windows \ Minidump \ 041,710 to 17,316-01.dmp...
Win 7 Bluescreen ntoskrnl.exe problem
Hello, I have this non stop problem with my new NW21MF Vaio. I start, first comes a bluescreen or Winows message that Winexplorer found a problem and shout down. I run the dump reader and every bluescreen is following (more then 50 times already): ADDITIONAL_DEBUG_TEXT: Use...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 15:48.

Twitter Facebook Google+

Windows 7 Forums

Seven Forums Android App Seven Forums IOS App