Jump to content
Axis3600

Breakpoint was hit (0X80000003)

Recommended Posts

Hello,

It's been 2 flights that I receive an error message on approach (FL100) I have absolutely nothing touched the parameters except that I activated the HT (I7 10700K).
DX11 driver 516.94.

Sans-titre.png

Message:

Expectation Breakpoint

A breakpoint has been reached.

(0x0000003) occurred in the application at location 0x00007FF7A4250682

Do you know where this message can come from that I never got before?

Edited by Axis3600

I7 10700K 5.1 GHz / GTX 1080 8 Go / 32 Go RAM 3200MHz / MSI MPG490 Gaming Plus / Samsung 970Evo M.2 500Go.

Share this post


Link to post
Share on other sites

Could be a compilation error. Break points are built into a program during debugging to stop the program and see if everything works correctly.

Since it is the GPU that triggered the error: try updating the driver of your graphics card. I had a CTD with SU10 on my first flight, and the problem disappeared after I did that.

Peter


(MSFS 2020, i7-10700KF, GTX 3080, 32 GB ram)

Share this post


Link to post
Share on other sites

So I have to switch to 517.40? I wanted to wait for the game ready to try DX12 for the moment I stay in DX11 the fact of having activated hyper threading has nothing to do?


I7 10700K 5.1 GHz / GTX 1080 8 Go / 32 Go RAM 3200MHz / MSI MPG490 Gaming Plus / Samsung 970Evo M.2 500Go.

Share this post


Link to post
Share on other sites

I had that with the new NVidia studio driver and DX12. I've rolled back the driver and gone back to DX11.

Share this post


Link to post
Share on other sites
14 minutes ago, jarmstro said:

I had that with the new NVidia studio driver and DX12. I've rolled back the driver and gone back to DX11.

The problem is that I never activated DX12 and I kept my pilot which had been stable for hours and hours of flight...


I7 10700K 5.1 GHz / GTX 1080 8 Go / 32 Go RAM 3200MHz / MSI MPG490 Gaming Plus / Samsung 970Evo M.2 500Go.

Share this post


Link to post
Share on other sites

Yes I've just realised that. Hmm. Maybe I'll give the new driver and DX12 another go. These error messages are new. Before,  the sim would just CTD and I'm wondering how reliable they are?

Edited by jarmstro

Share this post


Link to post
Share on other sites

Well, I did a DSIM and SFC/SCANNOW cleanup as well as CHKDSK /r I had no errors, I disabled the HT even if it's not the cause, you never know... And I changed an 8K texture to 4K never know too, I'll let you know if I have another issue and in that case I'll download the latest studio driver.


I7 10700K 5.1 GHz / GTX 1080 8 Go / 32 Go RAM 3200MHz / MSI MPG490 Gaming Plus / Samsung 970Evo M.2 500Go.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...