Jump to content

Recommended Posts

Posted

Recently I did a ram test with memtest, that reported an error.

So my question is: could it affect my burns, and how?

 

Sometimes, while verifying a dvd, just after burning it, imgburn shows an error.

At a second verifying attempt (Verify Against Image File), with the same drive, it seems the dvd's fine (no error messages)...

Could it depend on the bad ram? And which of the two verifying should be more trustworthy?

 

Thanks in advance

Posted (edited)
They're the same function so it doesn't matter which one you use - verify after write or the standalone one.

 

Bad ram would give you miscompare errors.

 

 

So, if I got it right:

- Bad ram could affect only the verifying process (and not the burning process).

- Even if i get a miscompare error, the dvd could be fine, and the error message may be because of bad ram.

 

If I don't get any message, can I be sure that there's no miscompare error?

(I'm asking this because, sometimes, at a second attempt i get no error, and would like to know if it's enough to consider the burn ok, even if "verify after write" was unsuccessful)

 

 

Thanks!

Edited by c4fen01r
Posted

bad ram is bad ram, and needs to be fixed

 

memtest error might indicate a problem with something else tho that was causing ram to show an error

 

the list of possible causes is a long one

Posted (edited)
bad ram is bad ram, and needs to be fixed

 

Yes, of course, and I'll do it soon :)

But in the meanwhile i would like to know if i can continue to burn dvds relying on the imgburn verify process

(no miscompare errors, even if with bad ram, and even if after multiple verify attempts = dvd burned ok).

Edited by c4fen01r
Posted
http://www.majorgeeks.com/download4181.html

 

use this progam to look at your older computer and see if the temperatures and voltages are an issue?

 

your ram might be fine, same thing for your burner

 

 

Thanks for your suggestion.

I installed the program... Should it give an advise if temperatures and voltages are an issue?

I don't know exactly what to look for :(

 

Anyhow, any answers to my previous question are welcome! :D

Posted

there's a report function for each module

 

sensor will show voltages

 

the overclock will show hardware specifics

 

what we need to see is these 2 parts

 

CPU Properties:

CPU Type AMD Athlon 64 3500+

CPU Alias Venice S939

CPU Stepping DH-E3

CPUID CPU Name AMD Athlon 64 Processor 3000+

CPUID Revision 00020FF0h

 

CPU Speed:

CPU Clock 2249.88 MHz

CPU Multiplier 9.0x

CPU FSB 249.99 MHz (original: 200 MHz, overclock: 25%)

Memory Bus 249.99 MHz

 

CPU Cache:

L1 Code Cache 64 KB (Parity)

L1 Data Cache 64 KB (ECC)

L2 Cache 512 KB (On-Die, ECC, Full-Speed)

 

Motherboard Properties:

Motherboard ID 63-1408-000001-00101111-063005-K8T800P$A0036001_BIOS DATE: 06/30/05 17:34:14 VER: 08.00.09

Motherboard Name Asus A8V Deluxe (5 PCI, 1 AGP, 4 DDR DIMM, Audio, Gigabit LAN, IEEE-1394)

 

Chipset Properties:

Motherboard Chipset VIA K8T800Pro, AMD Hammer

Memory Timings 2.5-4-4-10 (CL-RCD-RP-RAS)

Command Rate (CR) 1T

 

SPD Memory Modules:

DIMM1: Micron Tech. 256 MB PC4000 DDR SDRAM (2.5-4-4-10 @ 250 MHz) (2.0-3-3-8 @ 200 MHz)

DIMM2: Micron Tech. 256 MB PC4000 DDR SDRAM (2.5-4-4-10 @ 250 MHz) (2.0-3-3-8 @ 200 MHz)

 

BIOS Properties:

System BIOS Date 06/30/05

Video BIOS Date 04/08/11

DMI BIOS Version 1014.008

 

Graphics Processor Properties:

Video Adapter ATI Radeon 9600 XT (RV360)

GPU Code Name RV360 (AGP 8x 1002 / 4152, Rev 00)

GPU Clock 500 MHz (original: 500 MHz)

Memory Clock 297 MHz (original: 300 MHz)

 

and

 

Temperatures:

Motherboard 29 °C (84 °F)

CPU 39 °C (102 °F)

GPU 40 °C (104 °F)

GPU Ambient 34 °C (93 °F)

DW CDW63G0-D00NF0A 40 °C (104 °F)

Seagate ST3250823AS 41 °C (106 °F)

 

Cooling Fans:

CPU 2657 RPM

 

Voltage Values:

CPU Core 1.41 V

+3.3 V 3.25 V

+5 V 5.13 V

+12 V 12.10 V

 

 

your previous questions are not answerable(in my opinion)

Posted

CPU Properties:

CPU Type Intel Pentium 4

CPU Alias Northwood HyperThreading

CPU Stepping D1

Engineering Sample No

CPUID CPU Name Intel® Pentium® 4 CPU 2.60GHz

CPUID Revision 00000F29h

 

CPU Speed:

CPU Clock 2608.08 MHz (original: 2600 MHz)

CPU Multiplier 13.0x

CPU FSB 200.62 MHz (original: 200 MHz)

Memory Bus 160.50 MHz

 

CPU Cache:

L1 Trace Cache 12K Instructions

L1 Data Cache 8 KB

L2 Cache 512 KB (On-Die, ECC, ATC, Full-Speed)

 

Motherboard Properties:

Motherboard ID 05/12/2003-865-PE-JL79AC0CC-00

Motherboard Name Chaintech 9PJL APOGEE / 9PJL1 (5 PCI, 1 AGP, 4 DIMM, Audio, LAN)

 

Chipset Properties:

Motherboard Chipset Intel Springdale i865PE

Memory Timings 2.5-3-3-7 (CL-RCD-RP-RAS)

PAT Disabled

 

SPD Memory Modules:

DIMM1: SpecTek 256 MB PC2700 DDR SDRAM (2.5-3-3-7 @ 166 MHz) (2.0-2-2-5 @ 100 MHz)

DIMM3: SpecTek 256 MB PC2700 DDR SDRAM (2.5-3-3-7 @ 166 MHz) (2.0-2-2-5 @ 100 MHz)

 

BIOS Properties:

System BIOS Date 05/12/03

Video BIOS Date 04/11/03

Award BIOS Type Phoenix - AwardBIOS v6.00PG

Award BIOS Message 9PJL 05/12/2003

DMI BIOS Version 6.00 PG

 

Graphics Processor Properties:

Video Adapter nVIDIA GeForce FX 5200

GPU Code Name NV34 (AGP 8x 10DE / 0322, Rev A1)

GPU Clock 250 MHz

Memory Clock

 

 

 

Sensor Properties:

Sensor Type ITE IT8712F (ISA 290h)

 

Temperatures:

Motherboard 42 °C (108 °F)

Aux 31 °C (88 °F)

Maxtor 6B200P0 38 °C (100 °F)

Seagate ST3120023AS 48 °C (118 °F)

 

Cooling Fans:

CPU 3245 RPM

Chassis 2482 RPM

 

Voltage Values:

CPU Core 1.46 V

+2.5 V 1.49 V

+3.3 V 3.23 V

+5 V 5.16 V

+12 V 11.52 V

+5 V Standby 5.11 V

Debug Info F 34 44 FF

Debug Info T 31 42 127

Debug Info V 5B 5D CA C0 B4 3E A4 (F7)

Posted

No it's not just a problem with verify, *anything* that ever sits in memory is subject to corruption if it's faulty - this includes data being read from a file and written to a disc.

 

There's just no way of knowing that this corruption is taking place unless you compare it against a 'known' something (or of course if the application/computer just keeps crashing!).

Posted
There's just no way of knowing that this corruption is taking place unless you compare it against a 'known' something (or of course if the application/computer just keeps crashing!).

 

So I assume that when I verify against an image, and imgburn gives me no miscompare errors,

I should be sure that the content of the dvd is exactly like the one on my hd,

apart from any possible problems with ram.

 

The fact that at first it gives me miscompare errors may be because of bad ram,

but if at a second attempt the verify is ok, i could be sure that the burn was succesful...

 

This would be give me relief :)

Posted

Yeah, I would have to say it's very unlikely that the burn and the verify would both be corrupted at exactly the same spot, therefore if the verify passes it's fair to say the disc is fine.

 

If Verify fails once with miscompare errors and you do it again and it passes, the first was probably due to bad ram and so again it's safe to think the disc is fine.

 

If in doubt, take the best of 3!

Posted (edited)
Yeah, I would have to say it's very unlikely that the burn and the verify would both be corrupted at exactly the same spot, therefore if the verify passes it's fair to say the disc is fine.

 

If Verify fails once with miscompare errors and you do it again and it passes, the first was probably due to bad ram and so again it's safe to think the disc is fine.

 

 

Great!!

That's exactly what I supposed, but I wanted to hear from you!! :D

 

If in doubt, take the best of 3!

 

What do you mean with "the best of 3"?

Thanks again.

Edited by c4fen01r
Posted
Verify it 3 times!

 

Compare any miscompare error addresses and take an average.

 

 

Ok, even if, according to what we said earlier,

 

if I get no miscompare errors at the first verify, it would be useless to verify the dvd a second time.

 

And if I get no miscompare errors at the second verify, it would be useless to verify the dvd a third time... and so on

 

 

Don't you think? :)

Posted

It was said as a bit of a joke.

 

You shouldn't really be in a situation where you can't trust your PC's memory.

 

I'd concentrate more on fixing the ram issues right now than verifying discs and hold off on burning anything else until it's sorted.

Posted
You shouldn't really be in a situation where you can't trust your PC's memory.

 

I'd concentrate more on fixing the ram issues right now than verifying discs and hold off on burning anything else until it's sorted.

 

 

Anyhow, maybe I just worried too much about my RAM, probably it was just a false alarm...

 

memtest gave me errors in my RAM at the first pass, just after a few minutes.

 

Now I'+m testing it with memtest86+ , which seems to be more trustworthy: I'm at the third pass and still not getting any errors...

Posted

Don't forget that Microsoft made one too.

 

Give that a go when you're done with Memtest+.

 

You might want to enable the advanced tests though because the standard ones are done with pretty quickly.

 

If you're running Vista it's an option in the boot menu (maybe press F8 if it doesn't appear automatically?). Failing that, just download 'windiag' from microsoft's site.

Posted
I would give the computer a good cleaning and update my bios and retest the power

 

I always keep my pc quite clean...

As regards with bios update, I admit I've never done it, because it seems quite complicated (even just to find the correct update...)

 

 

try to get a cpu temp reading?

 

th_66219_cpu_122_427lo.jpg

 

Is it normal!?

Posted

What cpu is it as 127 seems rather hot and how its still working at that temp is ?

 

 

[edit]actually I will read thread again as you may have listed it, if not list your motherboard and cpu etc

Posted

It may be 127F, which is not all that bad (this is 53C = the temp my PC runs at under continuous 100% load).

 

127C and she's a goner.

 

Anyway, his Everest temps and voltages look OK, although I am a bit sus on those memory timings even though they are the SPD ones. I run faster RAM (Corsair PC3200) and only run it as 2-3-3-6. Also, his CPU Core voltage is just a tad high for mine. 1.40 is where is should be. I wonder if his PSU is on the blink.

 

Regards

Posted
It may be 127F, which is not all that bad (this is 53C = the temp my PC runs at under continuous 100% load).

 

127C and she's a goner.

 

Regards

 

 

It's strange since the other temperatures are in °C

But of course it's more than strange a 127°C temperature and the pc not exploding.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.