SH3 crashes with Vista and you have no clue? At least I got the error data now!

[johnno74]

Originally Posted by Alain-James

Well Secur32 can't be ended the same way as everything else, because it is specifically the process which manages ctrl-alt-suppr related processes

I may check in the activable processes if one can check it off, but I'd prefer not. It's really a vital aspect of the OS. But ultimately I may have to come to your solution Danlisa if the Secur32 version is a non-issue

Thanks in advance Seafarer

Secur32 is a dll, not an executable... It can't be exited or disabled because it isn't a complete program that runs in its own process, its a library that is loaded by pretty much every process. It is a core part of the OS, and it provides most of the security & user account functions in windows.

Just because this is where the crash occoured, doesn't necessarly mean this module caused the problem. For example, sh3 might have called secur32 with bad parameters, so the module threw an exception. The module that called secur32 process should caught that exception, and dealt with it somehow.
In this case there was nothing to handle the exception so windows had no choice but to kill the process.
The version you have listed (6.0.6000) is the version number of all of the DLLs in stock windows vista. I have v6.0.6001, which is vista SP1.

Because this DLL is used pretty much everywhere its not necessarily a starforce issue either (but it might be).

Originally Posted by ICZEOZN

I use an administrator user account, but I believe the "Run as administrator" command is superior. I may be wrong, but I believe Vista has both an "administrator" account and an "Administrator" (with a capital "a") account.

I suppose you could give that a try. When I did that, I think the update was already installed and I had just installed it again with the "Run as administrator

There is still only one administrator account, but what happens is with UAC on vista if you are an administrator it doesn't give you all of the administror privildeges initially. Your logon has the same rights as a non-admin user account. If you right-click on a program and select "run as administrator" then it runs the program with full administrator priviledges.
Some other stuff happens with file & registry virtualisation which means stuff that writes to restriceted areas of the registry and filesystem looks like it works, but doesn't really. This is what causes most problems for people with updates not getting applied etc. (I have turned this off)
If you use "run as administrator" to run a program the filesystem and registry writes aren't virtualised, and go to the real thing.

To make sure SH3 is sorted out, find SH3 and "run as administrator". This will ensure starforce gets a chance to install properly. Then run the starforce update with "run as administrator" to let it sort its thing out... then try SH3 again. If that fails, try SH3, with "run as administrator".

If it still doesn't work at least we know most likely it isn't starforce causing the problem.

I have been running SH3 on vista for 12 months now, and I have had zero problems. I have avoided the whole starforce problem... (shh...)

Hope this helps.

[Amiral Crapaud]

Hello Johnno

Thanks for the help but it really didn't work, even with the "run as administrator" administrator stuff.

I definitely start to believe the issue has something to do with my local configuration. There must be a program running up somewhere that doesn't like the idea of having SH3 running at the same time. Either that or something to do with the screen resolution (what is yours by the way, if I may ask?)

By the way I am gonna try some selective start, stopping unneeded application one per one to see if it has any effect at all.
Anyway, that's definitely not a Starforce issue. If Starforce was involved, I suppose I'd have problems during Starforce execution, prior to the intro and the game loading bar sequence...

Last error log still show the same kind of stuff

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />

<EventID Qualifiers="0">1000</EventID>

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2008-01-26T23:05:00.000Z" />

<EventRecordID>20003</EventRecordID>

<Channel>Application</Channel>

<Computer>Ordinator</Computer>

<Security />

</System>


- <EventData>
<Data>sh3.exe</Data>

<Data>1.4.0.1</Data>

<Data>32ce8647</Data>

<Data>Secur32.dll</Data>

<Data>6.0.6000.16386</Data>

<Data>4549bdd2</Data>

<Data>c0000005</Data>

<Data>000021f4</Data>

<Data>1598</Data>

<Data>01c8606fbecf9aab</Data>

</EventData>


</Event>

[ICZEOZN]

Originally Posted by Alain-James

...something to do with the screen resolution (what is yours by the way, if I may ask?)

My screen resolution is 1280 by 1024. I can't imagine any reason why this would be the cause of your problems. Are your graphics card driver's up-to-date? During the install process, you are asked to install codecs required to play the game. Did you install those?

I was hoping that I could help you resolve your problem since I had the same issue. I am afraid that I can't offer much help.

I wish you the best.

[Amiral Crapaud]

Yep, I specifically checked the codec box just to make sure. The codec issue had been raised earlier, but so far tweaking doesn't seem to affect them. But I wonder if there's anyway I can disable the main screen loop video and neutralize it for good, so I can check for sure if this problem isn't codec-related...

Video drivers are up to date too, and I tried several ones with no luck.

But thanks anyway, your recovering gave me some little hope Im sure I must have some problem related to yours, I just have to find the right thing to disable so I can have some happy kaleun time again

AJ

[johnno74]

I'm running at 1680x1080. Don't bother worrying about other apps running on your system, its highly unlikely to be them causing problems, unless you are running some really really weird/dodgy stuff.

You could be onto something with the codec issue though. I don't know where the main menu movie file is...

Have you installed any codec packs? Some of them are pretty crappy, and can leave behind a mess even when uninstalled. I generally stay clear of them.