Valeron
9th May 2007, 06:14
in the past few days, i usually met "bad" frame when encode with avisynth. no matter how i write the script and what filter used.
it's so weird the "bad" frame generally will only appear once in every encode.
here is a sample
i've ever runned memtest86+ and prime to check stability of my machine. 10 pass without error in memtest86+(i haven't tried to run it overnight), Prime for Windows can run for hours.
My hardware configuration:
CPU: AXP Barton 2GHz(200x10), slightly OC from 2500+.
RAM: Kingmax DDR PC3200 CAS by SPD 256M x2.
Mainboard: soltek 75FRN2-L(nforce 2 ultra400)
HDD: WD800BB + Hitachi T7K500 320G
OS: XP SP2 with latest patches
i'm confused about the bad frame produced. if avisynth is not safe enough to run together with other program? memleak? or probably another hardware failure such as IDE cable corrupt?
addon: memtest86+ will reserve 2M ram for bios and dos, will errors hide there?
it's so weird the "bad" frame generally will only appear once in every encode.
here is a sample
i've ever runned memtest86+ and prime to check stability of my machine. 10 pass without error in memtest86+(i haven't tried to run it overnight), Prime for Windows can run for hours.
My hardware configuration:
CPU: AXP Barton 2GHz(200x10), slightly OC from 2500+.
RAM: Kingmax DDR PC3200 CAS by SPD 256M x2.
Mainboard: soltek 75FRN2-L(nforce 2 ultra400)
HDD: WD800BB + Hitachi T7K500 320G
OS: XP SP2 with latest patches
i'm confused about the bad frame produced. if avisynth is not safe enough to run together with other program? memleak? or probably another hardware failure such as IDE cable corrupt?
addon: memtest86+ will reserve 2M ram for bios and dos, will errors hide there?