[jandarsun8]

I'm getting two specific error codes, a 0x0000007a and 0x0000004f. The 7a codes from what I've found on Google tend to be HD related, the 4f errors- memory. I've got four sticks in the thing and I've tried each stick in each slot with it bsod after about 2 minutes of being on. I ran Memtest86 17 hours last weekend on it before I stopped it with 53 errors but it stayed up and running that whole time with all four sticks in it. I've ran scandisk on it with no errors but I haven't ran Seagates diag test on them yet. It stay up and running that whole time as well.

With both error codes, I'm wondering if the memory errors Memtest picked up are really memory related or motherboard related. Being that it stayed up for hours at a time while running test, yet runs only for a couple of minutes while Windows launches, what would be your next step in trying to trouble shoot this problem?

I don't have another system that runs DDR2 memory so my next step was to do a fresh load of windows on another HD and see what happens. Thoughts?

Nothing recently has been installed and everything was running fine up until last Friday. The last three things installed before all this were a couple of days before hand and were the installation of Dragon Age: Awakening, DivX update and Firefox update to 3.6.2 (or 3.6.3).

[IvanV]

I'd say that 53 errors in Memtest speak for themselves. It doesn't matter that the test itself hadn't crashed, it's not supposed to, any number of errors other than 0 should indicate a memory related problem.

I'd check each memory stick with memtest individually to see which are bad and which are okay.

[Tipstaff]

Here's a thought: you said you tried each stick of RAM in each slot, but did you do a Memtest on each stick of RAM separately to determine which one generated the errors? Along with that you can run Memtest with a stick of RAM in each slot to see if your theory is right about the board being bad.

[Judas]

Generally you can produce millions of memory errors and still keep running the memtest for days or weeks without it rebooting.. that's the beauty of using memtest.... if it were to reboot on any major errors or minor, would kinda defeat the purpose of memtest.

getting ANY, even just 1 single ERROR in 17 hours is usually a sign of something being the culprit.

But indeed follow tipstaff on the suggestion, pull ALL but one stick out, and test each stick individually for a good duration until you can find which one is giving you the error. Usually you can tell cause the 53 errors likely would have occured in the same location every time over a period of 17 hours, usually you can pick out which on it is. for example:

for a 2x2gb kit, if any error occurs consistantly below the 2048mb range, it's likely the first stick giving the error, if it happens above the 2049mb range.. it's the 2nd.

with 4x2gb, each 1: 0-2048 2: 2049-4096 3: 4097-6144 4: 6145-8192 are the typical ranges.

[jandarsun8]

Hmm no I didn't run each chip separately with memtest. I'll run some more test on it this coming weekend, I had my daughter last weekend so I only swapped out parts when she was sleeping and probably skipped a couple of things but this is why I asked you guys, to get some more ideas. Thanks to all for posting, I'll post what I find.