Windows 95/98/Me/NTPost your Windows 95 / 98 / ME and NT questions here. Please make sure you specify your OS version.
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
I have a Windows ME backup machine. This morning when I tried to turn it on, Windows failed to load and the following error code was listed.
Error:OE7:167:82FA93CF
and a second error code
Error:OD:0987:000014E9
On reboot, the screen then lists 3 restart options, but each option fails with the same error codes. Thats as far as it gets.
Any suggestions as to what I might try, or what type of failure this may indicate? My first guess is the harddrive has dropped dead.
Bumps
Didn't find the information you thought to find? Check out these Similar Threads
This backup computer is an emachine I had given to my son a few years ago. He since has a new computer and I have the emachine as a backup. Unfortunately, the restore disk was lost long ago. I do have a Windows ME CD, and I have a copy of all the machine specific drivers, so I may be able to do that somewhere along the way.
However, after trying various things I have learned over the years, I have some additional good information. By using a Windows 98 boot floppy, I can access the harddrive. Scandisk reports no errors although initially it corrected a false free space reading on the drive.
I used an old dos shell program that lets me examine the harddrive and I have discovered a few things.
First, a full scandisk w/surface scan is good, and I can access all files on the drive. While checking the drive, I opened the bootlog. This has something very interesting which I feel sure someone more advanced than I will understand.
As I went thru the bootlog, everything was successfull, until near the very end. There was something I had never seen before. All the entries entries were of success before this point, then disaster. Here is the end of the bootlog text:
********** All entries prior to this point look good.
LoadSuccess = gdi.exe
LoadStart = user.exe
LoadStart = DDEML.DLL
LoadSuccess = DDEML.DLL
LoadStart = C:\WINDOWS\SYSTEM\USER32.DLL
[001107B0] Removing Unknown (HTREE\RESERVED\0)
[001107B1] Removed Unknown (HTREE\RESERVED\0)
[001107B1] Removing TCP/IP (NETWORK\MSTCP\0001)
[001107B1] Removed TCP/IP (NETWORK\MSTCP\0001)
[001107B1] Removing Dial-Up Adapter (ROOT\NET\0000)
[001107B1] Removed Dial-Up Adapter (ROOT\NET\0000)
[001107B1] Removing Processor support (ROOT\PROCESSOR_UPDATE\0000)
[001107B1] Removed Processor support (ROOT\PROCESSOR_UPDATE\0000)
[001107B1] Removing Microsoft Kernel System Audio Renderer (SW\{A7C7A5B0-5AF3-11D1-9CED-00A024BF0407}\{9B365890-165F-11D0-A195-0020AFD156E4})
[001107B1] Removed Microsoft Kernel System Audio Renderer (SW\{A7C7A5B0-5AF3-11D1-9CED-00A024BF0407}\{9B365890-165F-11D0-A195-0020AFD156E4})
[001107B1] Removing Microsoft Kernel DRM Descrambler Filter (SW\{EEC12DB6-AD9C-4168-8658-B03DAEF417FE}\{ABD61E00-9350-47E2-A632-4438B90C6641})
[001107B1] Removed Microsoft Kernel DRM Descrambler Filter (SW\{EEC12DB6-AD9C-4168-8658-B03DAEF417FE}\{ABD61E00-9350-47E2-A632-4438B90C6641})
[001107B1] Removing Microsoft Kernel GS Wavetable Synthesizer (SW\{6C1B9F60-C0A9-11D0-96D8-00AA0051E51D}\{9B365890-165F-11D0-A195-0020AFD156E4})
[001107B1] Removed Microsoft Kernel GS Wavetable Synthesizer (SW\{6C1B9F60-C0A9-11D0-96D8-00AA0051E51D}\{9B365890-165F-11D0-A195-0020AFD156E4})
[001107B1] Removing Microsoft Kernel Audio Mixer (SW\{B7EAFDC0-A680-11D0-96D8-00AA0051E51D}\{9B365890-165F-11D0-A195-0020AFD156E4})
[001107B1] Removed Microsoft Kernel Audio Mixer (SW\{B7EAFDC0-A680-11D0-96D8-00AA0051E51D}\{9B365890-165F-11D0-A195-0020AFD156E4})
[001107B1] Removing Microsoft Kernel Audio Splitter (SW\{2F412AB5-ED3A-4590-AB24-B0CE2AA77D3C}\{9B365890-165F-11D0-A195-0020AFD156E4})
[001107B1] Removed Microsoft Kernel Audio Splitter (SW\{2F412AB5-ED3A-4590-AB24-B0CE2AA77D3C}\{9B365890-165F-11D0-A195-0020AFD156E4})
[001107B1] Removing Microsoft Kernel DLS Synthesizer (SW\{8C07DD50-7A8D-11D2-8F8C-00C04FBF8FEF}\DMUSIC)
[001107B1] Removed Microsoft Kernel DLS Synthesizer (SW\{8C07DD50-7A8D-11D2-8F8C-00C04FBF8FEF}\DMUSIC)
[001107B1] Removing Plug and Play Software Device Enumerator (ROOT\SWENUM\0000)
[001107B1] Removed Plug and Play Software Device Enumerator (ROOT\SWENUM\0000)
[001107B1] Removing Composite Power Source (ACPI\COMPBATT\ROOT&*PNP0C08&0000)
[001107B1] Removed Composite Power Source (ACPI\COMPBATT\ROOT&*PNP0C08&0000)
[001107B2] Removing ACPI System Button (ACPI\BUTTON\ROOT&*PNP0C08&0000)
[001107B2] Removed ACPI System Button (ACPI\BUTTON\ROOT&*PNP0C08&0000)
[001107B2] Removing Intel 82810 System and Graphics Controller (PCI\VEN_8086&DEV_7120&SUBSYS_3154109F&REV_03\BUS_00&DEV_00&FUNC_00)
[001107B2] Removed Intel 82810 System and Graphics Controller (PCI\VEN_8086&DEV_7120&SUBSYS_3154109F&REV_03\BUS_00&DEV_00&FUNC_00)
[001107B2] Removing Plug and Play Monitor (MONITOR\CYB5931\PCI_VEN_8086&DEV_7121&SUBSYS_71218086&REV_03_BUS_00&DEV_01 &FUNC_00)
[001107B2] Removed Plug and Play Monitor (MONITOR\CYB5931\PCI_VEN_8086&DEV_7121&SUBSYS_71218086&REV_03_BUS_00&DEV_01 &FUNC_00)
[001107B2] Removing Crystal SoundFusion(tm) CS4281 Joystick (CS4281\*PNPB02F\0PCI&VEN_1013&DEV_6005&SUBSYS_00000000&REV_01&48F000)
[001107B2] Removed Crystal SoundFusion(tm) CS4281 Joystick (CS4281\*PNPB02F\0PCI&VEN_1013&DEV_6005&SUBSYS_00000000&REV_01&48F000)
[001107B3] Removing Crystal SoundFusion(tm) CS4281 WDM Audio (PCI\VEN_1013&DEV_6005&SUBSYS_00000000&REV_01\48F000)
[001107B3] Removed Crystal SoundFusion(tm) CS4281 WDM Audio (PCI\VEN_1013&DEV_6005&SUBSYS_00000000&REV_01\48F000)
[001107B3] Removing Conexant SoftK56 PCI Modem(M) (CXT\VEN_14F1&DEV_2013&SUBSYS_8850155D\WDMMDM0)
[001107B3] Removed Conexant SoftK56 PCI Modem(M) (CXT\VEN_14F1&DEV_2013&SUBSYS_8850155D\WDMMDM0)
[001107B3] Removing Conexant PCI Modem Enumerator (PCI\VEN_14F1&DEV_2013&SUBSYS_8850155D&REV_01\70F000)
[001107B3] Removed Conexant PCI Modem Enumerator (PCI\VEN_14F1&DEV_2013&SUBSYS_8850155D&REV_01\70F000)
[001107B3] Removing USB Root Hub (USB\ROOT_HUB\PCI&VEN_8086&DEV_2412&SUBSYS_24128086&REV_02&BUS_00&DEV_1F&FU NC_02)
[001107B3] Removed USB Root Hub (USB\ROOT_HUB\PCI&VEN_8086&DEV_2412&SUBSYS_24128086&REV_02&BUS_00&DEV_1F&FU NC_02)
[001107B3] Removing ACPI Generic Bus (ACPI\*PNP0A05\0)
[001107B3] Removed ACPI Generic Bus (ACPI\*PNP0A05\0)
[001107B3] Removing Communications Port (COM1) (ACPI\*PNP0501\00000001)
[001107B3] Removed Communications Port (COM1) (ACPI\*PNP0501\00000001)
[001107B3] Removing Printer Port (LPT1) (ACPI\*PNP0400\00000001)
[001107B3] Removed Printer Port (LPT1) (ACPI\*PNP0400\00000001)
[001107B4] Removing ACPI Power Button (ACPI\*PNP0C0C\0)
[001107B4] Removed ACPI Power Button (ACPI\*PNP0C0C\0)
[001107B4] Removing System board (ROOT\*PNP0C01\0000)
[001107B4] Removed System board (ROOT\*PNP0C01\0000)
As you can see, everything that was insatlled gets uninstalled. Then the BSOD with the error I listed.
Does this info help?. BTW, I repeated the bootup several times, and the date/time stamp on the bootlog indicates the log is showing what is happening.
Nope. Doesn't help me one bit. Can you get to a command prompt, as I posted earlier, to choose a restore point to a time before this started happening?
The system goes thru the boot process, as reflected in the bootlog, but then ends with the BSOD and error message. Any keyboard activity leads to a blank grey screen, and continued keyboard activity results in a beep with each successive key pressed.
Sorry about that Bumps. I see by your profile, you've listed yourself as experienced, so I'll leave it that you knew how to attempt a command prompt. All I've left for advice, would be the "over-install".
Daizy
*edit*
You've double checked your error messages? These are precisely the two you are getting?
Last edited by Daizy; 10th February 2003 at 23:29.
Yes, these are the only 2 errors listed. I'm going to take all the drivers of the harddrive before I try installing Windows ME over the proprietary emachine Windows ME, assuming the CD drive will work..
In fact, I think I will rename the current Windows directory, and just do a full install of Windows ME, assuming the CD works, and then try some old tricks I've used in the past for a similar problem.
Do the below in this order before trying to install!
1. Cleanups
These are for 95 98 ME only!
Boot to DOS from your w98 startup disk!
Type these commands
del c:\*.swp (may get file not found, is ok)
del c:\windows\*.swp
deltree c:\windows\shelli*.*
deltree c:\windows\temp\*.* (answer yes to all) "ALL"
deltree c:\windows\tempor~1\*.*
deltree c:\windows\history\*.*
deltree c:\windows\spool\printers\*.*
2. scanreg /restore
This will give you dated registy backups to chose from
Pick a date a day or 2 ago before this problem and restore.
3. Reboot but try your best to not let full windows boot. Tap the F8 key repeatedly to get the bootup menu and chose "SAFE MODE".
If you can get here (you have a chance) leave it and post back. I will wait!
I tried your suggestions this morning, but they had no effect.
The system is an emachine and the OS is ME, used primarily as an alternate backup to go online, browse and retrieve email. I use it sort of like a laptop when away from home, its cheap, small and no great loss if anything happened to it on the road.
The bootlog suggests (to me) that there is a problem, maybe a corrupt file with USER32.DLL. On 1 of the bootlogs, USER32.DLL was reported as FAILED.
Anyway, thanks for the suggestion, and if you have anymore I am open to try them. Right now I am in the process of retrieving the drivers from the system before I do something that may clobber them. When I have that process done, I will begin with the install/reinstall of ME, and maybe of 98.
I tried Normal Boot, Record a Bootlog, Safe Mode, and Step modes.
Each and everyone ended up with the BSOD and the error codes noted before.
I renamed Windows, and installed Windows ME to a new C:\Windows. The system then booted up properly.
Going back to the old Windows, same process ended up with BSOD.
Right now I am Installing Windows over the copy that will not boot properly. Daizy was probably right in saying I should do an over install initially, but I was more interested in trying to find out the specifics of the failure and if there were an alternate method to recover. At this point, it looks like the over-install may be the only solution at this level.
I guess its time to close this thread. Installing WindowsME over itself (the version that would always end with the BSOD) has everything back to normal.
