noam
asked on
windows protection error ???
my windows doesn't work it write to me :
" windows protection error please restart your computer "
and sometimes i have ablue screen "vxd error " or somthing like this.
what is the windows protecttion error ?
how can i fix this errors ?
tanks ?
" windows protection error please restart your computer "
and sometimes i have ablue screen "vxd error " or somthing like this.
what is the windows protecttion error ?
how can i fix this errors ?
tanks ?
a gpf can be caused by hardware such as bad memory (did you do a memory upgrade??) or by bad software (new drivers, older software)
a gpf can be caused by hardware such as bad memory (did you do a memory upgrade??) or by bad software (new drivers, older software)
a gpf can be caused by hardware such as bad memory (did you do a memory upgrade??) or by bad software (new drivers, older software)
Mark Aerts, please don't post the same comment 3 times. Watch out or I'll WinNuke your ass of this site!
Gee Noam, you're asking how to stop that 'Blue Screen Of Death', as it's commonly called from appearing, also how to stop windows protection errors and such...
I would advise you to re-install windows95 and bare the following in mind when maintaining your computer:
1. Defragment and Scan your drives regularly
2. When you're tired of a program (like a demo, for instance) you cannot just delete the folder, but you have to uninstall it, using the control panel applet called ' add/remove programs'
3. Don't install new drivers if you don't knwo the correct installation procedure. Leave this to an expert.
4. Get a virus scanning program, and scan your files every day!
These little guidelines should stop a lot of GPF's from occuring.
If you really want to play it safe, go for Windows NT.
I think this answers most of your question!
Kind Regards!
Simon
I would advise you to re-install windows95 and bare the following in mind when maintaining your computer:
1. Defragment and Scan your drives regularly
2. When you're tired of a program (like a demo, for instance) you cannot just delete the folder, but you have to uninstall it, using the control panel applet called ' add/remove programs'
3. Don't install new drivers if you don't knwo the correct installation procedure. Leave this to an expert.
4. Get a virus scanning program, and scan your files every day!
These little guidelines should stop a lot of GPF's from occuring.
If you really want to play it safe, go for Windows NT.
I think this answers most of your question!
Kind Regards!
Simon
Oh yeah, before I forget:
the Windows Protection error is when a program attempts to write to a memory address that has been reserved by windows for it's own use. Windows protects itself and BAM, you've got yourself one very nice crash!
the above explanation is rather simple, but it gives you an understandable idea of what is happening...
OK now,
see ya later!
Simon
the Windows Protection error is when a program attempts to write to a memory address that has been reserved by windows for it's own use. Windows protects itself and BAM, you've got yourself one very nice crash!
the above explanation is rather simple, but it gives you an understandable idea of what is happening...
OK now,
see ya later!
Simon
Mark Aerts, please don't post the same comment 3 times. Watch out or I'll WinNuke your ass of this site!
What is this Viper, you're not on one of those kiddy pages here. We try to help people,
never threaten them.
Willyou please go away.
BTW, it's veryeasy to have 3 posts go thru when EE is busy and you get the screen that says "Server to busy to handle your request".
Everytime you try it often make an identical post.
---------------
noam, please reject viper and read this.
http://www.slip.net/~gregoryn/fatal.htm
Regards
Bud
What is this Viper, you're not on one of those kiddy pages here. We try to help people,
never threaten them.
Willyou please go away.
BTW, it's veryeasy to have 3 posts go thru when EE is busy and you get the screen that says "Server to busy to handle your request".
Everytime you try it often make an identical post.
---------------
noam, please reject viper and read this.
http://www.slip.net/~gregoryn/fatal.htm
Regards
Bud
No threat from me, Smeebud.
It's a shame that EE's server can't take the traffic...
about that site of yours, i've seen it but it's way too elaborated for a novice computer user. Only when you get that exact same error all the time, this site is interesting!
The guidelines I provided to NOAM are general rules to keep in mind, and do make a difference, I'm sure you can agree on this!
If not, post an 'understandable' alternative, and you can winnuke MY ass to jupiter, for all i care...
But again, I'm just as serious about helping other guys (& girls, for that matter) out, if they have a problem!
with the kindest of regards possibly intended,
greetings!
Simon
It's a shame that EE's server can't take the traffic...
about that site of yours, i've seen it but it's way too elaborated for a novice computer user. Only when you get that exact same error all the time, this site is interesting!
The guidelines I provided to NOAM are general rules to keep in mind, and do make a difference, I'm sure you can agree on this!
If not, post an 'understandable' alternative, and you can winnuke MY ass to jupiter, for all i care...
But again, I'm just as serious about helping other guys (& girls, for that matter) out, if they have a problem!
with the kindest of regards possibly intended,
greetings!
Simon
Ok,
Peace.
I think you suggestions are very good. I'll take back the part about rejecting you. From what I've read of your's, you have a very good grasp of the [BIG UGLY BLUE SCREEN].
The only thing I would add is pertaining to #2 of your post. The "add/remove programs"
leave much to be desired leaving often a lot of junk in the registry and often files in windows, windows.ini, system and system.ini.
I recommend , well I like cleansweep.
The http://www.slip.net/~gregoryn/fatal.htm has a very good comprehensive look at the problem. if you have not seen it, you might like to take a look.
As far as winnuke goes. I know there are some nasty ones out there now. If you have any
suggestions as to how to get the estsecurity from them, I'd love to hear about it.
Noam, I'm kind of a fanatic when it comes to installations and un-nstallations so I've prepared the below, this works even with IE, believe it or not::))
------------
Take 5 extra minutes on installations and you
will always have a uncluttered system; and maybe
prevent yourself from having to reformat your harddrive
and reinstall Win95.
Utilities Needed:
1. Get WRP, free.
WRPV3.ZIP is the Best and easiest Registry Backup/Restore
I've Seen. Go To:
http://www.webdev.net/orca/ and Search for WRP and
download it and install. It's a well written batch file operation
that saves your,
AUTOEXEC.BAT
SYSTEM.DAT
USER.DAT
PROTOCOL.INI
SYSTEM.INI
WIN.INI
CONFIG.SYS
MSDOS.SYS
And will restore all to there original state if needed.
This has save my tail on many occasions.
2. Wmatch.exe. This small free utility can be obtained from
http://ftpsearch.ntnu.no/. It's 199.526 in size.
PURPOSE
WMATCH lets you place the filenames of two directories in
side-by-side windows, and then shows you which files are the
same and which are different.
3. Cleansweep, or a good installation monitor that records
changes to ALL system records. Including C:\Windows files,
C:\Windows\System files, System.ini, Win.ini, Config,sys,
Autoexec.bat, Protoco.ini, and most Important, your Registry.
OK. 1st thing to do is make a new directory, I call mine A-win,
then a subdirectory called A-sys. Putting these on a separate
drive is preferable, but if you don't have a separate drive,
the new directories will do just fine.
Now, open two instances of you file manager side by side.
Highlight all the files [not folders] in C:\Windows and Drag them
to A-win, thus copying them. Then do the same with
C:\Windows\Systems, Highlight and drag all files to Subdirectory
A-sys.
Now you have a easy to get at backup of the important files.
3. The extra mile: Copy all between the double lines and paste it
to notepad or your favorite text editor, then "Save as" Change.bat.
===================
@ECHO OFF
fc before.reg after.reg > changes.txt
===================
OK, the installation begins:
1. Here, before you do anything, you open your registry and export
the entire registry, named "BEFORE.REG" to C:\1
(C:\1 is my saving directory.)
Then after all the installation is finished you export again
only call this Export "AFTER.REG".
2. Run Wmatch and make sure that there are no "Different" files between
C:\Windows and A-win, nor C:\Windows\System and A-sys.
3. Run WRP backup for a fresh copy of your important system files.
4. Close all running applications; you must leave Explorer in your
Task Manager/Ctrl+Alt+Del on. 95 won't run without it.
5. Start your Cleansweep Monitor.
6. Click Start.....then Run.....then type or browse to the setup program
and run your installation.
7. If the program says to reboot, go to your Cleansweep Monitor 1st
and Stop the Monitoring, save the report to a text file, name it the
name of the "program.txt". Close the Monitor then reboot. Not all
programs need rebooting on installation.
OTHERWISE, After the installation of your new software you should
run it once before you stop Cleansweep Monitor.
Most of the programs store their settings not only during the installation
but during the first start. To log these modifications too, it is recommended
to start the program once, open some windows before you stop and
save your Cleansweep Monitor log.
8. Open your registry and make your "AFTER.REG"
then open a dos window and CD to you C:\1 directory and run your
"Change.bat". That will produce a text file that neatly shows you all
of the changes made to your registry. I always rename the
"Change.txt" to the name of the program.
9. That's it. You now have all changes recorded and the ability to
completely uninstall it if you don't like it.
10. If you're going to keep it, run Wmatch.exe and copy all new files
to their corresponding directories; A-win and A-sys.
If you want to uninstall it. Run Cleansweep remove. That takes care
of everything in most cases. If your removing the application either
right away or soon, when you do, re-boot to Real Dos Mode and
CD to WRP, EXAMPLE:
C:\WRP>RESTORE [enter]
and it will put your registry and other system files right back in the
exact shape they were in before the installation.
11. Run Wmatch to see that it shows no differences in your windows
files or your windows\system files periodically.
12. This sounds like a lot more work than it really is. It's about 5 extra
minutes on installations and you will always have a uncluttered
system.
Regards to all
Bud
Peace.
I think you suggestions are very good. I'll take back the part about rejecting you. From what I've read of your's, you have a very good grasp of the [BIG UGLY BLUE SCREEN].
The only thing I would add is pertaining to #2 of your post. The "add/remove programs"
leave much to be desired leaving often a lot of junk in the registry and often files in windows, windows.ini, system and system.ini.
I recommend , well I like cleansweep.
The http://www.slip.net/~gregoryn/fatal.htm has a very good comprehensive look at the problem. if you have not seen it, you might like to take a look.
As far as winnuke goes. I know there are some nasty ones out there now. If you have any
suggestions as to how to get the estsecurity from them, I'd love to hear about it.
Noam, I'm kind of a fanatic when it comes to installations and un-nstallations so I've prepared the below, this works even with IE, believe it or not::))
------------
Take 5 extra minutes on installations and you
will always have a uncluttered system; and maybe
prevent yourself from having to reformat your harddrive
and reinstall Win95.
Utilities Needed:
1. Get WRP, free.
WRPV3.ZIP is the Best and easiest Registry Backup/Restore
I've Seen. Go To:
http://www.webdev.net/orca/ and Search for WRP and
download it and install. It's a well written batch file operation
that saves your,
AUTOEXEC.BAT
SYSTEM.DAT
USER.DAT
PROTOCOL.INI
SYSTEM.INI
WIN.INI
CONFIG.SYS
MSDOS.SYS
And will restore all to there original state if needed.
This has save my tail on many occasions.
2. Wmatch.exe. This small free utility can be obtained from
http://ftpsearch.ntnu.no/. It's 199.526 in size.
PURPOSE
WMATCH lets you place the filenames of two directories in
side-by-side windows, and then shows you which files are the
same and which are different.
3. Cleansweep, or a good installation monitor that records
changes to ALL system records. Including C:\Windows files,
C:\Windows\System files, System.ini, Win.ini, Config,sys,
Autoexec.bat, Protoco.ini, and most Important, your Registry.
OK. 1st thing to do is make a new directory, I call mine A-win,
then a subdirectory called A-sys. Putting these on a separate
drive is preferable, but if you don't have a separate drive,
the new directories will do just fine.
Now, open two instances of you file manager side by side.
Highlight all the files [not folders] in C:\Windows and Drag them
to A-win, thus copying them. Then do the same with
C:\Windows\Systems, Highlight and drag all files to Subdirectory
A-sys.
Now you have a easy to get at backup of the important files.
3. The extra mile: Copy all between the double lines and paste it
to notepad or your favorite text editor, then "Save as" Change.bat.
===================
@ECHO OFF
fc before.reg after.reg > changes.txt
===================
OK, the installation begins:
1. Here, before you do anything, you open your registry and export
the entire registry, named "BEFORE.REG" to C:\1
(C:\1 is my saving directory.)
Then after all the installation is finished you export again
only call this Export "AFTER.REG".
2. Run Wmatch and make sure that there are no "Different" files between
C:\Windows and A-win, nor C:\Windows\System and A-sys.
3. Run WRP backup for a fresh copy of your important system files.
4. Close all running applications; you must leave Explorer in your
Task Manager/Ctrl+Alt+Del on. 95 won't run without it.
5. Start your Cleansweep Monitor.
6. Click Start.....then Run.....then type or browse to the setup program
and run your installation.
7. If the program says to reboot, go to your Cleansweep Monitor 1st
and Stop the Monitoring, save the report to a text file, name it the
name of the "program.txt". Close the Monitor then reboot. Not all
programs need rebooting on installation.
OTHERWISE, After the installation of your new software you should
run it once before you stop Cleansweep Monitor.
Most of the programs store their settings not only during the installation
but during the first start. To log these modifications too, it is recommended
to start the program once, open some windows before you stop and
save your Cleansweep Monitor log.
8. Open your registry and make your "AFTER.REG"
then open a dos window and CD to you C:\1 directory and run your
"Change.bat". That will produce a text file that neatly shows you all
of the changes made to your registry. I always rename the
"Change.txt" to the name of the program.
9. That's it. You now have all changes recorded and the ability to
completely uninstall it if you don't like it.
10. If you're going to keep it, run Wmatch.exe and copy all new files
to their corresponding directories; A-win and A-sys.
If you want to uninstall it. Run Cleansweep remove. That takes care
of everything in most cases. If your removing the application either
right away or soon, when you do, re-boot to Real Dos Mode and
CD to WRP, EXAMPLE:
C:\WRP>RESTORE [enter]
and it will put your registry and other system files right back in the
exact shape they were in before the installation.
11. Run Wmatch to see that it shows no differences in your windows
files or your windows\system files periodically.
12. This sounds like a lot more work than it really is. It's about 5 extra
minutes on installations and you will always have a uncluttered
system.
Regards to all
Bud
Bud:
about your remark:
"As far as winnuke goes. I know there are some nasty ones out there now. If you have any
suggestions as to how to get the estsecurity from them, I'd love to hear about it. "
What is estsecurity ?
about your remark:
"As far as winnuke goes. I know there are some nasty ones out there now. If you have any
suggestions as to how to get the estsecurity from them, I'd love to hear about it. "
What is estsecurity ?
Ok, Viper. Here's about all I know.
---------
http://www.windowscentral.com/features/reports/bugs/internet/fixall/
These are the patches for OOBNuke, Winnuke, Jolt, SSPING, IceNuke and TearDrop.
Patches for Microsoft Windows 95
Use the following steps to upgrade to Winsock 2.2 and patch the Internet bugs in
Windows 95. Be sure to perform these steps in the order as they appear.
1.Install the MS DUN 1.2 Upgrade (MSDUN12.EXE) and reboot.
2.Install the Winsock 2.2 Upgrade (WS2SETUP.EXE) and reboot.
3.Install the Winsock 2.2 Patch (VIPUP20.EXE) and reboot. This step fixes the IP
nukes such as SSPING and Teardrop.
4.Install the Land patch (VTCPUP20.EXE) and reboot.
5.Rename VNBT.386 to VNBT.BAK or use the VNBT.386 Fix (VNBT.EXE) and
reboot. This step fixes the WinNuke bug.
Patches for Microsoft Windows NT
1.Install Service Pack 3 (NT4SP3_I.EXE)
2.Install the Bonk, Boink and Teardrop2 patch (TEARFIXI.EXE). This patch
supercedes the ICMP-fix, OOB-fix, Simptcp-fix and Land hotfixes.
Regards
Bud
---------
http://www.windowscentral.com/features/reports/bugs/internet/fixall/
These are the patches for OOBNuke, Winnuke, Jolt, SSPING, IceNuke and TearDrop.
Patches for Microsoft Windows 95
Use the following steps to upgrade to Winsock 2.2 and patch the Internet bugs in
Windows 95. Be sure to perform these steps in the order as they appear.
1.Install the MS DUN 1.2 Upgrade (MSDUN12.EXE) and reboot.
2.Install the Winsock 2.2 Upgrade (WS2SETUP.EXE) and reboot.
3.Install the Winsock 2.2 Patch (VIPUP20.EXE) and reboot. This step fixes the IP
nukes such as SSPING and Teardrop.
4.Install the Land patch (VTCPUP20.EXE) and reboot.
5.Rename VNBT.386 to VNBT.BAK or use the VNBT.386 Fix (VNBT.EXE) and
reboot. This step fixes the WinNuke bug.
Patches for Microsoft Windows NT
1.Install Service Pack 3 (NT4SP3_I.EXE)
2.Install the Bonk, Boink and Teardrop2 patch (TEARFIXI.EXE). This patch
supercedes the ICMP-fix, OOB-fix, Simptcp-fix and Land hotfixes.
Regards
Bud
tnx bud,
I knew most of that, but thanks for the whole list!
All I actually wanted to know is what the word 'estsecurity' means...
greetz,
Simon
PS: I think noam's computer has crashed again, as he's not posting anymore! Auch, seems we got to him too late with the solution...
I knew most of that, but thanks for the whole list!
All I actually wanted to know is what the word 'estsecurity' means...
greetz,
Simon
PS: I think noam's computer has crashed again, as he's not posting anymore! Auch, seems we got to him too late with the solution...
Simon,
Typo, "estsecurity" was supposed to be "Best security".
I just went from 32mg to 64mg. 2 edo 32's. Now I've had a few of those ugly screens myself. Never had any with 32.
I think it's probably a tweak or balance between premanent swap, cache and
[vcache]
MaxFileCache=8192
-------
Any ideas??
There's a good article;
Memory Upgrades: The Truth About 64mg Ram Limits
http://developer.intel.com/design/pcisets/memory.htm
The Relationship Between Cache and Main Memory
I think we've lost noam?
Regards,
Bud
Good to meet you:)
Typo, "estsecurity" was supposed to be "Best security".
I just went from 32mg to 64mg. 2 edo 32's. Now I've had a few of those ugly screens myself. Never had any with 32.
I think it's probably a tweak or balance between premanent swap, cache and
[vcache]
MaxFileCache=8192
-------
Any ideas??
There's a good article;
Memory Upgrades: The Truth About 64mg Ram Limits
http://developer.intel.com/design/pcisets/memory.htm
The Relationship Between Cache and Main Memory
I think we've lost noam?
Regards,
Bud
Good to meet you:)
Bud,
I have 64Mb SDRAM on ASUS TX97-X and AMD K6-200 @225
Stable as hell. Go figure...
Try MinFileCache=<size of your MB cache>
MaxFileCache=4096
Works for me...
Da greetz!
Simon
I have 64Mb SDRAM on ASUS TX97-X and AMD K6-200 @225
Stable as hell. Go figure...
Try MinFileCache=<size of your MB cache>
MaxFileCache=4096
Works for me...
Da greetz!
Simon
OK,
Thanks, I'll give it a go.
Smee
Thanks, I'll give it a go.
Smee
hmm, I think bud fell of the screen
all that's left is smee...
Lousy sense of humor, i know, but what can you do while waiting for noam?
all that's left is smee...
Lousy sense of humor, i know, but what can you do while waiting for noam?
No, Mine was an attempt at humor.
A non-sober way of saying, 'It's me"::))>>smee.
It's how my name came about.
Might as well have some fun here.
Adios
Bud
A non-sober way of saying, 'It's me"::))>>smee.
It's how my name came about.
Might as well have some fun here.
Adios
Bud
I'll second that thought, bud!
I think noam has given up computers and has gone 'back to nature' or something...(?)
I think noam has given up computers and has gone 'back to nature' or something...(?)
Bud,
did you see the Windows 98 presentation in Chicago?
Maybe we should give Billy-Boy a call.
did you see the Windows 98 presentation in Chicago?
Maybe we should give Billy-Boy a call.
Simon,
No, missed that. Was it on TV or did you go live?
How was it.
All I read about 98 sounds good so far. As far as I know, we will have a choice to install
IE??
At what devious cost I wonder?
L8R
No, missed that. Was it on TV or did you go live?
How was it.
All I read about 98 sounds good so far. As far as I know, we will have a choice to install
IE??
At what devious cost I wonder?
L8R
It was on the news worldwide.
I didn't see it live as I live in Belgium (Europe), and chicago is kinda out of my way.
It was awesome. There was this MS-hotshot, together with Gates, and he was showing the audience the PnP-support. He hot-plugged a scanner, opened 'Imaging' and as he hit the SCAN-button: BAM, the o so very familiar BSOD. You should have seen the look on BG's face, and he murmeled something like 'Hmm, I think this is why we're not shipping Windows 98 yet'
I think it has made the news all over the world!
So Bill, if you'd ever get to read this thread, you know how to prevent this from happening! (wishful thinking...)
See ya!
Simon
I didn't see it live as I live in Belgium (Europe), and chicago is kinda out of my way.
It was awesome. There was this MS-hotshot, together with Gates, and he was showing the audience the PnP-support. He hot-plugged a scanner, opened 'Imaging' and as he hit the SCAN-button: BAM, the o so very familiar BSOD. You should have seen the look on BG's face, and he murmeled something like 'Hmm, I think this is why we're not shipping Windows 98 yet'
I think it has made the news all over the world!
So Bill, if you'd ever get to read this thread, you know how to prevent this from happening! (wishful thinking...)
See ya!
Simon
Ya know, That guy just doesn't care>
I read an article where he said, paraphrasing, "....I don't know why anyone would want to buy Win95 when we have the best 32bit system right here in NT....".
Go figure.
Bud
I read an article where he said, paraphrasing, "....I don't know why anyone would want to buy Win95 when we have the best 32bit system right here in NT....".
Go figure.
Bud
Obviously, he wouldn't be making this comment if Win95/98 was more expensive than WinNT...
Do you think NOAM has crashed together with Win98 ?
S.
Do you think NOAM has crashed together with Win98 ?
S.
I think NOAM has NOEM'ed himself.
B
B
Grandmaster B,
what the **** is NOEM'ed ? (i.e. what does the word mean?)
S.
what the **** is NOEM'ed ? (i.e. what does the word mean?)
S.
Maybe NOAM is sleeping... Wait a sec, I'll wake him up:
noam NOAM NOOOOOOOOOOOAAAAAAAAAAAAAM
WAAAAAAAAAKE UUUUUUUUUUUP
Good morning, kid, Could you please review my answer and give me some points....
Simon
noam NOAM NOOOOOOOOOOOAAAAAAAAAAAAAM
WAAAAAAAAAKE UUUUUUUUUUUP
Good morning, kid, Could you please review my answer and give me some points....
Simon
Bud,
how did it go with the MinFileCache/MaxFileCache?
Any improvements?
Simon
how did it go with the MinFileCache/MaxFileCache?
Any improvements?
Simon
1st NOEM'd as in
C:\WINDOWS\EMM386.EXE NOEMS
2. Yea, it works great, thanks. I have not had a error or blue screen since.
Good work.
Bud
C:\WINDOWS\EMM386.EXE NOEMS
2. Yea, it works great, thanks. I have not had a error or blue screen since.
Good work.
Bud
I have
[vcache]
MinFileCache=512
MaxFileCache=4096
This lets my system to write to the HDD like it's supposed to from time to time.
I think theerrors were because Ram and swapfile was holding instead of writting??
Bud
[vcache]
MinFileCache=512
MaxFileCache=4096
This lets my system to write to the HDD like it's supposed to from time to time.
I think theerrors were because Ram and swapfile was holding instead of writting??
Bud
Bud:
See,
ya still CAN teach an old dog new tricks...
I've only discovered this site less than a week ago, through my friend Mark Aerts (the one I was goin' to WinNuke, remember), and I already have 1700 expert points... Not too bad, I should think! (for a beginner, that is)
See ya,
Simon
See,
ya still CAN teach an old dog new tricks...
I've only discovered this site less than a week ago, through my friend Mark Aerts (the one I was goin' to WinNuke, remember), and I already have 1700 expert points... Not too bad, I should think! (for a beginner, that is)
See ya,
Simon
Simon, Noam is Hebrew-based name. Means "pleasant".
That is good Simon. Keep 'um coming
Who knows what lay silently hidden and unfostered in the depths of any persons mind?
Bud
Who knows what lay silently hidden and unfostered in the depths of any persons mind?
Bud
Well Bud,
in our case, plenty of witty remarks, I should say...
Simon
in our case, plenty of witty remarks, I should say...
Simon
ASKER
the error come bake after i do format to my h-disk and install the windows again
NOAM:
have you checked for viruses yet ? and scandisk?
Maybe your SIMM's are faulty!
Glad to see you're still with us!
S
have you checked for viruses yet ? and scandisk?
Maybe your SIMM's are faulty!
Glad to see you're still with us!
S
Does that error occure while booting your computer and prevent your from getting farter?
OeilNoir, I think your last word should be "further". "Farter" is
something (or someone) different :-)))
Noam, how about feedback on your hardware ? Did you tried to overclock
computer ?
something (or someone) different :-)))
Noam, how about feedback on your hardware ? Did you tried to overclock
computer ?
Noem,
Please read:
What Are Windows 95 Fatal Exception Errors
(scroll down for codes and fixes at bottom of page)
When you attempt to start Windows or an application inside of Windows, you may encounter errors
similar to the following:
A fatal exception <XY> has occurred at xxxx:xxxxxxxx
Fatal exception errors are codes returned by a program in the following cases:
- Access to an illegal instruction has been encountered
- Invalid data or code has been accessed
- The privilege level of an operation is invalid
When any of these occur, the processor returns an exception to the operating system, which in turn is
handled as a Fatal Exception Error. In many cases the exception is nonrecoverable and the system must
either be restarted or shutdown, depending upon the severity of the error.
In the following example of a Fatal Exception error
A fatal exception <XY> has occurred at xxxx:xxxxxxxx
the <XY> represents the actual processor exception from 00 to 0F.
The xxxx:xxxxxxxx represents the enhanced instruction pointer to
the code segment and the 8-bit address is the actual address where
the exception occurred.
Windows does not cause these errors, but has the exception handling routine for that particular
processor exception, which displays the above message.
The following article details the processor exceptions and their meaning.
For more information about troubleshooting strategies for Fatal Exception Errors, see the Knowledge
Base articles listed at the end ofthis document.
MORE INFORMATION
The following are the processor exceptions and their definitions:
00: Divide Fault
The processor returns this exception when it encounters a divide fault.
A divide fault occurs if division by zero is attempted or if the
result of the operation does not fit in the destination operand.
02: NMI interrupt
Interrupt 2 is reserved for the hardware Non-Maskable-Interrupt condition. No exceptions trap
through interrupt 2.
04: Overflow trap
The overflow trap occurs after an INTO instruction has executed and the 0F bit is set to 1.
05: Bounds Check Fault
The BOUND instruction compares the array index with an upper and lower bound.
If the index is out of range, then the processor traps to interrupt 05.
06: Invalid Opcode fault
This error is returned if any one of the following conditions are true:
- The processor tries to decode a bit pattern that does not correspond to any legal computer instruction
- The processor attempts to execute an instruction that contains invalid operands
- The processor attempts to execute a protected-mode instruction while running in virtual 8086 mode.
- The processor tries to execute a LOCK prefix with an instruction that cannot be locked.
07: Coprocessor not available fault
This error occurs if the computer does not have a math coprocessor and the EM bit of register
CR0 is set indicating that Numeric Data Processor emulation is being used. Each time a floating
point operation is executed, an interrupt 07 occurs.
This error also occurs when a math coprocessor is used and a task switch is executed.
Interrupt 07 tells the processor that the current state of the coprocessor needs to be saved so
that it can be used by another task.
08: Double Fault
Processing an exception sometimes triggers a second exception. In the event that this occurs,
the processor will issue a interrupt 08 for a double fault.
09: Coprocessor Segment Overrun
This error occurs when a floating point instruction causes a memory access that runs beyond the
end of the segment. If the starting address of the floating point operand is outside the segment,
then a General Protection Fault occurs (interrupt 0D).
10 (0Ah): Invalid Task State Segment Fault
Because the Task State Segment contains a number of descriptors, any number of conditions
may cause exception 0A. Typically, the processor can gather enough information from the Task
State Segment to issue another fault pointing to the actual problem.
See "Microsoft's Programming the 80386/80486 Guide" for more information.
11 (0Bh): Not Present Fault
The Not present interrupt allows the operating system to implement virtual memory through the
segmentation mechanism. When a segment is marked as "not present", the segment is swapped
out to disk. The interrupt 0B fault is triggered when an application needs access to the segment.
12 (0Ch): Stack Fault
A Stack Fault occurs with error code 0 if an instruction refers to memory beyond the limit of
the stack segment. If the operating system supports expand-down segments, increasing the
size of the stack should alleviate the problem. Loading the Stack Segment with
invalid descriptors will result in a general protection fault.
13 (0Dh): General Protection Fault
Any condition which is not covered by any of the other processor exceptions will result in a
general protection fault. The exception indicates that this program has been corrupted in memory
usually resulting in immediate termination of the application.
14 (0Eh): Page Fault
The Page Fault interrupt allows the operating system to implement virtual memory on a demand-paged basis.
An interrupt 14 usually isissued whenever an access to a page directory entry or page table with the present
bit set to 0 (Not present) occurs. The operating system makes the page present (usually retrieves the page
from virtual memory) and re-issues the faulting instruction, which then can access the segment.
A page fault also occurs when a paging protection rule is violated (when the retrieve fails, or data retrieved is
invalid, or the code that issued the fault broke the protection rule for the processor).
In these cases the operating system takes over for the appropriate action.
16 (10h): Coprocessor error Fault
This interrupt occurs when an unmasked floating-point exception has been signaled a
previous instruction. (Because the 80386 does not have access to the Floating Point Unit,
it checks the ERROR\ pin to test for this condition). This is also triggered by a WAIT
instruction if the Emulate Math Coprocessor bit at CR0 is set.
17 (11h): Alignment Check Fault
This interrupt is only used on the 80486 CPUs. An interrupt 17 is issued when code executing
at ring privilege 3 attempts to access a word operand that is not on an even-address boundary,
a double-word operand that is not divisible by four, or a long real or temp real whose address
is not divisible by eight. Alignment checking is disabled when the CPU is first powered up and
is only enabled in protected mode.
Fatal Exception
Error Using DHCP
SYMPTOMS
When you use Winipcfg.exe to release or renew IP addresses obtained using DHCP, or when you start
Windows 95 with the network adapter configured to obtain IP addresses using DHCP, you may
receive an error message similar to the following message on a blue screen:
Fatal exception 0E at 0028:C433442B in VXD octk16.sys (01) + 0000342B. This was called from
0028:C003C47C in VXD NDIS (01) + 00000D7C. It may be possible to continue normally.
CAUSE
When you are using the Windows 95 DHCP client, a buffer in memory used to send a DHCP message
may be freed before the message has been completely sent. The error occurs when the network
adapter driver attempts to access this buffer to send the information on the wire.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows 95. A fix to this problem is in
development, but has not been regression tested and may be destabilizing in production environments.
Microsoft does not recommend implementing this fix at this time. Contact Microsoft Technical
Support for more information on the availability of this fix.
MORE INFORMATION
The fatal exception error typically occurs in the MAC driver, although it may also occur in NDIS itself.
This symptom may occur more frequently with Token Ring adapters using locally administered
addresses (LAAs), although it has been reported to occur with Ethernet adapters and without using
LAAs. Fatal Exception Error When Starting an MS-DOS Session
BETA INFORMATION BETA INFORMATION BETA INFORMATION BETA
This article discusses a Beta release of a Microsoft product. The information in this article is provided
as-is and is subject to change without notice.
No formal product support is available from Microsoft for this Beta product. For information about
obtaining support for a Beta release, please see the documentation included with the Beta product files,
or check the Web location from which you downloaded the release.
BETA INFORMATION BETA INFORMATION BETA INFORMATION BETA
**************************
The information in this article applies to:
Microsoft Windows 98
SYMPTOMS
When you attempt to start an MS-DOS session in Windows 98, you may receive the following error
message:
A Fatal Exception 0E has occurred at 0028:C02B1E2B in VXD VCOND(03) + 0000176F.
The current application will be terminated.
CAUSE
This error message can occur if you are already running 64 MS-DOS sessions.
RESOLUTION
To work around this problem, quit one or more MS-DOS sessions before you start a new session. To
do so, type "exit" (without quotation marks) at a command prompt, and then press ENTER.
STATUS
Microsoft has confirmed this to be a problem in Windows 98. We are researching this problem and will
post new information here in the Microsoft Knowledge Base as it becomes available.
Keywords : kberrmsg win98 Version : WINDOWS: Platform : WINDOWS
"Fatal Exception 0D" Error Message Installing Program message: A Fatal Exception 0E has occurred
at 0028:C02B1E2B in VXD VCOND(03) + 0000176F
Last reviewed: March 20, 1998 Article ID: Q162390 95 WINDOWS kberrmsg kb3rdparty kbsetup
The information in this article applies to:
Microsoft Windows 95 Microsoft Windows 98
**************************
BETA INFORMATION BETA INFORMATION BETA INFORMATION BETA
This article discusses a Beta release of a Microsoft product. The information in this article is provided
as-is and is subject to change without notice.
No formal product support is available from Microsoft for this Beta product. For information about
obtaining support for a Beta release, please see the documentation included with the Beta product files,
or check the Web location from which you downloaded the release.
BETA INFORMATION BETA INFORMATION BETA INFORMATION BETA
**************************
SYMPTOMS
When you are installing any program that uses the Windows Install Wizard or the InstallShield
installation program, you may receive the following error message:
A Fatal Exception Error 0D has occurred in VxD VMM(01) + 00001840
CAUSE
This error can occur if you have Stacker version 4.1 installed on your computer.
RESOLUTION
To resolve this issue, use either of the following methods:
Contact Stac Electronics for a possible fix. Disable 32-bit disk access for all drives. To do this,
perform the following steps:
1. In Control Panel, double-click System.
2. On the Performance tab, click File System.
3. On the Troubleshooting tab, click the Disable All 32-Bit Protect-
Mode Drivers check box to select it.
4. Click OK.
MORE INFORMATION
The third-party product discussed in this article is manufactured by a vendor independent of Microsoft;
we make no warranty, implied or other- wise, regarding this product's performance or reliability.
Fatal Exception Error Starting Windows 95 error message: WINDOWS
This program has caused a Fatal Exception 0D at 00457:000040B1 and will be terminated
Last reviewed: February 11, 1998 Article ID: Q133440
**************************
BETA INFORMATION BETA INFORMATION BETA INFORMATION BETA
This article discusses a Beta release of a Microsoft product. The information in this article is provided
as-is and is subject to change without notice.
No formal product support is available from Microsoft for this Beta product. For information about
obtaining support for a Beta release, please see the documentation included with the Beta product files,
or check the Web location from which you downloaded the release.
BETA INFORMATION BETA INFORMATION BETA INFORMATION BETA
**************************
The information in this article applies to:
Microsoft Windows 95 Microsoft Windows 98
SYMPTOMS
When you start Windows 95, you may receive a blue error screen with the following error message:
WINDOWS This program has caused a Fatal Exception 0D at 00457:000040B1 and will be terminated.
Pressing any key causes the screen to turn black and the computer to stop responding (hang).
CAUSE
This problem can occur if you are using Adobe Type Manager with certain display drivers and the
Hardware Acceleration setting is not set to Full.
RESOLUTION
part 1
Bud
Please read:
What Are Windows 95 Fatal Exception Errors
(scroll down for codes and fixes at bottom of page)
When you attempt to start Windows or an application inside of Windows, you may encounter errors
similar to the following:
A fatal exception <XY> has occurred at xxxx:xxxxxxxx
Fatal exception errors are codes returned by a program in the following cases:
- Access to an illegal instruction has been encountered
- Invalid data or code has been accessed
- The privilege level of an operation is invalid
When any of these occur, the processor returns an exception to the operating system, which in turn is
handled as a Fatal Exception Error. In many cases the exception is nonrecoverable and the system must
either be restarted or shutdown, depending upon the severity of the error.
In the following example of a Fatal Exception error
A fatal exception <XY> has occurred at xxxx:xxxxxxxx
the <XY> represents the actual processor exception from 00 to 0F.
The xxxx:xxxxxxxx represents the enhanced instruction pointer to
the code segment and the 8-bit address is the actual address where
the exception occurred.
Windows does not cause these errors, but has the exception handling routine for that particular
processor exception, which displays the above message.
The following article details the processor exceptions and their meaning.
For more information about troubleshooting strategies for Fatal Exception Errors, see the Knowledge
Base articles listed at the end ofthis document.
MORE INFORMATION
The following are the processor exceptions and their definitions:
00: Divide Fault
The processor returns this exception when it encounters a divide fault.
A divide fault occurs if division by zero is attempted or if the
result of the operation does not fit in the destination operand.
02: NMI interrupt
Interrupt 2 is reserved for the hardware Non-Maskable-Interrupt condition. No exceptions trap
through interrupt 2.
04: Overflow trap
The overflow trap occurs after an INTO instruction has executed and the 0F bit is set to 1.
05: Bounds Check Fault
The BOUND instruction compares the array index with an upper and lower bound.
If the index is out of range, then the processor traps to interrupt 05.
06: Invalid Opcode fault
This error is returned if any one of the following conditions are true:
- The processor tries to decode a bit pattern that does not correspond to any legal computer instruction
- The processor attempts to execute an instruction that contains invalid operands
- The processor attempts to execute a protected-mode instruction while running in virtual 8086 mode.
- The processor tries to execute a LOCK prefix with an instruction that cannot be locked.
07: Coprocessor not available fault
This error occurs if the computer does not have a math coprocessor and the EM bit of register
CR0 is set indicating that Numeric Data Processor emulation is being used. Each time a floating
point operation is executed, an interrupt 07 occurs.
This error also occurs when a math coprocessor is used and a task switch is executed.
Interrupt 07 tells the processor that the current state of the coprocessor needs to be saved so
that it can be used by another task.
08: Double Fault
Processing an exception sometimes triggers a second exception. In the event that this occurs,
the processor will issue a interrupt 08 for a double fault.
09: Coprocessor Segment Overrun
This error occurs when a floating point instruction causes a memory access that runs beyond the
end of the segment. If the starting address of the floating point operand is outside the segment,
then a General Protection Fault occurs (interrupt 0D).
10 (0Ah): Invalid Task State Segment Fault
Because the Task State Segment contains a number of descriptors, any number of conditions
may cause exception 0A. Typically, the processor can gather enough information from the Task
State Segment to issue another fault pointing to the actual problem.
See "Microsoft's Programming the 80386/80486 Guide" for more information.
11 (0Bh): Not Present Fault
The Not present interrupt allows the operating system to implement virtual memory through the
segmentation mechanism. When a segment is marked as "not present", the segment is swapped
out to disk. The interrupt 0B fault is triggered when an application needs access to the segment.
12 (0Ch): Stack Fault
A Stack Fault occurs with error code 0 if an instruction refers to memory beyond the limit of
the stack segment. If the operating system supports expand-down segments, increasing the
size of the stack should alleviate the problem. Loading the Stack Segment with
invalid descriptors will result in a general protection fault.
13 (0Dh): General Protection Fault
Any condition which is not covered by any of the other processor exceptions will result in a
general protection fault. The exception indicates that this program has been corrupted in memory
usually resulting in immediate termination of the application.
14 (0Eh): Page Fault
The Page Fault interrupt allows the operating system to implement virtual memory on a demand-paged basis.
An interrupt 14 usually isissued whenever an access to a page directory entry or page table with the present
bit set to 0 (Not present) occurs. The operating system makes the page present (usually retrieves the page
from virtual memory) and re-issues the faulting instruction, which then can access the segment.
A page fault also occurs when a paging protection rule is violated (when the retrieve fails, or data retrieved is
invalid, or the code that issued the fault broke the protection rule for the processor).
In these cases the operating system takes over for the appropriate action.
16 (10h): Coprocessor error Fault
This interrupt occurs when an unmasked floating-point exception has been signaled a
previous instruction. (Because the 80386 does not have access to the Floating Point Unit,
it checks the ERROR\ pin to test for this condition). This is also triggered by a WAIT
instruction if the Emulate Math Coprocessor bit at CR0 is set.
17 (11h): Alignment Check Fault
This interrupt is only used on the 80486 CPUs. An interrupt 17 is issued when code executing
at ring privilege 3 attempts to access a word operand that is not on an even-address boundary,
a double-word operand that is not divisible by four, or a long real or temp real whose address
is not divisible by eight. Alignment checking is disabled when the CPU is first powered up and
is only enabled in protected mode.
Fatal Exception
Error Using DHCP
SYMPTOMS
When you use Winipcfg.exe to release or renew IP addresses obtained using DHCP, or when you start
Windows 95 with the network adapter configured to obtain IP addresses using DHCP, you may
receive an error message similar to the following message on a blue screen:
Fatal exception 0E at 0028:C433442B in VXD octk16.sys (01) + 0000342B. This was called from
0028:C003C47C in VXD NDIS (01) + 00000D7C. It may be possible to continue normally.
CAUSE
When you are using the Windows 95 DHCP client, a buffer in memory used to send a DHCP message
may be freed before the message has been completely sent. The error occurs when the network
adapter driver attempts to access this buffer to send the information on the wire.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows 95. A fix to this problem is in
development, but has not been regression tested and may be destabilizing in production environments.
Microsoft does not recommend implementing this fix at this time. Contact Microsoft Technical
Support for more information on the availability of this fix.
MORE INFORMATION
The fatal exception error typically occurs in the MAC driver, although it may also occur in NDIS itself.
This symptom may occur more frequently with Token Ring adapters using locally administered
addresses (LAAs), although it has been reported to occur with Ethernet adapters and without using
LAAs. Fatal Exception Error When Starting an MS-DOS Session
BETA INFORMATION BETA INFORMATION BETA INFORMATION BETA
This article discusses a Beta release of a Microsoft product. The information in this article is provided
as-is and is subject to change without notice.
No formal product support is available from Microsoft for this Beta product. For information about
obtaining support for a Beta release, please see the documentation included with the Beta product files,
or check the Web location from which you downloaded the release.
BETA INFORMATION BETA INFORMATION BETA INFORMATION BETA
**************************
The information in this article applies to:
Microsoft Windows 98
SYMPTOMS
When you attempt to start an MS-DOS session in Windows 98, you may receive the following error
message:
A Fatal Exception 0E has occurred at 0028:C02B1E2B in VXD VCOND(03) + 0000176F.
The current application will be terminated.
CAUSE
This error message can occur if you are already running 64 MS-DOS sessions.
RESOLUTION
To work around this problem, quit one or more MS-DOS sessions before you start a new session. To
do so, type "exit" (without quotation marks) at a command prompt, and then press ENTER.
STATUS
Microsoft has confirmed this to be a problem in Windows 98. We are researching this problem and will
post new information here in the Microsoft Knowledge Base as it becomes available.
Keywords : kberrmsg win98 Version : WINDOWS: Platform : WINDOWS
"Fatal Exception 0D" Error Message Installing Program message: A Fatal Exception 0E has occurred
at 0028:C02B1E2B in VXD VCOND(03) + 0000176F
Last reviewed: March 20, 1998 Article ID: Q162390 95 WINDOWS kberrmsg kb3rdparty kbsetup
The information in this article applies to:
Microsoft Windows 95 Microsoft Windows 98
**************************
BETA INFORMATION BETA INFORMATION BETA INFORMATION BETA
This article discusses a Beta release of a Microsoft product. The information in this article is provided
as-is and is subject to change without notice.
No formal product support is available from Microsoft for this Beta product. For information about
obtaining support for a Beta release, please see the documentation included with the Beta product files,
or check the Web location from which you downloaded the release.
BETA INFORMATION BETA INFORMATION BETA INFORMATION BETA
**************************
SYMPTOMS
When you are installing any program that uses the Windows Install Wizard or the InstallShield
installation program, you may receive the following error message:
A Fatal Exception Error 0D has occurred in VxD VMM(01) + 00001840
CAUSE
This error can occur if you have Stacker version 4.1 installed on your computer.
RESOLUTION
To resolve this issue, use either of the following methods:
Contact Stac Electronics for a possible fix. Disable 32-bit disk access for all drives. To do this,
perform the following steps:
1. In Control Panel, double-click System.
2. On the Performance tab, click File System.
3. On the Troubleshooting tab, click the Disable All 32-Bit Protect-
Mode Drivers check box to select it.
4. Click OK.
MORE INFORMATION
The third-party product discussed in this article is manufactured by a vendor independent of Microsoft;
we make no warranty, implied or other- wise, regarding this product's performance or reliability.
Fatal Exception Error Starting Windows 95 error message: WINDOWS
This program has caused a Fatal Exception 0D at 00457:000040B1 and will be terminated
Last reviewed: February 11, 1998 Article ID: Q133440
**************************
BETA INFORMATION BETA INFORMATION BETA INFORMATION BETA
This article discusses a Beta release of a Microsoft product. The information in this article is provided
as-is and is subject to change without notice.
No formal product support is available from Microsoft for this Beta product. For information about
obtaining support for a Beta release, please see the documentation included with the Beta product files,
or check the Web location from which you downloaded the release.
BETA INFORMATION BETA INFORMATION BETA INFORMATION BETA
**************************
The information in this article applies to:
Microsoft Windows 95 Microsoft Windows 98
SYMPTOMS
When you start Windows 95, you may receive a blue error screen with the following error message:
WINDOWS This program has caused a Fatal Exception 0D at 00457:000040B1 and will be terminated.
Pressing any key causes the screen to turn black and the computer to stop responding (hang).
CAUSE
This problem can occur if you are using Adobe Type Manager with certain display drivers and the
Hardware Acceleration setting is not set to Full.
RESOLUTION
part 1
Bud
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
- you try to install Win95 and got this error ?
- if not, did you got this error occasionally (pit'om ;) or you
tried to install something (what ?)
- what your hardware (CPU, RAM, motherboard, HDDs, CD, sound card,
video card)