View Full Version :
Bluescreen of Death when using Compressability Check in GKnot .21
hurzel5
7th December 2001, 11:37
With 0.20 the great compressability feature worked fine.
Now using it in 0.21 kills the whole program and brings up a bluescreen stating an error has happened ?
Anybody else have the same experience or hopefully otherwise?
Kruger
7th December 2001, 15:34
You're not alone. I have got the same problem with 0.21 but i haven't tried the older package (0.20) yet. I hope it's still there.
Kruger
8th December 2001, 17:30
I don't have the problem any more.
I switched my OS from win98se to win2k.
I don't know if it was the OS or some config issue,
so try switching OS or reconfig your system.
Everthing is working fine now,
thanks for this great tool.
hurzel5
8th December 2001, 17:56
so it's me or my Win ME...
I'll be switching soon too, thanks for the tip and happy encoding..
anr
10th December 2001, 00:30
hi all,
surprisely i've just tried 0.21 with blair witch project (what a pain in the ... movie to encode), and all i got after pushing the "now" button in the compressibility test section, is a BSOD! :)
hey wef? what do you change from .20 to .21 in this part? please put it back!
and no, i am not going to reinstall all my whole system just to use this feature :), i really don't care about win2k or winxp :D jejeje
regards,
anr
Sharro
10th December 2001, 10:37
If you do, please tell which one are you using.
Take Care.
Sharro
anr
10th December 2001, 14:24
hi all,
yes i've been using noiser filters, but the same setup as i used in the older 0.20, little noise and heavy noise,
in 0.20 it works, i am sure about that,
maybe thewef changed something in 0.21 in the compres.check part?
regards,
anr
Sharro
10th December 2001, 14:29
A lot of people were experiencing reproducible crashes if they set Medium or Heavy noise filter BEFORE RESIZING.
I have seen no solution for this problem on the forums.
Take care.
Sharro
TheWEF
10th December 2001, 14:41
i'm not 100% sure but i don't think i changed anything.
slapper
12th December 2001, 21:16
I have the same problem!
(Im using win98SE)
:confused:
The FX Files
13th December 2001, 00:44
This has happened for the first time for me today (Win98SE)... Since I've done a 4:3 rip for the first time, I guess... It seems it has something to do with that! Anyway, I tried a couple of times, the same happened both times, then I reeboted, and then it worked fine :confused: :eek:
For now, it's working, dunno when will it happen again nevertheless :rolleyes:
HARD_DRIVE
13th December 2001, 22:08
Hi, Im using .21 and Win2k on an AMD 1.33 machine running at 1426 Mhz,with 512 megs of ram, Im not using the compression check feature, and get a bluescreen everytime I use this App, sometimes its after its finished, sometimes before, Im not using any noise filters at all, can anyone help with this? This appears to be a great App for DivX, if I could just get it too perform properly.
When I was using Flask, my movies would have audio-video sync problems eveytime, I really wish I could get a good ripping App to work for me, so far I havent been successfull, any help would be appreciated.
Great work guys......Thanks. :-)
jreid
13th December 2001, 22:32
if you're willing to spend some time to learn the ins and outs of a program, you really can't beat doom9's nandub process for ripping. there's a lot more for you to do to rip a movie, but ultimately that gives you way more control.
gknot is another great process, but sort of works on top of nandub. if you're having trouble with the knot maybe just try going straight to nandub, and take that extra time to learn it. the effort is rewarding.
TheWEF
13th December 2001, 22:37
lower your clock-speed, check your ram,...
jwu42
16th December 2001, 01:08
Have to agree with TheWEF
I am a GKnot newbie (hell a DivX newbie) and got three errors (no BSOD) with gknot when I was OC'd (1.4 Tbird at 1.58). Set it back to default this morning and the compressablity check worked fine.
I still haven't been able to get gknot to encode a file yet though :(
Maephestus
17th December 2001, 04:27
I'm getting BSODs frequently now using Gknot 0.21. Athlon/Win2kPro, no it's not my CAS settings nor overclocking.
I'm suspicious of the following at the moment: GreedyHMA or Divx 4.11. I've stopped experimenting with both, and haven't had another BSOD in about a week (after about 12 BSODs last weekend).
Hope this info might help someone.
- Maephestus
Evaldas
17th December 2001, 21:34
I'm also cant use compressability check. Also I cant use heavy noise filter, I think i causes the line with SpatialSoftenMMX line in avs file. OS WIN98SE.
roy
19th December 2001, 11:03
I also got the same blue screen and my friends too. In 0.20 everything was ok. ANd I have to do it manualy. But I wonder if this problem happens only for evryone with amd processors. Does anyone with intel processor got the same problem?
Schultz
19th December 2001, 11:33
i am running WinXP with a PIII 500 and get a crash when attemping to do a Compressiblity check in .21
The FX Files
19th December 2001, 20:46
Yeah, me on a Win98SE P2 400MHz (yeah, I know)... Happened for a whole day, never happened again since... :confused: :eek: :rolleyes:
nikthebak
21st December 2001, 14:54
I also can't use compressibility check with GKnot 0.21. :confused:
I run a 633MHz Intel Celeron at standard speed and use the slowest possible memory settings. It crashes every time when I push Now -> OK in compressibility check.
I also use Win98SE like a lot of people with this particular Now-button crashing problem. And I wouldn't like to punish my system with more recent MS operating systems just to use compressibility check! So hopefully this issue gets addressed!
Schultz
21st December 2001, 16:19
Well i solved my problems divx 3.11 wasn't installed on my system.. I installed it and now compressibilty works fine.. Stupid me.
HARD_DRIVE
22nd December 2001, 19:42
Upgrade to the new codec DivX 4.12, solved my problems.
vBulletin® v3.8.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.