"The" log file? As in, like /var/log/messages or the output of dmesg?
If you only mean the program's own log, all that would be likely to show would be asserts and such where it deliberately shut itself down rather than go into an unexpected or untenable state...
If on the other hand main net needs more RAM than test net for a given sieve size, and the operating system shut you down for using too much RAM, the operating system's own log should say so somewhere...
In general if the operating system shut you down it should, somewhere, have said why.
-MarkM-
Here's the .wer file (is there somewhere else to look?) ...
Version=1
EventType=APPCRASH
EventTime=130188002101076763
ReportType=2
Consent=1
UploadTime=130188002101476786
ReportIdentifier=90e6d4ed-f13f-11e2-b1be-001cc0fa6641
IntegratorReportIdentifier=90e6d4ec-f13f-11e2-b1be-001cc0fa6641
Response.BucketId=119483045
Response.BucketTable=4
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=primecoin-qt.exe
Sig[1].Name=Application Version
Sig[1].Value=0.8.3.0
Sig[2].Name=Application Timestamp
Sig[2].Value=51e81bc8
Sig[3].Name=Fault Module Name
Sig[3].Value=primecoin-qt.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=0.8.3.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=51e81bc8
Sig[6].Name=Exception Code
Sig[6].Value=c00000fd
Sig[7].Name=Exception Offset
Sig[7].Value=0000000000b63876
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files (x86)\Primecoin\primecoin-qt.exe
UI[3]=primecoin-qt.exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=iData=1/nDumpFile=//Upload//iCab//5e9e45b16d7a4d7494b6a009e3ffccbd-374eb1ba359e4434c1816b58e399719f-4-119483045-AppCrash64-6-1-7600-2.cab/nDumpServer=watson.microsoft.com/nResponseServer=watson.microsoft.com/nResponseURL=//dw//StageFour64.asp?iBucket=119483045&szCab=5e9e45b16d7a4d7494b6a009e3ffccbd.cab&EventType=AppCrash64&BucketHash=374eb1ba359e4434c1816b58e399719f&MID=BD26F0E7-CAC8-4180-81CD-D19C0A18337C/nBucket=119483045/nBucketTable=4/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=primecoin-qt.exe
thanks for the assistance!
UPDATE : Well this is all moot now. I found that I can run hp3 just fine as high as 6553600 (with close to same testnet results as hp5 @ 6144000 <-- but is horrible setting for hp3) and able to mine live. it's a considerable amount less on PPS, but block wise it was running @ 20 every 10 minutes on testnet (vs 29 every 10 min w/hp5 - no other sievesize topped 15).
