Ue4 4.15. 2 is constantly freezing entire computer

Development Asset Creation
, ,
1

UPDATE ON THIS

I’ve been using it a while today with a few things different, and it has not freezed YET. anyways this may shed some light on the issue:

  • -ran the DDC thing in the cmd (project went from 4.12 to 4.15)
  • -stopped using a wacom tablet with unreal editor
  • -closed malwarebytes
  • closed f.lux

i’ll say if it freezes again.

After using this version of ue4 for either 1 minute or 1-2hrs,
(by using just meaning moving models around, copying, basic editor stuff, within a single level)

at a very random time it fully freezes my computer, and I have to power down fully.

Here are my specs:

  • Operating System: Windows 8.1 Pro 64-bit (6.3, Build 9600) Card name:
  • NVIDIA GeForce GTX 560 On the latest
    driver for GPU.
  • Processor: Intel(R) Core™ i7-6700
    CPU @ 3.40GHz (8 CPUs), ~3.4GHz
    Memory:
  • 16384MB RAM Available OS
    Memory:16314MB RAM

more details
I’m now running ue4 on its lowest graphical settings and doing it unlit doesn’t fix a thing…
Its basically being used like hammer editor at this point, and still constantly freezing my entire computer.

2

I have windows 10 with a 2011 -v3 cpu and mine frooze earlier baking a lightmaps… Ideal computer is 50,000 dollars plus.

3

Hello David Hyman Design,

I have a few questions for you that will help narrow down what issue it is that you are experiencing.

Quick questions:

  1. Can you reproduce this issue in a clean project?
  2. If so, could you provide a detailed list of steps to reproduce this issue on our end?
  3. Could you provide screen shots of any settings/blueprints that may be involved?
4

been using it a while today with a few things different, and it has not freezed YET. anyways this may shed some light on the issue:

-ran the DDC thing in the cmd (project went from 4.12 to 4.15)
-stopped using a wacom tablet with unreal editor
-closed malwarebytes

i’ll say if it freezes again.

5

UPDATE ON THIS - FIXED

  • It seems to have been a corrupted asset (possible a decal) that was
    causing this
  • either the shader was messed up in
    the new version OR it was refrencing
    an old map that I deleted
  • I migrated this decal and the other content to a blank 4.15 project, then
    I migrated THAT back into the main
    project, I also replaced all
    instances of this decal
  • I also ran the DDC thing in the cmd (project went from 4.12 to 4.15),
    that may have helped too.