Hello,

Since a week or two, when I try to play some (not all of them) 3D Game, my computer reboot by itself.

I want to precise that Auto Reboot on Error is disabled.

The entry in the System Event Log is :

Event ID: 1001
Source: Save Dump
Description:
The computer has rebooted from a bugcheck.
The bugcheck was :
0x0000009c (0x00000001, 0x00000000, 0xb2000000, 0x00000115)
Microsoft Windows 2000 [v15.2195]
A dump was saved in:
C:\WINNT\Minidump\Mini051200-05.dmp.

How can I know what is causing the problem?

Can somebody help me?

Your memory was overloaded I thinking.
The error code is error_stack_overflow.
Recursion too deep; the stack overflowed. 1001
Maybe I'm wrong but thats my thought.

Kenny

Go to the Microsoft Knowledge Base and search for 'Stop Messages', and narrow it down by entering the bugcheck code (the 0x0000009c bit) and see what comes up.
I think computing.net should devote a separate forum to Windows 2000 reboot/bSOD problems personally. There seem to be a lot of them.
Either that or scan the very helpful forums at www.ntcompatible.com and www.tomshardware.com for a possible solution.
Cheers

Thanks for you answers.

Kenny, do you know what could cause the stack overflow?

Hardware or software?

Richard, thanks for the adresses, but for the Microsoft KB, I already tried it and they don't have anything on this error code (just for NT4, and I don't think it means the same).

I agree with you about the reboot problems with Win2k.

But it just a question of time, people are not aware that a reboot in win2k is usually the same as a BSOD in 95/98.(learned it yesterday myself, after 2 days spent checking my hardware)

Software thats setting the stacks to high then your memory get overloaded.

You might be able to control it by not having to many programs starting up try disabling some from starting up.

Here is just a bit of something from Microsoft this is about NT but 2000 would also be included in this.

In the Microsoft Windows NT operating system, stack overflow is detected by hardware and software working together, using the page protection mechanisms. Each new Windows NT process has a maximum reserved stack size and an initial committed stack allocation. Committed memory is physically allocated to the process and is backed by the page file; it is a relatively "expensive" resource. Reserved memory is address space that is not mapped to real memory; it is a relatively "cheap" resource.

Try freeing up some memory.
Kenny

Hey Freekill,

I am having the same problem in Win2k. I was wondering what kind of Graphics card you use. I’m using a GeForce DDR (Prophet). I have only experienced this problem with the combination of GeForce based cards (several of them) and Win2k. My reboots are primarily in 3d apps, but, my system usually runs rock solid under Q3. Oddly, I’ve been getting reboots in 2D apps like AOK lately. I’m a LAN/computer tech myself and this issue is driving me nuts. I’ve tried swapping out hardware for almost every component in the system, aside from the HD, Power Supply, Floppy, and a CDR. I’m rather inclined to think it’s a complex interaction of several hardware components and Win2k, and not simply a stack overflow (which ought not happen with only standard processes and one app like AOK running).

Daren