New
#1
Some new BSOD
The computer has been working fine for a week and today I got two BSOD's again. But this time it seems something else is wrong, because previously I had some network adapter driver issues. Thank You for help.
Some new BSOD
-
-
New #2
These two crashes were caused by memory corruption. To test your memory
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.
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\081910-28610-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Whitespace at end of path element 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.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02a10000 PsLoadedModuleList = 0xfffff800`02c4de50 Debug session time: Thu Aug 19 05:46:23.623 2010 (GMT-4) System Uptime: 0 days 0:06:02.200 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {28, 2, 0, fffff80002ac2518} Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 ) 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: 0000000000000028, 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: fffff80002ac2518, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb80e0 0000000000000028 CURRENT_IRQL: 2 FAULTING_IP: nt!MiFindNodeOrParent+0 fffff800`02ac2518 48f7412800ffffff test qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: svchost.exe TRAP_FRAME: fffff88003139580 -- (.trap 0xfffff88003139580) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002ac2518 rsp=fffff88003139718 rbp=0000000000000000 r8=fffff88003139760 r9=0000000000000000 r10=fffffa800535ed80 r11=fffffa800533c610 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc nt!MiFindNodeOrParent: fffff800`02ac2518 48f7412800ffffff test qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h ds:00000000`00000028=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a7fca9 to fffff80002a80740 STACK_TEXT: fffff880`03139438 fffff800`02a7fca9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`03139440 fffff800`02a7e920 : fffffa80`03b7c000 fffffa80`0535edc8 fffff6fd`4001dbe0 fffffa80`03957601 : nt!KiBugCheckDispatch+0x69 fffff880`03139580 fffff800`02ac2518 : fffff800`02ac62d7 fffff800`02bfae80 00000000`00000001 00000000`00000001 : nt!KiPageFault+0x260 fffff880`03139718 fffff800`02ac62d7 : fffff800`02bfae80 00000000`00000001 00000000`00000001 fffff780`c0000488 : nt!MiFindNodeOrParent fffff880`03139720 fffff800`02ac625d : 00000000`63416d4d 00000000`00000002 00000000`00000000 00000000`00001000 : nt!MiLocateAddressInTree+0x17 fffff880`03139750 fffff800`02ac6368 : 00000000`00000000 fffffa80`03efb000 fffffa80`03bbe0b8 fffffa80`0535ee38 : nt!MiGetSharedProtosAtDpcLevel+0xbd fffff880`031397a0 fffff800`02a1e1cb : fffff800`02bf6c18 fffff800`02a93c80 fffff880`03139898 fffff800`02bfae80 : nt!MiGetSharedProtos+0x18 fffff880`031397d0 fffff800`02b86890 : 30400000`5b0f6d00 fffffa80`0535edc0 fffff800`02bfae80 fffff800`02a8e574 : nt! ?? ::FNODOBFM::`string'+0x927b fffff880`03139800 fffff800`02b86a70 : fffffa80`05cac720 00000003`00000000 fffffa80`0535ed80 fffffa80`0535ee38 : nt!MiEmptyPageAccessLog+0x160 fffff880`03139870 fffff800`02b86c76 : fffffa80`03b8d000 00000000`000012ea fffff680`0001baa0 00000000`00000000 : nt!MiAllocateAccessLog+0x80 fffff880`031398a0 fffff800`02ae8628 : 00000003`00000000 aea00000`b6e6e867 00000000`00000000 00000000`000012ea : nt!MiLogPageAccess+0x46 fffff880`031398f0 fffff800`02b02a5e : fffffa80`05cacab8 fffff880`00000001 00000000`00000001 fffff880`03139b70 : nt! ?? ::FNODOBFM::`string'+0x217c6 fffff880`03139aa0 fffff800`02a94ee2 : 00000000`0000016a 00000000`00000000 fffffa80`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x496d6 fffff880`03139b40 fffff800`02a95173 : 00000000`00000008 fffff880`03139bd0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e fffff880`03139b90 fffff800`02d24c06 : fffffa80`039ec1a0 00000000`00000080 fffffa80`039cd040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3 fffff880`03139d00 fffff800`02a5ec26 : fffff800`02bfae80 fffffa80`039ec1a0 fffff800`02c08c40 7effffff`ffffffff : nt!PspSystemThreadStartup+0x5a fffff880`03139d40 00000000`00000000 : fffff880`0313a000 fffff880`03134000 fffff880`031396d0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiFindNodeOrParent+0 fffff800`02ac2518 48f7412800ffffff test qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiFindNodeOrParent+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiFindNodeOrParent+0 BUCKET_ID: X64_0xA_nt!MiFindNodeOrParent+0 Followup: MachineOwner ---------
Old drivers that need updating
Code:adfs.SYS fffff880`068e5000 fffff880`068fd000 0x00018000 0x48640195 6/26/2008 16:52:37 TFsExDisk.sys fffff880`06862000 fffff880`0686b000 0x00009000 0x48c8b767 9/11/2008 02:15:03 000.fcl fffff880`06800000 fffff880`0682b000 0x0002b000 0x48dcdf7a 9/26/2008 09:11:22 btwl2cap.sys fffff880`0bd0e000 fffff880`0bd1a000 0x0000c000 0x49d6a9bd 4/3/2009 20:28:45 spldr.sys fffff880`0144c000 fffff880`01454000 0x00008000 0x4a0858bb 5/11/2009 12:56:27 GEARAspiWDM.sys fffff880`0545b000 fffff880`05468000 0x0000d000 0x4a1151c0 5/18/2009 08:17:04 amdxata.sys fffff880`00e0b000 fffff880`00e16000 0x0000b000 0x4a12f2eb 5/19/2009 13:56:59 o2mdgx64.sys fffff880`04e00000 fffff880`04e0f400 0x0000f400 0x4a15479a 5/21/2009 08:22:50 CtClsFlt.sys fffff880`0659f000 fffff880`065c92a0 0x0002a2a0 0x4a35d6e1 6/15/2009 01:06:41 PxHlpa64.sys fffff880`011c9000 fffff880`011d4e00 0x0000be00 0x4a416253 6/23/2009 19:16:35 btwavdt.sys fffff880`078ba000 fffff880`07935000 0x0007b000 0x4a431015 6/25/2009 01:50:13 btwrchid.sys fffff880`0bd1a000 fffff880`0bd1d880 0x00003880 0x4a431069 6/25/2009 01:51:37 SynTP.sys fffff880`05401000 fffff880`0544a000 0x00049000 0x4a451503 6/26/2009 14:35:47 Acceler.sys fffff880`05468000 fffff880`05474000 0x0000c000 0x4a453602 6/26/2009 16:56:34 btwaudio.sys fffff880`07935000 fffff880`079bb000 0x00086000 0x4a4b6ab0 7/1/2009 09:54:56 BCM42RLY.sys fffff880`079f5000 fffff880`079fe000 0x00009000 0x4a53e9af 7/7/2009 20:34:55 bcmwl664.sys fffff880`04ee5000 fffff880`0518d000 0x002a8000 0x4a53ec10 7/7/2009 20:45:04
-
New #3
I've just ran the memtest You told me to and there were no errors. Do You have any other suggestions? Ok I will try updating those drivers you've mentioned.
-
New #4
In addition to Kens advice which will probably solve the problem, may I suggest that you also update this driver. It was cited in the report as a problem. It may or may not help the BSOD problem, but it may help the network problems. Give it a try and tell us what happens.
The Rt64win7.sys is a Realtek NIC driver. As Ken pointed out, asking to update drivers, this is a good practice with BSOD
-
New #5
I've had several issues with the NIC driver yeah, but I have the latest drivers for my card. Also I have one question, all the drivers that zigzag3143 mentioned, should I just google for each file to which driver it belongs or do you guys use any program that tells you specifically for which device the driver is out of date. TY.
-
-
New #7
Your dump report listed all the drivers in use during the time of the crash. The dates of 7/09 is used as the cutoff for old drivers. That is the date that MS came out with its drivers for Windows 7. Windows 7 does not play nice with old drivers and most mfg updated after that date.
The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
-
Quote