On opening a previously used stable project....! HELP

Grazie wrote on 11/10/2002, 1:48 AM

Any takers...

"This program has caused an error in KERNAL32.DLL

This program will now close"

Prior to this, and within VF I got this lot!

"Sonic Foundry VideoFactory 2.0
Version 2.0c (Build 125)
Exception 0xC0000090 (float invalid operation) IP:0x7802EF59
In Module 'MSVCRT.DLL' at Address 0x78000000 + 0x2EF59
Thread: GUI ID=0xFFFD3E11 Stack=0xB85000-0xB90000
Registers:
EAX=0000177f CS=01a7 EIP=7802ef6a EFLGS=00010202
EBX=00001370 SS=01af ESP=00b85494 EBP=00b854ac
ECX=3fe01370 DS=01af ESI=0000ffff FS=1737
EDX=00000000 ES=01af EDI=00000003 GS=0000
Bytes at CS:EIP:
7802EF6A: DD 45 F8 59 59 EB A6 F6 .E.YY...
7802EF72: C3 20 75 ED DD 45 F8 53 . u..E.S
Stack Dump:
00B85494: 00001370
00B85498: 3FE01370 35690000 + A771370
00B8549C: 00B854F8 00A80000 + 1054F8
00B854A0: 00B8557C 00A80000 + 10557C
00B854A4: 00000000
00B854A8: 00000000
00B854AC: 00B85510 00A80000 + 105510
00B854B0: 0109BCE2 01000000 + 9BCE2 (VIDFACTK.DLL)
00B854B4: 00000000
00B854B8: 3FE00000 35690000 + A770000
00B854BC: 40390000 35690000 + AD00000
00B854C0: 0109BEFC 01000000 + 9BEFC (VIDFACTK.DLL)
00B854C4: 00000000
00B854C8: 00000000
00B854CC: 00B854F8 00A80000 + 1054F8
00B854D0: 00000000
> 00B85510: BFF11CE8 BFF10000 + 1CE8 (GDI32.DLL)
> 00B85514: 0109C2E5 01000000 + 9C2E5 (VIDFACTK.DLL)
00B85518: 00B8557C 00A80000 + 10557C
00B8551C: 0263A160 02340000 + 2FA160
00B85520: 00000000
00B85524: 00000000
> 00B85528: 011DFE64 01000000 + 1DFE64 (VIDFACTK.DLL)
00B8552C: 00000000
> 00B85530: BFF455D7 BFF40000 + 55D7 (USER32.DLL)
> 00B85534: 00457E0F 00400000 + 57E0F (VIDFACT2.EXE)
00B85538: 00B8557C 00A80000 + 10557C
00B8553C: 0263A160 02340000 + 2FA160
00B85540: 00000000
00B85544: 00000000
> 00B8554C: BFF41AE0 BFF40000 + 1AE0 (USER32.DLL)
> 00B85558: BFF1278F BFF10000 + 278F (GDI32.DLL)
> 00B8557C: 00447504 00400000 + 47504 (VIDFACT2.EXE)
- - -
00B8FFF0: 3E671746 35690000 + 8FE1746
00B8FFF4: 83984FEC 83965000 + 1FFEC
00B8FFF8: BFF7A24F BFF60000 + 1A24F (KERNEL32.DLL)
00B8FFFC: 00000000

=========================================

HELP!

Grazie

Comments

Grazie wrote on 11/10/2002, 2:12 AM

Hey, the only thing I can think of that is different, between versions of the project I've been working on, is that I used the SoFo audio effects plugins. Is it that I have to register these audio plugins with SoFo to make them acceptable for "re-openning" the project? Something similar to needing to register the MPEG1 codec to make that work? The audio effects plugins came with my bought version of VF 2.0c build 125.

Grazie

discdude wrote on 11/10/2002, 11:53 AM

Audio effects plugins? What sort of audio effects plugins do you have? All the ones I got are automatically registered when I install VF.

As far as your stack dump goes.
MSVCRT.DLL (Microsoft Visual C Runtime) - Many programs use this library. Faults in this dll are sometimes caused by using the "wrong" version. Unfortunately, since it is so popular many installers tend to overwrite it with their own old or buggy version. That is why in XP you have the "System Protection" feature.

GDI32.DLL (Graphical Display Interface) - Used to display menus, fonts, the desktop, etc. Faults in this dll usually indicate buggy display drivers.

USER32.DLL - Core Windows component used for message handling, timers, menus, and communications.

KERNEL.DLL - Another core Windows component used for resource and memory management.

The fact that you have faults in so many core windows dll does suggest that the problem lies with something that interfaces closely with the core of the OS, i.e., drivers. I recommend that you update your display drivers.

If memory serves, you have an Dell Inspiron 8000 running Windows ME. Was your graphics card a Nvidia GeForce GO?

Jimco wrote on 11/11/2002, 3:38 PM

You can also download Windbg from Microsoft and analyze the dump. Unless you're adept at such things though, might be more trouble than you want to deal with.

Discdude has a good plan of action, but VF is very GDI intensive, so it's not surprising to see that on the stack at this point. What you really need to find out is what was manipulating the memory at address 00B8FFFC. That memory has been corrupted.

Jim