How do I run Memtest86+ 1.70 iso on CD-ROM

[systemlord]

I have the Memtest86+ 1.70 iso image on my CD-ROM, but it says "Windows cannot open this file", "To open this file Windows needs to know what program created it". Is there some software that is needed? Thanks for your help!

 

[TyroneShoelaces]

You need to have the CD in your drive, then reboot the machine, and boot off the CD.

-TyShoe

 

[systemlord]

While were at it, I have been running my RAM (Crucial Ballistix PC2 8500) at 1200MHz @5-5-5-15 2.2v while playing Doom3 and other games while running Memtest (not Memtest86) the other day without one error, but today I seem to be getting errors all day, even after 6000% coverage. Chipset Timings have remained the same throughout testings. Any suggestions as to what is going on here? Thanks for your reply!

 

[systemlord]

You need to have the CD in your drive, then reboot the machine, and boot off the CD.

-TyShoe

How do I boot from CD ROM drive? I went into bios and set 1st boot device priority, but that didn't work. Am I missing something?

 

[TyroneShoelaces]

How do I boot from CD ROM drive? I went into bios and set 1st boot device priority, but that didn't work. Am I missing something?

Right after you get past the POST screen, you will probably see a message at the bottom of the screen. Something to the effect of "press any key to boot from CD". Now the hard part is finding that darn "ANY" key on your keyboard.

-TyShoe

 

[systemlord]

Right after you get past the POST screen, you will probably see a message at the bottom of the screen. Something to the effect of "press any key to boot from CD". Now the hard part is finding that darn "ANY" key on your keyboard.

-TyShoe

It says "Press any key to continue", but after that it boots to Windows and not CD drive.

 

[TyroneShoelaces]

It says "Press any key to continue", but after that it boots to Windows and not CD drive.

Sounds to me like the file may not have been burned properly, so your computer isn't recognizing that a CD is in the drive.

You need to burn the file to the CD as a bootable CD, not just an ISO CD. Details at this link... step 4.
If you have a CD-RW, try it with that so you don't keep burning coasters.

http://www.bay-wolf.com/bootcd.htm

-TyShoe

 

[systemlord]

Sounds to me like the file may not have been burned properly, so your computer isn't recognizing that a CD is in the drive.

You need to burn the file to the CD as a bootable CD, not just an ISO CD. Details at this link... step 4.
If you have a CD-RW, try it with that so you don't keep burning coasters.

http://www.bay-wolf.com/bootcd.htm

-TyShoe

This is just going Way over my head! My friend is the one with the CD-R drive, I only have a DVD-ROM drive for two years now. Why the hell is it so hard to just run a memory test, this Memtest86+ must be VERY old. How do I run two copies of Prime95, as I have tried to run both but the other one just takes over.

 

[TyroneShoelaces]

If you are using an old DVD-ROM drive, that could be the culprit, too. I had a DVD-ROM drive a couple years ago that would not read ANY burned disks of any sort. Do yourself a favor and get a DVD burner. Only $30-40 on Newegg.

If you have a floppy drive you could try downloading the floppy version. IIRC, it's a little more straight-forward on how to create a bootable floppy.

http://www.memtest.org/

-TyShoe

 

[TyroneShoelaces]

How do I run two copies of Prime95, as I have tried to run both but the other one just takes over.

When you get them both running, hit Ctrl-Alt-Del to bring up the Task Manager. Go to the processes tab. Right click on the PRIME95.EXE, and select "Set Affinity". Check only the box for CPU 0 for one instance, and CPU 1 for the other.

-TyShoe

 

[Mondoman]

It may be that your friend just burned a CD with the .iso file on it as a file. The .iso file is a whole CD *image*, essentially a snapshot of every sector on the CD. Your friend needs to burn a CD using the .iso file as the blueprint, not actually burn the .iso file itself onto the CD. Normally, you open the .iso file directly within the burning software (e.g. inside Nero, you would use the File/Open menu to open the .iso file, then burn the resulting project as a CD).
As TS suggested, the floppy version might be easier, and works just as well.
Download Orthos and use it instead of PRIME95 -- it takes care of making sure one copy of PRIME95 is running on each core.

 

[systemlord]

It may be that your friend just burned a CD with the .iso file on it as a file. The .iso file is a whole CD *image*, essentially a snapshot of every sector on the CD. Your friend needs to burn a CD using the .iso file as the blueprint, not actually burn the .iso file itself onto the CD. Normally, you open the .iso file directly within the burning software (e.g. inside Nero, you would use the File/Open menu to open the .iso file, then burn the resulting project as a CD).
As TS suggested, the floppy version might be easier, and works just as well.
Download Orthos and use it instead of PRIME95 -- it takes care of making sure one copy of PRIME95 is running on each core.

"Man I don't know if my RAMs good or bad". I ran Orthos for 14 hours with no error, but on Memtest I'M getting errors every 10-20 minutes. Before I was getting Memtest errors only at 1200MHz @2.2v so I went back to 800MHz 4-4-4-12 @2.2v and the errors are really showing up on Memtest just as much as if I was OC'ing @1200Mhz. What the hell is going on here? Is Memtest wigging out? Should I reset my cmos?

 

[systemlord]

Here is Super PI 32M test results and Orthos results> Memtest must be tripping.

 

[TyroneShoelaces]

What happens in memtest if you boot at 398 FSB or 402 FSB instead of 400? I've read in the past something about not booting at 400, or it can cause errors. NB strap or something? I haven't looked much into it, as I'm satisfied with my overclock, and nowhere near 400 FSB.

-TyShoe

 

[systemlord]

What happens in memtest if you boot at 398 FSB or 402 FSB instead of 400? I've read in the past something about not booting at 400, or it can cause errors. NB strap or something? I haven't looked much into it, as I'm satisfied with my overclock, and nowhere near 400 FSB.

-TyShoe

I have been stable at 400FSB for over 72 hours running Orthos, Everest, and Memtest but now Memtest out of the blue comes these mega errors. I've been at 400 fsb for two months now with 100% stability since day one with no strange behavor. Right now as I'm typing I'm running Orthos, Memtest, Speed Fan and IE7 with no errors, hows that for stability??

http://img68.imageshack.us/my.php?image=07162007211137kn9.jpg

 

[martyjs]

To test the memory properly you must run the bootable disk version of Memtest86+ as it tests the hardware directly. If your testing in from within Windows it can get false readings, as Windows tries to manage the memory.

 

[systemlord]

To test the memory properly you must run the bootable disk version of Memtest86+ as it tests the hardware directly. If your testing in from within Windows it can get false readings, as Windows tries to manage the memory.

So when Windows starts moving memory around that trips Memtest to produce false errors? Doesn't Windows asign memory to the running programs indipendantly?"Just when you think you knew it all, you learn something new."

 

[ALANMAN]

You should never think you know it all, thats a bad way of thinking IMO.

 

[systemlord]

You should never think you know it all, thats a bad way of thinking IMO.

That was just a figure of speach, lol.

 

[martyjs]

I work as a Computer Tech, the reason I started using Memtest is both our suppliers and the company's who supply the memory except Memtest results for RA's. Thats good enough for me.