keith
Mon Mar 10 09:05:47 PDT 2008
Where did Philo's reply go? No longer in this string.
Data Advisor 5.00
Memory test - passed
Smart Status test - passed
90 second test - passed
File structure test - "unknown" - Not sure what that means. File structure
unknown? Test result unknown?
MAXTOR Power Max 4.23 manufacturer's test (for Quantum drive) - all passed.
Start>run>MSInfo32>Software environment>Startup Programs
SystemTray Registry (Machine Run) SysTray.Exe
ScanRegistry Registry (Machine Run)
C:\WINDOWS\scanregw.exe /autorun
LoadPowerProfile Registry (Machine Run) Rundll32.exe
powrprof.dll,LoadCurrentPwrScheme
PCPitStopEraser Registry (Machine Run) C:\Program
Files\PCPitstop\Erase\PCPitStopErase.exe /remindme
AVG7_CC Registry (Machine Run)
C:\PROGRA~1\GRISOFT\AVG7\AVGCC.EXE /STARTUP
AVG7_EMC Registry (Machine Run)
C:\PROGRA~1\GRISOFT\AVG7\AVGEMC.EXE
AVG7_AMSVR Registry (Machine Run)
C:\PROGRA~1\GRISOFT\AVG7\AVGAMSVR.EXE
LoadPowerProfile Registry (Machine Service) Rundll32.exe
powrprof.dll,LoadCurrentPwrScheme
KB891711 Registry (Machine Service)
C:\WINDOWS\SYSTEM\KB891711\KB891711.EXE
KB918547 Registry (Machine Service)
C:\WINDOWS\SYSTEM\KB918547\KB918547.EXE
Ran some test from PCPitStop long ago and still have their site in IE
favorites list.
Maybe the problem has been staring me in the face at every startup for
months on end.
Sometime last year a neighbor gave me and plugged in a couple extra 128
memory chips to go with the one original 128.
At every startup I get the following message ;
'Memory write/read failure at 100002020, read 00000000, expecting
00EF00EF. Decreasing available memory.'
A short pause and the continues with start up.
Always assumed it meant one of the extra chips was bad and ignored it all
this time and was just to lazy to pull it/them back out.
If there is only one in there the system says 128. With any two or all
three in there, the system says only 256. Ergo the bad chip assumption.
Still getting these newer ones though: (only one at a time but with
different devices)
'While initializing device VDD , windows protection error. Need to
restart computer.'
Usually VDD or VDK. Ocassionally VPICD. Once or twice with
V86MMGR or that 386enhanced thing.
Might take a couple of restarts to get to the Normal or Safe Mode option and
then a couple of Normal attempts there.
Needless to say, I don't turm it off very often.
But lots of re-starts lately with the diskette tests and checking the HD
manufacturer and those memory chips.
And I have gotten a couple of regular, straight thru startups, too.
No Win 98 discs on hand here if that is.where the problem lurks.
"PCR" <pcrrcp@netzero.net> wrote in message
news:eKLVBtngIHA.4140@TK2MSFTNGP04.phx.gbl...
> keith wrote:
> | Baught some NEW, UNUSED floppies.
> | Downloaded the Windows Memory Diagnostic (mtinst.exe) again and ran
> | the test(s).
> | Ran the standard suite for 3 passes and the extended suite for 2
> | passes. All 'Successful' and no errors found.
>
> Very good. The RAM is fine.
>
> | The 'WinDiag / mtinst.exe' confusion was all mine. Wasn't sure what
> | to call it so typed the test name AND the file name.
>
> I see. OK.
>
> | There's probably an easy way to copy/paste or print the BIOS settings
> | but I just wrote them all down
> | and put them in the attached Word document.
> |
> | The large extra HD (for file storage) is the Seagate. The small main
> | HD is a Quantum.
> | Will try the Quantum/Maxtor links again and maybe the other RAM tests.
>
> Keep us informed. I think something could be wrong either with the hard
> drive itself or with the Windows file system. Another possibility is
> that there is too much in the Startup Group, going by your words--
> "dangerously low resources". Therefore...
>
> "START button, Run, MSInfo32, Software Environment, Startup Programs".
> Use the Edit menu to copy & post it.
>
> | Thanks again.
>
> You are welcome. That BIOS report isn't so huge. It looks fine to me,
> (although I don't know what Chassis Intrusion or DAC Snoop is). Auto is
> a good setting for the hard drives. I'll post it here, for others to
> easily see...
>
> Pentium II 400 Mhz System memory 15 MB SDRAM
> Level 2 Cache 512 KB Integrated Video Memory 8 MB SGRAM
>
> **********
>
> Diskette A 1.44 MB
> Diskette B Not Installed
>
> Drives Type CYLS HDS PRE SEC SIZE
> Primary
> Drive 0 Auto 913 255 -1 63 7509
> Drive 1 Auto EIDE Drive 65432
> Secondary
> Drive 0 Auto CD ROM Drive
> Drive 1 Auto CD ROM Drive
> **********
>
> Reserved Memory 15 - 16 M
> CPU Speed 400 Mhz
> Num Lock On
> Chassis Intrusion Disabled
> DAC Snoop On
> ACPI On
>
> **********
>
> Keyboard Errors Report
> System Password Not Enabled
> Password Status Unlocked
> Boot Sequence Diskette First
> Setup Password Not Enabled
> Auto Power On Disabled 00:00
> Power Management Regular
> Wake-up on LAN Off
>
> **********
>
>
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:uQX2aw%23fIHA.2448@TK2MSFTNGP03.phx.gbl...
>
> ...snip
> |> |> keith wrote:
> |> |> | Have seen a few errors at different times lately when booting /
> |> |> | rebooting after system lock-ups.
> |> |> |
> |> |> | 'While initializing device VPICD: Windows
> |> |> | protection error.' 'While initializing
> |> |> | (installing??) V86MMGR:
> |> |> | error cannot
> |> |> | install 386 enhanced MXSD'
> |> |> | Not sure if it said installing or
> |> |> | initializing. Not sure I got the MXSD part
> |> |> | correctly - MVXD?
> |> |> | or some variation.
> |> |> | And one about dangerously low resources.
> |> |> |
> |> |> | Tried a couple of SCANRE /RESTORE dates from prior to errors
> |> |> | but still got the VPICD error on this last boot.
> |> |> |
> |> |> | W98 with 2 drives - First is just Windows and other programs -
> |> |> | only 2 out of 6 gigs used
> |> |> | Second is just files, fotos,
> |> |> | vids - about 80 out of 95 gigs used.
> |> |> | Second has been as
> |> |> | high as 90 out of 95 without problems.
> |> |> | Its usually in the
> |> |> | 70-75 out of 90 range
> |> |> |
> |> |> | Have start up sequence set to display Normal, Safe Mode,
> |> |> | Command Promp Only , etc menu with 30 second wait period.
> |> |> | Ocasiionaly Normal doesn't load and it goes back to the
> |> |> | menu with Safe Mode hilighted but can usually choose Normal
> |> |> | again and complete the start-up.
> |> |>
> |> |> When an installation boots poorly only occasionally, the
> |> |> bootstrap is probably fine. That includes BIOS, MBR (Master Boot
> |> |> Record), PBR (Partition Boot Record), & all the files needed to
> |> |> boot, even the Registry.
> |> |>
> |> |> | Nothing out of the ordinary with SpyBot, Ad-Aware, SpyWare
> |> |> | Blaster or AVG scans.
> |> |> | Nothing new in Add/Remove Programs list or ALT/CTRL/DEL
> |> |> | list
> |> |> |
> |> |> | Thaught I'd post this first while this rig seems to be working
> |> |> | OK and will start searching for solutions / references.
> |> |>
> |> |> (1) Run the RAM test as philo posted.
> |> |> (2) Make a backup of your boot partition.
> |> |> (It may be on its way out!)
> |> |> (3) Run the hard drive diagnostic for your brand.
> |> |> This repairs the structure of the hard drive, if necessary.
> |> |> (4) Run a ScanDisk & Defrag.
> |> |> This repairs the Windows file system, but could also
> |> |> wreak havoc, if a big repair is necessary...
> |> |>
http://cquirke.mvps.org/9x/scandisk.htm
> |> |>
>
> ...snip
> --
> Thanks or Good Luck,
> There may be humor in this post, and,
> Naturally, you will not sue,
> Should things get worse after this,
> PCR
> pcrrcp@netzero.net
>
>