Sketchup crashes ntdll.dll without BugSplat

Hi guys,

Since a while Sketchup crashes without any error.
I have no idea why. Reinstalling it doesn’t help.

Have you installed any new plugins recently? I don’t know if the plugin directory is left as it is when uninstalling SU.

I just reinstalled my graphics drivers and that didn’t work either.

It can’t be any plugin.

Does Sketchup keep error logs?

Is it just one particular file?

Sometimes a particular file will cause this, especially if you have a lot of large sized textures in it.

Try using some other files and see if you can isolate the cause.

If it is one file try changing the name (long shot) try reducing texture sizes - deleting them off and making them smaller and reapplying them - if you can keep the file open long enough.

Hey it’s not a particular file. This is so frustrating.

What makes you sure?

Plugins are gone. I had a few but I think the folder is gone…

Check for “sketchup.exe” errors in the Windows Event Viewer.
Start Menu > Administrative Tools > Event Viewer
(or go through the Control Panel)

Logs are written to “%LocalAppData%/Microsoft/Windows/WER

Somehow the Sketchup instant crashes are not logged in the event viewer. I do have one from earlier today (by the way im Dutch :slight_smile: )

Naam van toepassing met fout: SketchUp.exe, versie: 16.1.1449.0, tijdstempel: 0x56ce064a
Naam van module met fout: ntdll.dll, versie: 10.0.10586.306, tijdstempel: 0x571af2eb
Uitzonderingscode: 0xc0000374
Foutmarge: 0x00000000000ee6fc
Id van proces met fout: 0x184c
Starttijd van toepassing met fout: 0x01d213fb48e7f35c
Pad naar toepassing met fout: C:\Program Files\SketchUp\SketchUp 2016\SketchUp.exe
Pad naar module met fout: C:\WINDOWS\SYSTEM32\ntdll.dll
Rapport-id: 900ece85-d5cc-4a34-a38d-772323d24048
Volledige pakketnaam met fout:
Relatieve toepassings-id van pakket met fout:

This shows in details tab:

SketchUp.exe
16.1.1449.0
56ce064a
ntdll.dll
10.0.10586.306
571af2eb
c0000374
00000000000ee6fc
184c
01d213fb48e7f35c
C:\Program Files\SketchUp\SketchUp 2016\SketchUp.exe
C:\WINDOWS\SYSTEM32\ntdll.dll
900ece85-d5cc-4a34-a38d-772323d24048

In reply to:

http://stackoverflow.com/questions/13388350/why-is-ntdll-dll-crashing-my-c-executable

Exception code 0xC0000374 means STATUS_HEAP_CORRUPTION. It is the most common way to crash a C++ program. – Hans Passant Nov 14 '12 at 23:27

(1) Okay try the default printer reassignment trick:

http://answers.microsoft.com/en-us/msoffice/forum/msoffice_install-mso_other/office-products-crashed-upon-launch-0xc0000374/9eb1251f-5a7d-4401-a955-155ac432e6ea?tab=question&status=AllReplies#tabs

(2) If that does not work, try disabling security anti-virus software.

(3) If that is not culprit, check all hardware drivers (some bluetooth drivers have been known to corrupt the heap.)

(4) A corrupt Windows user profile can also cause this. To test, create a new administrative user account, log off your normal account, and onto the new account, and try to start the crashing application.

Hi Dan,

It has to do something with a corrupt user account!

I just opened a guest account and I could just use Sketchup again.

Now how to uncorrupt my UA?

1 Like

This usually means the account’s registry hive is corrupted.

I would copy all files from the user documents, and plugins from appdata to a thumbdrive, and create a new account for yourself. Don’t delete the old account until you are sure you’ve got everything copied over.

There are account migration tools that can help you do this. There used to be one built into Windows. It might be now at Microsoft Download site. (Was called “Migration Wizard” or similar.)
These tools are similar to a backup utility but smarter. They will automatically select all your shortcuts, all your browser profiles, your email folders, your documents, your images, etc.

How could this have happened?

Anyway, every once in a while I freshen up my windows with a clean install. Takes allot of time but probably gets rid of the corrupted stuff. Ughhh… Or I just keep using Sketchup on the guest account haha.

Cheers!

Most often when I have seen it, it was due to a trojan (malware) corrupting the registry.