Muliple BSOD's, Stalls, failure to boot etc etc and I am now desperate

Dave76 · 16 Jan 2012

Since you have a new PSU install it so you can see if that is the cause.
When you have crashes indicating all the electrical components, as you are, so far you have possible causes as CPU, RAM, Graphics card, hard drive.
This does point to a PSU issue.

If, after the PSU is installed, you are still having crashes, then I would suggest the RAM might be suspect.
You can get 1600MHz RAM and run it at 1333MHz, it will be more stable at the lower frequency. You might be able to adjust settings to get it to run at 1600MHz. This will take a lot of testing and can not be guaranteed to work.

Be sure to get RAM listed on your motherboard site or listed on the RAM site as compatible with your motherboard.
Stay away from RAM that says it is compatible with Intel and AMD, as they tend to be more stable on Intel systems than AMD
systems.
M4A87TD/USB3 Memory QVL: Qualified Vendors List, select Memory QVL.

Let us know the results from the new PSU.

Racehunter · 16 Jan 2012

New Antec 750W Truepower (New) PSU fitted today at 11:00 UK time. Booted up correctly and did not fault even when I tried to 'confuse' the system by multy tasking straight from the off. Since then I have left it running Prime95 torture test just to see, and so far, so good. Early days I know, but as I had said previously, a critical time for BSOD'd was straight after booting up and when switching quickly between programs/files/etc.

As a precaution I have ordered new RAM, and that was not the easy job I thought it would be! My motherboard may only be 12 months old, but finding any listed on the QVL that is still available was impossible. I had just as much difficulty with RAM manufacturers sites, finding the M4A87TD/USB3 even listed. In the end I settled for Kingston Hyper-X KHX1600C9D3K2/8G. Hope I haven't made a mistake..........

I will keep you informed as to the operation of the PC and really hope the problem has been found.

Layback Bear · 16 Jan 2012

Just make sure you ram is set no higher than the motherboard specs. I have used Kingston ram for years with no problems. Come back and let us know how things are going.

Dave76 · 17 Jan 2012

Good news.

Glad to hear it seems to be better, even if just initially.

Let us know if you get another crash, and especially if you don't.

Can't find any info on their website about compatibility, some RAM manufacturers have easy access to information and some don't.
Makes me a bit nervous when you can't get information...

Racehunter · 19 Jan 2012

Dave,

I went to the Kingston .com, clicked on Memory (top right), then selected Desktop/Notebook. In the drop down menu titled Find the right memory, I selected Asus/ASmobile as manufacturer, M4 motherboard as Product Line, which allowed me to select my board (M4A87TD/USB3) From the memory offered I selected what I later purchased. I hope this is OK?

Mind you, I am still having problems. The last time I posted I had installed the PSU but later that evening, after a restart, it crashed and again when booting the following morning. By chance the memory arrived in the mail that morning (18th) so I fitted it and set the RAM frequency at 1333Ghz. It has stalled a couple of times since and properly crashed twice, so I am still losing the battle.

The mini dump file is attached. Looks like major component swapping (and cost) now!

Dave76 · 21 Jan 2012

Sorry to hear that.

I went to the same site, most other RAM sites list the motherboards that their RAM is compatible with, when they list a lot of Intel boards and a couple of AMD boards it usually turns out that the RAM may have problems on an AMD board.

Your method of finding the RAM is correct.
It appears that the last letter in the part number indicates if it is for AMD, the X at the end is for Intel, so you have the right one according to their memory finder.

Latest crash: STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel

The Driver Verifier enabled crash blames MsMpEng.exe which is a core process of Microsoft Security Essentials.
This is likely the result and not the cause of the crash.
The cause is hardware - RAM.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008887, The subtype of the bugcheck.
Arg2: fffffa8005bcd490
Arg3: fffffa8005a75030
Arg4: 0000000000000500

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_8887

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  2

STACK_TEXT:  
fffff880`039633d8 fffff800`02e25556 : 00000000`0000001a 00000000`00008887 fffffa80`05bcd490 fffffa80`05a75030 : nt!KeBugCheckEx
fffff880`039633e0 fffff800`02ec1deb : 7ff00000`00000000 fffff8a0`00293028 fffffa80`00000001 7ff00000`00000000 : nt! ?? ::FNODOBFM::`string'+0x117e6
fffff880`03963470 fffff800`02eaf695 : 00000000`00000000 00000001`e99c38c0 fffffa80`05bd0460 fffff800`030c6ac0 : nt!MiResolveTransitionFault+0x16b
fffff880`03963500 fffff800`02eae053 : f8a00029`30280400 fffff980`02103000 fffff6fc`c0010818 fffff800`030c6ac0 : nt!MiResolveProtoPteFault+0x325
fffff880`03963590 fffff800`02e9e9db : fffffa80`09abc000 fffff880`03963a18 fffff880`03963740 fffff800`02e8ee7d : nt!MiDispatchFault+0x1c3
fffff880`039636a0 fffff800`02e8ed6e : 00000000`00000000 fffff980`02103000 fffffa80`09c1ba00 00000000`0000000e : nt!MmAccessFault+0xe1b
fffff880`03963800 fffff800`0318d687 : fffff8a0`00000001 00000000`00003000 fffff880`03963a58 fffff880`03963a50 : nt!KiPageFault+0x16e
fffff880`03963990 fffff880`012f8c85 : fffffa80`0003d000 fffffa80`069cc5a0 fffff8a0`00010000 fffff8a0`0000000e : nt!CcMapData+0x117
fffff880`03963a50 fffff880`012e216d : fffff8a0`022d1ec0 00000000`00000003 fffff8a0`023acdf0 fffff8a0`0039cbc0 : Ntfs!FindFirstIndexEntry+0x1fa
fffff880`03963ae0 fffff880`012e09ce : fffffa80`09c1ba40 fffff8a0`023acdf0 fffff8a0`0039cbc0 fffffa80`09c1ba40 : Ntfs!NtfsRestartIndexEnumeration+0xed
fffff880`03963d00 fffff880`012e1ff1 : 00000000`00000000 00000000`00000008 fffffa80`083fbc90 fffffa80`08f48c10 : Ntfs!NtfsQueryDirectory+0x94e
fffff880`039640a0 fffff880`012e48ef : fffffa80`09c1ba40 00000000`00000000 00000000`00000002 00000000`00000000 : Ntfs!NtfsCommonDirectoryControl+0xa1
fffff880`039640e0 fffff800`03336c16 : fffffa80`08f48c10 fffffa80`08f48c10 fffffa80`09c1ba40 fffff880`03964108 : Ntfs!NtfsFsdDirectoryControl+0x10f
fffff880`03964150 fffff880`010b8bcf : fffffa80`08f48fb0 fffff880`03964200 fffffa80`09e55010 fffffa80`093180c0 : nt!IovCallDriver+0x566
fffff880`039641b0 fffff880`010bbaea : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`09e55010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`03964240 fffff880`010d9978 : fffffa80`08994bc0 00000000`00000022 fffffa80`0856d010 fffffa80`09e550c0 : fltmgr!FltPerformSynchronousIo+0x2ca
fffff880`039642e0 fffff880`019d2d71 : 00000000`00000000 00000000`00000020 fffff880`039643a0 fffff880`03964430 : fltmgr!FltQueryDirectoryFile+0x98
fffff880`03964320 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : luafv!LuafvNormalizeNameComponentEx+0x145


STACK_COMMAND:  kb

SYMBOL_NAME:  ZEROED_PAGE_CORRUPTED

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware_ram

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x1a_8887_VRF_ZEROED_PAGE_CORRUPTED

BUCKET_ID:  X64_0x1a_8887_VRF_ZEROED_PAGE_CORRUPTED

Followup: MachineOwner
---------

First crash with the new RAM: STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
The Driver Verifier enabled crash blames ipoint.exe which is a Microsoft IntelliMouse driver.
The cause again points to RAM, memory corruption.

Code:

*******************************************************************************
*                                                                             *
*                        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: fffff8a001f17000, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8000319409a, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003104100
 fffff8a001f17000 

FAULTING_IP: 
nt!MiCompressRelocations+23f
fffff800`0319409a 8802            mov     byte ptr [rdx],al

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x50

PROCESS_NAME:  ipoint.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009ea75e0 -- (.trap 0xfffff88009ea75e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000001f7 rbx=0000000000000000 rcx=000000000000fb9e
rdx=fffff8a001f17000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000319409a rsp=fffff88009ea7770 rbp=fffff8a001eb4000
 r8=fffff8a001eb4bac  r9=0000000000000d02 r10=000000000021f591
r11=fffff8a001ebdbc8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe nc
nt!MiCompressRelocations+0x23f:
fffff800`0319409a 8802            mov     byte ptr [rdx],al ds:8000:fffff8a0`01f17000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e7d9fc to fffff80002ed1c40

STACK_TEXT:  
fffff880`09ea7478 fffff800`02e7d9fc : 00000000`00000050 fffff8a0`01f17000 00000000`00000001 fffff880`09ea75e0 : nt!KeBugCheckEx
fffff880`09ea7480 fffff800`02ecfd6e : 00000000`00000001 fffff8a0`01f17000 fffff8a0`01e00000 00000000`00000006 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`09ea75e0 fffff800`0319409a : fffffa80`0727b7c0 00000000`00000003 00000000`00000010 fffff800`03193e60 : nt!KiPageFault+0x16e
fffff880`09ea7770 fffff800`03192d84 : 00000000`000a9a88 00000000`00000080 00000000`00000001 00000000`00000004 : nt!MiCompressRelocations+0x23f
fffff880`09ea77c0 fffff800`031cefdc : fffff8a0`01d92000 fffff880`09ea79b8 00000000`0000014d 00000000`00000000 : nt!MiRelocateImage+0x6f4
fffff880`09ea7930 fffff800`031ad596 : fffff880`09ea7b80 fffff880`09ea7ca0 00000000`00000000 00000000`00000001 : nt!MmCreateSection+0x8bc
fffff880`09ea7b30 fffff800`02ed0ed3 : fffffa80`071df7a0 00000000`0014a678 fffff880`09ea7bc8 00000000`0014a908 : nt!NtCreateSection+0x171
fffff880`09ea7bb0 00000000`77b517ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0014a658 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b517ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiCompressRelocations+23f
fffff800`0319409a 8802            mov     byte ptr [rdx],al

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiCompressRelocations+23f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_VRF_nt!MiCompressRelocations+23f

BUCKET_ID:  X64_0x50_VRF_nt!MiCompressRelocations+23f

Followup: MachineOwner
---------

First, post a snip of the CPU, Mainboard, Memory, and SPD tabs.

Run memtest86+ for a full 7 passes, best to run overnight, with both RAM cards installed.
RAM - Test with Memtest86+
Let us know the results.

Dave76 · 22 Jan 2012

Check the above post for additional information.

Disable driver verifier.

To Turn Driver Verifier OFF

• Select 3rd option on the 1st Driver Verifier screen – “Delete existing settings”

• Bring up an elevated administrative cmd/DOS screen - - type verifier /reset

Racehunter · 06 Feb 2012

Well, before I had read the bottom of the previous post with additional information (requiring me to post a snip af various tabs etc) I contacted Asus and told them of the problems and what tests had been done. They said it sounded like the Mobo and I duly returned it for testing through my supplier. I have just had an email that states 'No Fault Found' which basically means that once again, I am no closer to a solution

I am going to arrange for the board to be shipped back and should have it in a couple of days, so should I resume testing or start replacing other components? I will not let it beat me.........

Steve

Racehunter · 06 Feb 2012

Just done a little research and almost by accident came across the following thread on nvidia forums. Its a long thread but it does seem that there may be an issue with 400 and 500 series Nvidia GPU's and some motherboards. Perhaps i should try a Radeon card/

The Nvidia 400/500 series lockup club! - NVIDIA Forums

Dave76 · 06 Feb 2012

After reading that thread, I don't blame you, RMA the nvidia card if you can and get a Radeon.

It's a bad enough issue but, the support from nvidia is horrible.
Thanks for the link, will keep it for reference.

Let us know what you decide to do.