Thanks for the reply.

With the new release I can't start SUPER without windows crashing and going blue screen

Really awfull : crashes also my PC with "blue screen of the death" and reboot....

Pleaz help !!!!!!!!

Launch of SUPER doesn't work better when checking "XP SP2" compatibility......

Really a shame that I won't use my favorite's encoding software anymore....

Thanks for your suport

Hello,
I have the same problem after I have installed Sp 1 for Vista. The system makes a Reboot. Executing in a compatibility mode does not bring about any change. Can be started incredibly without Reboot only if I start Vista in the protected mode.

I think the version 30 was a fast shot.

There is hope, I got it to start, Iclosed all process I could in task manager including anti virus and now it works. Now I only haveto test my forward to get the process that causes the problem.It can take time since it requires alot of reboots but I have a feeling it is itunes or antivirus. I will be back with details

Problem keeps repeating after i kill just about every process running in the system (except windows-related ones).

I'll try to post my debug info later, if i can.

Man I hate Vista, it is the most flawed and crippled OS i've ever seen, and SP1 only makes it worse!!

Thanks for the support anyway.

Let's see... First of all, debug info:



*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 8742fd90, Terminating object
Arg3: 8742fedc, Process image file name
Arg4: 82225e00, Explanatory message (ascii)

Debugging Details:
------------------




PROCESS_OBJECT: 8742fd90

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 00000000

PROCESS_NAME:  csrss.exe

EXCEPTION_RECORD:  8e3489dc -- (.exr 0xffffffff8e3489dc)
ExceptionAddress: 7573e0f9
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000004
Attempt to read from address 00000004

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.

CUSTOMER_CRASH_COUNT:  2

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.

READ_ADDRESS: GetPointerFromAddress: unable to read from 8216e6d8
Unable to read MiSystemVaType memory at 8214f2e0
00000004

FAILED_INSTRUCTION_ADDRESS:
+7573e0f9
7573e0f9 ??              ???

BUGCHECK_STR:  0xF4_C0000005

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

STACK_TEXT: 
8e3484e4 822caf70 000000f4 00000003 8742fd90 nt!KeBugCheckEx+0x1e
8e348508 8225b0f5 82225e00 8742fedc 8742ffb8 nt!PspCatchCriticalBreak+0x73
8e348538 8225b09c 8742fd90 87cfc890 c0000005 nt!PspTerminateAllThreads+0x2c
8e34856c 820999aa ffffffff c0000005 8e3489b0 nt!NtTerminateProcess+0x1c1
8e34856c 82098a01 ffffffff c0000005 8e3489b0 nt!KiFastCallEntry+0x12a
8e3485ec 8207421b ffffffff c0000005 1d61b872 nt!ZwTerminateProcess+0x11
8e3489b0 82074b84 8e3489dc 00000000 8e348d64 nt!KiDispatchException+0x41b
8e348d34 8209d4a3 0221f484 0221f4a0 00000000 nt!KiRaiseException+0x175
8e348d50 820999aa 0221f484 0221f4a0 00000000 nt!NtRaiseException+0x33
8e348d50 7573e0f9 0221f484 0221f4a0 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0221f77c 00000000 00000000 00000000 00000000 0x7573e0f9


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0xF4_C0000005_IMAGE_csrss.exe

BUCKET_ID:  0xF4_C0000005_IMAGE_csrss.exe

Followup: MachineOwner
---------





As you can see (same as Kurgan here) problem takes place within csrss.exe, which is a windows process.


Next, typing DXdump.exe in SUPER directory...Nothing happens, nothing is written


About the crash, I'll try to post more info later (now is not really a good time to crash my pc, sorry)

SUPER installation process is correct, all files intalled and it tries to open help page with Internet Explorer.

When launching SUPER, IT APPEARS several seconds on the tray bar, then crashes. No "Looking for updates" window or any other message is shown.

Thanks again!!! I'll probably won't be able to read the forum again till friday, then i'll post more info, if you need it.

96crypt_mod wrote:

we are really willing to help (it's obvious) but we need details, more details..

1)please run the debugging tools for windows by Microsoft as indicated here
http://www.w3exchange.com/p7293-2008-03 … html#p7293
2)once installed, open the exe file WinDbg.exe
3)go to File>Open CrashDump
4)select the dump file(s) that are usually located in \windows\Minidump they have dmp extension
5) try to read what caused the crash.

6)go the where SUPER(C) is installed. (DO NOT LAUNCH SUPER)
7)open a DOS box then type DXdump.exe then hit enter, nothing should happen and nothing should be written.

8)provide some detailed info at which level the crash is occurring,
a.did you get a small window box saying all files were correctly installed during installation
b.did it open an internet page
c.do you see the bar icon of SUPER(C) just before the crash on the tray bar

The crash is

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.0.6001.2.1.0.768.2
  Locale ID:    1033

Additional information about the problem:
  BCCode:    f4
  BCP1:    00000003
  BCP2:    996BF8D8
  BCP3:    996BFA24
  BCP4:    82288330
  OS Version:    6_0_6001
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\Mini032608-01.dmp
  C:\Users\******\AppData\Local\Temp\WER-112773-0.sysdata.xml
  C:\Users\******\AppData\Local\Temp\WER444F.tmp.version.txt

Read our privacy statement:
  http://go.microsoft.com/fwlink/?linkid= … cid=0x0409


a.did you get a small window box saying all files were correctly installed during installation

YES

b.did it open an internet page

YES

c.do you see the bar icon of SUPER(C) just before the crash on the tray bar

YES


The V30 did not crash on initial start up after the installation, but blue screen crash happen after reboot of my computer.

I'm using Vista sp1. the previous version did work on my com in sp1

ans by the way I DONT SEE ANY UNINSTALL file for this program? not in the windows uninstaller and it did not have any shortcut at start menu

Last edited by alexdino (2008-03-26 04:09:32)

Hi !
I've just had the "blue screen" problem...
I'm not very good at computers, and I'm French, so I didn't understand everything in the posts, but I have tried running Super as administrator, I've tried the XPsp2 compatibility, and nothing will work, it's still that horrible blue screen...
The thing is, I had kept the setup file for the previous Super version (ferbruary 2008), which worked, and I thought I would uninstall the March version and put back the old one : the install was ok, everything was right, but when I tried to launch Super, it never did !
So, when I have the March version, I get the blue screen, and when I have the February version, nothing happens...
I really hope there will be a solution, because Super saves my (working) life very often !

I DONT SEE ANY UNINSTALL file for this program?  WHY

The uninstalled in the program remover finally appear, after i did some codec installation/uninstallation. 

The problem occur maybe the use of video codec in vista?

hi all i've got the same problem...bluescreen

Probleemhandtekening:
  Gebeurtenisnaam van probleem:    BlueScreen
  Versie van besturingssysteem:    6.0.6000.2.0.0.768.3
  Landinstelling-id:    2067

Aanvullende informatie over dit probleem:
  BCCode:    f4
  BCP1:    00000003
  BCP2:    88186B38
  BCP3:    927B8CD4
  BCP4:    00000000
  OS Version:    6_0_6000
  Service Pack:    0_0
  Product:    768_1

Bestanden die helpen bij het beschrijven van het probleem:
  C:\Windows\Minidump\Mini033108-01.dmp
  C:\Users\**\AppData\Local\Temp\WER-89918-0.sysdata.xml
  C:\Users\**\AppData\Local\Temp\WER96C2.tmp.version.txt

Lees onze privacyverklaring:
  http://go.microsoft.com/fwlink/?linkid= … cid=0x0413


sysdata

Windows NT  Version 6.0 Build: 6000
Product (0x3): Windows Vista (TM) Home Premium
Edition: HomePremium
BuildString: 6000.16584.x86fre.vista_gdr.071023-1545
Flavor: Multiprocessor Free
Architecture: X86
LCID: 1043

i've tried the solution of installing deinstalling set on winXP SP2
but that dont work at all...(looks to simpel to work anyway)

are there any other solutions?because earlier versions dont open here...

my dump file in debug..

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, 88186b38, 927b8cd4, 0}



Probably caused by : csrss.exe

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 88186b38, Terminating object
Arg3: 927b8cd4, Process image file name
Arg4: 00000000, Explanatory message (ascii)

Debugging Details:
------------------




PROCESS_OBJECT: 88186b38

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 00000000

PROCESS_NAME:  csrss.exe

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xF4

CURRENT_IRQL:  0

STACK_TEXT: 
8ce71cf0 926167e8 000000f4 00000003 88186b38 nt!KeBugCheckEx+0x1e
8ce71d34 9260514f 86b4da70 00000001 927dff40 win32k!xxxDesktopThread+0x240
8ce71d48 926d8d19 00000004 0094fe24 8ce71d64 win32k!xxxCreateSystemThreads+0x54
8ce71d58 81c8caaa 00000004 0094fe64 778d0f34 win32k!NtUserCallNoParam+0x1b
8ce71d58 778d0f34 00000004 0094fe64 778d0f34 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0094fe64 00000000 00000000 00000000 00000000 0x778d0f34


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0xF4_IMAGE_csrss.exe

BUCKET_ID:  0xF4_IMAGE_csrss.exe

Followup: MachineOwner

hope you can do anything with this...

Last edited by wimpi (2008-03-31 07:24:31)