XMP causing CTDs. Also new microstutters have appeared

[109Sqn 1,557]

14 minutes ago, Maxis said:

So it looks like you're gonna have to get your hands dirty and MANUALLY overclock/set  the ram to the XMP specs.. If your down to try ill help .. If your not .. We can try the DDR4 3200 that you have in the other rig. Mind you .. the timings that you have in the 64gig kit is kinda awful anyway (sorry for being harsh ) so what are the xmp timings on the 3200 kit ?

I'm open to help, thanks.

Don't apologise - it's the system and Corsair setting those timings, not me!😄

The 3200 is Corsair Vengeance ‎CMK16GX4M2B3200C16. . Corsair state Tested latency  16-18-18-36, 1.35v (SPD 15-15-15-36, 1.25v, 2133MHz). I'm 40min into testing the 4 stick (no errors so far) but happy to quit and check the XMP timings.

...;

Right, both XMP profiles again show the same, in this case they match the Corsair default of 16-18-18-36, 1.35v. 

XMP disabled shows just 2133MHz and (under DRAM Timing Control, Primary Timings) 16-18-18-36 again.

Edited January 26, 2022 by 109Sqn

[Maxis 1,861]

Ok So you have an Asus bios

You want to go to Ai Tweaker

Enable the XMP profile then scroll down the page to the part that says DRAM Voltage .. you should be able to adjust this by using the plus or minus sign on the keyboard.. i would just add .05 volt and retest

I would tack on up to .1 volts then no more.

 

If your still not having any luck

 

Your second option is to

Enable XMP in AI Tweaker

Then start lowering the Ram speeds one step at a time until you get a stable memtest.

Here is a video .. The user in the Video is using an Asus bios as well (Note the fix is in the second half of the video around 4:12)

 

 

Edited January 26, 2022 by Maxis

[109Sqn 1,557]

Had a hiccup there when the BIOS could see the SSD with the clean OS install but didn't see it in the Boot list but I can now get into that OS again.

No wonder I couldn't change the voltages before - I've got used to BIOSes allowing mouse control, so assumed I could change the voltage by clicking in the box and typing a value!😊

I'll watch that video then get to work.👍

This could take a while...

[109Sqn 1,557]

I'm taking the night off from trying to fix this because yet another obstacle has reared its head - suddenly MemTest86+ won't run! Or, more specifically, the BIOS won't detect the root of the USB stick to enable me to boot from it, even though it still notices the Partition on the USB. Previously, it recognised the root and the partition as separate boot sources, and always booted from the root into MemTest.

[109Sqn 1,557]

Still stumped by this latest twist. I redownloaded the MemTest files in case the originals had become corrupt, but the BIOS still wouldn't recognise the root of the USB stick. Tried different USB ports and a different USB stick, but still the same problem. I even checked the BIOS was still set to recognise legacy USB, which it is (although it wouldn't have seen the USB as a boot drive if it had changed the setting back).

I'm not sure if I should try re-flashing the BIOS with the current version (if that's possible?). I'm even tempted to upgrade to Win11 to see if that  would a) allow the USB to boot to MemTest again and/or b) help with the original RAM and microstutter issues, but that seems like a desperation tactic. 

[Paul J 349]

Just an observation, 109: I also have the ASUS UEFI bios, and it does support a mouse interface - and when I went into the BIOS last week in an attempt to get my act together - mine didn't work either - the pointer 'floated' around at the bottom of the screen, responsive horizontally, but wouldn't move up the screen. Disconnecting my Logitech/Saitek Yoke and a reboot fixed it.  I'm thinking you may have some strange issue with your USB system? Maybe?

Edited January 29, 2022 by Paul J

[martin-w 3,235]

My Logitech mouse worked absolutely fine in the Z690 Apex UEFI. 

The badly warped Z690 Hero I sent back was a bit troublesome though for a while. 

 

[109Sqn 1,557]

Another update:

I decided to give up (for a while at least) trying to solve the XMP issue (and I haven't reflashed the BIOS yet) and just try running MSFS with the 3200MHz RAM (2 sticks, then all 4) at the BIOS's stock speed to see how it would behave. Well, there's been some Good, some Bad. And some Ugly.

The Good: Microstutters are gone, things are pretty smooth.

The Bad: Frame rates seem mostly good at around 40fps but occasionally drop to about 11-14fps near or on the ground. Too early to tell if the complexity of the airport or if it's addons only or default too.

The Ugly: At time, the flight is freezing - audio continues but the image freezes. But it's only the prevailing flight sounds, i.e. changing my hardware control settings (e.g. throttle) makes no audible difference. If left long enough (30s to 1 minute or so), the sim will CTD*. And if I go back to AddonLinker (which has been running during the flight) and try to relaunch the sim, it will often (but not always) say it is already running even though Task Manager no longer shows it running. The GPU is unsurprisingly running at 100% each time it freezes. SU7 had previously taken the strain off the GPU but all of a sudden it is going back up to 100% regularly. Dev Mode shows me as GPU Limited but will occasionally switch to CPU Limited and has even been rapidly flickering between the two - don't know if that is simply showing an even load between the two or not.

(* the latest CTD resulted in the good old IRQL_not_less_or_equal error which I've never had before in Win10).

Also, no idea if it's connected to any of the issues I've had recently, but Xbox Game Bar shows the correct framerate (when compared to Dev Mode) but has started freezing on a lower rate. Usually it seems to stop at about 20fps even though Dev Mode shows it running nicely at 50fps or so. I've run a Repair on Game Bar to no avail. I can live with that inaccuracy but have to be concerned that it's a knock-on effect of one or more of the problems I've experienced so far.

 

If I could at least stop the CTDs, I might be tempted to try the Win11 upgrade to see if the Alder Lake compatibility improves at least some of the performance issues.

Edited January 30, 2022 by 109Sqn

[Paul J 349]

Question: Why are you running Addon Linker while the sim is running?

[Paul J 349]

and. . . what errors does the Event viewer show?

[109Sqn 1,557]

14 minutes ago, Paul J said:

Question: Why are you running Addon Linker while the sim is running?

I usually use it to launch the sim because it confirms that it has launched. I just leave it running because it doesn't use any significant resources. I don't make any changes while running the sim though of course.

 

36 minutes ago, Paul J said:

and. . . what errors does the Event viewer show?

Must admit, I haven't been checking that. I'll have a look at the next freeze to make sure I'm looking at exactly the right timestamp.

[Paul J 349]

Hmph. Honestly, 109 - I would not be a). running AL whilst the sim is running, and b). Until you are happy that the PC is very stable with say, X-P or any of the other sims - with a default BIOS - I would not be installing MSFS - and even when confident the PC is now ok - and you feel it's ready for MSFS - do the install per the book, with zero addons, lots of "low", and then run it for a week or two - simple VFR first and progressively building up the complexities - weather, distance, graphics, lots of flying and then bring in one addon at a time.
There is a reason for the issues you're having, and just piling it all back together and hoping it's going to work, is the wrong way to do it. You need to be very methodical here - one change at a time, running tests, doing every change empirically, and making notes as you go. You might even dig up some of Nick Needham's old overclocking notes - just to read, and to glean his methodology in testing for stability under loads. There are many very smart PC builders here and around the weeb, but very few as deadly serious as Nick when it comes to testing..  
I'm sure Maxis will be reading this to, and he may well, (I hope) jump in, if or when he feels the need. Meanwhile - keep the communication here going. Ok?

pj

[109Sqn 1,557]

I'm not sure why AddonLinker would cause an issue just sitting there, but ok, for the sake of 'eliminating it from enquiries' (as the UK police say), I can shut it down before the sim loads.

I don't use X-Plane, FSX is installed but I never use it. I have a few games (Forza Horizon 4 and Forza Motorsport 7 are probably the most demanding graphics-wise) and they have shown no issues since these problems all arose.

BIOS is running at default currently. 

It's not a case of installing MSFS - it has been installed since I got this PC, before these problems and has never been uninstalled. So it's not a case of "just piling it all back together" though I get your point about 'going back to basics' with the settings and gradually ramping them up before trying with any of my addons.

 

 

Prior to reading your post, I had landed at Orbx Dundee EGPN. I then planned and started a flight from there to Orbx (Pyreegue) Glasgow EGPF (without exiting the sim), and as I began to taxi from my gate, I got a freeze and CTD. The Event Viewer says:

Quote

[Event 1000, Application Error]
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001b2372a
Faulting process id: 0x4fd4
Faulting application start time: 0x01d81635896d1114
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.21.18.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.21.18.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 12db7ab3-2c8c-4a19-8212-c67e35dda433
Faulting package full name: Microsoft.FlightSimulator_1.21.18.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

-------------------------
[Event 1000, Application Error]
Faulting application name: LogiOverlay.exe, version: 9.50.269.0, time stamp: 0x61d6a7dc
Faulting module name: amdxn64.dll, version: 8.14.10.26, time stamp: 0x5d65baa0
Exception code: 0xc0000005
Fault offset: 0x000000000005c62f
Faulting process id: 0x3850
Faulting application start time: 0x01d816234a90da2c
Faulting application path: C:\ProgramData\Logishrd\LogiOptions\Software\Current\LogiOverlay.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\u0347173.inf_amd64_278cfea1d12001d0\B346462\amdxn64.dll
Report Id: 316672bb-cfb4-492d-a008-fc5623f55f0f
Faulting package full name: 
Faulting package-relative application ID: 

--------------------------
[Event 1026, .NET Runtime]
Application: LogiOverlay.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFE48D3C62F

--------------------------
[Event 4101, Display]
Display driver amdkmdap stopped responding and has successfully recovered.

--------------------------
[Event 100, Client-Licensing]
ClipSVC service is starting.  Caller: TriggerStarted

--------------------------
[Event 101, Client-Licensing]
ClipSVC service is running.  Version 10.0.19041.1151

--------------------------
[Event 102]
ClipSVC service has shutdown.

--------------------------
[Event 217, AppModel-Runtime]
Destroyed Desktop AppX container 72041901-8216-11ec-9d67-84144db4d49d for package Microsoft.FlightSimulator_1.21.18.0_x64__8wekyb3d8bbwe.

--------------------------

LogiOverlay.exe is part of the Logitech Options software which connects my Bluetooth mouse and keyboard to this and 2 other PCs. (Edit: only this PC has been on when these freezes have occurred, so it's not trying to communicate with them).

 

amdkmdap, being the display driver, could potentially be the culprit. That's if it consistently comes up after every freeze. I did post that I'd had trouble updating the driver due to Visual C++ files missing, so I might have to revert to my previous driver if it does continue to appear in Event Viewer, and if it reverts successfully. I'll try to replicate the freezes a few more times (shouldn't be too difficult) and see if the driver keeps appearing in the logs.

Edited January 31, 2022 by 109Sqn

[109Sqn 1,557]

Replicated the above Flight Plan and completed the flight with no errors. but my next flight from Prestwick to Glasgow froze and CTDed during taxi after landing.

Quote

02:15.31
[Event 1001, Windows Error Reporting]
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffe68f9a6a8050
P3: fffff80126a6077c
P4: 0
P5: 387c
P6: 10_0_19044
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20220131-0215.dmp
\\?\C:\WINDOWS\TEMP\WER-15984187-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERED9E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERED9F.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREDAD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREDBE.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_c12b1692e63b187c25b2f4daad68239aab5ec2e_00000000_0fa57a0a-0436-48e7-a8ea-960f5ead5196

Analysis symbol: 
Rechecking for solution: 0
Report Id: 0fa57a0a-0436-48e7-a8ea-960f5ead5196
Report Status: 4
Hashed bucket: 
Cab Guid: 0

------------------------
02:15.34
[Event 1001, Windows Error Reporting]
Fault bucket 2250540151902873144, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: LogiOverlay.exe
P2: 9.50.269.0
P3: 61d6a7dc
P4: amdxn64.dll
P5: 8.14.10.26
P6: 5d65baa0
P7: c0000005
P8: 000000000005c62f
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF53F.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF649.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF65A.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF65A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF66B.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LogiOverlay.exe_fa0f5a91c7f2cc3a5e302fd9b326febc7f50_fda1167f_1b39fe90-f5b5-4d56-a108-17fbb129d1d6

Analysis symbol: 
Rechecking for solution: 0
Report Id: 41d84c0e-349e-4941-afe5-2b10e6385af9
Report Status: 268435456
Hashed bucket: 56ad716c83ac02ff9f3b865822eca638
Cab Guid: 0

------------------------
02:15.35
[Event 1001, Windows Error Reporting]
Fault bucket 1843145982036648931, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.FlightSimulator_1.21.18.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 0.0.0.0
P4: 00000000
P5: FlightSimulator.exe
P6: 0.0.0.0
P7: 00000000
P8: c0000005
P9: 0000000001b2372a
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF687.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF7D0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF7D1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF7D3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF7F3.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_2e5f911b73c3f81bab8f15fa8ce2df34f3d8d2_7727e49a_98addec7-ed49-49b2-96ba-9a1960eee870

Analysis symbol: 
Rechecking for solution: 0
Report Id: 29256e5f-18c1-4e1a-8082-877708e3b443
Report Status: 268435456
Hashed bucket: 874c744a069b2b2a59942b81587ba3e3
Cab Guid: 0

-------------------------
02:15.32
[Event 7040, Service Control Manager]
The start type of the Touch Keyboard and Handwriting Panel Service service was changed from auto start to demand start.

-------------------------
02:15.32
[Event 7040, Service Control Manager]
The start type of the Touch Keyboard and Handwriting Panel Service service was changed from demand start to auto start.

------------------------
02:15.33
[Event 9027, Desktop Window Manager]
The Desktop Window Manager has registered the session port.

------------------------
02:15.33
[Event 1026, .NET Runtime]
Application: LogiOverlay.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFE1100C62F

------------------------
02:15.33
[Event 1000, Application Error]
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001b2372a
Faulting process id: 0x387c
Faulting application start time: 0x01d816413d957349
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.21.18.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.21.18.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 29256e5f-18c1-4e1a-8082-877708e3b443
Faulting package full name: Microsoft.FlightSimulator_1.21.18.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

-------------------------
02:15.33
[Event 1000, Application Error]
Faulting application name: LogiOverlay.exe, version: 9.50.269.0, time stamp: 0x61d6a7dc
Faulting module name: amdxn64.dll, version: 8.14.10.26, time stamp: 0x5d65baa0
Exception code: 0xc0000005
Fault offset: 0x000000000005c62f
Faulting process id: 0x1900
Faulting application start time: 0x01d81640e25c937d
Faulting application path: C:\ProgramData\Logishrd\LogiOptions\Software\Current\LogiOverlay.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\u0347173.inf_amd64_278cfea1d12001d0\B346462\amdxn64.dll
Report Id: 41d84c0e-349e-4941-afe5-2b10e6385af9
Faulting package full name: 
Faulting package-relative application ID: 

---------------------------
02:15.33
[Event 263, Win32k (Win32k)]
A pointer device has no information about the monitor it is attached to.

----------------------------
02:15.36
[Event 100, Client-Licensing]
ClipSVC service is starting.  Caller: TriggerStarted

----------------------------
02:15.36
[Event 100, Client-Licensing]
ClipSVC service is running.Version 10.0.19041.1151

----------------------------
02:15.36
[Event 217, AppModel-Runtime]
Destroyed Desktop AppX container 72041b25-8216-11ec-9d67-84144db4d49d for package Microsoft.FlightSimulator_1.21.18.0_x64__8wekyb3d8bbwe.

----------------------------
02:15.36
[Event 4101, Display]
Display driver amdkmdap stopped responding and has successfully recovered.

And there is is at the end: "Display driver amdkmdap stopped responding and has successfully recovered." There's a discussion at AMD Community I will have to read through to see if it's of any help.

 

 

[Emerson67 248]

23 hours ago, 109Sqn said:

And there is is at the end: "Display driver amdkmdap stopped responding and has successfully recovered."

Try the TDR tweak: