when you get your new ram if you still get the same errors and bsod then you can start thinking you may have a mobo problem
always try to buy listed ram if you can , it's another small guarantee in an unsure world
There is no reason why you shouldn't run 2x2gig ram, but buy it all at the same time from the same firm, as the cost of metals change so components get built to different tolerances and ram can vary
I'm buying a package of 2x2 so it's not a problem.when you get your new ram if you still get the same errors and bsod then you can start thinking you may have a mobo problem
always try to buy listed ram if you can , it's another small guarantee in an unsure world
There is no reason why you shouldn't run 2x2gig ram, but buy it all at the same time from the same firm, as the cost of metals change so components get built to different tolerances and ram can vary
However, this is 1600mhz ram, I want to run in in 1066, is it a problem ?
Thanks.
Here is also my dump file for this morning BSOD...IRQ_Not less than equal...what is that ?
I'm buying a package of 2x2 so it's not a problem.when you get your new ram if you still get the same errors and bsod then you can start thinking you may have a mobo problem
always try to buy listed ram if you can , it's another small guarantee in an unsure world
There is no reason why you shouldn't run 2x2gig ram, but buy it all at the same time from the same firm, as the cost of metals change so components get built to different tolerances and ram can vary
However, this is 1600mhz ram, I want to run in in 1066, is it a problem ?
Thanks.
Here is also my dump file for this morning BSOD...IRQ_Not less than equal...what is that ?
Hi
As before Memory corruption
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\012110-14539-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\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 Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a68000 PsLoadedModuleList = 0xfffff800`02ca5e50 Debug session time: Thu Jan 21 10:36:58.572 2010 (GMT-5) System Uptime: 0 days 0:06:42.601 Loading Kernel Symbols ............................................................... ................................................................ .............. Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffff68000106570, 0, 0, fffff80002aedae2} Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1c2 ) Followup: MachineOwner --------- 2: 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: fffff68000106570, memory referenced Arg2: 0000000000000000, 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: fffff80002aedae2, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d100e0 fffff68000106570 CURRENT_IRQL: 0 FAULTING_IP: nt!MiAgeWorkingSet+1c2 fffff800`02aedae2 488b19 mov rbx,qword ptr [rcx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: SearchIndexer. TRAP_FRAME: fffff880033167a0 -- (.trap 0xfffff880033167a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff68000106570 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002aedae2 rsp=fffff88003316930 rbp=0000000000106570 r8=0000000000000001 r9=fffffa800685d958 r10=0000000000000005 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe cy nt!MiAgeWorkingSet+0x1c2: fffff800`02aedae2 488b19 mov rbx,qword ptr [rcx] ds:fffff680`00106570=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ad9469 to fffff80002ad9f00 STACK_TEXT: fffff880`03316658 fffff800`02ad9469 : 00000000`0000000a fffff680`00106570 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx fffff880`03316660 fffff800`02ad80e0 : 00000000`00000000 00000980`00000000 00000000`00001000 fffff800`02c0cbfe : nt!KiBugCheckDispatch+0x69 fffff880`033167a0 fffff800`02aedae2 : 00000003`00000000 4e000000`ae04e867 00000000`00000000 00000000`00000ce0 : nt!KiPageFault+0x260 fffff880`03316930 fffff800`02b5aa0e : fffffa80`0685d958 fffff880`00000001 00000000`00000001 fffff880`03316bb0 : nt!MiAgeWorkingSet+0x1c2 fffff880`03316ae0 fffff800`02aee6e2 : 00000000`00000193 00000000`00000000 fffffa80`00000000 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x49926 fffff880`03316b80 fffff800`02aee96f : 00000000`00000008 fffff880`03316c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e fffff880`03316bd0 fffff800`02d7d166 : fffffa80`039ecb60 00000000`00000080 fffffa80`0396d9e0 00000000`00000001 : nt!KeBalanceSetManager+0x1c3 fffff880`03316d40 fffff800`02ab8486 : fffff880`02f63180 fffffa80`039ecb60 fffff880`02f6dfc0 00200008`80000000 : nt!PspSystemThreadStartup+0x5a fffff880`03316d80 00000000`00000000 : fffff880`03317000 fffff880`03311000 fffff880`03316710 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiAgeWorkingSet+1c2 fffff800`02aedae2 488b19 mov rbx,qword ptr [rcx] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiAgeWorkingSet+1c2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiAgeWorkingSet+1c2 BUCKET_ID: X64_0xA_nt!MiAgeWorkingSet+1c2 Followup: MachineOwner ---------
This mean my memory is faulty I guess. I'm in process of RMA. I'm also buying new QVL ram.
can someone just confirm again that using memory that is downclocked is not a problem ?
I got that. Thanks.
Pretty sure it isnt a problem. As soon as I get my QVL ram, I will format, clean install, and if you see another post from me with an attached files, I will be probably crying.
lol
Still, now I have a pretty good idea what to do. And it is all because of you guys.
I know it's probably my ram, it's a kind of relief in a certain way. I just hope my Mobo is not in fault. If it's the case, I'm gonna throw it away, and I'll bring back my mobo with my old OCZ ram, 3 years old ram that never had a single problem and I'll buy a whole new system in december.
It's been a pain in the ass from the beginning. Hopefully new ram will mean problem solved.
Thanks again to everyone, and sorry for always disturbing you with my many questions.
i know people will want to lynch me for saying this but get something besides an Asus board their boards aren't that great
In december 2006, I bought a P5W DH deluxe by asus. it costed me 300$ back then.
It's the best motherboard I ever owned. I did many upgrade on it and it would take everything I thrown at it.
Never had a single blue screen in 3 years of heavy use.
Of course, it's more than the double I paid for the one I hve now...I guess it make a difference.
Next time I,ll throw in 100$ more for the mobo and I'll make sure I have a premium or a deluxe one if I buy from asus.
Still, I think my ram is faulty and I also think my Mobo dot no like that ram, even if it was not faulty.
I'm buying QVL ram in 2 days, when I receive it I'll send back the RMA one. (newegg gave me until february 20th for them to receive it) So I'm less in a panic now, this mean I wont spend 2 weeks without a computer.
I'm just afraid there is a chance my mobo is faulty and that I'll have to replace it thought. (let's hope not, some computers geek at my job told me it is unlikely that my mobo is faulty in my situation I described them)
My friends will bring some generic ddr3 ram this week end we will test it on it.
But I'm afraid my Mobo wont like it and I think I might get memtest error. Is it possible in this situation that memtest86+ 4.0 detect error but that the cause is the mobo not liking the ram ???
Wich mobo you would suggest me for my Q6600 and some ddr3 ?
I know socket 775 is disapearing...but my q6600 still rock even in heavy gaming so I do not want to change it for now.
depends on your budget
Quote