I am experiencing a problem in UE 4.6 when using the material editor. My crash logs are attached:
The issue happens sporadically when dragging a pin to connect two material nodes - upon releasing the mouse button to make the connection my PC crashes and immediately reboots. I experienced this issue with 4.5, but once I installed 4.6 I thought it had been resolved, until it happened earlier today.
I’d love to get this resolved, not really sure what could be causing it. Thanks for your time.
I want to try together as much information for our internal tests as possible and the crash logs go along way toward the reproduction internally, but I do have a few questions to help narrow down the issue. Are you getting prompted to submit the Crash report via the Crash Reporter Dialog Window or is it immediately rebooting your system? If it is immediately rebooting the system what else do you have running in addition to the editor, include all background programs as well? Is your CPU making any funny or loud noises just before it reboots? I can see from the crash reports that you are running a fairly higher end system, but is there anything setup in your system which would not been shown in the crash reports, SLI (multiple Graphics Cards) for instance?
As far as the Test3 project itself, can you let me know what it is based, is it a compiled C++ or a binary C++ project or is it a compiled Blueprint or a binary blueprint project (binary = Launcher)? What template did you use, First person, third person or was it a Blank project? Did you include Starter Content?
In the actual Material Editor when it crashed what where you using as a preview mesh? Was it Cube, Sphere or Custom Mesh and if it was Custom what type and how many vertices/polys did it have?
Any additional information you can give me will help us quickly find a solution to this issue.
Thanks for your reply. I never see the Crash Reporter Dialog - as soon as I let go of the mouse button my PC immediately reboots. It has happened several times, but the most recent time I had Chrome and Photoshop open in addition to the editor and launcher. In terms of background system-tray programs, I have Corsair Link, Samsung Magician, Razer Synapse, GeForce Experience, and Creative Cloud running. I’m not hearing any strange CPU noises, just standard fan noises. No SLI either - just the single 980.
The Test3 project is a Blueprint project, Blank template with no starter content. I don’t really understand compiled vs binary Blueprint project, but I created it by going to the New Project tab in “Unreal Project Browser” (4.6), selecting the Blueprint tab, choosing the Blank template, and deselecting starter content.
I was using the plane as the preview mesh in the Material Editor, trying to set up a GUI element similar to the Material Based Images section on this page in the docs so I was using those types of nodes. The scene itself isn’t complex at all, and I don’t see any issues when various running example projects - just this one Material Editor issue.
I appreciate your help. If I can provide any more information, please let me know. Thanks again!
Thanks for the additional information, I think I have enough now to begin to dig into this issue. Binary is referring to the Launcher as opposed to the compiled GitHub version.
I am a little concerned about the forced reboot that appears to happen. The engine does not have the CPU authority to cause that behavior so something is interacting with Windows to cause the reboot. If you would not mind going into your Windows Event Viewer (You can get to it by searching for Event Viewer in the Windows Apps search area.) Look at the critical or Error logs and try to narrow down which one resulted in the Reboot (most assuredly this is a Critical Issue) and the bring up the details by right clicking and “View All instances of this event.” Whether it is a single event or multiple select them all and Save Selected Events and place in a zip file and upload here.
Here are some screenshots to help with the above directions:
Thanks for the quick reply. I have attached the events from the Critical section. The event from January 30 most likely corresponds to the crash logs I submitted. I’m pretty sure the three events from January 20 were when I experienced the issue in 4.5 so I included them as well.
I appreciate your assistance. This is a strange issue and I wouldn’t be surprised if something about my machine is causing it as I just built it recently. Look forward to hearing back from you.
Thanks,
cedixon
edit: Forgot to add it was a binary Blueprint project, from the launcher.
We are on the right track. In the event viewer again look for Errors that would have happened right before (a minute to 5 minutes) the Critical on 1/30. Also try verifying your installation in the launcher as well, I don’t think this will fix the problem but it will check for a possible corruption to the engine install.
I verified the installation of 4.6 and 4.5 and they both look good. I didn’t see any Errors that happened right before the Critical, but I did find one that happened 13 seconds later so I have attached it. Thanks again for helping me out.
Ok after looking into your event logs, you are definitely have an issue with your hardware. My first focus would be on looking at the power requirements of your Video Card and whether your current PSU (power supply) can maintain the needed power. This relationship is extremely important if you have overclocked your video card or motherboard as power requirements will go up. Assuming the parts are fairly new and in good working order, I would next test the GPU / CPU temperature. From your description of the crash, it sounds to me as if the GPU is drawing too much power OR overheating when the material editor goes to compile and the CPU protects itself by forcing a restart.
I do not believe it would be a CPU or Memory problem as you would be getting Windows Blue Screens if those components failed.
Thanks for looking into this. I did some research into the Critical event and it does seem to be power related. Nothing is overclocked and my PSU should be able to supply more than enough power, so either it is faulty or something else in the chain is causing the error (power strip/outlet).
I’m sure it will be easy enough to resolve either way. Thanks for your time and pointing me in the right direction, you were really helpful.
