General discussion

Locked

my new comp locks up all of a sudden?

By alfretto ·
The problem pc has win98 se, and was on a dsl modem till last nite - i deleted the ppoe adapter in network properties, and had no problem getting it to go online or operate while connected to router/cable modem until today.

i had just ripped/re-encoded one of MY dvds to the D drive - plenty of room - and was about to do the final prep when this Asus m/b/AMD cpu based pc blue-screened me - it did it last night once or twice, but now the blue-screens are near constant - the message is

"An exception OE has occurred at 0028:0241E0C0 in VxD --. this was called from 0028:C1C2A428 in VxD scsi1hlp(03) + 00000508."

then after a hard reboot, it froze again and the resultant blue screen message stated that the "exception OE occurred at 0028:1C10C1 in VxD ... called from ... " same as above

win98se
amd1700
asus av733 m/b
512k ram
40g WD caviar/120g WD caviar
built in soundcard
prolink 440 mx vid card
linksys net card

it all worked fine, i had just re-set the router and hooked up the cables and made sure that this Asus was recognized correctly by the router.

Its frozen now, wont respond . . . I did remove the Enternet 300 app that DSL uses, and did a registry clean, and i added Norton Utilities 2002 last nite to defrag the C Drive.

I'm not sure where to look, hope that the fatal OE message can give you a clue, thanks in advance, will be looking in.

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by TheChas In reply to my new comp locks up all ...

Start by reducing the amount of RAM.

The symptoms sound very similar to the problems with large amounts of RAM with W98.
This bug is VERY configuration dependant.
It is very possible that removing the ppoe adapter triggered the bug on your system.

One of the errors when the bug is triggered, is that Windows runs out of RAM when installing device drivers.

I limit ALL of my W98 boxes to no more than 384MB of RAM just to avoid the bug.

The only problem is that often when you get vxd errors, the vxds that were loading become corrupted and you need to wipe them out and reload Windows.

Chas

Collapse -

by alfretto In reply to

i have 5 pcs, 4 with cable isp, all are amd and have 512k, but uptil now i havent changed one over from ppoe to straight adapter. I havent seen this kind of BSOD before - its not a pci card thing, i dont believe. So how do i wipe out the vxds ?

Collapse -

by TheChas In reply to my new comp locks up all ...

As I said, the large RAM error is VERY configuration dependant.

Most of the vxd files are in the C:\Windows\System32
folder.

If you can boot into safe mode, you can run Windows explorer, and delete them from their.

Otherwise, boot from a startup floppy.

Use the old DOS commands to browse the hard drive.
(hit return at the end of all the following commands, spaces are important)

C:
CD \Windows\system32
Dir *.vxd

The last command will list all .vxd files on the screen.
Use
del {file name}.vxd
to delete individual files.

DOS will truncate long file names, and use the ~ and a number for each similar long file name.

Chas

Collapse -

by alfretto In reply to

Chas, pershate the help, but the vxd files are in the System folder, not the System32 folder. Shouldn't i be a bit discriminating in deleting these files ?

Collapse -

by TheChas In reply to my new comp locks up all ...

In answer to your concern, yes you need use some discrimination.

Start with the vxd files that are causing errors.

Keep in mind, that you will need to re-install some device drivers and applications after deleting the problem vxd files.

I'm on a XP box at the moment, and things are a little different there.

From memory, I think there is a sub-folder of the System32 folder that has the .vxd files I am concerned about.

A few of these files are re-created each time Windows loads or upon a configuration change.

By the way, VXD stands for Virtual Device Driver.
They are used by both hardware drivers and software.

Chas

Collapse -

by alfretto In reply to

i took off du meter, which was the first app to quit responding. I also removed EZCD as i had already installed prassi primo, didnt see that. those two usually do not get along, or is it Nero that Prassi doesnt like ?

but in the end chas, you were probably right about the vxds, but not in windows - when i removed Enternet 300 in going to cable isp from dsl isp, i forgot about the folder Efficient Networks, which is all about dsl - yes, inside were 2 vxds. Problem fixed, u gets the points !! well deserved, too.

Collapse -

by alfretto In reply to my new comp locks up all ...

the problem is, the pc does not have any VXD files in system folder, even with Show all files checked.

I just tried to copy over a Prassi Primo app, and it bsod-ed me again. It was fine for the last hour or so, sitting, with WE and IE open. I also have Nero and EZCD on it, but Prassi app was just the exe being copied over from teh cdrom drive.

Collapse -

by alfretto In reply to

I dont know how to identify which vxd files are troublesome.

Collapse -

by alfretto In reply to my new comp locks up all ...

This question was closed by the author

Back to Windows Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums