Most of us may heard about Y2K problem,as it was one of the biggest problem for computer science and IT.

Now the date of today is 19th Jan 2015,exact after 23 years a big problem is waiting,that is Y2K38 BUG,which will occur on 19th Jan 2038 03:14:08 UTC,

The Year 2038 problem is an issue for computing and data storage situations in which time values are stored or calculated as a signed 32-bit integer, and this number is interpreted as the number of seconds since 00:00:00 UTC on 1 January 1970 ("the epoch").^[1] Such implementations cannot encode times after 03:14:07 UTC on 19 January 2038, a problem analogous to the "Y2K problem" (also known as the "Millennium Bug"), in which 2-digit values representing the number of years since 1900 could not encode the year 2000 or later. Most 32-bit Unix-like systems store and manipulate time in this "Unix time" format, so the year 2038 problem is sometimes referred to as the "Unix Millennium Bug" by association.[wiki]

Modern computers use a standard 4 byte integer for this second count. This is 31 bits, storing a maximum value of 2³¹. The remaining bit is the sign. This means that when the second count reaches 2147483647, it will wrap to -2147483648. 
The precise date of this occurrence is Tue Jan 19 03:14:07 2038. At this time, a machine prone to this bug will show the time Fri Dec 13 20:45:52 1901, hence it is possible that the media will call this The Friday 13th Bug.