8 minutes ago, mpo910 said:

I am very curiuous how this will end up.....HF3?

Crashing will stop if you get your system stable. Really, its THAT easy.

But i understand that for some its easier to pass the buck to LM.

6 minutes ago, JoeFackel said:

Crashing will stop if you get your system stable. Really, its THAT easy.

But i understand that for some its easier to pass the buck to LM.

I am VERY aware of that. First thing I do is test my system and lower down some settings. I did not pass something to LM because I always assume that the error is on my end and not on LM end.

But mostly this indicates that there is something not quite clear to users or the version is indeed instable and has some issues.

A lot of CTD messages on LM site are rushing in...more this ime as with HF1 (whatever this would mean....).

But thanks for reminding me. Alsways appreciate this.

 

Marcus

Edited June 24, 20205 yr by mpo910

3 hours ago, micstatic said:

Sure did

Are you overclocking your video card by any chance?

S.

3 hours ago, mpo910 said:

I dod not pass something to LM because I always assume that the error is on my end and not on LM end.

Didn't mean especially you with my comment.

3 hours ago, mpo910 said:

A lot of CTD messages on LM site are rushing in...more this ime as with HF1 (whatever this would mean....).

I always knew that CTD messages will also come with HF2. And they will come with every word not allowed update ... because they will be ANYTIME guys who refuse to listen to experienced users saying they should look at their unstable systems.

Sadly there is no hotfix or update which can fix stubborness. An fix for the error sitting in front of the monitor would cure A LOT of problems, and that applies to software in general.

Edited June 24, 20205 yr by JoeFackel
typo

Worth checking whether your PSU rails are stable using HW monitor, might not be related to this if ithe problem is code based but worth a try . A few years back I was getting plagued by CTDs on a new top end build with a 1080ti, I thought I had a pretty decent PSU as it was 860w rated and cost £60

Anyway to cut a long story short, I ended up observing my 12v rail whilst simming, and noticed that the V would periodically dip momentarily. This wouldn’t always crash the sim but some did coincide .

I swapped the PSU out for a gold type supply and haven’t seen any issues since (except for running an AVX offset now!)

worth a shot

11 minutes ago, JoeFackel said:

Didn't mean especially you with my comment.

I always new that CTD messages will also come with HF2. And they will come with every word not allowed update ... because they will be ANYTIME guys who refuse to listen to experienced users saying they should look at their unstable systems.

Sadly there is no hotfix or update which can fix stubborness. An fix for the error sitting in front of the monitor would cure A LOT of problems, and that applies to software in general.

No one really asked for your opinion. You simply injected it, but ok mister experienced! 

@SolRayz,

I am interested in knowing what your even viewer says when you CTD and also if you are OC your video card.

S.

9 minutes ago, kand said:

Worth checking whether your PSU rails are stable using HW monitor, might not be related to this if ithe problem is code based but worth a try . A few years back I was getting plagued by CTDs on a new top end build with a 1080ti, I thought I had a pretty decent PSU as it was 860w rated and cost £60

Anyway to cut a long story short, I ended up observing my 12v rail whilst simming, and noticed that the V would periodically dip momentarily. This wouldn’t always crash the sim but some did coincide .

I swapped the PSU out for a gold type supply and haven’t seen any issues since (except for running an AVX offset now!)

worth a shot

This is something I will be checking in the morning. Thanks for the useful advice, unlike some others, so called experienced wise guys. 

3 minutes ago, simbol said:

@SolRayz,

I am interested in knowing what your even viewer says when you CTD and also if you are OC your video card.

S.

I have gotten a few of these...

Log Name:      Application
Source:        Application Error
Date:          6/23/2020 22:52:21
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SolRayz-PC
Description:
Faulting application name: Prepar3D.exe, version: 5.0.31.35253, time stamp: 0x5eebf566
Faulting module name: KERNELBASE.dll, version: 10.0.19041.292, time stamp: 0x84cd251b
Exception code: 0xc0020001
Fault offset: 0x0000000000023e49
Faulting process id: 0x1e78
Faulting application start time: 0x01d649ea5228f172
Faulting application path: D:\P3D\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 3e5db1ba-64d5-41ef-93e1-5eb66cce2560
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-06-24T05:52:21.5657014Z" />
    <EventRecordID>5176</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>SolRayz-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>5.0.31.35253</Data>
    <Data>5eebf566</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>10.0.19041.292</Data>
    <Data>84cd251b</Data>
    <Data>c0020001</Data>
    <Data>0000000000023e49</Data>
    <Data>1e78</Data>
    <Data>01d649ea5228f172</Data>
    <Data>D:\P3D\Prepar3D.exe</Data>
    <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
    <Data>3e5db1ba-64d5-41ef-93e1-5eb66cce2560</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

This was the last crash I had for the evening. While switching to another airport. Loading would occurs successfully, then black screen and ctd with a Device Hung. Event name is D3DDRED2, which i have never seen before. 

Log Name:      Application
Source:        Windows Error Reporting
Date:          6/23/2020 23:59:29
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      SolRayz-PC
Description:
Fault bucket 1755039947168926258, type 5
Event Name: D3DDRED2
Response: Not available
Cab Id: 0

Problem signature:
P1: VEN_10DE
P2: 26.21.14.4614
P3: 0x887A0006
P4: 3
P5: Prepar3D.exe
P6: 5.0.31.35253
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5697.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER56A7.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER56B5.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER56D5.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_VEN_10DE_26fbac81cf78cffc932d7fce6a11dbe1dc167fb_00000000_93c901af-7427-4c4d-aaef-fca41cadd5ed

Analysis symbol: 
Rechecking for solution: 0
Report Id: 93c901af-7427-4c4d-aaef-fca41cadd5ed
Report Status: 268435456
Hashed bucket: a8406188f5641fe1385b2788899fca32
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-06-24T06:59:29.7454283Z" />
    <EventRecordID>5309</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>SolRayz-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>1755039947168926258</Data>
    <Data>5</Data>
    <Data>D3DDRED2</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>VEN_10DE</Data>
    <Data>26.21.14.4614</Data>
    <Data>0x887A0006</Data>
    <Data>3</Data>
    <Data>Prepar3D.exe</Data>
    <Data>5.0.31.35253</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5697.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER56A7.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER56B5.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER56D5.tmp.txt</Data>
    <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_VEN_10DE_26fbac81cf78cffc932d7fce6a11dbe1dc167fb_00000000_93c901af-7427-4c4d-aaef-fca41cadd5ed</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>93c901af-7427-4c4d-aaef-fca41cadd5ed</Data>
    <Data>268435456</Data>
    <Data>a8406188f5641fe1385b2788899fca32</Data>
    <Data>0</Data>
  </EventData>
</Event>

 

No GPU overclock on my RTX2080

Thanks will pass this on.

HF2 is pushing video cards harder, so it is important to understand a pattern here. Are you guys (people experiencing CTD) over clocking the video cards by any chance?

S.

1 minute ago, simbol said:

Thanks will pass this on.

HF2 is pushing video cards harder, so it is important to understand a pattern here. Are you guys (people experiencing CTD) over clocking the video cards by any chance?

S.

Thank you. I have also gotten a few "unknown" faulting module crashes.

Faulting application name: Prepar3D.exe, version: 5.0.31.35253, time stamp: 0x5eebf566
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0x3094
Faulting application start time: 0x01d649e3b7ba5192
Faulting application path: D:\P3D\Prepar3D.exe
Faulting module path: unknown
Report Id: 0c24d78a-d2da-4584-bf26-ded31e2d86bb
Faulting package full name: 
Faulting package-relative application ID: 

Just now, SolRayz said:

Thank you. I have also gotten a few "unknown" faulting module crashes.

Faulting application name: Prepar3D.exe, version: 5.0.31.35253, time stamp: 0x5eebf566
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0x3094
Faulting application start time: 0x01d649e3b7ba5192
Faulting application path: D:\P3D\Prepar3D.exe
Faulting module path: unknown
Report Id: 0c24d78a-d2da-4584-bf26-ded31e2d86bb
Faulting package full name: 
Faulting package-relative application ID: 

This could be related to a 3rd party add-on. In hence the fault on unknown. But it has error code 5 which is "Access denied". You running P3D as Admin?

S.

 

23 minutes ago, kand said:

Worth checking whether your PSU rails are stable using HW monitor, might not be related to this if ithe problem is code based but worth a try . A few years back I was getting plagued by CTDs on a new top end build with a 1080ti, I thought I had a pretty decent PSU as it was 860w rated and cost £60

Anyway to cut a long story short, I ended up observing my 12v rail whilst simming, and noticed that the V would periodically dip momentarily. This wouldn’t always crash the sim but some did coincide .

I swapped the PSU out for a gold type supply and haven’t seen any issues since (except for running an AVX offset now!)

worth a shot

Rare, but possible. Had that some time ago with the rig of an customer and his cheapo 1000W PSU. Swapped it for an premium 700W Enermax and his problem were gone.