Thread stuck in device driver

[Prefect47]

Just got Jedi Knight II and was all ready for some serious gaming - but the game won't even start properly! Locks up my WinXP pro bad with a white 60Hz screen, and after a hard reboot the watchdog states "thread stuck in device driver" as the cause.

I've looked around and found out that this is not a Matrox-specific problem but rather M$/D3D-specific, but still, is there any way around it?

Running Marvel G200 (and an even more ancient Voodoo2 card) on an Abit BX6v2/P3 933/256Mb. I am using w2k drivers though in order to get TV-out working, but no other game has had this problem.

[bsdgeek]

M$/D3D-specific

Uh... JKII is an OGL game.

[Prefect47]

Originally posted by bsdgeek

Uh... JKII is an OGL game.

OK, just m$-specific then.

[MultimediaMan]

No, it is JK specific.

Raven/Lucasarts has a great thing going here, but the need to patch the Audio (Fast, Quick and In a Hurry), and they need to fix their OpenGL default settins (Badly).

Matrox is doing the right thing and looking into a possible Driver/ICD issue with JKII, hopefully something good will come out of it.

[Prefect47]

Originally posted by MultimediaMan
No, it is JK specific.

Possibly, except I've now gotten the exact same error (hard lockup at start of 3D graphics) with Simon the Sorcerer 3D, but at least that can be played on my V2 through Glide...