◀ PrimeChain | Verify Prime Numbers | LESS THAN 500 COINS CREATED PER DAY ▶

[AngelLox]

Okay, tried adding conf file with no luck. Still zero connections. Not sure what extension I should use.
Tried .txt and .conf neither names in roaming app, seems to work. Had no conf file before, just stopped downloading
new blocks, with zero connections. Nothing in RPC commands allows one to add nodes that way either. Not pinging
to try and find connections either.

Make sure your conf name is right with capitol letters and everything? To be sure i always use the exact name of the wallet folder for the .confs

[MoreBloodWine]

@IGS

Noticed you removed your out of town post that you'd be keeping an eye on the thread.

Anyway, the previous install it ran fine for a while. Re DL'd the client from the main post here.

On a brand new install with nothing done but MBAM, MS Security Ess., and BTC, DOGE, LTC & GRID clients.

It's doing it again but with this "new" little window.

Try this:  Open and Run your command prompt as administrator (Your PC's cmd.exe NOT the wallet console)

At the prompt type: BCDedit.exe /set increaseUserVA 2800

Hit: enter

Prompt should read:  "The operation completed successfully."

Restart your machine.

The error should be fixed.

That'll do what exactly ?

Before the fresh os, it did the "stop" thing. The cc++ thing started after the clean os install.

[cjmoles]

@IGS

Noticed you removed your out of town post that you'd be keeping an eye on the thread.

Anyway, the previous install it ran fine for a while. Re DL'd the client from the main post here.

On a brand new install with nothing done but MBAM, MS Security Ess., and BTC, DOGE, LTC & GRID clients.

It's doing it again but with this "new" little window.

Try this:  Open and Run your command prompt as administrator (Your PC's cmd.exe NOT the wallet console)

At the prompt type: BCDedit.exe /set increaseUserVA 2800

Hit: enter

Prompt should read:  "The operation completed successfully."

Restart your machine.

The error should be fixed.

That'll do what exactly ?

Before the fresh os, it did the "stop" thing. The cc++ thing started after the clean os install.

Did you try it?  It just releases more memory for your cache....Your Boot Configuration Data...too much to get into...just try it...you can always reset back to default.

[MoreBloodWine]

@IGS

Noticed you removed your out of town post that you'd be keeping an eye on the thread.

Anyway, the previous install it ran fine for a while. Re DL'd the client from the main post here.

On a brand new install with nothing done but MBAM, MS Security Ess., and BTC, DOGE, LTC & GRID clients.

It's doing it again but with this "new" little window.

Try this:  Open and Run your command prompt as administrator (Your PC's cmd.exe NOT the wallet console)

At the prompt type: BCDedit.exe /set increaseUserVA 2800

Hit: enter

Prompt should read:  "The operation completed successfully."

Restart your machine.

The error should be fixed.

That'll do what exactly ?

Before the fresh os, it did the "stop" thing. The cc++ thing started after the clean os install.

Did you try it?  It just releases more memory for your cache....Your Boot Configuration Data...too much to get into...just try it...you can always reset back to default.

Tried with no change, same c++ and "stopped" thing.

So how do I default bcd ?

[prfields6038]

Been off line for a couple of days, who won the lotto?

[forzendiablo]

im selling all my coins now

[Jugg3]

im selling all my coins now

You dont need to say that its ok, there will be someone else picking it up.

[MoreBloodWine]

@IGS

Noticed you removed your out of town post that you'd be keeping an eye on the thread.

Anyway, the previous install it ran fine for a while. Re DL'd the client from the main post here.

On a brand new install with nothing done but MBAM, MS Security Ess., and BTC, DOGE, LTC & GRID clients.

It's doing it again but with this "new" little window.

Try this:  Open and Run your command prompt as administrator (Your PC's cmd.exe NOT the wallet console)

At the prompt type: BCDedit.exe /set increaseUserVA 2800

Hit: enter

Prompt should read:  "The operation completed successfully."

Restart your machine.

The error should be fixed.

That'll do what exactly ?

Before the fresh os, it did the "stop" thing. The cc++ thing started after the clean os install.

Did you try it?  It just releases more memory for your cache....Your Boot Configuration Data...too much to get into...just try it...you can always reset back to default.

Tried with no change, same c++ and "stopped" thing.

So how do I default bcd ?

?

Been off line for a couple of days, who won the lotto?

I'll find the post when I'm home.

[iGotSpots]

im selling all my coins now

..he said as the price trends upwards

[iGotSpots]

@IGS

Noticed you removed your out of town post that you'd be keeping an eye on the thread.

Anyway, the previous install it ran fine for a while. Re DL'd the client from the main post here.

On a brand new install with nothing done but MBAM, MS Security Ess., and BTC, DOGE, LTC & GRID clients.

It's doing it again but with this "new" little window.

Try this:  Open and Run your command prompt as administrator (Your PC's cmd.exe NOT the wallet console)

At the prompt type: BCDedit.exe /set increaseUserVA 2800

Hit: enter

Prompt should read:  "The operation completed successfully."

Restart your machine.

The error should be fixed.

That'll do what exactly ?

Before the fresh os, it did the "stop" thing. The cc++ thing started after the clean os install.

Did you try it?  It just releases more memory for your cache....Your Boot Configuration Data...too much to get into...just try it...you can always reset back to default.

Tried with no change, same c++ and "stopped" thing.

So how do I default bcd ?

I have a feeling your cpu is overheating or you have a bad ram stick. I meant hardware, not software

[MoreBloodWine]

@IGS

Noticed you removed your out of town post that you'd be keeping an eye on the thread.

Anyway, the previous install it ran fine for a while. Re DL'd the client from the main post here.

On a brand new install with nothing done but MBAM, MS Security Ess., and BTC, DOGE, LTC & GRID clients.

It's doing it again but with this "new" little window.

Try this:  Open and Run your command prompt as administrator (Your PC's cmd.exe NOT the wallet console)

At the prompt type: BCDedit.exe /set increaseUserVA 2800

Hit: enter

Prompt should read:  "The operation completed successfully."

Restart your machine.

The error should be fixed.

That'll do what exactly ?

Before the fresh os, it did the "stop" thing. The cc++ thing started after the clean os install.

Did you try it?  It just releases more memory for your cache....Your Boot Configuration Data...too much to get into...just try it...you can always reset back to default.

Tried with no change, same c++ and "stopped" thing.

So how do I default bcd ?

I have a feeling your cpu is overheating or you have a bad ram stick. I meant hardware, not software

I seriously doubt any of that. I can run any program I want on top of what I do now and get no issues heat / memory issues. As much as I like your coins they're the only ones to have ever given me issues... BUCKS and now this.

But ya, no heat / ram issues to speak of as I can bog down everything and not miss a beat but soon as I load PRIME, it might run for a few mins then BAM... dies.

@cjmoles: So how do I default bcd ?

[iGotSpots]

I dunno what to tell you, sorry. I haven't seen any other issues from anyone else to get a common symptom. If anyone else has wallet issues, please post, both positive and negative experiences so I know what can be kept/cut

BUCKS and PRIME are as different as you can get client-wise, so if both gave you issues, it is 100% to be local and not a problem with the wallets themselves

Other than software (which you eliminated) and hardware, I am not sure what to suggest next. I would try cleaning cpu cooler and un/reseating all ram sticks in case one wiggled loose (most likely)

[MoreBloodWine]

I dunno what to tell you, sorry. I haven't seen any other issues from anyone else to get a common symptom. If anyone else has wallet issues, please post, both positive and negative experiences so I know what can be kept/cut

BUCKS and PRIME are as different as you can get client-wise, so if both gave you issues, it is 100% to be local and not a problem with the wallets themselves

Other than software (which you eliminated) and hardware, I am not sure what to suggest next. I would try cleaning cpu cooler and un/reseating all ram sticks in case one wiggled loose (most likely)

I reseated RAM when I got the system and CPU was as clean as they get when I hooked it up some months back. Really wish I knew what was up though because I can run 20 instances of any one client but I run one of prime and I'm lucky if it stays up for more than 10 minutes. Might just try a laptop with Linux if you can please get me a Linux Qt.

Really need the other guy to chime in about default BCD though.

[shogdite]

Im having the same wallet problem. I deleted it and downloaded it again and it worked till I tried to send coins. Then it broke. What should I do? I cant even send coins out so im starting to feel locked in a box.

[iGotSpots]

Im having the same wallet problem. I deleted it and downloaded it again and it worked till I tried to send coins. Then it broke. What should I do? I cant even send coins out so im starting to feel locked in a box.

Thanks for report. I will be out of town for a few weeks, but when I get back I will keep trying to narrow it down. If possible, please keep me posted on performance

Try sending from debug window and see if it still freezes

sendtoaddress ADDRESS AMOUNT

Before I left, I had two running on Mint and Windows 7, but I am unable to replicate this myself still on either OS. Don't worry, I'm not going anywhere. When I get back into town, we will get it sorted

[shogdite]

Im having the same wallet problem. I deleted it and downloaded it again and it worked till I tried to send coins. Then it broke. What should I do? I cant even send coins out so im starting to feel locked in a box.

Thanks for report. I will be out of town for a few weeks, but when I get back I will keep trying to narrow it down. If possible, please keep me posted on performance

Try sending from debug window and see if it still freezes

sendtoaddress ADDRESS AMOUNT

Before I left, I had two running on Mint and Windows 7, but I am unable to replicate this myself still on either OS. Don't worry, I'm not going anywhere. When I get back into town, we will get it sorted

Ok I can wait a week. Please post an update as soon as possible when you get back please.

[iGotSpots]

It will probably be about two weeks, one of my events was postponed, but if you two can figure out what you have similarly for system setup it will help me out a ton for where to look/how to replicate it

[MoreBloodWine]

It will probably be about two weeks, one of my events was postponed, but if you two can figure out what you have similarly for system setup it will help me out a ton for where to look/how to replicate it

I really don't know what to tell you about setup.

Win 7 64 bit clean install all updates done.

Other that than I have MBAM, MS Security Essentials and the following clients.

BTC, LTC, DOGE & GRID and just started running CAT which is going without missin a beat.

[iGotSpots]

Ah nice you grabbed CAT. Told you it worked well  ;p

When I get back I can give you a script to compile on Linux if you dont know how since you said that was an option. Just on my phone and my gfs shitty laptop til then. If you don't wanna wait, you can copy the old BALLS script for the Pi wallet and just rename BALLS to PRIME and it should work on both desktop and arm systems (uses qt4 so no issues there, specifically to make arm use easier)

[MoreBloodWine]

Ah nice you grabbed CAT. Told you it worked well  ;p

When I get back I can give you a script to compile on Linux if you dont know how since you said that was an option. Just on my phone and my gfs shitty laptop til then. If you don't wanna wait, you can copy the old BALLS script for the Pi wallet and just rename BALLS to PRIME and it should work on both desktop and arm systems (uses qt4 so no issues there, specifically to make arm use easier)

I'll just wait because I'm not missing much stake wise, and the downtime should earn me weight even if I'm not running so all I'm missing is the shot at a prime I'd probably never get. But ya, linux qt is an option since I have the build laptop from BUCKS goin to no real use.

SO ya, I'll wait til ur back to get me a linux qt or w/e.

As for CAT, I don't know that I'd say it works well yet as I'm still fuzzy on parts of it but it seems to work ok.

Playing with it on a trex coin atm since c-cex isn't part of it.