|
-
October 30th, 2003, 02:39 PM
#1
packard bell and vpowerd.vxd errors
Its me margaret.
I have here a PAckard Bell PC with Win98FE installed. Mobo has the Intel 82371EB chipset on board.
I am getting the following blue screen when windows tries to boot:
fatal exception 0E at 0028:C1C01010 in VXD VpowerD(08)
It then goes ahead and pulls up the windows background, and locks up.
So, I went in to control panel in safe mode and turned on compat. mode for the drives. Windows boots normally, but I cannot use the CD-ROM.
I downloaded the drivers from Intel for the chipset and installed, but still get the error when I turn compat off.
Any suggs?
Thanks,
Al
"It is very dark here. You are likely to be eaten by a grue."
-
October 30th, 2003, 03:18 PM
#2
Driver Terrier
This is an APM (ADvanced Power Management) problem. Does the bios allow you to set APM on or off?
Is the bios set for PNP OS aware?
Which exact PB?
-
October 30th, 2003, 03:38 PM
#3
Bios power management is disabled, plug and play os is on.
This system is a model 7905 (I know from experience that the model number basically means nothing). Is a Pentium 2 -350 slot 1 mobo. Is a tower model where the bottom and side panel are one piece (really goofy)
Thanks,
Al
-
October 30th, 2003, 03:50 PM
#4
Driver Terrier
Have you tried it with the powermanagement enabled in bios?
-
October 30th, 2003, 04:01 PM
#5
Driver Terrier
From you description I believe that your PB has the 870 motherboard shown here - if thats the case a bios upgrade available here should sort the problem
-
October 30th, 2003, 05:52 PM
#6
NooNoo,
Thanks for the links. That is the correct mobo. I went ahead and updated the BIOS. It still does the same thing. I am stumped, man.
Al
-
October 31st, 2003, 06:23 AM
#7
Driver Terrier
Pull the enum key in safemode, reload all drivers.
-
October 31st, 2003, 01:44 PM
#8
ok, i tried that as you said. When it asked me to reboot I did (should I have?) Anyway, the same error message about the vpowerd vxd is appearing (again).
Al
-
October 31st, 2003, 02:07 PM
#9
Driver Terrier
go into safe mode
start, run, type in sysedit, click ok
Look in win.ini and system.ini for vpowerd.vxd
put a ;
thats a semicolon
in front of the line that has it in there, save the file(s) and reboot
does that cure it?
-
October 31st, 2003, 04:02 PM
#10
actually I didn't see vpowerd.vxd in any of those files. It is in the registry, though.
Al
-
October 31st, 2003, 04:12 PM
#11
Driver Terrier
ok export the key that mentions it - file, export and save it somewhere you can find it again easily, then delete the key and reboot - if worst comes to worst you can remerge the exported key in safemode again.
-
October 31st, 2003, 04:16 PM
#12
Driver Terrier
Just seen and obscure reference... is the file VPOWERD.VXD in c:\windows\system or c:\windows\system32 ?
-
October 31st, 2003, 05:31 PM
#13
Hi,
It actually is located in two places:
Windows\system
Windows\iosubsys
I will also try the reg hack.
Thanks NooNoo,
Al
-
October 31st, 2003, 06:08 PM
#14
Well,
I think I may have just fixed it. I actually deleted both copies of vpowerd.vxd and rebooted. Everything came up normally, no error messages. Even 32 bit disk access is activated. May not have been the normal way to fix, but it worked this time.
Thanks for all your help, NooNoo and others.
Al
-
November 1st, 2003, 05:24 AM
#15
Driver Terrier
Pleasure - yes unauthodox... you may find shutdown problems or irq sharing problems - but we will cross that bridge later.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|
Bookmarks