sorry another bsod while installing win update sp 4
i reformated the hd and installed a fresh win 7 64 bit
Memory corruption caused by ASACPI.sys (2005) and really old drivers.
First
ASACPI.sys Sun Mar 27 22:30:36 2005
[quote]
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).[/quote
Then
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.
Next
Update the video drivers to current
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper
When it is removed then download and install the fresh copy.
Finally update the rest of the old drivers
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
Code:
nvm62x64.sys fffff880`040cc000 fffff880`0412fd80 0x00063d80 0x48f8fd12 10/17/2008 17:01:06
spldr.sys fffff880`015bb000 fffff880`015c3000 0x00008000 0x4a0858bb 5/11/2009 12:56:27
spsys.sys fffff880`038c7000 fffff880`03938000 0x00071000 0x4a085e7a 5/11/2009 13:20:58
nvlddmkm.sys fffff880`046b6000 fffff880`051bdb00 0x00b07b00 0x4a0c8387 5/14/2009 16:48:07
amdxata.sys fffff880`00e4d000 fffff880`00e58000 0x0000b000 0x4a12f2eb 5/19/2009 13:56:59
DMP
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\101110-21434-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0285e000 PsLoadedModuleList = 0xfffff800`02a9be50
Debug session time: Tue Oct 12 02:07:03.571 2010 (GMT-4)
System Uptime: 0 days 0:06:47.350
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800028ffba5, fffff880079c1090, 0}
Probably caused by : memory_corruption ( nt!MiRemoveNode+215 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800028ffba5, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880079c1090, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!MiRemoveNode+215
fffff800`028ffba5 488b01 mov rax,qword ptr [rcx]
CONTEXT: fffff880079c1090 -- (.cxr 0xfffff880079c1090)
rax=00ff000000000000 rbx=fffffa80041da990 rcx=00ff000000000000
rdx=fffffa80041ed401 rsi=fffffa8003857120 rdi=fffffa8003efc060
rip=fffff800028ffba5 rsp=fffff880079c1a60 rbp=fffffa80041ed4a8
r8=fffffa8003ef00d0 r9=fffff80002a5ca80 r10=0000000000000001
r11=00000000000006e3 r12=fffffa8003857120 r13=0000000000240000
r14=0000000000240fff r15=0000000000000001
iopl=0 nv up ei ng nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010283
nt!MiRemoveNode+0x215:
fffff800`028ffba5 488b01 mov rax,qword ptr [rcx] ds:002b:00ff0000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: mscorsvw.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800028a17a7 to fffff800028ffba5
STACK_TEXT:
fffff880`079c1a60 fffff800`028a17a7 : ffffffff`ffffffff 00000000`00000001 fffffa80`041ed060 fffffa80`03efc060 : nt!MiRemoveNode+0x215
fffff880`079c1a90 fffff800`02bb3dcf : fffff8a0`08e4ea70 00000000`00000001 00000000`00000000 fffffa80`03efc060 : nt!MmCleanProcessAddressSpace+0x1b3
fffff880`079c1ae0 fffff800`02b8b85b : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`079c1ba0 fffff800`028cd993 : fffffa80`041ed060 000007fe`00000000 00000000`00323c01 fffffa80`03efc060 : nt!NtTerminateProcess+0x25b
fffff880`079c1c20 00000000`7712001a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001ef608 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7712001a
FOLLOWUP_IP:
nt!MiRemoveNode+215
fffff800`028ffba5 488b01 mov rax,qword ptr [rcx]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiRemoveNode+215
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
STACK_COMMAND: .cxr 0xfffff880079c1090 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x3B_nt!MiRemoveNode+215
BUCKET_ID: X64_0x3B_nt!MiRemoveNode+215
Followup: MachineOwner
---------