its me again... (my last thread)
https://www.sevenforums.com/crashes-d...ml#post1024767
and another BSOD, this time i just booted w7 and let it alone ( idle) in the desktop 3 minutes and BAM, this time it doesnt make a reference to the NTFS file, ( hal.dll) im sending the new dumps, HELP!
These were caused by memory corruption. Please run memtest
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.
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\102010-20607-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
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e07000 PsLoadedModuleList = 0xfffff800`03044e50
Debug session time: Wed Oct 20 23:08:49.599 2010 (GMT-4)
System Uptime: 0 days 0:02:43.410
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
.............................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002f7ddac, fffff880031396a8, fffff88003138f00}
Probably caused by : memory_corruption ( nt!MiLogPageAccess+1fc )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002f7ddac, The address that the exception occurred at
Arg3: fffff880031396a8, Exception Record Address
Arg4: fffff88003138f00, Context Record Address
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!MiLogPageAccess+1fc
fffff800`02f7ddac 488901 mov qword ptr [rcx],rax
EXCEPTION_RECORD: fffff880031396a8 -- (.exr 0xfffff880031396a8)
ExceptionAddress: fffff80002f7ddac (nt!MiLogPageAccess+0x00000000000001fc)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88003138f00 -- (.cxr 0xfffff88003138f00)
rax=f683fffffd500000 rbx=fffffa8008eb4000 rcx=00fffa8008eb4220
rdx=fffff683fffffd50 rsi=00000000000002e6 rdi=fffb41fffffea800
rip=fffff80002f7ddac rsp=fffff880031398e0 rbp=0000000000000000
r8=0000000000000001 r9=fffffa8008e903f8 r10=0000000000000005
r11=0000000000000000 r12=000000000000034e r13=fffff70001080488
r14=fffff80002fedc10 r15=fffffa8007137240
iopl=0 nv up ei ng nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287
nt!MiLogPageAccess+0x1fc:
fffff800`02f7ddac 488901 mov qword ptr [rcx],rax ds:002b:00fffa80`08eb4220=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030af0e0
ffffffffffffffff
FOLLOWUP_IP:
nt!MiLogPageAccess+1fc
fffff800`02f7ddac 488901 mov qword ptr [rcx],rax
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff80002ee11d8 to fffff80002f7ddac
STACK_TEXT:
fffff880`031398e0 fffff800`02ee11d8 : 00000003`00000000 2e600002`5bd0c867 00000000`00000000 00000000`000002e6 : nt!MiLogPageAccess+0x1fc
fffff880`03139930 fffff800`02ef9a0e : fffffa80`08e903f8 fffff880`00000001 00000000`00000001 fffff880`03139bb0 : nt! ?? ::FNODOBFM::`string'+0x21846
fffff880`03139ae0 fffff800`02e8d6e2 : 00000000`000000a4 00000000`00000000 fffffa80`00000000 00000000`00000007 : nt! ?? ::FNODOBFM::`string'+0x49926
fffff880`03139b80 fffff800`02e8d96f : 00000000`00000008 fffff880`03139c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03139bd0 fffff800`0311c166 : fffffa80`0792e040 00000000`00000080 fffffa80`0790f040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03139d40 fffff800`02e57486 : fffff800`02ff1e80 fffffa80`0792e040 fffff800`02fffc40 203d501c`fdb4eed2 : nt!PspSystemThreadStartup+0x5a
fffff880`03139d80 00000000`00000000 : fffff880`0313a000 fffff880`03134000 fffff880`03139710 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiLogPageAccess+1fc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
STACK_COMMAND: .cxr 0xfffff88003138f00 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x7E_nt!MiLogPageAccess+1fc
BUCKET_ID: X64_0x7E_nt!MiLogPageAccess+1fc
Followup: MachineOwner
---------
Plus update 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
Old drivers
Code:
AsIO.sys fffff880`03b72000 644d65f3`03b78000 0x644d6d7300006000 0x416e4c91 10/14/2004 05:53:21
ADIHdAud.sys fffff880`0493f000 644d65f3`049a9000 0x644d6d730006a000 0x4612c785 4/3/2007 17:30:45
Quote