cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Fatal error message

SOLVED

Re: Fatal error message

Thank you, super helpful!!!!

Re: Fatal error message

Worked perfect for me too! Thank you so much!!!

Re: Fatal error message

Mahesh can you please brife me how to create opengl configuration....

Please

Re: Fatal error message

Re: Fatal error message

How could you tell what caused the crash? We have a computer that is crashing regularly, and I need to figure out what is going on.

First time was this:

Thread 7460

=====================

0x000000007777BB7A NULL (NULL:0) (ntdll:0x0000000077730000) ( 0x1eb28360, 0x69bbb1e4, 0x0, 0x1e10000 )

0x000007FEFD4F10AC NULL (NULL:0) (KERNELBASE:0x000007FEFD4F0000) ( 0x45ab2d88, 0x0, 0x0, 0x998 )

0x000007FEDEC625B9 NULL (NULL:0) (prowt:0x000007FEDCDA0000) ( 0x2354cdc0, 0x1, 0x20d14a8, 0x40 )

0x000007FEDEC57DB5 NULL (NULL:0) (prowt:0x000007FEDCDA0000) ( 0x206b2500, 0x0, 0x45ab2d70, 0x7fffffff )

0x0000000078C31DB7 NULL (NULL:0) (MSVCR100:0x0000000078C10000) ( 0x78cc1ac0, 0x206b2540, 0x0, 0x0 )

0x0000000078C31E53 NULL (NULL:0) (MSVCR100:0x0000000078C10000) ( 0x0, 0x0, 0x0, 0x0 )

0x00000000776259BD NULL (NULL:0) (kernel32:0x0000000077610000) ( 0x0, 0x0, 0x0, 0x0 )

so I assumed it was the same issue you mentioned before.

This time we didn't get the traceback.log notice, but it did create a log of the below.

Thread 5928

=====================

0x000000007777D43A NULL (NULL:0) (ntdll:0x0000000077730000) ( 0x20000, 0x20000, 0x0, 0x0 )

0x000000007774EBED NULL (NULL:0) (ntdll:0x0000000077730000) ( 0xa48410, 0x3, 0xa48410, 0xa48080 )

0x00000000776259BD NULL (NULL:0) (kernel32:0x0000000077610000) ( 0x0, 0x0, 0x0, 0x0 )

Re: Fatal error message

Hi,

I have had similar problems (Win10 x64 v1803/Creo 3 M170/Quadro P4000) when running CNC Sequence in ModuleWorks. Either the Creo crashed with "Except Acces Violation" or whole PC crashed with BSOD.

 

I have opened a case but PTC hid the head in the sand - didn't even bother to reply to my mails. What a surprise!

 

To make long story short: I have tried more than 10 drivers:

- The certified driver by PTC  for quadro 377.11 was the cause of BSOD and other problem - do not install this driver

- The newest up to day 391.89 had different glitches, but was not causing BSOD - do not install this driver either

- I have ended with 386.28 which is up to now the best for my PC and GPU

- I have always performed "Clean install" and installed only GPU driver, Nvidia control panel, Sound driver - do not install other drivers.

 

Also, I have to mention, that it was vital to change in NVIDIA Control Panel Global Presets to Dassault Systems CATIA-compatibile. Otherwise the driver would not display hidden lines correctly in Creo. What a funny think to run Creo with CATIA Settings:-)) Do not change other settings - leads often to problems with Creo and crashes.


Thank you PTC for allowing me to pay maintenance cost and not helping me at all!

Re: Fatal error message

Hi,

I have had similar problems (Win10 x64 v1803/Creo 3 M170/Quadro P4000) when running CNC Sequence in ModuleWorks. Either the Creo crashed with "Except Access Violation" or whole PC crashed with BSOD.

 

I have opened a case but PTC hid the head in the sand - didn't even bother to reply to my mails. What a surprise!

 

To make long story short: I have tried more than 10 drivers:

- The certified driver by PTC  for quadro 377.11 was the cause of BSOD and other problem - do not install this driver

- The newest up to day 391.89 had different glitches, but was not causing BSOD - do not install this driver either

- I have ended with 386.28 which is up to now the best for my PC and GPU

- I have always performed "Clean install" and installed only GPU driver, Nvidia control panel, Sound driver - do not install other drivers.

 

Also, I have to mention, that it was vital to change in NVIDIA Control Panel Global Presets to Dassault Systems CATIA- compatibile. Otherwise the driver would not display hidden lines correctly in Creo. What a funny think to run Creo with CATIA Settings:-)) Do not change other settings - leads often to problems with Creo and crashes.


Thank you PTC for allowing me to pay maintenance cost and not helping me at all!

Highlighted

Re: Fatal error message

After several hours or so of testing, I have to add that so far, the best driver is for P4000 version 385.69, which is also delivered with new HP Z4 G4 and certified (see PTC HW datasheet). Other drivers lead to different graphical glitches as seen on picture (lines going from surface to eternity).

For correct functionality I had to (after clean installation) change in Nvidia Control Panel->Global Preset to Catia-compatibile and under tab "Adjust image setting with preview" change to "Let the 3D application decide". Now it seems to work.