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

    • Win11Debloat 2026.06.14 by Razvan Serea Win11Debloat is a lightweight, easy to use PowerShell script that allows you to quickly declutter and customize your Windows experience. It can remove pre-installed bloatware apps, disable telemetry, remove intrusive interface elements and much more. The script also includes many features that system administrators and power users will enjoy. Such as a powerful command-line interface, support for Windows Audit mode and the option to make changes to other Windows users. All changes made by Win11Debloat can be easily reversed, and most removed apps can be restored via the Microsoft Store. A full guide on how to undo the changes is available here. Win11Debloat features: Below is an overview of the key features and functionality offered by Win11Debloat. Please refer to the wiki for more information about the default settings preset. Remove a wide variety of preinstalled apps. Click here for more info. Disable telemetry, diagnostic data, activity history, app-launch tracking & targeted ads. Disable tips, tricks, suggestions & ads across Windows. Disable Windows location services & app location access. Disable Find My Device location tracking. Disable 'Windows Spotlight' and tips & tricks on the lock screen. Disable 'Windows Spotlight' desktop background option. Disable ads, suggestions and the MSN news feed in Microsoft Edge. Hide Microsoft 365 ads on the Settings 'Home' page, or hide the 'Home' page entirely. Disable & remove Microsoft Copilot. Disable Windows Recall. Disable Click to Do, AI text & image analysis tool. Prevent AI service (WSAIFabricSvc) from starting automatically. Disable AI Features in Edge. Disable AI Features in Paint. Disable AI Features in Notepad. Disable the Drag Tray for sharing & moving files. Restore the old Windows 10 style context menu. Turn off Enhance Pointer Precision, also known as mouse acceleration. Disable the Sticky Keys keyboard shortcut. Disable Storage Sense automatic disk cleanup. Disable fast start-up to ensure a full shutdown. ...and more. Once you’ve downloaded the Win11Debloat file (Get.ps1), just follow these quick steps: Locate the Get.ps1 script file. Right-click the file and select Run with PowerShell from the context menu. If prompted by User Account Control (UAC), select Yes to grant the script the necessary administrative permissions. Win11Debloat 2026.06.14 changes: This is a minor release that hopefully addresses the false positives in Windows Defender and Bitdefender that prevented users from downloading and/or running Win11Debloat. Refactor Get-RegFileOperations.ps1 to address false positives by @Raphire in #626 Add logging around WinGet app retrieval and increase timeout to 20s by @Raphire Download: Win11Debloat 2026.06.14 | Open Source View: Win11Debloat Home Page | Screenshots 1| 2 Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Still using Microsoft Money 2005 in 2026 here!
    • I have a couple to mention, and they still run great on Windows 11 Adobe Lightroom Version 2 Alcohol 120% CLZ Book, Comic, Game, Movie, & Music Collector (PC - No longer sold / Grandfathered in - now mobile apps/online only) DVDDecrypter ISO Buster Pro version 1.9.1 (Still supports HD-DVD too) Nero Burning Rom 8 (Only the burning software, no backup, media converter, etc)   OpenAL (Runtime) - GuildWars 1 Reforged still uses it for 3d headphone audio PowerDVD 12 Ultra SPTD (SCSI Pass through Direct Driver) UltraISO Windows Media Encoder 9 WinImage You can tell I still sport an optical drive    
    • Linux 7.1 arrives with an NTFS overhaul and major hardware performance boosts by Paul Hill The founder of the Linux kernel has just announced the availability of Linux 7.1. This is a stable version of the kernel that will now be tested by various Linux distributions before it is shipped to users through update managers. Some users, like those on Debian, for example, might not get it for a long time, if at all, while Fedora users can expect it in the near future. With Linux 7.1 out on time, the merge window for Linux 7.2 is now open, giving contributors the opportunity to send in major new features that have been waiting for the last two months. Torvalds warned that he is currently travelling and will be in another timezone, so timing for the merge window may be irregular due to timezone differences and limited internet access. Torvalds said that he has already fetched early pull requests to allow him to do some offline work, but the travel could still cause disruption. Right now, he is not planning to extend the release, but did consider it. He said he might later regret not extending, though. In terms of this last week of development for Linux 7.1, Torvalds said there were no major or alarming changes. This week consisted mostly of smaller driver updates to GPU, networking, and sound, networking fixes, trace tooling fixes, and misc minor fixes. The shortlog this week lists fixes for driver bugs, memory leaks, I/O and USB fixes, networking and RDMA fixes, DRM/graphics fixes, and tooling and verification improvements. Specific fixes include USB series heap-overflow and buffer overflow fixes, and multiple use-after-free, memory-leak, and refcount corrections across subsystems such as i2c, zram, gpio, and net. There are fixes for graphics drivers, including amdgpu, i915, and virtio, as well as hypervisor and virtualization tweaks affecting mshv, vmbus, and hyperv. According to Phoronix, anyone running Linux 7.1 should look out for the new NTFS driver, Intel FRED for improved performance on Panther Lake and future CPUs, faster graphics with Intel Arc Battlemage, and improvements for older AMD Radeon GPUs. If you are running Linux on your computer and everything is fine, then you don’t need to worry about updating to Linux 7.1 as a priority; just wait for it to be pushed to you. If you have tried Linux on hardware but it didn’t work properly, trying again with a distro that uses Linux 7.1 could cause Linux to work on your machine, thanks to the new hardware support.
    • you can also do this with this tool: PowerSettingsExplorer made by mbk1969 at 3dguru forum.. I found it by accident researching on modern standby and annoying quirks of it in 2022
  • Recent Achievements

    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      507
    2. 2
      +Edouard
      197
    3. 3
      PsYcHoKiLLa
      139
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      81
  • Tell a friend

    Love Neowin? Tell a friend!