Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

BSOD clock error cause?

Featured Replies

Occasionally I get a Blue Screen Of Death, whilst flying the 747-400X, with the message which says something like "a clock synchronisation from a subsystem failed". I have the uiautomationcore.dll of the correct level installed on my Win7-64 PC.

 

On restart, the flight continues as normal.

 

Is this more likely to be caused by the underlying Win7 or FSX than by the PMDG software?

 

Any help would be great from someone with relevant expertise!

 

Cheers, R

Cheers, Richard

Intel Core i7-7700K @ 4.2 GHz, 16 GB memory, 1 TB SSD, GTX 1080 Ti, 28" 4K display

Win10-64, P3Dv5, PMDG 748 & 777, Milviz KA350i, ASP3D, vPilot, Navigraph, PFPX, ChasePlane, Orbx 

Personally I run windows 8 64bit with fsx and pmdg products no problem at all, you tried running the program full administrator rights and compatabilty for windows vista or xp that might help

 

Paul

Paul,

 

Flying The Virtual Skies Since FS95

BSOD could well be hardware? possibly a faulty ram stick, rum memtest for a while to see if that fails. Orthos is good for stress testing a machine too.

Banner_FS2Crew_NGX_Driver.jpg

Blue screens of death are triggered by unrecoverable faults during the execution of kernel mode code, i.e. device drivers or NT kernel routines, for example. FSX and all PMDG software runs entirely in user mode, and as such cannot directly trigger a BSOD. It can precipitate one, though, by calling driver API routines that expose the underlying fault (either caused by a poorly coded driver or defective hardware). However, don't waste your time tinkering with FSX or any addon in order to resolve the issue; you'll be barking up the wrong mode.

 

In short: a BSOD is always the result of issues with either your kernel mode drivers and code, your hardware, or both.

 

Further information about the distinction between user and kernel mode: http://msdn.microsoft.com/en-us/library/windows/hardware/ff554836%28v=vs.85%29.aspx

 

Information about analyzing BSOD crash dumps (a.k.a. "minidumps"): http://support.microsoft.com/kb/315263

  • Commercial Member

Petja - you deserve an award for being one of the first users here I've ever seen articulate this 100% correctly.

 

BSODs are almost always the result of hardware or driver issues. Common causes we see at support:

 

- Unstable overclocking of the CPU, GPU or RAM.

- Overheating of the CPU, GPU or RAM.

- Bad RAM.

- Power supply issues causing the CPU to not receive the proper voltage.

- Corrupt or otherwise buggy drivers.

Ryan Maziarz
devteam.jpg

For fastest support, please submit a ticket at http://support.precisionmanuals.com

I've had a very stable FSX system for quite a while (with overclock) but a couple months ago I started getting BSOD's after around 2 hours into flights which was very frustrating. After piles of testing and much trial and error it iurns out one of my RAM modules was faulty and causing it. Now I am back and stable again.

Jay Vorkapic

 

pmdg_trijet.jpg

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.