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

    • PDF-XChange Editor 11.0.1.0 by Razvan Serea PDF-XChange Editor is a comprehensive PDF editor that allows you to create, view, edit, annotate, and digitally sign PDF documents with ease. With advanced features like OCR, document security, and PDF optimization, PDF-XChange Editor is a powerful tool for both personal and professional use. Whether you need to edit text, images, or links, or add comments, stamps, or watermarks, PDF-XChange Editor provides all the necessary tools to make your PDFs look perfect. Additionally, it supports a wide range of file formats, including PDF, XPS, and DOCX, making it easy to convert and share your documents. PDF-XChange Editor key features: Edit text and images in PDF documents Add and remove pages from PDF files Annotate and markup PDFs with comments, highlights, and stamps Use OCR to convert scanned documents into searchable text Create and fill out PDF forms Sign and certify PDF documents digitally Add and edit hyperlinks within PDFs Extract text and images from PDF files Batch process multiple PDF files at once Customize the interface to your preferences Work with multiple documents in tabs Convert PDFs to other formats such as Word, Excel, and HTML Use advanced redaction tools to permanently remove sensitive information Add customizable headers and footers to PDFs Merge multiple PDF documents into a single file Split PDF documents into multiple files Add watermarks to PDF documents Use the measurement tools to calculate distances and areas in PDFs ....and much more PDF-XChange Editor 11.0.1.0 changelog: Fixed a crash in the new Open/Save dialog box when creating a new folder in an unavailable network path. (49552) Fixed a rare/infrequent crash on some dynamic XFA forms after changing their field values. [installer] Fixed an issue where shortcuts were lost during an upgrade from the previous version. [installer] Fixed an issue preventing migration of serial keys during updates from version 10. Fixed the issues with the shell context menu after installation of version 11. Fixed the issue with filtering comments. (49478) Fixed the issue that caused "Error [IO subsystem]: Invalid access mode." when converting PDFs to MS Office formats. Fixed an issue with the context menu position on some multi-monitor systems. (48467) Fixed an issue with handling complex custom file filters, displayed by JS, in the new Open/Save Files dialog box. (49486) Fixed several issues with the new 'Select Folder' dialog box. (49505) Fixed an issue with the new custom 'Open File' dialog box when using double-click to open it. (49498) Fixed an 'infinite' loop/proliferation in the 'Open Files' and 'Manage Places' dialog boxes. (49526) Fixed an issue with handling the mouse wheel inside the document "Find" box. (49539) Fixed an incorrect behaviour in the 'Go back (Alt+Left)' button in the new Open/Save Files dialog box. (49510) Fixed an issue with the shortcut keys (Alt+Left/Right) after navigating via breadcrumb paths in the new Open/Save Files dialog box. (49554) [installer] Fixed an issue with redrawing the progress text in the EXE installers. Fixed the issue where a mouse click outside of the polyline/polygon context menu during annotation creation would cancel the annotation. (49475) We switched back to using the system Open/Save/SelectFolder dialog box by default, instead of using the new one, because some popular features such as the QuickAccess/Recent items are missing in the new version. These will be added in a future release. Replaced the 'Extension' column in the new Open/Save File dialog box with a more user-friendly 'Type' column. Also fixed some issues when handling the 'Show file extension' option. (49497) Added the ability to authenticate local network shares in the new Open/Save Files dialog box. (49557) Improved the handling of dates after 01.01.2030 in XFA files - now such dates are stored properly when set via the dropdown widget. Flags NoZoom and NoRotate are now respected for only a limited subset of annotations. Download: PDF-XChange Editor (64-bit) | Portable ~300.0 MB (Shareware) Download: PDF-XChange Editor (32-bit) | Portable ~200.0 MB Download: PDF-XChange ARM64 | 276.0 MB Download: PDF-XChange Portable @PortableApps.com | 97.0 MB View: PDF-XChange Editor Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Still 3x what it should cost. So, it seems the trick is to increase price by 6x so that a reduction in price back to 4x looks like a steal. "You savvy shoppers win again!" I'm glad I'm not in a desperate spot to actually even need this overpriced crap. Hopefully, it comes back down by the time for when (or if) I ever do.
    • Although AI is great and has it's use cases they likely have massively overhyped it and it has not delivered as per their expectations. I fully expect them to start saying the same things again when it does get to a certain level of intelligence!
    • Microsoft wants to end printer driver headaches with Windows Ready Print by Usama Jawad A few days ago, Microsoft released Windows 11 Experimental build 26300.8553, bringing a ton of enhancements such as Start menu customization, search improvements, Taskbar polish, and other minor UI tweaks. Another relatively major enhancement snuck deep within the change log was related to upgrades to the Windows printing experience. Now, Microsoft has shared more details about these benefits. For starters, Microsoft has renamed its Modern Print Platform to Windows Ready Print. The company believes that this name highlights its shift in strategy, which now focuses on modernizing, securing, and streamlining the printing experience for Windows devices. Some of the upgrades present in Windows Ready Print have already been seeded to customers and partners. This includes ending support for third-party printer drivers via Windows Update and transitioning towards the Internet Printing Protocol (IPP) and the native Windows IPP printer driver. In line with these changes, new printer installations will default to Windows Ready Print on eligible devices starting from July 2026. However, Microsoft recognizes that not all environments will be able to migrate to this platform immediately, so it will allow users to choose between installing the printer via Windows Ready Print or the traditional OEM process. Users will be able to toggle this configuration through Settings > Bluetooth & Devices > Printers & Scanners > Printer preferences. This control applies only to new printer installations, and its functionality can also be modified via Group Policy as follows: Launch Group Policy Editor Navigate to Local Computer Policy -> Administrative Templates -> Printers Find and select 'Configure Windows Ready Print driver ranking' -> double click to open it Select 'Enabled' (if you wish to enable Windows Ready Print driver selection) or 'Disabled' (if you wish to explicitly disable Windows Ready Print driver selection). Select Apply Select OK Similarly, if you set up Windows protected print mode through the same setting in Windows 11, it will also default to using Windows Ready Print exclusively. Microsoft hopes that these improvements will help eradicate dependency on OEM-specific driver installation processes and simplify printer installations. We'll likely find out more about other tangible benefits in the coming months.
  • Recent Achievements

    • One Month Later
      johnjacobb40 earned a badge
      One Month Later
    • One Year In
      Primer1st earned a badge
      One Year In
    • Experienced
      JayZJay went up a rank
      Experienced
    • Reacting Well
      Sir_Timbit earned a badge
      Reacting Well
    • Week One Done
      rubentuben8 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      513
    2. 2
      PsYcHoKiLLa
      231
    3. 3
      +Edouard
      138
    4. 4
      ATLien_0
      87
    5. 5
      Steven P.
      81
  • Tell a friend

    Love Neowin? Tell a friend!