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

    • Zed 1.7.2 has landed with updated OpenCode models, bug fixes and other improvements by David Uzondu Zed 1.7.2 recently landed on the stable release channel, bringing a host of AI-related features including automatic context compaction and settings-based skill management, along with other things like better Markdown preview rendering and custom git commands in the graph view. Starting with the AI stuff, the developers introduced "/compact", a command that basically summarizes your conversation history on demand. This tool prevents your active chat window from hitting token limits by compressing older parts of the dialogue into a brief overview. In addition to that, the team relocated skill management to the settings UI, improving how the application communicates errors regarding those skills, and updated the OpenCode model roster to support DeepSeek V4 Flash, MiniMax M3, Qwen 3.7 Plus, and Nemotron 3 Ultra Free. External agent users can also monitor context window cost metrics and delete individual sessions directly from their history. Right-clicking ref labels in the git graph now opens a context menu that runs different actions against selected targets, kind of how VS Code does it. Here are some of the bug fixes this new release brings: The active agent fails to auto-select when creating a new git worktree. A scrollbar unexpectedly appears on wrapped code blocks in the agent chat. Collapse indicators for project headers appear when performing sidebar searches. Bracketed ellipsis title prefixes fail to show the ellipsis icon properly. Project icons render incorrectly in the recent projects picker. Diff hunk controls appear inside non-editable commit view multibuffers. The software update button hangs indefinitely on the downloading stage. Restoring an agent terminal in a remote project triggers a sudden crash. Splitting a pane that contains an active commit view causes a crash. Linux Wayland freezes when trying to read the clipboard from laggy external apps. Zed is a "newish" code editor trying to break the massive stronghold VS Code has on the developer community. Funny enough, the editor was created by former GitHub employees who worked on the Atom text editor (which Microsoft killed in 2022, several years after it bought GitHub). The project officially hit version 1.0 back in April, introducing platform parity for Windows and Linux alongside deep support for DeepSeek-V4-Pro.
    • 26H2 absolutely will support ARM Windows just not on devices that came with 26H1. This is evident by the fact I am running 26H2, which on my MacBook Neo and Surface Pro 12 (inch), within a VM.
    • Mp3tag 3.35 by Razvan Serea Mp3tag is a powerful and yet easy-to-use tool to edit metadata (ID3, Vorbis Comments and APE) of common audio formats. It can rename files based on the tag information, replace characters or words from tags and filenames, import/export tag information, create playlists and more. The program supports online freedb database lookups for selected files, allowing you to automatically gather proper tag information for select files or CDs. Mp3tag supports the following audio formats: Advanced Audio Coding (aac) Free Lossless Audio Codec (flac) Monkeys Audio (ape) Mpeg Layer 3 (mp3) MPEG-4 (mp4 / m4a / m4b / iTunes compatible) Musepack (mpc) Ogg Vorbis (ogg) OptimFROG (ofr) OptimFROG DualStream (ofs) Speex (spx) Toms Audio Kompressor (tak) True Audio (tta) Windows Media Audio (wma) WavPack (wv) Mp3tag 3.35 changelog: This version introduces a new Files options page, enhanced toolbar customization, support for RF64 WAV files, improved Discogs and MusicBrainz tag sources, and many other improvements and fixes. See the Release Notes for more details. Download: Mp3tag 64-bit | 5.7 MB (Freeware) Download: Mp3tag 32-bit | 5.2 MB Link: Mp3tag Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The FIFA World Cup is not US centric.
    • It’s amusing how Microsoft is pushing IT admins as if this was a major, game-changing update. In reality, it’s just an enablement package that bumps the build number, which is disappointing compared to the more substantial 22H2 and 24H2 releases. Technically, 25H2, 26H1, and the upcoming 26H2 are essentially the same, differing only in support schedules. They could have included the Windows K2 improvements here, but chose not to. The era of Windows being in the backburner continues, and this 26H2 release feels like an afterthought. Shame, Nadella, shame.
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!