Stability of the latest update? (CL1904627)

Development Platform & Builds
, , ,
1

I recently downloaded and installed the latest update (CL1904627) for UE4 over the weekend and from the get go I’ve been having issues with it blue screening my laptop. 3 times during the install process and everyone now and again when ever UE4 is running. Everything seems to be fine in the editor itself but I can’t seem to pin point anything in particular that I’m doing that might be causing it.

Any suggestions? (I’ve tried logging the blue screen messages but I’m not fast enough)

Specs:
System Model: HP Pavilion dv7 Notebook PC

Processor: Intel(R) Core™ i7 CPU Q 720 @ 1.60GHz (8 CPUs), ~1.6GHz

Memory: 8192MB RAM

Card name: ATI Mobility Radeon HD 5650
Dedicated Memory: 1011 MB
DirectX Version: DirectX 11

2

You should try using either Resplendence Software - WhoCrashed, automatic crash dump analyzer or Blue screen of death (STOP error) information in dump files. to get more information. Very useful tools for figuring out BSODs!

(But it’s probably either a driver issue or overheating - a particular issue with laptops…)

3

Thanks Neil.Griffiths for the links. I downloaded “whocrashed” and its showing me more information.

These are the errors/BSOD’s I got during the installation of the latest update (Took several tries), followed by the ones from today. Hopefully this information is more useful. Thanks for the help guys/gals.

On Sun 17/11/2013 14:48:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111713-39873-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFFA808D924C58, 0x2, 0x0, 0xFFFFF80002C84BBA)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 17/11/2013 14:39:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111713-36894-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFFA808717CD28, 0x2, 0x0, 0xFFFFF80002CDA861)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 17/11/2013 14:17:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111713-27253-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF68000002C68, 0x73D00001032C5005, 0xFFFFFA800CE0A280)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 17/11/2013 14:09:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111713-25568-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFD7FFFFFFFF8, 0x0, 0xFFFFF80002C5D73B, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.*

On Mon 18/11/2013 22:36:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111813-18033-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF96000147FE6)
Bugcheck code: 0x50 (0xFFFFF900433FC458, 0x0, 0xFFFFF96000147FE6, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Mon 18/11/2013 22:36:52 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngCopyBits+0x145A)
Bugcheck code: 0x50 (0xFFFFF900433FC458, 0x0, 0xFFFFF96000147FE6, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Mon 18/11/2013 22:18:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111813-21028-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF8800554B4E2)
Bugcheck code: 0x50 (0xFFFFFA8087551030, 0x0, 0xFFFFF8800554B4E2, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

4

http://support.microsoft.com/kb/314063

IRQL_NOT_LESS_OR_EQUAL is almost certainly a driver bug. It’s probably your graphics card driver - but I’m only saying that based on my previous experience.

BUT… your other crashes (stop code 0x5 - PAGE_FAULT_IN_NONPAGED_AREA) leads me to Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA - Windows drivers | Microsoft Learn - and it really does sound like you have faulty RAM. It could also be antivirus software so I’d try removing that first…

5

Hi Micheal,

Thank you for your system information and report. I have a few questions to help narrow down potential causes. When your computer is “Bluescreening”, which error message or code is it returning? Is this a memory dump, exception error (BSoD) or something else? Are you getting a crash callstack?

Thank you,

Alexander

6

I am getting the same

7

Hello,

This is a question from the beta version of the engine. We are marking this answered for tracking purposes. If you are experiencing an issue similar to this please post a new question.

Thank you.