HA!

Yes, happened when I produced a video with the P4 3.2 going against the Athlon XP 3200+.

I used the latest NV driver, but for me, it didn't happen on the P4, but the Athlon XP machine restarted at the same spot, tried 2 boards.

Some of my viewers contacted me and told me an older driver solved this issue.

Interesting that the P4 has SSE2, the P3 and Athlon XP doesn't.

Do you know what driver version exaxtly fixes this issue ?

this seems to be a known BSOD combination: pentium3+geforce6/7+3dmark03(mother nature), many people and i have experienced it. the exact reason is not known, as such a combination rarely crashs in other 3d applications.

i heard some people said that it works in windows98, while others say that the geforce6800 series with native agp support(nv40) would work, but i havn't tried it myself.

i tested this now on a Pentium 4 1,3Ghz S423 with 1,5Gb RD-Ram - GeForce 6200 also produces same crash..

No problem on my current PIII system.
PIII-S @ 1575, EVGA 6800GT with 81.98 drivers (the latest driver 307.83 also works fine), Apollo Pro 266T chipset, 2GB DDR, XP Pro SP3.

I did, however, have that exact problem with a P3-800/FX5200/440BX based system. 😖
I wonder if it's a power delivery issue? I'm pretty sure the FX5200 worked fine on an i815 system, though I don't have any saved screenshots or benchmark data of the i815 system to confirm.

Not really i use a recapped Enermax and the GeForce 6200 isnt that powerhungry.
The other Machine has a cheap but new chinese supply and my Xeon has also a cheap but well tested China supply.

So i can definitiv rule that out.
Maybe AGP related Issue ?
With FX Cards i have no issues. Only with the 6xxx Cards.

I'm ruling out power.

I don't know the driver version I'm afraid. You could dig through the video comments though.

I would try the very early launch release driver.

Try this:
I had the same problem back then with my Celeron Tualatin 1400 + Geforce 6600GT AGP in mother nature and the last option solved it for me.

Cool! Would you happen to have a link for this?

That screenshot is from Rivatuner.

Awesome! I will try that tweak when I do another project to do with the XP CPU.

This sounds vaguely familiar to me. A long time ago I think I had BSODs happening in that same test on a P3-S I was building for someone. That's where the turtle is crawling up out of the water, isn't it?
At the time I thought this crash implied a serious problem that might occur in real games, so it was among the reasons that I switched to a different board/CPU.
The card was probably an FX5700 Ultra but it could have been a Ti4200 which I switched to somewhere along the way.
My FX5700U proved to be occasionally glitchy when put under stress, so for me it could be dismissed as hardware. But as I recall that particular test was always blue screening at the same point.

Yup, it's the scene with the turtle 😀 😀

Matze79, in participation of imminent arrival of some high powered AGP graphics card, I've assembled the Athlon XP 3200+ machine again:

- Athlon XP 3200+
- Abit NF7-S
- 2x 1 GB DDR 400 3-3-3-8
- AGP GeForce 6600 GT
- Windows XP SP3
- nForce driver 5.10
- GeForce driver 93.71 WHQL from November 2006

The machine now completes 3DMark2003 including the nature test. Here a shot I took:

Ancient thread revival!

I've been banging my head against the wall trying to get 3DMark 03 to get past the Mother Nature test on a couple of retro builds I've done with GeForce 6x00 cards and this last post detailing GeForce driver version 93.71 has finally fixed it! Thank you! 😀

Yeah this is kind of a notorious crash. I guess it's some driver bug that only happens with certain hardware combinations, not sure if the exact cause has been pinned down.
Maybe it's a combination of certain graphics cards with CPUs that don't support SSE2, but Standard Def didn't have the crash on 81.98 with a P3 and 6800GT. Maybe it doesn't affect 6800GT?
Anyway, it's good to know 93.71 fixes it.

I should have said this is on an Asus A7V333 with an AthlonXP1900+

I had the crash on a 6600GT too - but it now works perfectly!