Any possible solutions? Ok - seen ms driver updates cause problems before. I can understand the logic behind your suggestion, however, considering i cannot boot from CDs to access the recovery console BartPE is supposed to be able to run off a USB thumb drive if you have one of those and can boot from it? Under its boot menu, i put 'removable drives' on top, the installation of BartPE went without errors I can understand this can be a longwinded process So it seems my faulty laptop refuses to boot from anything To make sure you have configured your Bios to actually boot from USB if it can, as some just can't have a look at this site and perhaps the HP one too.
Linney, My phoenix bios likes to display usb drives as a hard disk, so i did expand that under the boot menu and prioritise that. Replace the disk, and then press any key' Presumably im getting this error as the laptop is trying to boot from the usb? I suggest you reset the Bios back to Safe defaults save that setup and exit, and then again further set up the Bios so that it boots from CD-Drive first and hard drive last, exit and save that setting.
You are going to get your CD Drive sorted before you can make any further progress. When we get a CD drive that works there are several more steps we can try to get the hard drive booting in the laptop. Does your laptop still have no floppy access, if it did we can make suggestions that avoid the use of the CD drive? Perhaps it is time to throw in the towel and have a repairer look at the malfunctioning laptop. Your hard drive sounds like it is OK, however the things that connect it to the rest of the machine may have broken, disconnected, or otherwise failed.
Too many computers I guess. Red Flag This Post Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework. The Tek-Tips staff will check this out and take appropriate action. Click Here to join Tek-Tips and talk with other members!
Already a Member? Unload the hive. When you're prompted, enter the name OfflineSystemHive for the new hive. Check the data for the Default value. Check whether the PendingFileRenameOperations key exists. Follow steps in the "Troubleshooting if this issue occurs after a Windows Update installation" section.
Step 11 doesn't apply to this procedure. If these keys exist, check each one to make sure that it has a value that's named Start , and that it's set to 0.
If it's not, set the value to 0. If any of these keys don't exist, you can try to replace the current registry hive by using the hive from RegBack. To do this, run the following commands:.
Check whether there are any non-Microsoft upper and lower filter drivers on the computer and that they don't exist on another, similar working computer. If they do exist, remove the upper and lower filter drivers:. These filters are mainly related to storage. You might find these filter drivers in some of the following registry entries. These entries are under ControlSet and are designated as Default :. We ran malware bytes on them both, and for some strange reason they are both stuck in a boot loop with the 7B STOP error after Malware Bytes asked to reboot to finish deleting the spyware.
The spyware was minor, only 4 found on the Dell, and 7 on the Sony. Here's the systems and their errors. The error occurs during both normal boot up, and safe mode. The windows logo appears for just a split second then the error occurs. I've tried doing the registry replacement, this had no effect either.
We'd hate to have to go into fully backing up and resetting up these systems, especially since the clients only brought them in for cleanup.
Any solutions guys and gals? We will treat this report as confidential and anonymous. To see what data this error report contains, click here.
In this scenario, you receive the following Stop error message:A problem has been detected and Windows has been shut down to prevent damage to your computer Easy CD Creator 5. You may receive a "Stop" error message that is similar to one of the following error messages:A problem has been detected and Windows has been shut down to prevent damage to your computer If the error message still appears and if you want to see the data that the error report contains, click the "click here" link at the bottom of the message box.
If the error message remains on the screen, click the "click here" link at the bottom of the message box if you want to see the data that the error report contains. A Stop 0x error may occur in Scsiport. Note: The parameters may vary, but the specific stops "0x1E" and "0x50" do not. Once you hit any key, the system then starts to load Windows, after which you receive the following: A problem has been detected and windows has been shutdown to prevent damage to your computer.
The referenced article may contain extraneous text. If this screen appears again, follow these steps:Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need. If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.
However, this error does not mean that the hive is damaged or that it was not loaded successfully. The Stop 0x77 message indicates that a page of kernel data requested from the paging virtual memory file could not be found or read into memory. This Stop message can also indicate disk hardware failure, disk data corruption, or possible virus infection. Common Causes of STOP Messages 0x and 0xA - STOP Messages 0x and 0xA are related kernel traps that are caused when the operating system tries to load a page into memory from the paging file on the hard disk, but cannot access the page because of either a software or hardware failure.
The Stop 0x79 message indicates that the hardware abstraction layer HAL and the kernel type for the computer do not match. This error most often occurs when ACPI firmware settings are changed.
For example, you might install Windows XP Professional on an xbased computer with the firmware ACPI enable option enabled and later decide to disable it. This error can also result when you try to run an existing installation on new hardware. How to move a Windows installation to different hardware - The source and destination computers must use the same type of HAL. There is one exception to this rule. The Stop 0x7A message indicates that a page of kernel data was not found in the paging virtual memory file and could not be read into memory.
This might be due to incompatible or defective disk drivers, firmware, or hardware, bad sector in a paging file, a virus, or failing RAM. Windows XP lost access to the system volume or boot volume during the startup process. This error always occurs while the system is starting and is often caused by one of the following: Hardware problems e. ARC paths are used to define the path to the Windows installation on Intel xprocessor-based machines. See: BOOT. Contact your product support representative for assistance.
The following status will assist them in diagnosing the problem. Power down or reboot your computer now. The symptoms that you have to install an OEM device driver include the following: The computer may keep restarting and never start the GUI installation after the text mode Setup is finished.
The Setup program may stop, and you may receive an error message if the Setup program does not correctly detect the controller. If you are booting from the installation floppy disks or CD-ROM disc, you receive the following error message: Setup did not find any hard disk drives installed in your system.
If you are upgrading by using the Winnt To quit setup press F3Windows could not start because of the following ARC firmware boot configuration problem. Please check the windows documentation about ARC configuration options and your hardware reference manuals for additional informationStop: 0xb 0xfc, 0xc, 0x, 0x Windows XP Setup may stop responding hang and display a blank black screen after the first reboot; After you install Windows XP, secondary hard drives that worked and appeared correctly in the following operating systems may appear to be damaged or have a size of zero bytes: Microsoft Windows Millennium Edition Me ; Microsoft Windows 98 Second Edition; Microsoft Windows 98; Microsoft Windows Related Articles: How to move a Windows installation to different hardware - The source and destination computers must use the same type of HAL.
The information in this article may be useful to help you avoid some common upgrade-related issues. A microcode reliability update is available that improves the reliability of systems that use Intel processors - A "stop 0x7E" error that may occur during startup on some systems that are running an older Pentium 5 CPU. This error may occur after you close a program that has an open handle to a file on a universal serial bus USB 2.
You change the file but do not save it. You disconnect the USB 2. You disconnect the portable computer from the docking station. You close the program. You are not prompted to save the file, and a 0x7E Stop error occurs. You receive a stop error 0x7E in Pci.
Note The four parameters in this error message may vary depending on the cause of the stop error. You receive a "Stop 0xE" error message after you upgrade to Windows XP Service Pack 2 on a non-Intel-processor-based computer - After you upgrade a computer that uses a processor other than an Intel processor to Microsoft Windows XP Service Pack 2 SP2 , you may receive the following error message after you restart the computer:A problem has been detected and Windows has been shut down to prevent damage to your computer After you log on, you receive the following error message:Microsoft Windows The system has recovered from a serious error.
You receive the following Stop error message on a blue screen:A problem has been detected and Windows has been shut down to prevent damage to your computer This error may occur during startup or after you have started the computer.
Setup may restart during the hardware detection phase of Windows XP installation - When you perform a new Microsoft Windows XP installation or a repair installation, your computer may restart when Setup reaches the hardware detection phase.
Related Article: How to troubleshoot hardware and software driver problems in Windows XP - After you install a new hardware device or new software, your computer may start to restart spontaneously, or you may receive error messages on a blue screen.
One of three types of problems occurred in kernel-mode: A condition that the kernel is not allowed to have or intercept also known as a bound trap , e. Software problems Hardware failuresThis error is usually caused by a hardware failure, more often than not, faulty RAM. This error may also be caused by over-clocking. When you try to print by using one of these drivers after you install security update , you may experience the following symptoms: Your computer automatically restarts.
After you log on, you receive the following error message:Microsoft WindowsThe system has recovered from a serious error. You receive the following Stop error message:A problem has been detected and Windows has been shut down to prevent damage to your computer When you shut down and restart your computer, the computer starts normally.
However, the Stop error recurs regularly. To interpret it, you must identify which exception was generated. May also be reported as 0xE. You start to print a large drawing in Visio. When you click Cancel in the Print dialog box to cancel the print job, you experience one or both the following symptoms: Visio stops responding hangs.
You may see reference to the Usbser. You may receive the Stop error when you use the keyboard to activate and control the menu items of some programs. If you click Cancel in the Printing dialog box, you may receive a 0xE Stop error message.
The power indicator on your computer indicates that the computer is not on standby. Error code 4. Error code 7. Error message in the win32k! You may receive a Stop error message on a blue screen when you start a Microsoft Windows Server based computer or a Microsoft Windows XP-based computer When you start a Microsoft Windows Server based computer or a Microsoft Windows XP-based computer, you may receive a Stop error message on a blue screen.
This error message may appear randomly. To signal a hardware error, the processor signals the detection of a machine check error by generating a machine check exception Interrupt This article is fully applicable to Windows XP but Microsoft fail to make that point clear.
You receive a "Stop 0xC" error message when you shut down a computer that is running the Microsoft Storport storage driver in Windows Server SP2 When you shut down a computer that is running the Microsoft Storport storage driver Storport. It is not known if this error occurs on bit Windows XP, and if your problem is a Storport driver on a bit XP then there is nothing to stop you from trying the driver fix for bit Windows Server When this occurs, the computer stops at a blank screen.
The mouse pointer is displayed, but you cannot move it. The computer does not respond either to mouse movements or to keyboard input; If your floppy disk drive is not present in My Computer, the Standard Floppy Disk Controller device in Device Manager may display the following error status:This device cannot find enough free resources that it can use.
You receive the following "Stop" error message on a blue screen:A problem has been detected and Windows has been shut down to prevent damage to your computer Please read the Readme.
0コメント