Tosiba laptop could not start not even with safe mode.
It prompted with the following messages:
Multi O Disk O rdisk O partition (1) Windows/System32/ntokrnl.exe
Multi O Disk O rdisk O partition (1) Windows/System32/hal.dll
Multi O Disk O rdisk O partition (1) Windows/System32/kdcom.dll
Multi O Disk O rdisk O partition (1) Windows/System32/bootvid.dll
An expert who has achieved level 3 by getting 1000 points
An expert that got 20 achievements.
An expert that got 10 achievements.
An expert that got 5 achievements.
Re: Tosiba laptop could not start not even with safe...
The error message refer to system files it cannot load dur to either corrupted or missing files.
You can try to do a repair with your Windows CD install disk and if this does not work you will need to reinstall Windows again together with any drivers that Windows didn't install and your programs.
Note you will lose you data in this process, hoped you backed up your files.
a 6ya Technician can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repair professionals here in the US. click here to Talk to a Technician (only for users in the US for now) and get all the help you need. Goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
The BOOT.INI file may be corrupt. Boot to a command prompt and rename original file c:\ren boot.ini boot.tmp. Now type edit. and insert the following script.
[boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
Save as boot.ini. Alt key gives you the menu options You can also create the file elsewhere and copy to c:\ Remember to rename original. Note! This is a single partition standard from factory configuration.
<windows root>system32hal.dll. is missing or corrupt. â How to fix it?â The Hal.dll file is the first file
that boot.ini tells the system to look for at boot. â Looking at it this way, this error message can be
rather misleading. In fact the reason could be a number of things, such as: â The boot.ini file is
actually corrupt or damaged, â or it is pointing the Startup to look in the wrong place.
The Hal.dll file is located in the System32 directory of your %SystemRoot% which in a default XP
setup is:â C:WindowsSystem32.â You can use the Dos boot disk (or NTFS Reader above) to
quickly determine if the file is missing.â If it is, then you should extract it from your XP CDrom and
place it in its proper location.Boot to your XP CDrom, and then choose 'r' to go to the Recovery
Console.â With your XP Cdrom in the drive, issue this command:Expand D:i386hal.dl_
C:Windowssystem32â â (This assumes the CDrom is D and your System Partition is C) â If this
does not cure your issue this may be due to issues in your boot.ini file.â â The boot.ini file is
actually corrupt or damaged, or it is pointing the Startup to look in the wrong place.
Resolution:â The easiest way to fix this is to boot to the Recovery Console and replace the old
boot.ini with a new one.â Once you have booted to the Recovery Console run these commands at
the prompt:Attrib -H -R -S C:boot.iniâ â â (This removes the attributes and allows deletion).
DEL C:boot.iniâ â â â â â â â â â â â â â â â â â (Deletes the corrupted boot.ini
file)â â â â â â â â â â â â â â â â â â â â â â â â â â â â
BootCfg /Rebuildâ â â â â â â â â â â â â â â â (Recreates the new boot.ini file)If you would like
to view the boot.ini file, you will need a boot disk to get to the DOS prompt.â If you have formatted
with FAT32, then you may use a Windows boot disk (such as a W98 disk), but if you are running
NTFS, you will need a NTFS reader boot disk, such as NTFS Reader For DOS which is available for
download here.â To diagnose the problem, copy the boot.ini file from the hard drive (C:boot.ini) and
open it with Notepad.â You will want to verify that the "Default=" line as well as the ARC path line
are pointing to the right location.â Here is two examples of boot.ini files (ARC paths start with multi):
multi(0)disk(0)rdisk(0)partition(1)WINDOWS="Microsoft Windows XP Professional" /fastdetect This
is a sample of the above Boot.ini file after adding another partition running Windows 2000
Professional. [boot loader]
multi(0)disk(1)rdisk(0)partition(1)WINDOWS="Windows XP Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)WINNT="Windows 2000 Professional" /fastdetect
if you are using windows xp, then follow these steps: 1) right click "my computer" icon, select "advanced" tab, click settings button towards the right of "start up and recovery" and click "edit" tab a notepad window appears with some text in it which reads something like this :
[boot loader] timeout=0 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /FASTDETECT
modify that text to look like this: [boot loader] timeout=0 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /FASTDETECT /3GB /userva=2800 /NoExecute=Op
Warning : only the "/3GB /userva=2800 /NoExecute=Op" has to be added extra else you will mess up
2) save the notepad and insert max ram, and check, if any BSOD's if the problem persists, then it is hardware related.. Most probably one of your ram stick may be the problem child(which may be either incompatible with your motherboard or defective)
what are the things that you added recently, hardware(additional hdd, memory, video card) or software (antivirus, office, etc games.) try running a hard drive diagnostics, usually computer manufacturer install a hdd diagnostics on their BIOS that you can run. hit me back on the results.
If this is all you are seeing, then this is not an error. What is happening here is that your computer is loading Safe Mode. This is a way to load Windows operating system without any extra software or programs, using the most basic drivers and software to load. There are a lot of benefits to accessing this mode, especially if you installed a program that stops you from getting into Normal Mode, or you have a virus that does the same. It makes it easy to troubleshoot. Here is a link to a website with a little more info:
I would suggest using the Windows Disk, if you have one, go through normal windows installation. At the point of installation just after pressing F8 it will detect windows exists and offer you a repair option press R to repair