View Single Post
  #3  
Old July 7th 05, 04:53 AM
TheRealFastlane
external usenet poster
 
Posts: n/a
Default

Thanks Ron, I guess I can go back to the onboard intel now that I've
upgraded to 512 ram, was minimimizing shared system ram.
Grahics is a 3DFX Voodoo3/2000, no longer supported but I do have the
latest drivers which are 3rd party (but very reliable).
After installing the removing an Nvidia graphics card because of
problems, on start/restart the system would detect new hardware and
insist on installing it, a second pci compatible vga display.
I never did figure that out.

On Wed, 06 Jul 2005 16:54:56 GMT, Ron Martell
wrote:

TheRealFastlane wrote:

HP Pavilion 6735 OEM Win ME.

Getting BSOD's off and on for the last week+
and no clue why. No info in faultlog.

1 instance of
VFAT(01) + 00006AD5 Error 0E: 0028:C0045195

Several random instances of
VMCPD(01) + 0000061C Error 0D: 0028:C0056F28

I havent changed/modified anything related but Im
guessing its something graphics since it occurs
inconsistently when I attempt to start Diablo2-LOD,
Bejeweled2 Deluxe or Solitaire maniac (so far).
At this BSOD the numlock/capslock will toggle but it
will not 3 finger. Pressing any single key returns to
the desktop which now appears to be 640x480 with
wallpaper but no icons, the taskbar and tasklist keypress
are inop, Alt-F4 brings up the shutdown/restart window but
it wont, Alt-Enter brings up the taskbar settings window.

Last but not least, I tried the MS KB and can find nothing on
the following exception 57H error:
RPCSS caused an exception 57H in module RPCRT4.DLL at 01a7:7fad3544

Thanks

-- Keyboard not detected
Press F1 to continue



Fatal Exception 0E errors in the 0028 address segment (your first one)
are often associated with video driver problems so one thing you might
try is to download the latest Windows Me drivers for your video card
from the manufacturer's web site and install them.

Have you tried using System Restore to set the system back to the most
recent restore point that is prior to the onset of this problem?
Going back a week can be a bit risky because of the many changes that
can occur during that time but it might just solve the issue. Make
sure you create a new restore point before you do this.

Good luck


Ron Martell Duncan B.C. Canada



-- Keyboard not detected
Press F1 to continue