Recommended Posts

Hello everyone,

Don't really want to flood the forum or anything, but I seem to have a problem with my PC. Just as the title says, my computer crashes while rendering.

I've done some 3D renders of low- to medium-poly models without really complicated geometry in the past and everything has been working properly. However I've recently finished modelling a high-poly object which I really want to render. But the PC starts working on it, then crashes into a blue screen with a crash dump.

I've tried several different rendering programs and it happens with all of them. Sometimes it even crashes in pre-render phase, while I am setting the lighting options and such.

I'm guessing the problem lies in the hardware, maybe in RAM or CPU. But I don't have enough knowledge to confirm/deny that, which is why I came here. I don't think the problem could be heat-related since the chrashes happen 1-5mins from the start of rendering.

The PC specs are as follows:

CPU: AMD Phenom 9850 Quad-Core 2.5GHz (poorly ventilated, not overclocked)

Motherboard: ASUS M2N68-AM

PSU: Aero Cool E80-700 700W

GPU: ATI Radeon HD 7850 (overclocked, dual fans)

RAM: 4GB (can my motherboard support more?)

OS: Windows 7 Ultimate 64bit

I think that pretty much covers my problem. Any help would be appreciated.

Link to comment
https://www.neowin.net/forum/topic/1129444-pc-crashes-while-rendering-in-3d/
Share on other sites

Hello everyone,

Don't really want to flood the forum or anything, but I seem to have a problem with my PC. Just as the title says, my computer crashes while rendering.

I've done some 3D renders of low- to medium-poly models without really complicated geometry in the past and everything has been working properly. However I've recently finished modelling a high-poly object which I really want to render. But the PC starts working on it, then crashes into a blue screen with a crash dump.

I've tried several different rendering programs and it happens with all of them. Sometimes it even crashes in pre-render phase, while I am setting the lighting options and such.

I'm guessing the problem lies in the hardware, maybe in RAM or CPU. But I don't have enough knowledge to confirm/deny that, which is why I came here. I don't think the problem could be heat-related since the chrashes happen 1-5mins from the start of rendering.

The PC specs are as follows:

CPU: AMD Phenom 9850 Quad-Core 2.5GHz (poorly ventilated, not overclocked)

Motherboard: ASUS M2N68-AM

PSU: Aero Cool E80-700 700W

GPU: ATI Radeon HD 7850 (overclocked, dual fans)

RAM: 4GB (can my motherboard support more?)

OS: Windows 7 Ultimate 64bit

I think that pretty much covers my problem. Any help would be appreciated.

You need to remove your GPU OC before you can continue troubleshooting, anything OC'd can cause bluescreens

Also install something like coretemp to monitor your temps while you render

CPU: AMD Phenom 9850 Quad-Core 2.5GHz (poorly ventilated, not overclocked)

NEXT!

People need to understand, if you don't get good air flow around the CPU your going to kill the machine.....try wrapping your head in 3 or 4 scalfs then go to the gym...you're gonna collapse.

I would look at the CPU and GPU temps. Also try running memtest to make sure the ram isnt taking a dump on you. Try running a benchmark also like 3d mark just to rule out the OC on the GPU as well.

Try and post a screen shot of the BSOD if you can. That will also help.

remove the GPU and attempt to render the 3D again

What do you mean? Just to remove the GPU entirely from the case and try to run the render that way? Will it even work?

CPU: AMD Phenom 9850 Quad-Core 2.5GHz (poorly ventilated, not overclocked)

NEXT!

Even though it's poorly ventilated as I mentioned, it has never suffered from excess heat and the temperature readings have always been low enough. The CPU has a little fan on it, not sure about the effectiveness of it.

What do you mean? Just to remove the GPU entirely from the case and try to run the render that way? Will it even work?

Even though it's poorly ventilated as I mentioned, it has never suffered from excess heat and the temperature readings have always been low enough. The CPU has a little fan on it, not sure about the effectiveness of it.

Problem is now you are stressing the CPU more than likely almost to it's limit....you are rendering 3D we are not talking about burning a few dvd's 3D rendering is crazy on the CPU

What do you mean? Just to remove the GPU entirely from the case and try to run the render that way? Will it even work?

Even though it's poorly ventilated as I mentioned, it has never suffered from excess heat and the temperature readings have always been low enough. The CPU has a little fan on it, not sure about the effectiveness of it.

How do you know your GPU is overclocked if you don't know how to remove the OC ?

You should also stick a fan at the front of your case sucking in, and a fan at the back blowing out, that way you always have a 1 directional airflow moving hot air out and cool air in

The GPU is over-clocked by ASUS and I can manually tweak the clock speeds with the software provided, so I assume it's a legit OC (it even says it on the packaging). I can max out the GPU Clock at 1050MHz, GPU Voltage at 1165mV and Memory Clock at 5800MHz.

Ever since the last Windows reinstall in autumn I haven't been monitoring the temperatures. Can you recommend the best tool for the job?

I would look at the CPU and GPU temps. Also try running memtest to make sure the ram isnt taking a dump on you. Try running a benchmark also like 3d mark just to rule out the OC on the GPU as well. Try and post a screen shot of the BSOD if you can. That will also help.

Please tell me how to do the memtest and benchmark, I've never done it before. Also, what's a BSOD?

Firstly the GPU is unlikely to be the culprit if he's rendering, he hasn't specifically mentioned what render suite(s) he's using, but they all crash, and most render suites won't use the GPU for rendering, unless specifically set to it and most can't even then.

HE probably hit on the problem in his first post. bad memory. Rendering especially high poly rendering uses a LOT of memory, in fact it's probably the first time he's ever been close to using all of his computers memory.

DO you have 1 4GB stick or 2 2GB sticks ? if it's 2 sticks, remove one at a time and check.

also what resolution are you rendering the output at ?

The GPU is over-clocked by ASUS and I can manually tweak the clock speeds with the software provided, so I assume it's a legit OC (it even says it on the packaging). I can max out the GPU Clock at 1050MHz, GPU Voltage at 1165mV and Memory Clock at 5800MHz.

If you have not moved the sliders for the OC, then it is a factory OCd card from ASUS, if you have moved the sliders, then it is a Custom OC by you

Put the sliders to where ever they were when you got the card, or disable the overdrive check box and hit apply

BSOD = Blue Screen Of Death

For monitoring

GPUz - GPU temps

CPU-z or coretemp - CPU temps

Firstly the GPU is unlikely to be the culprit if he's rendering, he hasn't specifically mentioned what render suite(s) he's using, but they all crash, and most render suites won't use the GPU for rendering, unless specifically set to it and most can't even then.

HE probably hit on the problem in his first post. bad memory. Rendering especially high poly rendering uses a LOT of memory, in fact it's probably the first time he's ever been close to using all of his computers memory.

DO you have 1 4GB stick or 2 2GB sticks ? if it's 2 sticks, remove one at a time and check.

also what resolution are you rendering the output at ?

My main renderer with which I work with is Keyshot 2, but Vray, Indigo and others failed too. I have 2 sticks of 2GB of RAM. But how does removing one stick at a time help me? Do you think one of them could be corrupt or something?

If you have not moved the sliders for the OC, then it is a factory OCd card from ASUS, if you have moved the sliders, then it is a Custom OC by you

Put the sliders to where ever they were when you got the card, or disable the overdrive check box and hit apply

BSOD = Blue Screen Of Death

For monitoring

GPUz - GPU temps

CPU-z or coretemp - CPU temps

I have tried rendering with various clock settings and it's still the same, although maybe I didn't try rendering with stock clock speeds.

I have tried rendering with various clock settings and it's still the same, although maybe I didn't try rendering with stock clock speeds.

Well my last 6850 would crash either the display driver or the machine if I even OCd 1MHz

Again, you can not troubleshoot an OCd machine, I`m not saying it is 100% the GPU, but you need to have everything @ stock

Well my last 6850 would crash either the display driver or the machine if I even OCd 1MHz

Again, you can not troubleshoot an OCd machine, I`m not saying it is 100% the GPU, but you need to have everything @ stock

Would setting the clock speeds to stock card speeds (from google) do the job?

EDIT: Well, as it turns out, I cannot go below Memory Clock speed 3880 MHz and google says the stock speed is 1200MHz, so...yeah

Edited by Redix

Go download memtest86 and burn a cd from it. Pop the CD in and reboot the computer and boot to the CD. Run the test with 1 stick at a time them pop them all back in if they pass and run a test with them all in. That will rule out the Ram for sure.

A screenshot of the blue screen would be a big help also. But rule out he ram first. Trust me.

Would setting the clock speeds to stock card speeds (from google) do the job?

EDIT: Well, as it turns out, I cannot go below Memory Clock speed 3880 MHz and google says the stock speed is 1200MHz, so...yeah

Just uncheck the Overdrive option in CCC and hit apply, the card will drop to its factory clock speeds

Capture.PNG

So, I was surprised when it reached 15% of the rendering process...but then it crashed again, so removing the OC doesn't seem to help. Also, the BSOD.

Stop 0?00000050: PAGE_FAULT_IN_NONPAGED_AREA ? This Windows stop error indicates that information that the operating system was looking for was not found in memory (ram). This occurs when the system looks for information in the ram that doesnt exist. This is usually caused by defective RAM (once again, including Ram on your motherboard, L2 cache and video card ram).

Get your ram testing on ;)

Stop 0?00000050: PAGE_FAULT_IN_NONPAGED_AREA ? This Windows stop error indicates that information that the operating system was looking for was not found in memory (ram). This occurs when the system looks for information in the ram that doesnt exist. This is usually caused by defective RAM (once again, including Ram on your motherboard, L2 cache and video card ram).

Get your ram testing on ;)

I'd have thoroughly tested RAM today, but it turns out I have no empty CDs left which I can use and the nearby stores have none. I hate putting off such tasks but I just have no options right now. So tomorrow I'll go to a bigger store further away, find & buy those CDs and start working.

Hopefully the problem is one of my regular RAM units and not motherboard RAM or anything like that. That would be an excuse to buy more RAM.

Though what I did today was I opened the case to provide better ventilation for any components that could be overheating. I started rendering once again, and checked if there was any excessive heat coming from somewhere. No, there wasn't. And the air coming from the fan on the CPU is just mildly warm under full rendering. So maybe we can abandon the overheating theory.

Hopefully the problem is one of my regular RAM units and not motherboard RAM or anything like that. That would be an excuse to buy more RAM. Though what I did today was I opened the case to provide better ventilation for any components that could be overheating. I started rendering once again, and checked if there was any excessive heat coming from somewhere. No, there wasn't. And the air coming from the fan on the CPU is just mildly warm under full rendering. So maybe we can abandon the overheating theory.
Using your PC with the side panel off will only disrupt the normal airflow of the PC and make it not as cool as it could be; it's a very poor way of measuring temperature.

And I don't know what you mean by regular RAM and motherboard RAM...there's only one type of RAM inside your PC, and those are the two 2GB sticks in their slots...

This topic is now closed to further replies.
  • Posts

    • Apple Watch Series 11 GPS just crashed to 30% off in this fast-moving Prime Day deal by Karthik Mudaliar The Apple Watch Series 11 is available for $279, down from its $399 list price, saving buyers $120, or 30%. Amazon labels the offer as selling fast, so the current price may not remain available for long. This GPS model features a 42mm aluminum case, an Always-On Retina LTPO3 OLED display capable of reaching up to 2,000 nits, and an Ion-X glass surface with improved scratch resistance. Apple rates Series 11 for up to 24 hours of normal use or up to 38 hours in Low Power Mode, with fast charging providing up to eight hours of use from a 15-minute charge. Health and fitness tools include sleep scoring, temperature sensing, ECG support, heart-rate alerts, workout tracking, sleep apnea notifications, and hypertension notifications, where available. The watch also carries IP6X dust resistance and 50-meter water resistance. This configuration is best suited to iPhone owners who want comprehensive health tracking, notifications, contactless payments, and workout data without stepping up to a larger or cellular-equipped model. The smaller case should also appeal to buyers who prefer a lighter watch, while the S/M band fits wrists measuring 130mm to 180mm. With the current generation now significantly below its usual retail price, this is a strong time to replace an aging Apple Watch or buy a first model without compromising on Apple’s newest health and display features. Grab the discounted Apple Watch Series 11 (sold and shipped by Amazon) Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • The laptop in the bedroom is an Acer with i7-10510U CPU. Acer's website states they will not be upgrading it so I had little choice other than disable secure boot. I know next to nothing on these matters so hopefully it will be fine.
    • GitHub removes manual model selection from Copilot free and student plans by Karthik Mudaliar GitHub is removing the ability to manually select an AI model from its Copilot Free and Student plans, making its automatic routing system the default and only way to choose a model. This means users on these tiers will no longer be able to deliberately select a particular OpenAI, Anthropic, Google, or Microsoft model for a task. In its announcement, GitHub said Copilot Auto will dynamically choose what it considers the best model for each request. Free and Student accounts will retain access to models from multiple families, although the available selection will continue to depend on the restrictions attached to each plan. GitHub did not identify a fixed pool of models that Auto will always use, and its documentation warns that model availability can change over time. GitHub describes Auto as more than a random fallback system. On supported surfaces, its task-optimization technology evaluates the complexity of a request alongside real-time information about model health and availability. Straightforward prompts can be routed to faster and less expensive models, while more demanding coding tasks may be sent to higher-cost reasoning models. The company says this approach should reduce rate limiting, latency, and failed requests. Auto generally selects one model along natural prompt-caching boundaries rather than repeatedly switching models during a session, as GitHub found that mid-session changes increased costs without producing sufficient improvements in output quality. Users can still check which model generated a response. In Copilot Chat, the information appears when hovering over an answer, while Copilot CLI and the Copilot cloud agent display the selected model alongside their output. Auto is available in Copilot Chat, Copilot CLI, and the cloud agent, with the exact implementation and release status varying between supported development environments. The latest restriction follows several months of adjustments to Copilot’s individual plans. GitHub temporarily halted new Pro, Pro+, and Student subscriptions in April as it sought to manage demand and service reliability. It later introduced token-based billing and began gradually reopening individual-plan registrations on June 17. Alongside the picker change, GitHub is retiring the “Preview” label from Microsoft-developed models. It argues that the label is no longer necessary because Auto handles model routing and models are continuously updated behind the scenes.
    • Look up 'inflation' kid. Ask an AI for the numbers between both games.
  • Recent Achievements

    • One Year In
      Philsl earned a badge
      One Year In
    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
  • Popular Contributors

    1. 1
      +primortal
      461
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      124
    4. 4
      Michael Scrip
      79
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!