[kju]

gday 

returning every few years to FSO with much delight - thanks to everyone for the excellent effort. 

Unfortunately I am plagued with a repeatable bluescreen when executing the launcher.exe (5.5.0.4 - MD5: 75D669E0881DE68F99AA73F76EEFBB53).
Same with the wxlauncher-0.8.0.exe (installer md5: FCE3848C573812F3AC848EB9BEA844F6).

It does not happen every day, yet if it happens, it does several times in a row and I skip the day trying to play FSO.

Unfortunately I cannot find anything in the windows logs nor a fs2_open.log (haven't run it with -debug yet,
but unsure if that helps at all with my launcher problems).

The system is XP32b, Intel-M SSD, Q6600, 3GB RAM, 1 GB RAM drive and prime stable.
Even ArmA works just fine (with is a every touchy game engine in terms of hardware).
No virus (used antiVir) nor adware found (Spybot - S&D).

Any ideas or what information could be useful to provide?
The only thing I can think of is the bluescreen text; yet its somewhat generic for the most part.

Dxdiag and hijackthis.log attached.


Thanks for your help! 

[attachment deleted by admin]

[General Battuta]

That sounds like it may be a hardware issue on your end...but I can't imagine why you'd be getting it in the launcher of all things. Have you tried running a build directly? If so please run a debug build and post the fs2_open.log file.

[kju]

Thanks for the response General Battuta 

Do you mean to create a link to the actual FSO exe and adding the parameters myself /
or doing so via a batch file?

[General Battuta]

Well I reckon you can just click on the exe can't you?

[Iss Mneur]

Well I reckon you can just click on the exe can't you?

Yes.  The windows FSO binaries are smart enough to figure the rest out.

The only time the launcher is needed is when you want to change the selected mod or the selected cmdline flags.

[kju]

Thanks everyone. Looks good for now. 

Will still continue trying to narrow the bluescreen source.