Right but that was in X2 and Alex seems to have confirmed it was a reproduceable problem up to X3d but hasn't had it in X3e. I think it may have even been logged on one of the "fixed" lists for one of the patches (but I am not sure). So if it does remain in X3e then it needs to be confirmed that it is still a problem for some users. It may be hardware/configuration specific at this point and you may be the answer to it getting solved. If you can't provide a recipe (because sometimes these things are intermittent) then at least report it to them with your system specs and as much detail as you can and maybe they can pinpoint it themselves.
 
I'm on your side, man. I had a lot of the same issues you did throughout the X2 fiasco. I'd like the last of those quirks stamped out of existence as I'm sure the Bakers do as well.
 
Cheers.

ok...So when you upgraded to X3x...Did you do a complete reinstall of Win?...
 
Here is my problem...I was trying out this Thunderbolt system with many DAWS...It was working sort of smashingly...until I started getting into the use of my plugins...
 
 I cloned the Drive from a different system, which brought the Machine ID along with it, into the new Board and builds I now have/had in use below, in my spec.
 
On the old system, Acid Pro 7.0e continually crashed....And screwed up a lot of data in the OS, with data dumps, and Sonar along with it...So as to cause issues with other things, when I used it.
 
Any way the new Build with the cloned drive...I had a tech geek in to try to solve the error events...Not Possible, using Arconis bare metal backup, to fix the machine ID...which it did do!...the os was corrupted...but it worked fantastically for awhile in record mode and play back in sonar x3e..with thunderbolt and firewire adapter.
 
I got MS to remote view...Again not possible to solve for the issues the board and its drivers were throwing up in error reports in event viewer, with the cloned drive.
 
So I  did a Bios update, reinstalled the OS win 7 64 bit...And then tried to put all the new drivers for the board, downloaded from ASUS....Some of those Drivers would not install properly....So as a Raw Build, I went back to MS Tech support , to have them Remote control, and seek out the issues...With nothing installed other that Drivers that would install, and those that would not, and some MS updates....It took 4 days to solve with a level 3T tech ...and get the system working properly.
 
Just installing Drivers...MS did something in the device manager...to show Ghost Devices...Not sure what he did...but I could see solid devices, and some kind of greyed out...The greyed out ones were Ghost device drivers put in, that were conflicting with the installed Drivers....As I tried several times to install what I thought were the most up to date Drivers for my Motherboard...which seemed not to want to install on this system they were designed for.
 
MS is still scratching their heads, Most likely?
 
So you see...It is not always the Software, or the OS, or the Board, or devices upon it....Sometimes it is Just Pilot error...Sometimes it is all of the above....
 
 
So no worries...There are ways to find out....Just have to make the move...and dig in..or do not ...the problem remains...only until solved for....And for that solution someone with the issue has to dig into it...and post up...all info as best they can...or tell the builders...or get a tech head onboard to seek out ...
 
Just saying...Somethings are not always evident to the eye of the beholder, until uncovered by those who see, or have the tools to do so , and know how to use them!....
 
 
Again nothing But blessings, in wishing you that Bliss we all seek!

I looked into this further, looks like my memory failed me, the issue I was thinking about was lag with the now time... which was fixed in X3E. Sorry.
 
So this is a different issue, I'm not familiar with any steps to reproduce an issue with a disappearing now time marker.
 
BTW I would consider updating your display drivers, and making sure Windows update is up to date (including most of the optional updates) at this point. Cheers...

When updating drivers...Remove/uninstall the old, and put in the new....right?

here is something to look into...it helped me, just recently as I said.
 
http://www.symantec.com/business/support/index?page=content&id=TECH63808

I'm not understanding what Les is on about here to be honest (sorry Les).


I just want to refer to post #10 here in regards to the next course of action.
After referring to post #10, the only other thing I would consider right now is updating your display drivers, and make sure Windows update is up to date (including most of the optional updates) at this point. I would not do anything else...
 
Cheers...
 
Alex

Bottom line,  there's no point complaining about an issue if your not willing to put time in and follow advice given here on how to resolve it.
I visit and read this forum every day and have yet to read a thread with a disappearing Now Time marker.
And I agree the first place I'd look is my Video display drivers,
Or at my DPCLatency. Run the DPCLAT test and see if some background process is interfearing.

Just to make sure, when being addressed to update Video Drivers, Or system Drivers...is best to uninstall old ones.... Alex, >..not much to understand really in that post....Right?...And if one does not do that correctly...Ghosting Devices will be installed...and cause Issues!....As I said....So...Take it from there people....And may you all find Bliss...Perhaps?...Sometime it starts at the beginning of installation of WIN...and Drivers...unsuppectingly seeming normal procedure for the OS to do ...and then most move to install the board's latest drivers and software...Not knowing some devices have been installed by MS doing its things, once it finds a path to update....And usually does install its own versions of Drivers, before one boots up for the first time in that installation.....Wink wink....So are we on the same page?....Probably not...but you will be soon!
 
 
Cheers!

I remember an issue with the disappearing now time marker, both personally and reported on here.
 
It was quite a while ago, though.  Possibly X2, if not X1.
 
I have certainly not experienced it with X3e, or seen any other posts about it.  I would have thought that if this were still a general issue with X3e, then some forum members would be bringing it to our attention on a regular basis.
 
As it doesn't appear regularly, then there must be something else afoot with your system, I would have thought. 
 
Contacting Support is probably your best option.

@Sir Les - Well NVidia driver nowadays come with a clean install option nowadays. I'm not sure about other install packages from other manufacturers. I'm certainly not against clean reinstalls. I doubt any other device drivers would cause the issue. If there was a firmware upgrade for the graphics card that is a possibility as well but I don't normally give that out as general advice (firmware updates for graphics cards can be a different kettle of fish compared with other firmware updates which are quite consumer friendly nowadays).
 
Cheers..