BSOD with assorted stop codes

Hiya.

After about 50 attempts at installing Windows 7 Ultimate 64-bit to a newly built computer, I finally got it installed, despite all the "source file unavailable" messages and random BSODs, and ran it rock solid stable for about 6 hours last night. When I turned it on this morning, however, I was met with a BSOD upon loading my desktop with some error messages relating to various programs that I didn't have time to read. This, coincidentally, occurred on my previous fresh W7x32 install the day before, too.

I got home from work today and fired it up, just to see what would happen, and each time it loaded to desktop, I got hit with a BSOD, each time with different stop codes, ranging from "reference_by_pointer" to "system_service_exception". I ran the windows memory diagnostic on the RAM I have in my system now, and it showed that I had an error (though wasn't kind enough to tell me what kind and on which module...) I ran the test again on each module and each time the test showed negative on errors, so I put both sticks back in, but this time in the second bank, to test - surprise surprise, the test shows errors.

Having had the computer warmed up now for a few hours, it seems to be fairly stable, and I'm running memtest on the pair of DIMMs as we speak. The tests are so far showing negative on errors.

I'll upload the stack dumps as soon as it's finished testing the RAM (I'm on my laptop atm) but in the meantimes, what are your initial thoughts? Chipset errors on the motherboard that stops it running correctly in dual channel mode? Dead RAM? Any help would be appreciated.

Thanks,
Dave.

System spec: AMD Phenom II 955 3.2GHz, 4GB Geil Black Dragon 1333 RAM (2x2GB), Asus M4A88TD-M EVO/USB3 motherboard, 1TB SATA Samsung HDD, 2x LG DVD-RW (IDE), Asus 5770 ATI graphics card and a 700watt PSU.

Okay, after running memtest within windows for an hour or so, 100% tested showed 0 errors. Quite why windows memory tester is returning errors, but memtest isn't, is beyond me, but there you go. I'm attaching my stack dumps with this post - hopefully that'll help someone diagnose the issue.

Another couple of hours running stable last night after it'd warmed up, I turn my computer on this morning and I get a "spooler subsystem app has stopped working error" on boot, then a BSOD with a 0x19 bad_pool_header stop code about 5 minutes later, while idling on desktop.

I'd be willing to bet that once it's warmed up a little, it'll be stable all day.

Still no ideas?

Edit: And one more BSOD for good measure. This one with a 0x24 stop code, citing ntfs.sys in the main body text.

Okay, just a few updates.

The first thing I did when I got home this afternoon was to attempt to run Windows - this, as expected, resulted in a BSOD. I then ran Memtest86+ on both sticks in their original configuration, and found no less than 60,000 errors from test 4 onwards on the first pass. I then proceeded to test each stick individually in each slot, with each test returning no errors whatsoever. I've just finished running a test again on the original configuration with both sticks in, and guess what? No errors after 2 passes. I'm about to boot into Windows and check stability and I'll let you know what happens.

ttran, to answer you questions:

I originally ran the windows memory diagnostic from the boot menu - I assume it's the most recent version to my copy of Windows 7 Ultimate, which returned harware errors but wasn't more specific. After that, I ran a program simply called memtest from within Windows and returned no errors at all.

I've run chkdsk and although it did turn up a few orphaned files etc, these appeared to be from the system not shutting down correctly on any of its numerous BSODs, and I couldn't see anything critical in the results. I attempted to run the Samsung HDD utility this evening, but it failed to run, citing:

"Cant open CD driver CD001. SHUCDX can't install

your ram drive is loaded at c:
Out of memory error
Bad command or filename"

So I haven't gone any further with that for now. I am also not overclocking anything, and running everything at stock settings, with memory voltage and timings by SPD.

Jonathan_King: I'll remove Comodo and run the driver verifier tomorrow, after I've conducted a few more tests - I don't want to eliminate too many things at once in case I miss the issue altogether.

I'll run another memtest tomorrow on a cold boot (as the system seems to run stable after a while) and see what happens, and then I'll run it overnight to check again.

At the moment, I'm stumped as to whether it's the motherboard, RAM or CPU (seeing as the memory controller is on board with AMD chips?) Indeed, I may have to RMA the lot and leave them to figure it out.

Thanks, both of you, for your help so far.

Upon running memtest86+ again when I got home from work today on a cold system, I'm so far at 6,000+ errors from test 5, 6 and 7, with test 8 still to come.

I am geniunely stumped. No errors on a warm system, yet tens of thousands on a cold boot. I'm pretty much ruling out Windows or HDD errors here, though you're welcome to disagree.

Dry joint or bad soldering on the motherboard maybe? I could do with pinning this problem down to a specific piece of hardware to avoid RMAing the whole damn kit and kaboodle.

I've also started a new thread at Memory issues with Asus M4A88TD-M Evo/USB3 - AnandTech Forumsin an effort to spread the net a little wider and get some input from the hardware crowd. Feel free to offer any sagely advice with regards to what they say.

Thanks again.