BSOD and ntoskrnl.exe

[Gabriele]

Hi people,
some months ago I had some bsod on my pc (with Win7 x64), that disappeared when I upgraded the bios.
Now they come back again and by the bluescreenviewer I see that the cause is the ntoskrnl.exe.
Could someone help me?

 

[zigzag3143]

Hi people,
some months ago I had some bsod on my pc (with Win7 x64), that disappeared when I upgraded the bios.
Now they come back again and by the bluescreenviewer I see that the cause is the ntoskrnl.exe.
Could someone help me?

There are 3 problems

1-ASACPI.SYS a major cause of BSOD's in the 2005 rev.

The pre 2009 version of this driver is a known BSOD cause.

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it. (ASUSTeK Computer Inc. -Support- Drivers and Download Tools)
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).


2-AVG remnants. Also a known BSOD cause and not installed properly. Remove and replace with Microsoft Security essentials

AVG - Download tools

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


3-Memory corruption. Probably caused by one of the above but to be sure run memtest.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86.com - Memory Diagnostic

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

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-23946-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
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c57000 PsLoadedModuleList = 0xfffff800`02e94e50
Debug session time: Wed Apr 20 04:39:25.844 2011 (GMT-4)
System Uptime: 0 days 0:00:10.857
Loading Kernel Symbols
...............................................................
..............
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa802bb4d4a0, 2, 1, fffff80002cecb7f}

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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.
Arguments:
Arg1: fffffa802bb4d4a0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002cecb7f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eff0e0
 fffffa802bb4d4a0 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReplenishPageSlist+100
fffff800`02cecb7f f00fba6b1000    lock bts dword ptr [rbx+10h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880009a92d0 -- (.trap 0xfffff880009a92d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffffffffff000 rbx=0000000000000000 rcx=fffff88003ce9000
rdx=0000000000354000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d0c5d0 rsp=fffff880009a9468 rbp=fffff8a0002ac620
 r8=fffff80002e41e80  r9=0000000000000100 r10=0000000000000080
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po cy
nt!KeCopyPage+0x50:
fffff800`02d0c5d0 0f280410        movaps  xmm0,xmmword ptr [rax+rdx] ds:0004:00000000`00353000=????????????????????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cc6ca9 to fffff80002cc7740

STACK_TEXT:  
fffff880`009a8a78 fffff800`02cc6ca9 : 00000000`0000000a fffffa80`2bb4d4a0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009a8a80 fffff800`02cc5920 : 00000000`00000001 fffffa80`2bb4d490 00000980`00000000 0000007f`fffffff8 : nt!KiBugCheckDispatch+0x69
fffff880`009a8bc0 fffff800`02cecb7f : fffff8a0`00338010 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009a8d50 fffff800`02ced0af : fffff800`02f01400 00000000`00000043 fffffa80`05153490 fffffa80`05151c90 : nt!MiReplenishPageSlist+0x100
fffff880`009a8db0 fffff800`02ce52c7 : 00000000`00000002 fffffa80`00000002 fffffa80`0548dc28 00000000`00000002 : nt!MiRemoveAnyPage+0x24f
fffff880`009a8ed0 fffff800`02cedd67 : 00000000`00000000 00000000`00353000 fffff880`009a92d0 fffff680`00001a98 : nt!MiResolveDemandZeroFault+0x577
fffff880`009a8fc0 fffff800`02ce35be : 00000000`00000000 00000000`00353000 fffff680`00001a98 fffffa80`0548dc28 : nt!MiResolveProtoPteFault+0x3b7
fffff880`009a9060 fffff800`02ce1743 : 00000000`00000000 00000000`00353000 00000000`001b463b 00000000`00000000 : nt!MiDispatchFault+0x1de
fffff880`009a9170 fffff800`02cc582e : 00000000`00000000 00000001`b463b963 00000000`00000000 fffff6fc`4003fd78 : nt!MmAccessFault+0x343
fffff880`009a92d0 fffff800`02d0c5d0 : fffff800`030aa905 00000001`b463c963 00000000`001b463b fffff8a0`002ac620 : nt!KiPageFault+0x16e
fffff880`009a9468 fffff800`030aa905 : 00000001`b463c963 00000000`001b463b fffff8a0`002ac620 fffff8a0`002bf890 : nt!KeCopyPage+0x50
fffff880`009a9470 fffff800`030ad2e8 : 00000000`00000000 fffff8a0`002ac620 fffff880`03ce8000 00000000`00353000 : nt!MiLoadImageSection+0x325
fffff880`009a95c0 fffff800`030afc8d : fffff880`009a9738 00000000`00000000 fffffa80`05515b00 00000000`00000000 : nt!MmLoadSystemImage+0x4b8
fffff880`009a96e0 fffff800`031f5ad6 : fffffa80`05515be0 fffffa80`05515be0 fffffa80`05515b10 fffff8a0`0000001c : nt!IopLoadDriver+0x44d
fffff880`009a99b0 fffff800`031f6c92 : fffff800`00000000 fffff8a0`0032f4e0 ffffffff`8000012c fffff8a0`0032ffe0 : nt!IopInitializeSystemDrivers+0x1d6
fffff880`009a9a40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IoInitSystem+0x9b2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiReplenishPageSlist+100
fffff800`02cecb7f f00fba6b1000    lock bts dword ptr [rbx+10h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiReplenishPageSlist+100

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+100

BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+100

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

 

[Bradford1040]

I wanted to start my own thread but could not find how

never mind figured it out

 

[Gabriele]

thank you zigzag3143, I will try and let you know.

 

[Gabriele]

1-ASACPI.SYS a major cause of BSOD's in the 2005 rev.

The pre 2009 version of this driver is a known BSOD cause.

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it. (ASUSTeK Computer Inc. -Support- Drivers and Download Tools)
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).


2-AVG remnants. Also a known BSOD cause and not installed properly. Remove and replace with Microsoft Security essentials

AVG - Download tools

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

I correct this two points, but the BSODs reappears again. I have done the memtest on every ram and every slot and all passed the test (minimum 5 test each combination ram-slot).

Anyone has other suggestions?

 

[shadowkiller]

not a soloution, but im having a similar issue, started a new thread and its waiting moderator approval.

tried memtest, etc.. still there, and minidump file always seams to have NTOSKRNL.exe some where in it.. tried a fresh instal of win7 and its still an issue..

so frustrating and im lost as to where to go from here..

good luck with your issue,

 

[Gabriele]

here the new files and report