CheesePoofs
Diamond Member
I posted this in general hardware, but got few replies so I'm going to try here ...
I was running memtest to test my new OC (265*9=2385mhz, mem at 170mhz) and it froze on test 5. By froze, I mean the time stopped going, percent done didn't change, and I couldn't enter the menu, but the plus sign after memtest continued blinking.It said the test was 25% done, the pass was 92% done. It was in its second pass. This is impossible though, test 5 is only halfway through.
I restarted the computer and just ran memtest again, just test 5 this time. On the fourth pass, it again froze at the test being 25% done, pass 92% done. This is also impossible, because since I was only runnign one test, if it was 25% done with the test it'd be just about 25% done with the pass.
This all happened on the system in my sig. The ram is rated at pc3200, and it was running at the pc3200 timings with 2.8v.
I'm using the memtest that came with my bios, I believe its version 1.51.
I didn't know memtest stalled at all, let alone twice in the same way, so is this just a bug in the program?
I was running memtest to test my new OC (265*9=2385mhz, mem at 170mhz) and it froze on test 5. By froze, I mean the time stopped going, percent done didn't change, and I couldn't enter the menu, but the plus sign after memtest continued blinking.It said the test was 25% done, the pass was 92% done. It was in its second pass. This is impossible though, test 5 is only halfway through.
I restarted the computer and just ran memtest again, just test 5 this time. On the fourth pass, it again froze at the test being 25% done, pass 92% done. This is also impossible, because since I was only runnign one test, if it was 25% done with the test it'd be just about 25% done with the pass.
This all happened on the system in my sig. The ram is rated at pc3200, and it was running at the pc3200 timings with 2.8v.
I'm using the memtest that came with my bios, I believe its version 1.51.
I didn't know memtest stalled at all, let alone twice in the same way, so is this just a bug in the program?