Bluescreen during use of AutoGK

[ilhyfe]

Hi all,

since I changed m<y hardware from AMD64 to intel Core2Duo I get random bluescreens when I use AutoGK. I tried the lastest beta AND stable version (both ran fine on my AMD). I don't think its a CPU/RAM issue since memtest didn't find any error and I can render 20+ jobs in vdub mod manually, without any problems. Maybe someone of you has the same problem...

[Sharktooth]

No. It's your new hardware coz on another PC it just works well.
Check the temperatures and do some other burn-in tests.
It could even be a defective CPU cache...

[CWR03]

If you changed motherboard and processor but kept the same hard drive with the Windows install, you may have conflicting drivers. If possible, remove any trace of old drivers, or reinstall Windows after a full format.

[ilhyfe]

I reinstalled my System 4 or 5 times. And as i said, I can encode 22 mpeg's to xvid with vdubmod, if I do it "manually", but max 1-2 with AutoGK.
So temperature, cpu etc. can't be the problem....

[jggimi]

"random bluescreens" is insufficient information for anyone to do more than provide some conjecture that such a problem tends to be hardware.

If any of these problems was recorded in your system's Event Log, you will find information there that you might share with others.

More information = Better help.

[ilhyfe]

More information = Better help.

I know but I don't have more information. There's no entry in the eventlog. all I can say is the error message on the blue screen. It's either

1. DRIVER_IRQL_NOT_LESS_OR_EQUAL
2. PAGE_FAULT_IN_NON_PAGEABLE_ARE

STOP 0x00000000000000??

And no, I DON'T have nay problem with any driver. I CAN use vdubmod if I build my joblist manually and it DOES encode for hours (at least I tested 12h). And I can play BF2 for hours.

AutoGK gives me a bluescreen while encoding the 1. or 2. movie.

[Sharktooth]

Definatly a driver or hardware problem.
The fact you can succesfully encode it manually doesnt mean your system is stable. The instability could be "triggered" only in certain conditions.

[jggimi]

I know you do not believe you have a hardware problem. It is, unfortunately, still possible that you do.

Please run two different stress tests, each for multiple hours.

1. Prime95
2. Memtest86

If, you run each type of test for 6-8 hours or longer, and the tests run successfully, only then can you say that your problem is likely to be software related: autogk, middleware, or operating system.

For assistance, links, and other help with possible hardware problems, please see Hardware problems / How to test system stability (http://forum.doom9.org/showthread.php?t=54130).

[ilhyfe]

Ok I let Prime95 run tonight and memcheck tomorrow.

[ilhyfe]

Ok, i ran 2 Threads of Prime95 (for each CPU) with a 900 MB ram to use (i got 2 GB) for 12 hours, no problem. I ran memchack from a knoppix cd, no problems.

Btw, I get the same error if I use DVD Rebuilder

[Sharktooth]

uhm... try changing video driver version.

[jggimi]

It appears that the problem is not in your main PC hardware -- memory, CPU, power supply, or PCI bus. However, that first BSOD with "irql not less or equal" tends to mean that either there is a hardware problem in an untested hardware component, or that there is a driver or OS software problem, or that there is a hardware configuration problem of some kind that the OS or failing driver are unable to survive.

While the problem manifests during use of AGK, your symptoms do not indicate an AGK problem.

I'm going to move this thread to our PC HW/SW forum, where those with more expertise can guide you through the capture of additional diagnostic information (such as taking a memory dump and backtrace at the time of the failure). Should their analysis point to AGK as the culprit, we'll be happy to take the thread back here for Len0x to look at for possible bug fix.

Googling for those two BSODs shows all sorts of different causes, even including firewall and security software middleware (Norton, ZoneAlarm, etc.).

[Pookie]

I agree with Sharktooth - Video driver

[ilhyfe]

I agree with Sharktooth - Video driver

How would a video driver cause a bluescreen, while encoding an xvid?
Btw, work find on Windows Vista RC1...

[foxyshadis]

In XP video drivers sit in the kernel. (Anything in the kernel can cause a bluescreen; that's why 98 was so crashy, all kinds of drivers in the kernel.) In Vista they exist outside it, and thus can't cause a kernel panic if they crash. Did you at least try upgrading?

[UofC]

One of the down sides to new technology is that it is often untested in the real world. The driver issue will be resolved in time and you can contact the maker with information to help push the development.

A pagefile error would be up to MS to fix and we all know they are not ahead of the curve in terms of driver and bug development.

You may want to try a clean install with minimum drivers to see if the program will run. If you have the time you might be able to weed out the offending driver.

[ilhyfe]

i tried an older gk driver which used to work fine on my old amd64 system but it didn't work. i didn't get blue screens but my pc did a hard reset and i even had to reinstall my sound driver after that.

another strange thing: the first job in autogk alway works....

[Pookie]

another strange thing: the first job in autogk alway works....

That would be more indicative of heat problems. Install Speedfan, and have it log your system temps every 5 minutes while you're encoding.

http://www.almico.com/sfdownload.php

Another great tool is Throttlewatch , which will tell you if your CPU is throttling back due to overheating, AND will show you if your voltage is fluctuating wildly.
Start it and press F5 to begin capturing stats while you're running AutoGK.

http://www.panopsys.com/Downloads.html

Also possible that something is leaking ram/resources - you can simply do a Ctrl-Alt-Del to bring up task manager and look for apps that are increasing in RAM size.
ProcessExplorer from http://www.sysinternals.com/Utilities/ProcessExplorer.html will give you a much more detailed view of loaded apps and their resource usage.
I don't know what AutoGK is compiled with, but perhaps it is using a leaky system .dll.

Finally, if AutoGK is using DirectShowSource from Avisynth, you could be looking at a decoder or directX issue. Try a different version of directshowsource.dll, upgrade/downgrade your copy of FFDshow (if you have it installed), and install the latest directx 9.0c updates (aug 2006?). A problem in that area would result in a video driver crash message, as all components are depending on DirectX.

[ilhyfe]

Hi,

since everyone told me it must be a hardware problem (also in the DVD-RB forums), I removed one of my rams. After that, AutoGK worked fine. I tested it with both rams again and PC crashed. Now I tested both rams on one channel (single channel instead of dual channel :() and it seems to work fine now. Very strange...

[CWR03]

Perhaps you're using RAM that isn't rated for using with dual channel?

[jggimi]

I ran memchack from a knoppix cd, no problems.
Which tests, and how many cycles? I would think that memtest86 should have caught this. By default (using the memtest86 download -- not sure what knoppix uses) all tests but the bitfade test are run by default each cycle. The bitfade test is a separate, 3 hour test.

A single cycle of tests is often not enough. See www.memtest86.com for further information.

[ilhyfe]

I ran memtest86 over night, I think 9 hours+ and after that prime95 for several hours.
I bought a package of 2 x 1024 MB DDR2 Ram from OCZ (for dual channel :))