Lockups / Reboots

Hi all,

I am trying to establish the cause of some random crash to reboot / locks up that have occurred on my father’s system. His spec is as follows: Alpine Flight Computer Systems EGLL System

There is no pattern to the lock ups… It can be on the menu screen or within flight. Generally, the first indication of an issue is the graphics on the screen lockup / go strange followed by a restart a few seconds later. It can go many hours without happening but equally happen before flying setting up the flight.

I have got some .dmp files but I am not sure how to decode these to look for clues.

So far I have ran a memory test to verify the RAM. There is an XMP profile enabled running at 3200 but other than that, everything is totally standard.

There are an awful lot of things that could make this happen, and a large amount of threads here on it.
This is a link to the main thread on the issue.

It is the #1 issue on the Bugs Feedback Snapshot

You could also ust the search function at the top right of the page for
Stutters CTD
There are a lot of returns on that topic, you will need to scan through and see if any offer some advice for your specific issue.
Good luck, let us know how you make out

2 Likes

Does it only happen with msfs? I assume you mean whole pc is restarting not just crashing to desktop.

1 Like

reboots… hmmm … It looks like a “Be quiet” pc-case … how are the fans configured ?.. in case there are original be quiet fans you might run into heat issues with the default fan-curves. May yu can try to play some hours to play with open pc case …

EDIT: short chat with @TheSevenflyer and we want mentioned that you can instead also increase the fan-speed in generall , because open pc-case can result in not optimal airflow for other compontents.
Also remember that you can set in nvidia control center a max fps limit, so that the card no allways run in full load.

2 Likes

Yes whole PC reboots. PC only has MSFS atm.

I’ve installed a bunch of updates for MSFS, installed latest Windows 10 21H2 updates etc. Now monitoring it…

I think if the reboots persist, I will run some temperature monitoring / see if there is a way to adjust fan speeds. Not sure how to do this mind you.

This may indicate an issue outside of MSFS, although you might not be noticing it elsewhere because almost nothing is making the computer work as hard as MSFS.

Some possible reasons that I’ve personally had cause graphics glitches and a restart are a misconfigured overclock, a bad memory stick, a faulty power supply, and an overheating CPU.

I’d recommend installing a monitoring tool like HWMonitor and checking CPU and GPU temperatures during flight. Above 95’C is definitely a problem. Below 80’C is definitely not a problem. In between, maybe or maybe not?

memtest64 and cinebench r23 are some programs to stress test memory and CPU respectively

you should reach out to alpine systems too and ask for their troubleshooting procedure. If you’re paying the premium for a prebuilt they should be providing premium service too

1 Like

Alpine have been working with us on this and already sent two new Crucial memory modules although the memtest I ran came back clean anyway.

I did disable Intel Adaptive Boost Technology as I read this can cause issues. Since doing this and the latest round of updates it seems better but time will tell.

I’ll definitely get HWMonitor on there.

1 Like

I didn’t mention it but graphics card hardware or driver version may be at fault. It’s a long shot, but if you have an old one lying around, and you still crash with that card, your dad’s card’s probably not the culprit

1 Like

Is there a view on enabling Intel Adaptive Boost Technology? I disabled it as I heard it can cause issues.

Is the CPU overclocked? This sounds like an overclock/temp/undervoltage issue. Not saying that is in fact the problem, but likely if the CPU is overclocked. Don’t just go throwing parts and money at this issue just yet. Also, if you are using an Nvidia card, use the 497.29 driver.

1 Like

I wouldn’t expect the gpu driver to cause a full pc restart but yeah no point just buying lots of different things.
@DeltaEcho56 how old is this pc?
Have you got any info about temps yet if seeing high temps on cpu especially maybe the cpu needs new thermal paste or isn’t seated very well.

1 Like

Thanks folks…

PC not overclocked; will need to take a look at temperatures when I’m next over.

So PC is ~3 months old. Running latest 511.65 drivers. To take this right back, there were issues from the outset with random CTD and lockups / reboots. In early January the memory was swapped to different brand (Crucial) by Alpine (even though memtest came back clean) and the reboots / lockups went away. However, my dad did notice juddering / jumpiness in the graphics during play especially at low speed.

I have another thread (High End System - Juddering Advice Sought - #6 by HRHighness4588 )where in parallel I was trying to resolve a juddering issue with the graphics. Following the guides this has improved but the biggest difference was after I tried enabling Intel Adaptive Boost Technology; this seemed to smooth things up nicely but seemingly at the cost of stability as we had three lockups / reboots so I disabled it.

Does anybody have a view on the Intel Adaptive Boost Technology? It does seem to have stabilized (too early to be sure) since I disabled this. But I think it should work with it enabled. Now of course with it enabled the temps might go up so need to look closely at that.

This thread reported issues with those drivers Fixed crashes by reverting Nvidia drivers!

2 Likes

No overclocking = stability

Power supply issue.

Start by removing any overclocking then checking Windows for updates. Then run in command prompt…

sfc /scannow

Thank you all…

At this stage, I am now able to reproduce the BSOD crash scenario almost at will… With render scaling at 200 it crashes within minutes; same at 195,190 and 185. It is stable at 180.

An example crash log is below:

From application logs:

Log Name: Application
Source: Windows Error Reporting
Date: 10/02/2022 14:33:37
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-LG4P1RA
Description:
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 124
P2: 0
P3: ffff9681a5437028
P4: be000000
P5: 800400
P6: 10_0_19044
P7: 0_0
P8: 768_1
P9:
P10:

Attached files:
?\C:\WINDOWS\Minidump\021022-4140-01.dmp
?\C:\WINDOWS\TEMP\WER-5984-0.sysdata.xml
?\C:\WINDOWS\MEMORY.DMP
?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER20F5.tmp.WERInternalMetadata.xml
?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2106.tmp.xml
?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2143.tmp.csv
?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2144.tmp.txt

These files may be available here:
?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_fc286c48eb24dd7c3d303c14fe57de28f71df6a_00000000_cab_f6c3bb64-c90f-44bd-8747-a407c526227b

Analysis symbol:
Rechecking for solution: 0
Report Id: 153d8fe7-741a-44a6-be3c-416f12469805
Report Status: 2049
Hashed bucket:
Cab Guid: 0
Event Xml:

1001
0
4
0
0
0x80000000000000

4942

Application
DESKTOP-LG4P1RA

0
BlueScreen
Not available
0
124
0
ffff9681a5437028
be000000
800400
10_0_19044
0_0
768_1

?\C:\WINDOWS\Minidump\021022-4140-01.dmp
?\C:\WINDOWS\TEMP\WER-5984-0.sysdata.xml
?\C:\WINDOWS\MEMORY.DMP
?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER20F5.tmp.WERInternalMetadata.xml
?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2106.tmp.xml
?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2143.tmp.csv
?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2144.tmp.txt
?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_fc286c48eb24dd7c3d303c14fe57de28f71df6a_00000000_cab_f6c3bb64-c90f-44bd-8747-a407c526227b

0
153d8fe7-741a-44a6-be3c-416f12469805
2049

0

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff9681a5437028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

In System Logs:

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: FlightSimulator.exe

STACK_TEXT:
ffffa90104614908 fffff80232eb422a : 0000000000000124 0000000000000000 ffff9681a5437028 00000000be000000 : nt!KeBugCheckEx
ffffa90104614910 fffff8022fa915b0 : 0000000000000000 ffff9681a5437028 ffff96819c71db20 ffff9681a5437028 : nt!HalBugCheckSystem+0xca
ffffa90104614950 fffff80232fb616e : 0000000000000000 ffffa901046149f9 ffff9681a5437028 ffff96819c71db20 : PSHED!PshedBugCheckSystem+0x10
ffffa90104614980 fffff80232eb5b51 : ffff9681a54a2ac0 ffff9681a54a2ac0 ffff96819c71db70 ffff96819c71db20 : nt!WheaReportHwError+0x46e
ffffa90104614a60 fffff80232eb5ec3 : 0000000000000002 ffff96819c71db70 ffff96819c71db20 0000000000000002 : nt!HalpMcaReportError+0xb1
ffffa90104614bd0 fffff80232eb5da0 : ffff96819c71bb20 10fb80ff00000001 0000000000000000 3c1d7602f9800575 : nt!HalpMceHandlerCore+0xef
ffffa90104614c20 fffff80232eb5ff1 : 0000000000000010 0000000000000001 0000000000000000 48ffffa847e90035 : nt!HalpMceHandler+0xe0
ffffa90104614c60 fffff80232eb525b : 0000000000000000 0000000000000000 ffffa90104614ef0 b24a05c7ffffa81a : nt!HalpMceHandlerWithRendezvous+0xc9
ffffa90104614c90 fffff80232eb7aa5 : ffff96819c71bb20 20e2c148320fc000 0ee8ba0f48c20b48 0f20eac148d08b48 : nt!HalpHandleMachineCheck+0x5f
ffffa90104614cc0 fffff80232f0d459 : b8707280000008fe a20fc93380000008 c160244489c18b44 410e750fe1830ce9 : nt!HalHandleMcheck+0x35
ffffa90104614cf0 fffff80232e064fa : 0000008e8788e0d2 37728000001efe81 b8307316e5ba0f41 a20fc9338000001e : nt!KiHandleMcheck+0x9
ffffa90104614d20 fffff80232e061b7 : ffffa90100000000 fffff80232e060ec 000000002c31764f 0000000000000000 : nt!KxMcheckAbort+0x7a
ffffa90104614e60 fffff80232c3a650 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277
ffff950f7f9f1340 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KeFlushMultipleRangeTb+0x160

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

Render-Scaling 200 ? … I hope you mean LOD instead…

Otherwise: you wrote somewhere you are at 1440p which mean: 5260 x 2880 => 15 MegaPixel , note: 4K is 8 MPixel ! In another post you mention: 3440×1440 => 6880 x 2880 => ~20MPixel

So, your BSODs come in these case definitive from an absolut overloaded GPU / system.

1 Like

Thanks for your feedback.

It was render scaling… I turned this up to get rid of jerkiness and load up the GPU. At 200 everything is silky smooth but crashes are very frequent (same signature as previous). We have lowered it and it is more stable but it has still crashed on lower settings.

Would you expect a heavily loaded system to BSOD? I might expect a CTD / bad performance but even under very heavy load if the HW was good then I wouldn’t expect a BSOD.

Have you monitored your PC temps at that load on your GPU?
That certainly would cause it.

2 Likes

I will keep the render scaling down… I did have a HWInfo screen up and temperatures weren’t wild late 70’s early 80’s on GPU.

1 Like