quick question.

[Kanabis]

hello, I would have posted this in alternate currencies but I cant yet. This is my question. My litecoin client 0.6.3c-win32 is crashing on startup. this is the error I am getting.

A fatal error occured. Litecoin can no longer continue safely and will quit.

exception: st9bad_alloc
std::bad_alloc
c:\users\Sxlosnman\desktop\litecoin-0.6.3c-win32\litecoin-qt.exe in runaway exception.

ok I have tried to re install and I keep getting the same error. this is puzzling because I had litecoin running on this system before

win 7 64bit  hd6670  dualcore amd athlon 2gig memory.

I have no idea what that error even means. is the file size trying to change ie a virus? Maybe someone with more technical knowledge can tell me more and maybe how to fix it.

I have absolutely no anti virus, I almost always know what im clicking but it wouldnt surprise me the slightest if I got one now, Ive been running alot of bitcoin and litecoin programs lately and I could dl'd something with a virus I dunno. What do you think? thanks in advance. 

oh yeah have fun hacking my wallet which will take you days and yield you about 3 litecoins and ZERO bitcoins. have fun with that.

[DarkHyudrA]

#OFF

I almost always know what im clicking

Nice description of a 100% secure way of no malware and whateverware on your PC.
#ENDOFF

I believe that like most of the uninstallers, Litecoin doesn't remove the files from "%APPDATA%/Litecoin". Downloading all the whole blocks is a pain in the a**, but some of those files could be corrupted.

oh yeah have fun hacking my wallet which will take you days and yield you about 3 litecoins and ZERO bitcoins. have fun with that.

If someone is going to hack your wallet, remember that is a program that do the work, the hard work is to "put" the program in the PC, if you encrypt your wallet, even a keyboard hook do the work

[greyhawk]

I have absolutely no anti virus, I almost always know what im clicking but it wouldnt surprise me the slightest if I got one now, Ive been running alot of bitcoin and litecoin programs lately and I could dl'd something with a virus I dunno. What do you think?

You should smoke less.

[Kanabis]

now what kinda attitude is that? thats like telling me to breath less lol. anyways im downloading avast as we speak. if i find a virus ill report back to hopefully save the next noob like me with the same problem. if its not a virus id still like someone to possibly explain to me what that error means, what its doing and obviously why its happening.

after my scan I am going to follow darkhyudra's advice and clear all litecoin files in the appdata roaming directory. iv already backed up my wallet so it should be no biggie.

[girafon]

hello, I would have posted this in alternate currencies but I cant yet. This is my question. My litecoin client 0.6.3c-win32 is crashing on startup. this is the error I am getting.

A fatal error occured. Litecoin can no longer continue safely and will quit.

exception: st9bad_alloc
std::bad_alloc
c:\users\Sxlosnman\desktop\litecoin-0.6.3c-win32\litecoin-qt.exe in runaway exception.

ok I have tried to re install and I keep getting the same error. this is puzzling because I had litecoin running on this system before

win 7 64bit  hd6670  dualcore amd athlon 2gig memory.

I have no idea what that error even means. is the file size trying to change ie a virus? Maybe someone with more technical knowledge can tell me more and maybe how to fix it.

I have absolutely no anti virus, I almost always know what im clicking but it wouldnt surprise me the slightest if I got one now, Ive been running alot of bitcoin and litecoin programs lately and I could dl'd something with a virus I dunno. What do you think? thanks in advance.  

oh yeah have fun hacking my wallet which will take you days and yield you about 3 litecoins and ZERO bitcoins. have fun with that.

Any virtualization solution involved ?

If your litecoin client runs in a VM, depending of the virtualization solution, it could be the origin of your problems.
(for example, default openvz containers won't "see" any swap, buffers or cache ; if you hit available memory limit, application may fail to allocate more memory)