uncontrolled bed temp

Hey guys...so I am printing in pla with first layer temp of 60c and 65c after that in slic3r. After 5-10 minutes of printing the temp of my heatbed jumps to around 110c and stays there consistently...The temp is so high that it causes my prints to lose adhesion to the bed. What could be causing this? I ran PID Autotune for the bed but it made no difference. Could it be an error in the marlin settings, a bad thermistor, a glitch in pronterface, or something else?????

p.s. Im running a RAMPS 1.4 board

Did you look in your gcode to see if bed temp is told to increase? That will give you a better idea of the where the problem is.

how would I go about doing that...do I need some sort of editor to read the files??

you can open them with notepad. Pronterface has an editor under tools.
you are looking for M140 Sxxx.

IT says s65 so its setting the temp correctly in slic3r

Try using Cura once.
I get warnings in Cura, when I have some "tweek@z" in memory from the last print job.

I assume, "tweek@z" -function is implemented in slic3r too?
-Olaf

hmm...ill try cura later today...but something else wierd is going on...so in slic3r i just set a print to print without the heated bed at all...so once in pronterface I printed the object and as the object prepared for printing, it bypassed the bed heating step and skipped directly to the nozle heating stage just as it was supposed to but once i started the print, I noticed that the heated bed turned on and heated to that same 110c temp and maintained it...Ive gone through the marlin config.h file line by line and nowhere do I see this number listed....wth is going on?????

You have bugged up slic3r, that´s what´s going on!
Try Cura once or reinstall slic3r.

lol...well...ive tried Cura and I like it alot more...the bed temp seems to stay quite constant....but its not printing properly...it starts out t fine and then starts doing these wierd jagged zig zag lines and printing multiples with some of the copies overlapping what is already there...ive seen others have this problem on youtube...but i dont remember ever seeing a solution