Be sure to let me know that you're seeing the 0x0000008E STOP code and also what steps, if any, you've already taken to resolve it.Also, please make sure you've looked at How To Fix STOP 0x0000008E Errors Restart your computer if you haven't already done so. We're a friendly computing community, bustling with knowledgeable members to help solve your tech questions. Microsoft Windows XP Service Pack 2 RC1 , Update CD Build 2096) under the Name column. weblink
Sometimes resolving your blue screen of death problems may be as simple as updating Windows with the latest Service Pack or other patch that Microsoft releases on an ongoing basis. Thread Status: Not open for further replies. CLICK HERE to verify Solvusoft's Microsoft Gold Certified Status with Microsoft >> CLOSE Win 2000 ALL How-tos Win 10 Win 8 Win 7 Win XP Win Vista Win 95/98 Win NT Follow the on-screen commands. http://www.bleepingcomputer.com/forums/t/206521/win-2000-system-no-longer-boots/
A backup of the registry is essential BEFORE making any changes to the registry.OK, now back to business...Did the CHKDSK /R in the Recovery Console fix any errors? PC2 Intel 8088 4.77MHz, 640kB RAM, MS DOS 5.0, 30MB hdd. Advertisements do not imply our endorsement of that product or service. Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows.
Please enter a valid email address. www.memtest.org For the Vista Memory Diagnostic Tool Start - type in Search box -> Memory - find Memory Diagnostics tool at top of list - Right Click - RUN AS ADMIN PC4 Intel Celeron 400MHz, 256MB RAM, OS/2 Warp 3.0 Connect + Windows fw3.11, 545MB hdd. I have the Knack. ** If I haven't replied in 48 hours, please send me a message.
Restore your computer. PC4 Intel Celeron 400MHz, 256MB RAM, OS/2 Warp 3.0 Connect + Windows fw3.11, 545MB hdd. Always check in Device Manager - Drivers tab to be sure the version you are installing actually shows up. If we have ever helped you in the past, please consider helping us.
In fact, nearly 10% of application crashes in Windows are due to memory corruption. http://www.geekstogo.com/forum/topic/286086-bsod-fltmgrsys/ http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm How to Install a Device Driver in Vista Device Manager http://www.vistax64.com/tutorials/193584-device-manager-install-driver.html If you update drivers manually then it is a good idea to disable Driver Installations in Windows Updates, this To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. The latest known version of Fltmgr.sys is 188.8.131.52, which was produced for Windows.
If you haven’t added any new memory, the next step is to perform a diagnostic test on your computer’s existing memory. have a peek at these guys PC7 Intel Celeron 1700MHz, 256MB RAM, Windows 2000, 40GB hdd. All Rights Reserved Tom's Hardware Guide ™ Ad choices How To Fix STOP 0x0000008E Errors Search the site GO Windows Error Messages Basics Maintenance Symptoms How To Windows Question : How to deal with such blue screen? > It is the second time, that happend. > > Thanks a lot for the response. > > Pierre Bernard > >
Do you have additional information? More specifically, these fltmgr.sys errors can be caused by: Incorrectly configured, old, or corrupted Microsoft Windows XP Service Pack 2 RC1 , Update CD Build 2096 device drivers. (very common) Corruption I then tried the Recovery Console feature, but when I entered my Administrator password, it said my password was invalid! check over here Solvusoft's close relationship with Microsoft as a Gold Certified Partner enables us to provide best-in-class software solutions that are optimized for performance on Windows operating systems.
Drivers are possible however that would be unusual - maybe chipset drivers. DriverDoc updates all of your PC device drivers, not just those associated with your SYS blue screen error. Extract the file folder anywhere you can get to easily (eg.
Locate fltmgr.sys-associated program (eg. I have the Knack. ** If I haven't replied in 48 hours, please send me a message. After doing the in place upgrade though I get a different BSOD at startup with the error message being: FLTMGR.sys - address F738B2B2 at F7373000, Datestamp 408025lda I hope this is This problem has dragged on for three days now and I have to take drastic action.
It brought me back to exactly the same bsod as in the photo, and there are no new .dmp files on the system. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards,Arthur Li TechNet Community SupportMarked as answer by Arthur_LiMicrosoft Removing the pointer may clear up the problem. this content Note: if you already have items unchecked under msconfig > startups and are in "selective" startup mode - you should note what these are before beginning.
Unfortunately, when I try to boot to safe mode all I see is a dialouge box saying: "Windows XP Setup cannot run under safe mode. As a result, you may experience blue screen errors associated with fltmgr.sys. Edited by Tommy in Scotland, 26 February 2009 - 09:26 AM. SYS files such as fltmgr.sys are third-party (eg.