hangin/Crashing when rendering with MR, Maya or Vue

[kafl]

Hello there

Im having some seirous issues with one of work PC's that keeps crashing while rendering.

I have tried many things - but i would like to know bit more about what to do before going to reinstall entire system.

HArdware and system
Machine is Dual Xeon motherboard s5000X with two quadcore Xeon processors.
OS is windows 7 pro.

I tried with 4 x 2 gig ram and with different 4 x 8 gig ram - to test if it was ram.

I had an idea it was a harddrive issue - and tried many different cables for that.
Issue:
It crashes while rendering using Maya, Mental ray og Vue Xtream.
It sometimes has to do with bit warm temperature inside the room (im assuming 35 degree or so) - but unfortunately it also happens with "normal" temperature like 20 degree or so.

THe crashes that i have seen (in normal temperature) have startet with a system being "unstable" normally where a render that takes 1 minutes renders for 30 frames, then they start taking longer and longer - and then they stop - they take longer - but they use 100% for only the 1 minute it takes to render and then 0% for rest of the time.
In this period if i try doing anythign - even running taskmanager and shutting down the process mayabatch.exe or any other program it will not do it.
I can select end process - and choose yes when im asked - but process is never terminated.

The more keys and buttons i press the more things start to hang - and at no point am i able to turn of the machine - even using the on off buttom on machine - only if I hold down the button.

IF i do nothing it will at some point crash.
Im curious if this is somehow a hardware - like graphics card etc. issue or if it is somehow some virus, trojan, or simply some bad programming/bad drivers or something like that.(i have tried scanning for virus etc.)

I have run some memtes - i dont remember running CPU test.

I apreciate all help.

I will gladly share any info and files that i can - if that can help.

Best regards
Karsten


I also now have uploaded the ystem info Windows_NT6_BSOD_jcgriff2 as requested

 

[writhziden]

Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html even though you are not getting a blue screen crash. The logs in those reports include application and system logs and errors on the system. There is also useful information in those reports for tracking down program conflicts, etc.

 

[kafl]

added Windows_NT6_BSOD_jcgriff2

I also now have uploaded the ystem info Windows_NT6_BSOD_jcgriff2 as requested

 

[writhziden]

Device Concerns:

Intel (R) PRO/1000 EB Network Connection with I / O Acceleration # 2 PCI \ VEN_8086 & DEV_1096 & SUBSYS_34728086 & REV_01 \ 6 & 35BB4ADF & 0 & 00100010 This device is disabled.

Were you aware of the above? If so, please explain so we may understand your troubleshooting steps.

Also, even though devices are disabled, some devices still load their drivers. If those drivers are corrupted/buggy/outdated, they can cause conflicts on the system.​

Software Concerns:

Security Software: ??? Make sure to install security software. I recommend either of these:

• Microsoft Security Essentials - Free Antivirus for Windows coupled with Malwarebytes. Do not start the free trial of Malwarebytes. Just use the standalone version, update it, and scan your computer once a week with Malwarebytes and with Microsoft Security Essentials.
  
  
• http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627

After installing your security software, update it, and then run full scans today with each program. Report back the results of the scans.​

Analysis:

I am unable to read the logs since they are not in English, unfortunately. You should read through your Event Viewer logs for errors and critical errors: http://www.sevenforums.com/tutorials/226084-event-viewer-open-use-windows-7-a.html

I did see an Event ID: 41, which may indicate a hardware issue. Run some hardware checks.

• If you are overclocking any hardware, please stop.
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!
  
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[kafl]

Hello Again.

I can see that i actually posted this problem some time ago. Then i got the aboe reply, and i had some time but not enough to try out the Things.

Now i have gone through almost all the tests - and there are a few things that i could check. I ran the furmark cpu burner, first with music playing and with the GPU burning test too and that crashed very short after. Then i ran it Again just with GPU and CPU at same time and it crashed. I then ran it with CPU only and it crashed.

This tells me that i have bit issues with the CPU's - or maybe the Bios settings. Can anyone comment/advise me how to go on. I can either test if it is only one cpu mauybe that is bad? or i need to make some settings in the Bios, or install some other CPU drivers than the ones i have or anything?

Again - any advise is apreciated.

Best regards
Karsten

 

[kafl]

oh and i forgot to say that as far as i can see the CPU did not get extremely hot it was at 70 degrees all the time - i assume that is ok.

I could see 4 temperartures - but im not sure what im looking at. I have 2 physical cpus with 4 cores each - so maybe im only looking at the 4 on one cpu. I was using the realtemp software