Unsolved
This post is more than 5 years old
5 Posts
0
27181
Precision M6400 memory (?) problems
Hello there, i need some urgent help.
I own a precision M6400 with the following specifications:
-----------------------------------
- Core 2 Duo 2.8GHz
- Core 2 Duo 2.8GHz
- 4Gbyte RAM, (2x2Gb)
- Nvidia 3700M 1Gb
- 2x320Gbyte WD HD (AHCI mode, no RAID)
- Vista x64 SP1 (freshly installed)
- Only DELL (updated) drivers, all installed in the right order.
- Bios revision is A03.
-----------------------------------
After a huge number of "random" BSODs in the last few days, all with different STOP messages(IRQ_NOT_LESS_OR_EQUAL, BAD_POOL, ...), i checked carefully my DDR3 RAM sticks and this is the scenario i discovered:
1) My 2 memory sticks have same size and specifications, but come from different manufacturers. They were both mounted by DELL.
2) My 2 memory sticks are mounted in A and B slot (under the keyboard) and work as dual channel.
3) When both the sticks are present they result error free when checked with memtest86+ (checked for 3 hours, 3 passes), but they fail consistently "windows memory diagnostics" tool test.
4) Each one of the 2 sticks - when individually tested - passes flawlessly both memtest86+ and "windows memory diagnostics" tool test.
5) Changing the slots in which the 2 DDR2 sticks are mounted does not help, "windows memory diagnostics" tool test still fails.
The question is: which is the clue ? Can ithe BSODs be related to the different manufacturer for the 2 sticks ? Can it be a dual channel issue ?
Also: where i should theoretically put the sticks to achieve dual channel ? It seems they worked ok in A/B slots, but the manual is not clear about it and leaded me to suppose that maybe the right slots are A/D and B/C ?
I think the problem i memory related, since i tested CPU cache many times with different stress applications and the CPU itself passes many hours of SuperPI calculations.
1) My 2 memory sticks have same size and specifications, but come from different manufacturers. They were both mounted by DELL.
2) My 2 memory sticks are mounted in A and B slot (under the keyboard) and work as dual channel.
3) When both the sticks are present they result error free when checked with memtest86+ (checked for 3 hours, 3 passes), but they fail consistently "windows memory diagnostics" tool test.
4) Each one of the 2 sticks - when individually tested - passes flawlessly both memtest86+ and "windows memory diagnostics" tool test.
5) Changing the slots in which the 2 DDR2 sticks are mounted does not help, "windows memory diagnostics" tool test still fails.
The question is: which is the clue ? Can ithe BSODs be related to the different manufacturer for the 2 sticks ? Can it be a dual channel issue ?
Also: where i should theoretically put the sticks to achieve dual channel ? It seems they worked ok in A/B slots, but the manual is not clear about it and leaded me to suppose that maybe the right slots are A/D and B/C ?
I think the problem i memory related, since i tested CPU cache many times with different stress applications and the CPU itself passes many hours of SuperPI calculations.
Can the problem be motherboard / memory controller related?
Please give me any advices.
ejn63
9 Legend
9 Legend
•
87.5K Posts
0
April 26th, 2009 04:00
That error is commonly caused by a failing hard drive. Power on, press F12, load the Dell diagnostics and run the extended - NOT just the quick - hard drive tests. Record any errors.
fabrizioT
5 Posts
0
April 26th, 2009 08:00
Hi ejn63,
when you say "That error" are you referring to what ? maybe to some specific STOP messages ? If so, which one ? Let me understand please.
However, I checked both my internal hard disks through DELL diagnostics and they are both fine.
Let me add that i installed Vista x64 ALSO on a LACIE eSata disk and it's afflicted by the same kind of random BSODs as the internal disk Vista install.
ejn63
9 Legend
9 Legend
•
87.5K Posts
0
April 26th, 2009 08:00
These errors:
"(IRQ_NOT_LESS_OR_EQUAL, BAD_POOL, ...)"
are almost always faulty hard drive errors.
what happens if you DISCONNECT the eSATA drive?
fabrizioT
5 Posts
0
April 26th, 2009 09:00
Hi again, thanks for your kind support.
Most of the BSODs happened when eSATA was NOT plugged in, so the problem can't be considered strictly related to eSATA itself..
Here is the raw winDBG output for a "IRQL_NOT_LESS_OR_EQUAL" error minidump, maybe it can help ?
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 1, fffff80001e7fd5b}
Probably caused by : memory_corruption ( nt!MiComputeFlushRange+2bb )
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: 0000000000000000, 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: fffff80001e7fd5b, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002043080
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiComputeFlushRange+2bb
fffff800`01e7fd5b 488908 mov qword ptr [rax],rcx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffffa6002470840 -- (.trap 0xfffffa6002470840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80097c5988
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001e7fd5b rsp=fffffa60024709d0 rbp=0000000000000000
r8=0000000000001000 r9=fffff8801558a800 r10=0000000000000002
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
nt!MiComputeFlushRange+0x2bb:
fffff800`01e7fd5b 488908 mov qword ptr [rax],rcx ds:0002:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80001e6ad2e to fffff80001e6af90
STACK_TEXT:
fffffa60`024706f8 fffff800`01e6ad2e : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffffa60`02470700 fffff800`01e69c0b : 00000000`00000001 00000000`00000000 00000000`00000000 fffffa80`0b5a8910 : nt!KiBugCheckDispatch+0x6e
fffffa60`02470840 fffff800`01e7fd5b : 00000000`00000000 fffffa60`024709f8 00000000`00000001 00000000`00000007 : nt!KiPageFault+0x20b
fffffa60`024709d0 fffff800`01e7ca0a : 00000000`00000000 fffffa80`0a64f010 00000000`00001000 fffffa60`02470ca0 : nt!MiComputeFlushRange+0x2bb
fffffa60`02470a30 fffff800`01e805a9 : fffffa80`00000001 00000000`00000000 00000000`00000000 fffffa80`063fe040 : nt!MmFlushSection+0x3a
fffffa60`02470af0 fffff800`01e84070 : fffffa80`049495e0 00000000`00000000 00000000`00000001 fffffa60`02470ca0 : nt!CcFlushCache+0x65a
fffffa60`02470be0 fffff800`01e84bbb : 00000000`00000000 00000000`00000000 fffff880`00000000 fffffa60`02470d00 : nt!CcWriteBehind+0x1c0
fffffa60`02470c70 fffff800`01e77c46 : fffffa80`036bb2f0 fffff800`020188a0 fffffa80`08a61960 fffffa80`00000001 : nt!CcWorkerThread+0x17b
fffffa60`02470cf0 fffff800`0208f5bf : fffffa80`036bb2f0 fffffffe`9a5f4400 fffffa80`063fe040 00000000`00000080 : nt!ExpWorkerThread+0x11a
fffffa60`02470d50 fffff800`01ea63e6 : fffff800`01f8e680 fffffa80`063fe040 fffffa80`06460720 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`02470d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiComputeFlushRange+2bb
fffff800`01e7fd5b 488908 mov qword ptr [rax],rcx
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiComputeFlushRange+2bb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49ac93f5
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MiComputeFlushRange+2bb
BUCKET_ID: X64_0xA_nt!MiComputeFlushRange+2bb
Followup: MachineOwner
---------
fabrizioT
5 Posts
0
April 26th, 2009 14:00
The following is the crash info for the BSOD i have just had :(
This time it's a NTFS.SYS error; eSata was plugged.
Definetely need some help here ...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa8108557ab0, 0, fffffa60014c7b2d, 5}
Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+2dd )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8108557ab0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffffa60014c7b2d, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000203d080
fffffa8108557ab0
FAULTING_IP:
Ntfs!NtfsDeleteScb+2dd
fffffa60`014c7b2d 488b4120 mov rax,qword ptr [rcx+20h]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffffa6001d9d860 -- (.trap 0xfffffa6001d9d860)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88009e2dbd0 rbx=0000000000000000 rcx=fffffa8108557a90
rdx=fffffa8008558010 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa60014c7b2d rsp=fffffa6001d9d9f0 rbp=fffffa8002931180
r8=0000000000000000 r9=0000000000000000 r10=fffff88009e2daa0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
Ntfs!NtfsDeleteScb+0x2dd:
fffffa60`014c7b2d 488b4120 mov rax,qword ptr [rcx+20h] ds:03ab:fffffa81`08557ab0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80001e730d0 to fffff80001e64f90
STACK_TEXT:
fffffa60`01d9d768 fffff800`01e730d0 : 00000000`00000050 fffffa81`08557ab0 00000000`00000000 fffffa60`01d9d860 : nt!KeBugCheckEx
fffffa60`01d9d770 fffff800`01e63b19 : 00000000`00000000 fffffa60`00b4b6e2 fffffa80`01818000 fffffa60`01d9da88 : nt!MmAccessFault+0x4f0
fffffa60`01d9d860 fffffa60`014c7b2d : fffff880`099c3701 fffffa60`01d9da88 00000000`01010000 fffffa60`01d9da88 : nt!KiPageFault+0x119
fffffa60`01d9d9f0 fffffa60`01417579 : fffff880`09e2daa0 fffff880`09e2da01 00000000`00000000 00000000`0000001c : Ntfs!NtfsDeleteScb+0x2dd
fffffa60`01d9da30 fffffa60`014c768b : fffff880`09e2daa0 fffff880`09e2dbd0 fffff880`09e2da00 00000000`00000000 : Ntfs!NtfsPrepareFcbForRemoval+0x89
fffffa60`01d9da80 fffffa60`0141eb92 : fffffa80`042bcd20 fffffa60`01d9dc70 fffff880`09e2ded8 fffff880`09e2daa0 : Ntfs!NtfsTeardownStructures+0x8b
fffffa60`01d9db10 fffffa60`014d2e18 : fffffa60`01d9dc70 fffff800`01fa68a0 fffff880`09e2daa0 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffffa60`01d9db50 fffffa60`014bbe0e : fffffa80`042bcd20 fffff880`09e2dbd0 fffff880`09e2daa0 fffffa80`02931180 : Ntfs!NtfsCommonClose+0x348
fffffa60`01d9dc20 fffff800`01e71c46 : 00000000`00000000 fffff800`02012800 fffffa80`07ca5001 fffffa80`00000003 : Ntfs!NtfsFspClose+0x15e
fffffa60`01d9dcf0 fffff800`020895bf : fffffa60`0146cee8 e80c75ff`50f8458d fffffa80`01877720 00000000`00000080 : nt!ExpWorkerThread+0x11a
fffffa60`01d9dd50 fffff800`01ea03e6 : fffffa60`005ec180 fffffa80`01877720 fffffa60`005f5d40 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`01d9dd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
Ntfs!NtfsDeleteScb+2dd
fffffa60`014c7b2d 488b4120 mov rax,qword ptr [rcx+20h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: Ntfs!NtfsDeleteScb+2dd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 479190d1
FAILURE_BUCKET_ID: X64_0x50_Ntfs!NtfsDeleteScb+2dd
BUCKET_ID: X64_0x50_Ntfs!NtfsDeleteScb+2dd
Followup: MachineOwner
---------
ejn63
9 Legend
9 Legend
•
87.5K Posts
0
April 26th, 2009 15:00
When the pair is installed, does the failure occur in just one module (one socket), or in both of them? And when you swapped the modules, did the error follow the module, or occur in the original socket?
fabrizioT
5 Posts
0
April 27th, 2009 07:00
Like i said before, memtest86+ did not found any RAM errors running for about 3 hours with both the sticks inserted, nor with any single one (i swapped the sockets too). On the contrary Vista "memory diagnostic tool" raised errors (rather useless because generic), but only with both the sticks inserted.
So, at least till this morning, i thought my ram sticks could be fine, but maybe incompatible, since each one seemed to be ok when tested individually with both the tools ...
I was surprised then, because after having run memtest86+ overnight on a single RAM stick, i finally found it faulty.
It failed test 8 on pass 17(!) after roughly about 8hours of memory stress.
I've got only that single fail in a 26 passes session. Obviously i've repeated the memtest86+ session, narrowing the boundaries and finally having the memory issue confirmed.
Now i am thoroughly testing the same way the second ram stick.
So far it completed 27 passes without errors.
That will probably exclude both any problem with the stick itself and any hypothethical issue for the L2 cache of the CPU.
Hope to get this mess finally sorted ...