BSOD

Help

Tattooz said:

Help

Hi T and welcome


Memory corruption caused by your 2005 asacpi.sys


I would update it
ASACPI.sys Sun Mar 27 22:30:36 2005

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
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 8th item down).
Download and install it.
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).

ALSO

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. 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.


Ken

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\080110-20373-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a5a000 PsLoadedModuleList = 0xfffff800`02c97e50
Debug session time: Sun Aug  1 00:58:29.983 2010 (GMT-4)
System Uptime: 0 days 4:15:10.575
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 5b7ac, 2, 26915}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000005b7ac, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0000000000026915, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002b5a2bc to fffff80002aca600

STACK_TEXT:  
fffff880`02f167f8 fffff800`02b5a2bc : 00000000`0000004e 00000000`00000099 00000000`0005b7ac 00000000`00000002 : nt!KeBugCheckEx
fffff880`02f16800 fffff800`02a7a4fd : ffffffff`ffffffff 00000000`00000001 ffffffff`ffffffff 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`02f16840 fffff800`02bd12ba : fffffa80`039a93f8 fffff880`02f16a50 00000000`00000000 fffffa80`0000000a : nt! ?? ::FNODOBFM::`string'+0x20443
fffff880`02f16a30 fffff800`02b4c852 : fffffa80`015c17e0 fffff880`00000001 00000000`00000000 fffff880`02f16bb0 : nt!MiEmptyWorkingSet+0x24a
fffff880`02f16ae0 fffff800`02adede2 : 00000000`00002fc3 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x49594
fffff880`02f16b80 fffff800`02adefe4 : 00000000`00000008 fffff880`02f16c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`02f16bd0 fffff800`02d6fa86 : fffffa80`015c17e0 00000000`00000080 fffffa80`015a36f0 00000000`00000001 : nt!KeBalanceSetManager+0x138
fffff880`02f16d40 fffff800`02aa8b06 : fffff800`02c44e80 fffffa80`015c17e0 fffff800`02c52c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f16d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02b5a2bc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

Ok I updated the drivers and for a couple days I did not get any bsod. Then I think there were 2 or 3 in one day after that. My brother suggested to me to move my memory stick to the second slot and again for a couple days I did not get bsod. But have gotten some since then as well. I have run memtest with my stick in slot 1 and slot 2. After 6 passes in each slot it showed no errors. So the blue screens seem to be less frequent but I am still getting them.

Does anyone have any additional advice for me? I am still getting blue screens.