BSoD Memory Dump whenever rendering Videos

[shadowfigure]

For the past few days, i've been searching, and searching, and searching some more, but no SOLID answer that works for everyone.

Here's the deal, I got a brand new PC.

Specs:

OS: Windows 7 64 bit.
CPU: AMD FX-8350 8-Core 4.40 GHz (OC by 10%)
GPU: Geforce Nvidia 460
Ram: 16 gbs

I can fraps gameplay with no problem, I can stream (VIA Twitch) No problem, but when I try to Render a video (any format, any program) it crashes if it's longer then 3-5 mins in length. Rarely it will just crash the program, but 95% of the time it causes a Memory Dump BSoD and restarts. I've been pulling my hair out over this issue. I made sure I updated all the drivers that I could think of, everything seems up-to-date. Did a ram test (the windows 7 one, not the memtest86 which if I get recommended to try, I will do.) but I mean a brand new PC w/ parts and I have bad ram sticks?

I've made sure to watch both my temps and Task manager CPU to see if I can see anything fishy before a crash, but my temps stay really nice. generally 35-48C (I have 6 fans + liquid cooling) The GPU is a Cyclone cooled Nvidia (which keeps thing very nicely cooled to w/ all the fans.) My CPU generally sticks around 60-80% when rendering.

Thanks in advance for any help! and be sure to tell me if I missed any specs and i'll post em.

[aedipuss]

redo the bios without any overclocking and see if it goes away.

[jman98]

ANY component in ANY hardware device can be bad when first bought. Look I'm not saying it's likely, but hell yes, you COULD have theoretically bought a PC with bad memory in it. I work in IT for a living and I have years of problem solving experience in the field. I learned a long time ago that the surest path to failure was to insist on blind faith that something cannot possibly be the cause of your problem. So keep an open mind but I agree that this is unlikely in a new PC. But it's not impossible.

Memtest86 can be useful, but I have read others say that sometimes it can't find memory problems and other times it reports false positives. The only time I ever used it, I felt that its results were inconclusive. You could remove memory and see if that fixes the problem. Assuming your mobo doesn't require pairs of memory, you could just remove a RAM stick and try an encode. If it crashes, replace the RAM and remove another one. Repeat and see if it ever eliminates the problem. If so, that RAM is likely bad.

I think it's likely some kind of BIOS setting and I agree with the suggestion that aedipuss has. You don't need to overclock with that kind of horsepower in your CPU.

[deadrats]

take a look in Event Viewer (it's under Admin Tools) and look through the logs, it should give you a good idea of what the problem is.

[jman98]

take a look in Event Viewer (it's under Admin Tools) and look through the logs, it should give you a good idea of what the problem is.

It's worth a look, but as Microsoft is sort of infamous for their "Well,it could be ANY piece of hardware in this computer" error messages that provide no way or narrowing down the possibilities, don't hold your breath on that. But it's worth a shot.