Random BSODs, all diff errors

sorry I should have told you to read the manual about the ez flash asus uses, you just drop the bios on a flash drive and it basically updates itself with a few pieces of input.

well if you want to test the ram you can just let this run overnight.
RAM - Test with Memtest86+

Okay well this happens now and then I'm either missing something obvious or it's hardware. I'm going to see about having another dump file reader look over this just to make sure.

yes please upload your most recent .dmp files so they can be analyzed with windows debugger, and also download and run CPU-Z select the memory and speed tabs and post screenshots here please ?

I have seen problems with this motherboard identifying Ram speed settings when set to auto ?

SteveS97 said:

Update: Using memtest, I have verified 2 working DIMM slots, and 2 working modules of RAM. I currently have those 2 modules installed (I had 4 modules at my disposal). So from this point on, let's assume it is not RAM.

In addition, crashed 3 more times since last post, 1 had a "Memory_Management" BSOD, and 2 were just straight crashes, no BSOD. Two new minidumps have been created and I ran the BSOD Dump & System File Collection app again.

In the middle of building some systems atm so I will look at your .dmp files as soon as I can but in the interim why would some of the .dmp files have incorrect timestamps ?

Also you can not assume your problem is not Ram related as no memory tester is definitive and nothing tests your memory like an O/S can , to quote since windows 95 Microsoft have stated about memory testing programs

Defective memory chips may not be detected by memory checking tools. Some memory checking programs are not adequate tests because they do not test RAM in the same way that Windows uses RAM. Most memory checkers use read/write cycles when scanning memory. Since Windows is executing code from memory, it uses execute cycles. Execute cycles are different from read/write cycles and are more vulnerable to parity errors. It is possible for memory checking programs to find parity errors if the memory is extremely faulty.

ok at first glance this chipset driver

AtiPcie.sys fffff880`017dd000 fffff880`017e5000 0x00008000 0x4a005486 05/05/2009 16:00:22

is old and needs updating ?

I am also confident that with your listed causes showing as ntoskrnl.exe, wmiamcpi.sys, cdrom.sys, HDAudBus.sys, usbfilter.sys suggests this is more likely to be a hardware issue ?

I would be looking at making sure all cards are properly seated and all cables are properly connected then monitoring temperatures and checking voltages and power supply and most likely Ram incompatibility ?

the ram you are using is not on the mobo QVL > Attachment 163842 , which suggests your ram choice could be causing problems ?

your ram currently shows as underclocked ?

I would try going into your BIOS settings and setting the ram speed manually then monitoring CPUZ readout and system stability ?



===================================
On a side note my customer with this same motherboard, on my advice kept all other components and changed the mobo and his bluescreens are gone. My theory is this motherboard is unstable with some ram combinations ?