Random BSOD while doing 3D rendering.

I was rendering a scene in Softimage and watching YouTube at the same time. Oddly, I got a BSOD. I never got one while rendering. Please note, when Softimage renders it uses up all CPU resource.






Intel 3770K 3.5Ghz
16GB XMS 3 Corsair Ram
Sapphire AMD HD 7950 3GB
ASUS P8Z77-V motherboard
Samsung 830 SSD 128GB
1TB Seagate HDD
500GB Western Digital HDD
Samsung Blu Ray drive
Be Quiet! Pure Power 530W L8 BN181 PSU

I'm running Windows 7 Home Premium 64bit. Everything is fully updated.


Edit:

I just finished running memtest with no errors

A stop 0x124 is a hardware error.

Are you overclocking?

Code:

CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3569

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800f379028, f2000000, 70150}

Probably caused by : GenuineIntel

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