Puter problems

[Torque]

I keep getting this screen can anyone tell me what to do???

fatal exception oe has occured at 0028:co2b4115 in vdx ifsmgr(04)

thx in advance from a puter dweeb.

[Wardog]

Sound like a DX Driver problem.Might try reinstalling DX7a

------------------
 
 
-= Death From Behind =-

[This message has been edited by Wardog (edited 03-08-2000).]

[weazel]

You have a Voodoo based card I`m assuming from the error,it looks to be a problem in the Voodoo control panel if I`m not mistaken.Uninstall it if this is the case and search for files related to the card and delete them,clean your registry of voodoo related strings and reinstall.

------------------
   
 JG2 "Richthofen"

[This message has been edited by weazel (edited 03-08-2000).]

[hblair]

hmmm, lets see here.

<scratches head>

OH! Yeah that problem...

Go to DOS Prompt.

Type: format C:

This will clear up all your problems while keeping our arses safe for a day or two!

 



[This message has been edited by hblair (edited 03-08-2000).]

[Torque]

Ya sorry i was sooo pissed forgot to say i'm CL rivatnt1 16 mg


heh thx hb was thinking that myself wanna come over and do it fer me.

[Minotaur]

 

Originally posted by Torque:
I keep getting this screen can anyone tell me what to do???

fatal exception oe has occured at 0028:co2b4115 in vdx ifsmgr(04)

thx in advance from a puter dweeb.

LOL

That means you have to stop hacking into your graphic files and putting view holes in the rear cockpit of your F4U!  

Just kidding, I am clueless as well.  Good Luck!  



------------------
Mino
The Wrecking Crew
Trainer

[Edbert MOL]

Direct from Microsofts tech-support Knowledge base (Technet)...pasted between the horizontal lines.
_____________________________ _____________

SUMMARY
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 non-recoverable 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 32-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.

_____________________________ _________

Basically you'll want to do some clean booting to try and identify which VXD (device driver)is causing the problems. Run MSCONFIG from the run command, just be carefull in there and keep track of all changes you make  

[SC-GreyBeard]

the device driver that is failing, IS
ifsmgr.vxd

All I could find on that particular file is that it is a Windows operating system file..
(Virtual device driver)

(well DUH!!!!)

and it's part of the 32 bit processing, or at least it resides in c:\windows\system\vmm32
which seems to me to be part of the "virtual memory module, 32 bit" part of the windows operating system.

Which Windoze are you using????
(God help ya if you have win95 still....)

1st, see if you can find the file on your HD.
using the find, files\folders

you could try looking it up using the regedit,, but be careful....
Any changes there means yer screwed....

If you find the file check the
version info, and let me know what the numbers are..

we'll match em up for comparison...
(it could be corrupted)

Good luck!!



------------------
GreyBeard
Flight Commander, Aces High
"Skeleton Crew"
"Fly with Honor"[/i]

[DoctorYO]

Note this was taken from BB http://computing.net/windows95/wwwboard/forum/1336.html

also note next time you have problem virus whatever.. a easy method to recieve instant information is to use the most powerful tool on the net... "THE MIGHTY SEARCH ENGINE"

type your problem and like magic you get answers; not all accurate but with some common sense you can make do.

I would suggest trying to get your hands on this file and manually copying it over your current one for starters..then possible try to reinstall windows and the then test your ram... in that order..  And by all means start reading up.  With all the witchdoctor advise you were given this thread I would suggest not doing some of the things some people suggested.  Read for your self and make educated decision, and not voodoo tech support.

Note I have tried none of these links for validity and this is just a example so use as such.

Regards,


DoctorYO

Name: Jakub Coltun
Date: August 27, 1999 at 11:26:49
Subject: Fatel Exception, VXD IFSMGR, VXD VNBT
 
Reply:
IFSMGR.vxd is located @
C:\windows\system\vmm32 and is 182kb for the version I have 4.00.1111
BELOW ARE THE BEST TIPS I FOUND:

SORRY FOR MESSED UP FORMATTING>>>

IFSMGR go to: http://marketwizz.net/windows95/win95a/index.html

There is a fix for these related errors, It seems that the
BSOD (Blue Screen of Death) Calling to IFSMGR.vxd
on an 0E error is caused primarily by computers running
Windows 9x and a network with tcp/ip running. The
BSOD after cancelled (Press any key) will let you run
normally but you wont be able to access the internet or
any tcp/ip resources. The file you want to run is located
at:

For the Windows 98 version: http://www.mcs.net/~revolutn/win98_vxd_fix.htm

For the Windows 95 version: http://www.mcs.net/~revolutn/vxdfaq.htm

You need to copy the Windows 95/98 cab files to your
'C:\Windows\Options\Cabs' directory, it's only a dos bat
file!


Fatal exception IFSMGR
Reply:

Microsoft's Knowledge Base Article ID: Q137335, In
titled: "Error Message: Invalid VxD Dynamic Link Call
from..." explains why these "blue screens" appear.

The url is:
 http://www.microsoft.com/support/kb/articles/q137/3/35.asp

Also, IFSMGR is the Installable File System Manager,
for VFBACKUP Helper Driver for Backup Applications.
(See article)

Fatel Exception, VXD IFSMGR, VXD VNBT
I had the exact same problem before. I would get the
message only when on the internet and it would lock the
system up. It ended up to be a bad RAM chip. Once
replaced I never had the problem again.

ifsmgr.vxd version 4.00.1112 which is the latest
file. I think.

you should be able to find this file from the net.

what you want to do is go into your
windows/system/vmm32 directory then rename your
current file to ifsmgr.old

they copy the latest file into the directory.
then reboot.

 


[This message has been edited by DoctorYO (edited 03-09-2000).]

[Swager]

I second Hblair's fix.  This would keep torque out of the arena for awhile!  

Sorry Torque, but this is a desperate self preservation measure!    


Actually I'm sorry I can't help ya, but good luck!!

------------------
Swager
"Damn.....I can't believe I missed that shot!!!"
 
JG2 "Richthofen"

[This message has been edited by Swager (edited 03-09-2000).]

[Torque]

thx all did the what Hb said.