Click to See Complete Forum and Search --> : Stack Overflow Problem


Laacke
May 4th, 2001, 09:37 AM
Hey ladies and gents
After starting up my machine this morning I got a "blue-screen-of-death" that came up right after everything loaded up, and it stated:
------------------------------------
WINDOWS
Terminating thread due to a stack overflow problem. A VxD, possibly recently installed, has consumed too much stack space. Increase the setting of 'MinSPs' in SYSTEM.INI or remove recently installed VxD's. There are currently 3 SPs allocated.
Press any key to continue
------------------------------------
Any ideas what this means? I went into MSConfig but couldn't find anything called "MinSPs" under the SYSTEM.INI tab.

Any help would be much appreciated.

Cheers

Laacke
May 4th, 2001, 09:51 AM
I'm sorry... I should probably elaborate a little more about my system. It's a Dell OptiPlex GX110 PIII 550 running Windows 98SE. Just installed Norton A/V 5.0 a week ago with no problems (until today if this is the culprit?) Am I forgetting anything?

LagMonster
May 4th, 2001, 09:55 AM
How much RAM do you have? Do you have a Big enough Swap file? Try reinstalling that app.

Did the computer shut down properly the last time? Have you updated your version of windows. Some times with faster computers the shutdown process can corrupt files(rare). But they have a fix for it.

LagMonster
May 4th, 2001, 09:56 AM
I've also notice when in a BSOD if you hit [enter] it sometime recovers from the error, but any other key will terminate the application. I don't know why, its just something i have noticed.

tiffin_tom
May 4th, 2001, 10:15 AM
First thing you'll want to do is make sure your System.ini isn't disabled in MSCONFIG

Then go here (http://support.microsoft.com/support/kb/articles/q149/0/83.asp?LN=EN-US&SD=gn&FR=0&qry=minsp&rnk=1&src=DHCS_MSPSS_gn_SRCH&SPR=W98)

imaeditedbysowulo
May 4th, 2001, 11:54 AM
I have run into that problem with a GX110 also. I tried changing the MinSP's to 4, but it didn't seem to decrease the frequency of the problem. I ended up reimaging the box and never have seen that error again.