Some new information to add, the program only crashes if I have alternating P-1's. I had set the program up to run a 45M P-1, 7M P-1, 45M, 7M... after each 7M it would crash trying to start the next 45M. So I set it up to run the last 7 7M I had and then do all the 45M. The program has completed all the 7M and done 3 45M and not crashed once.

If it's that weird I suspect we'll require George to answer this one. It's certainly way beyond me.

bcp,
Looks like it might actually be a problem with Windoesn't...you are up to the latest patches, right?

[QUOTE=Christenson;281044]bcp,
Looks like it might actually be a problem with Windoesn't...you are up to the latest patches, right?[/QUOTE]

I know SP2 has been installed, and every day or 2 there seems to be more, so if not, it must be close.

[QUOTE=bcp19;281099]I know SP2 has been installed, and every day or 2 there seems to be more, so if not, it must be close.[/QUOTE]SP3 came out in 2008.

Testing the new 27.1 on my 2500 and it came back:
[code]Problem signature:
Problem Event Name: APPCRASH
Application Name: prime95_271.exe
Application Version: 27.1.1.0
Application Timestamp: 4edf1c41
Fault Module Name: prime95_271.exe
Fault Module Version: 27.1.1.0
Fault Module Timestamp: 4edf1c41
Exception Code: c0000005
Exception Offset: 01c4821a
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160
[\code]

System is a build, P67B3 motherboard, 2500K, 8GB ram, Vista (completely up to date, check for updates comes up empty). From what I have been noticing, I think it has something to do with memory allocation/drallocation. Since this is a 32 bit program I had to drop down to 3600 on memory, but upon completion of a 47M P-1/start of another it crashed. I'm going to reboot and set memory to 2000 and see how it fairs.

Have you tried running Memtest? That's pretty much guaranteed to pinpoint whether or not it's a memory issue.

[QUOTE=Dubslow;281443]Have you tried running Memtest? That's pretty much guaranteed to pinpoint whether or not it's a memory issue.[/QUOTE]

Did you not read bcp19's original post? Obviously not...

"Even though the system is only a couple weeks old, I downloaded memtest last night and ran it for 12 hours. It completed 8 passes on the memory with no errors, so I am now checking with the people who understand programming far more than I do to see if a possible solution can be found.

My suggestion, and it's not meant as flippant... Have you tried running Linux and mprime?

Whoops. Read the first paragraph -- not the stuff below the quotes :blush:

Perhaps, bcp19, you should just ignore everything I post in this thread

[QUOTE=chalsall;281444]Did you not read bcp19's original post? Obviously not...

"Even though the system is only a couple weeks old, I downloaded memtest last night and ran it for 12 hours. It completed 8 passes on the memory with no errors, so I am now checking with the people who understand programming far more than I do to see if a possible solution can be found.

My suggestion, and it's not meant as flippant... Have you tried running Linux and mprime?[/QUOTE]

I know absolutely nothing about Linux and in a lot of ways do not have the time to learn it.

Program just completed it's last run of a 47M exp and crashed again with 2GB memory selected. I recently installed MVS10 and clicked the debug option when it crashed and it came up with "Unhandled exception at 0x0204821a in prime95_271.exe: 0xC0000005: Access violation reading location 0x04332000." My knowledge of programming is woeful, so this means nothing to me, but it may be usuable to others.

In with my deallocation theory, I noticed that there is 1.6 GB of memory in use which + the 2 GB I allocated for the P-1 means that if the program for some reason could not reuse the memory it just used, that there is not enough below 4GB (being a 32 bit build) for it to allocate another 2 GB. Rebooting and trying again with 1GB allowed.

FWIW, on my father's computer we recently encountered a pair of 4 GB DDR3-1333 RAM sticks which survived 1 hour of memtest without any errors (a memtest triggered after a number of blue screens in Win 7), but miserably failed at the mprime torture test (4M-8M FFT, use 7000 or 7500 MB of RAM) under Linux after about five seconds of such treatment.
We returned the faulty sticks to the reseller, and bought other sticks instead, which survived hours of the same treatment, and also hours of msieve with a 4.6 GB matrix - so we declared the new chips good enough :smile: