When you say, "But two values in price attribute which are coming are 20,000 and 90,000." I assume you are talking about the two extreme price values that the software automatically fills in the 30x1 table under HB estimation "Attribute Coding + Price".
Regarding the two values in that table, the software does its best to guess what the min and max prices used were, by examining the questionnaire settings. But, if you do something complicated such as scripting your base price to be different for different segments of respondents, then it can guess incorrectly. This does not bother proper data collection and simply may be reset properly by you before computing utilities under HB.
Just change the min and max values to cover the full range of prices that were actually shown across all respondents. These extreme end points are only used for converting the price slope to discrete utility endpoints that the software moves forward into the market simulator to be used as endpoints along the price slope. When the simulator computes utility for any price point along this continuum, it uses a straightline interpolation that is faithful to the original linear utility estimation. So, everything is OK.