Bootcamp: hal.dll and disk error SOLVED. Simple workaround

Many people had the "hal.dll missing" and "No disk" error while trying to install Windows with bootcamp on OSX leopard. I read a lot of workarounds and solutions, which some are complicated and some just don't work.
Here is my simple workaround to get rid of errors:
(Principle: force the shell of windows to appear before installation, so that we can quick format the bootcamp partition with" format" command)
1. Create a windows partition with bootcamp as usual (if you have already one then restore the OSX partition)
2. Restart and boot on windows cd. (press the option key ("alt") during restart)
3. When bluescreen appears and drivers are loading, press repeatedly F6 and F10. You should get a message that no SCSI disk was found and that you should press "S" or "enter" to continue. Press "enter". Now you should get a black screen in console mode.
4. Now we format the bootcamp partition. Type this: "FORMAT C: /Q /FS:NTFS". Put FAT32 instead of NTFS if you want the file system to be FAT32.
5. Press 'Y' to confirm.
6. Restart the computer, boot on cd, and install windows as usual. When arrived on partitionning during install, DO NOT REFORMAT!!!! Install on the partition that we just created before!
PS: I think that bootcamp just messes up the windows partition. That's why you get "disk error". When formatting during the windows installation, the partition is correct for windows but it overwrites entirely the bootcamp partition instead of just formatting it. I think that the quick format from the shell does just change the file system without modifying the partition itself. However, it works, so why bother why it does?....
Let me know if you have difficulties.
Message was edited by: febex

Perhaps you need to use an XP cd with sp2 slipstreamed, install boot camp update 2.1, then SP3.
The following URL has a note: --> http://support.apple.com/downloads/BootCamp_Update_2_1_for_WindowsXP
Important: Installation of Boot Camp 2.1 is required before installing Windows XP Service Pack 3 (SP3)

Similar Messages

Boot Camp ****: HAL.DLL and other problems

Okay I am really frustrated, so if I come off like a jerk... well, I don't mean to, but my frustration is going to bleed into the tone of this post. Let me ask you not to reply that I have a bad Windows CD. I've been a gosh darn network administrator for over ten frakking years now, and I successfully use the same bleeping CDROM disk on dozens of other computers all the bleeping time.
Okay, now that I've got that off my chest, here's the situation: I have a Windows XP Pro CD with Service Pack 3 slipstreamed into it. I downloaded it from Microsoft. My organization has a Select Agreement with them, so we can do that. There is a winnt.sif file on it that automates a few things (such as entering the key number), but it allows me to do the partitioning and formatting manually.
If I leave the partition as FAT32, then when the Windows installer attempts to reboot into the GUI portion of the install, then it says, "Disk Error. Press any key to restart." Pressing keys does nothing, so I have to power it off.
If I format the partition with NTFS (tried both Quick and Full formats with the same results), then it finishes the text mode portion of the install, reboots, and tells me that I'm missing HAL.DLL.
I have tried several different sizes of partitions (partitioning with the Boot Camp utility... not the Windows installer), and been through the text portion of Windows install at least a dozen times. I have searched the Net, and failed to find a CD that would allow me to attempt installing Windows off my RIS server. I have burned new copies of my CD onto CDR and CDRW media. The only thing I cannot do is obtain an original XP CD since our organization isn't big enough to qualify for Microsoft to send us Select CD's (and my boss ain't gonna pay for a retail copy just so that I can run Boot Camp). And please don't ask me if I'm properly licensed to install Windows on my Mac. I know the Windows EULA inside and out. It's all legit.
Any help here would truly be appreciated.

Perhaps you need to use an XP cd with sp2 slipstreamed, install boot camp update 2.1, then SP3.
The following URL has a note: --> http://support.apple.com/downloads/BootCamp_Update_2_1_for_WindowsXP
Important: Installation of Boot Camp 2.1 is required before installing Windows XP Service Pack 3 (SP3)

Server connection: drops and disk errors

Currently, I'm the only workstation using a Mac Pro (the rest are G5s), and my connection to our art server (running Win 2003) constantly drops, whereas the G5s stay connected just fine. Also, today this same server started giving me code -41 disk error messages; I can't save or re-write anything onto the server, even though there's a good 20GB of storage available.

John,
We lost the connection earlier this evening, and even though the lights were all still on on the Router, the only way to regain our connection seemed to be turning the router off and on (we did this at the plug, i'm not sure this is what we're meant to do!).
Are the events in my event log worrying at all? I'm scared by them!
Tina

SBOD and disk errors-- oh my!

A month ago, a few weeks after I upgraded from Snow Leopard to Mountain Lion on my ~2010 21.5" Intel iMac, performance started to deteriorate, and the spinning beachball of death (SBOD) began to appear. (I do think the upgrade is a red herring.)
Safari seemed to trigger it most, though it happened at other times. So I disabled extensions and plugins, etc-- no dice. Then I looked at the console and saw that Kernel: disk0s2 I/O errors often happened when the SBOD appeared.
Questions:
1) I am hoping this is a hard drive problem based on the details below, labeled WHY I THINK DRIVE PROBLEM-- what do you all think?
2) When I wiped my disk (details below) I neglected to save the recovery partition. How do I get this back?
3) For some reason, I cannot boot off of my original snow leopard installation disc-- it always hangs after showing the bootup apple on the gray screen.
4) I also cannot use the "D" key on bootup to hardware test the system.
How can I get my recovery partition back? How can I test my system? Do you think the hard drive will have auto-mapped bad blocks, or do you think an imminent crash will occur?
DETAILS:
Disk Utility showed S.M.A.R.T. Verified, and said "No Apparent" problems with the hard drive (partitions) or volume-- though I am beginning to think that it would say a concrete slab had no apparent problems. I got SuperDuper (yes, I waited until I had problems! ) and tried making a current full backup to my time machine disk with SuperDuper, but it hung.
I tried resetting the NPROM and SMC, and around this time the iMac stopped booting-- it would hang with the spinning lines under the Apple on the gray screen forever. This happened regardless of pressing Command-R, or trying to go into Safe Mode. At these times, the top left of the iMac, above the slit, would get very hot. No fan would run.
I tried a number of things. Maybe the option key would have always worked, or maybe I had initially used the wrong key combination for NPROM, or hadn't waited long enough before restarting for the SMC. In any case, eventually I was able to boot again.
WHY I THINK DRIVE PROBLEM:
This time, I got a USB drive (Seagate Backup Plus) and used SuperDuper to back up to it. There were several places where I had to delete files to continue. It always stopped at the same file until I deleted it. On a large file, I attempted to use "Curl -C - -O file://<pathname>" to copy, but it never could copy past a certain point in the file.
This makes me think the problem is indeed a disk error, as opposed to a cable, controller, or software-- unless the controller is hiccupping with a certain bit combination of drive address, which I guess is possible.
I WIPED MY DISK: Anyway, I got the drive backed up with some original corrupted files deleted. Then I used Disk Utility to wipe the original disk, and did one pass zeroing it out. Then I restored the drive.
The result is a wonderfully responding iMac again... but I'm waiting for the other shoe to drop.

The boot drive is failing, or you have some other hardware fault.
Make a "Genius" appointment at an Apple Store, or go to another authorized service center.
Back up all data on the internal drive(s) before you hand over your computer to anyone. There are ways to back up a computer that isn't fully functional — ask if you need guidance.
If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
Keeping your confidential data secure during hardware repair
*An SSD doesn't need to be zeroed.

How do I correct error messages MSVCR80.dll and windows error 7 126?

After installing the latest itunes update, I received two error messages: MSVCR80.dii and windows error 7 126? I cannot access itunes at all and am eager ti fux these errors. If Apple itunes is at fault I sure wish they would fix the problem. At least I'll save money if I can't access itunes!

Hey koicaretaker!
Here is an article that will help you troubleshoot this issue:
iTunes 11.1.4 for Windows: Unable to install or open
http://support.apple.com/kb/TS5376
Thanks for using the Apple Support Communities!
Cheers,
Braden

Pacman downloading slowly and signature errors [Solved]

So, I'm trying to do a clean install of Arch Linux. I've chrooted into the system and tried to download wireless_tools, netcfg, and dialog to set up my wireless connection but ran into two issues. First, sometimes I would get a message that says something like:
error: failed retrieving file 'wireless_tools-29-7-x86_64.pkg.tar.xz' from mirror.us.leaseweb.net : Operation too slow. Less than 1024 bytes/sec transferred the last 10 seconds
From what I gathered then it should try the next mirror in my mirrorlist until it finds one with a decent speed. However, then it checks the package integrity and I get more error messages. For each package there's a message like:
error: wireless_tools: signature from "Gaetan Bisson <[email protected]>" is invalid
and then:
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Any ideas on what's causing this/how to fix it?
Last edited by TKing (2012-10-02 21:45:47)

Did you set the hostname in both files:
https://wiki.archlinux.org/index.php/Be … e#Hostname
/etc/hostname
Needs to just contain one line, the hostname.
/etc/hosts
You need to edit two of the lines to the exact same text string you put in /etc/hostname
My /etc/hostname:
Jeremiah
My /etc/hosts:
# /etc/hosts: static lookup table for host names
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 Jeremiah localhost
::1 Jeremiah localhost
# End of file
If those three different text entries do not exactly match then you will have network troubles.

Skype crash and disk errors - a cautionary tale

Skype crashed (again) hanging the whole computer. Forced shutdown: restarted in single-user mode and ran Applejack. Reported a number of overlapping files. Nasty.
Ran DiskWarrior. It reported 197,192 overlapping files and hung. I thought about it a bit, re-ran Applejack and flushed the caches. This left only a couple of minor errors which were easily repaired.
Presumably Skype messed up its own cache files (197,000 though...!). Anyway, despite what Applejack's instructions say, it looks like it's worth clearing the caches before doing a disk repair - or at least before doing anything else if this sort of error shows up.

Most modern drives automatically map bad sectors during use. It is a transparent process. Just because the drive has bad sectors means nothing - practically every drive will have them. What would be disturbing is if the automatic sector mapping is failing and is not discovering the bum sectors. This is why once a drive starts to behave badly and DiskWarrior can''t fix it, I never trust it again.
If I keep it in use, about the only thing it's good for is a render scratch drive - that is - a drive that simply holds temp files. That way, when it dies, nothing serious is lost. Using it as your only back up, especially after it has given fair warning of going bad, would be ... um ... not smart.
Under the fwiw category, external drives can act flaky simple through dying power supplies. The drive mechanism may be fine but is being corrupted by intermittent or wavering voltage.
Also, I'm no fan of partitioning. ymmv.
Regards,
x

Surface Pro 2 freezes briefly - storachi and disk error

Hello tech net
I am running a surface pro 2 with windows 8.1 (updates current as of 3 days ago), 4 GB RAM, 64GB HD. For the last several months the device will freeze up for about 5-10 secs multiple times per hour, and then resolve on it's own. During that
time task manager shows the disk is at 100% and event viewer will display 2 Warnings: an storachi (129) and a disk (153) error. This is in addition to a service control error (7000) that happens multiple times per second but doesn't seem to
affect performance. These freezes happen when plugged in, on battery, SDXC card installed or not, wi-fi or not, and no particular program running. It even happens when I'm not using the device if I go back thru event viewer. The 100% on disk is
not associated with any increase in process or app activity. Most of the time there are a couple 0.1MB/s demands like outlook, explorer or service host running but nothing that looks unusual when it spikes and freezes.
I am not a tech person and my online search for help has yielded a wide variety of solutions to this problem that didn't seem to be reliable fixes and sounded a little beyond my usual capabilities. Anyone know if this is fixable or do I need to send
the device back?
Thanks!

Not much information here to go on. Can you supply the bdd.log file. Copy to a public share like OneDrive, and share the link.
Typically any problems with format and partition have to do with the storage driver. Are you using the latest ADK from Microsoft? As Surface Pro 2 only supports Windows 8.x, you should *only* be using uEFI mode and GPT.
THe default MDT Task Sequence will do the right thing, *however*, if you change the settings in the "FOrmat and Partition Disk" step, you are then responsible for the settings from then on.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

P45 NEO-3: Random freeze,boot and disk error

Hello,
Running windows 7 64 Ultimate
3 different errors:
1: "A disk read error occurred Press Ctrl + Alt + Del to restart"
2: Random freeze when using the pc
3: Can't find booting device or something
it's random .. sometimes working 1 hour and problem .. sometimes (like now) no problems 20 hours+
I have this PC over 1 year and the problem started 3 months ago.. I've bought new HDD Western Digital 1TB
My specs:
MB MSI P45 NEO3-FR S775
DDR2 2x2GB 800 Kingston
CPU Desktop Core 2 Quad Q9550 2.83Ghz
VGA PCX XFX 8600GT 250MB DDR3 DVI
Fortron 400w Power supply
DVD LG 20x GH20NS10 Sata
Can someone help me with this?
Is this a hardware or/and software problem?
Thanks

What is your current BIOS Version?
Quote
Fortron 400w Power supply
What is the exact model name of that PSU? How many +12V lines does it have and what is the amperage limit on each of them? (Look at the sticker on the PSU).
Quote
DDR2 2x2GB 800 Kingston
What is the exact model name/number? (There should be a sticker on the modules telling you that.)
What is the brand & model name of your hard drive? Go to the manufacturer's product site and look for a diagnostic utility for DOS. Then use this tool to do a full check of your hard drive.
what kind of hard drive are you using?
Quote
Running windows 7 64 Ultimate
Are we looking at a "fresh" installation you put on for your current hardware configuration or is it an installation from an older system with different specifications?

No sound (but beep present) and vlc error [Solved]

Hello,
I don't know why but after reboot Arch, I don't have any sound except I can hear the beep. I try different methods to have sound again. But none of them worked.
I really don't know what to do.
If it cant help , the output of cat /proc/asound/cards is:
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xd4520000 irq 54
1 [Generic ]: HDA-Intel - HD-Audio Generic
HD-Audio Generic at 0xd4420000 irq 55
I have a .asoundrc in my home which is:
pcm.!default {
type hw
card 0
ctl.!default {
type hw
card 0
When I test that command: speaker-test -c 2.
I hear nothing and the output is :
Playback device is default
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 64 to 1048576
Period size range from 32 to 524288
Using max buffer size 1048576
Periods = 4
was set period_size = 262144
was set buffer_size = 1048576
0 - Front Left
1 - Front Right
When I run vlc i have a error which is :
pulse audio output error: PulseAudio server connection failure: Connection refused.
I think that error is because I install pulseaudio. But when I change the audio device with PCH or Generic, I have this error:
mpgatofixed32 audio converter error: libmad error: bad main_data_begin pointer.
And sound it's not working in any browser. But what I find weird it's I can't hear sound like music but I can still hear the beep when I'm on a tty.
I thank you in advance for your help.
Last edited by sylflo (2013-10-09 08:13:27)

You should avoid using card number in your .asoundrc. Using card name is recommended, since soundcards may be recognised in different order at boot. It may interfere with modules. So assuming your default card name is PCH use following code:
pcm.!default {
type hw
card PCH
ctl.!default {
type hw
card PCH
Instead of simply using speaker-test try
aplay -D PCH /usr/share/sounds/alsa/Front_Left.wav
#eventually
aplay -D plughw:PCH /usr/share/sounds/alsa/Front_Left.wav
#or
speaker-test -D PCH
to test a specific card directly.
Next check your loaded sound modules. Your should have snd-hda-intel specified to load somewhere in /etc/modules-load.d, so to check this you can use:
grep -Ri snd /etc/modules-load.d
#also check what you have loaded
lsmod | grep snd_hda
From what I understand your hardware is, you should have snd-hda-intel model=pch loaded. Check /etc/modprobe.d also. Maybe it got changed in the upgrade.
The reason your hearing sound is that you have pcspkr module loaded and I assume most engineers design a hardware mix/mux between internal and external speakers in laptops, even though they seem to be two different devices. You should be able to use beep or something similar in X to test it.
Is a user required to be in audio user group to use pulseaudio? Is the pulseaudio server running?
Do you have a HDMI output on your laptop? I think the second soundcard is from your graphicscard and they usually use only one digital output, so if that card is used as primary you will not hear a thing.
Last edited by emeres (2013-10-09 07:21:58)

X264-git and GPAC error [SOLVED]

I'm currently having problems with compiling x264 from git with support for GPAC on 64 bit. It makes no difference if I'm using GPAC 0.4.4 or CVS. The error is simply this:
gcc wrote:/usr/bin/ld: cannot find -lgpac_static
The only relevant search I came up with has this solution:
http://mailman.videolan.org/pipermail/x … 01917.html
This doesn't work because gpac_static.a doesn't exist here. The only thing I could think of was to try get GPAC to create a static library, and that changed nothing. Is anyone here able to get this working lately? I'd really like to get mp4 functionality back in x264.
Last edited by skottish (2008-05-21 15:37:16)

Thanks daneel971. I appreciate your help.
I removed the version of GPAC that I had on my system to try to diagnose my build problems after doing what you and another user at doom9 suggested. So, I tried that "old" way. Of course I would use a PKGBUILD for this normally, but it wasn't working and this is a good test to make sure that I didn't screw anything up with my modifications. 'configure' works fine. Either I'm really dumb today or something is very wrong here.
[skottish@iasE gpac]$ make
make -C src all
make[1]: Entering directory `/home/skottish/gpac/src'
gcc -O3 -fPIC -DPIC -fno-strict-aliasing -Wno-pointer-sign -Wall -I/home/skottish/gpac/include -c -o utils/os_divers.o utils/os_divers.c
utils/os_divers.c: In function 'gf_sys_get_rti':
utils/os_divers.c:1143: warning: format '%lld' expects type 'long long int *', but argument 3 has type 'u64 *'
utils/os_divers.c:1146: warning: format '%lld' expects type 'long long int *', but argument 3 has type 'u64 *'
gcc -O3 -fPIC -DPIC -fno-strict-aliasing -Wno-pointer-sign -Wall -I/home/skottish/gpac/include -DGPAC_IPV6 -c -o utils/os_net.o utils/os_net.c
utils/os_net.c: In function 'gf_sk_connect':
utils/os_net.c:407: warning: cast from pointer to integer of different size
utils/os_net.c:417: warning: cast from pointer to integer of different size
utils/os_net.c: In function 'gf_sk_bind':
utils/os_net.c:517: warning: cast from pointer to integer of different size
utils/os_net.c:533: warning: cast from pointer to integer of different size
utils/os_net.c: In function 'gf_sk_setup_multicast':
utils/os_net.c:738: warning: cast from pointer to integer of different size
utils/os_net.c:762: warning: cast from pointer to integer of different size
gcc -O3 -fPIC -DPIC -fno-strict-aliasing -Wno-pointer-sign -Wall -I/home/skottish/gpac/include -c -o utils/os_module.o utils/os_module.c
gcc -O3 -fPIC -DPIC -fno-strict-aliasing -Wno-pointer-sign -Wall -I/home/skottish/gpac/include -c -o utils/os_thread.o utils/os_thread.c
utils/os_thread.c: In function 'RunThread':
utils/os_thread.c:97: warning: cast to pointer from integer of different size
gcc -O3 -fPIC -DPIC -fno-strict-aliasing -Wno-pointer-sign -Wall -I/home/skottish/gpac/include -c -o utils/list.o utils/list.c
gcc -O3 -fPIC -DPIC -fno-strict-aliasing -Wno-pointer-sign -Wall -I/home/skottish/gpac/include -c -o utils/base_encoding.o utils/base_encoding.c
gcc -O3 -fPIC -DPIC -fno-strict-aliasing -Wno-pointer-sign -Wall -I/home/skottish/gpac/include -c -o utils/bitstream.o utils/bitstream.c
gcc -O3 -fPIC -DPIC -fno-strict-aliasing -Wno-pointer-sign -Wall -I/home/skottish/gpac/include -c -o utils/color.o utils/color.c
In file included from /home/skottish/gpac/include/gpac/events.h:34,
from /home/skottish/gpac/include/gpac/user.h:35,
from utils/color.c:26:
/home/skottish/gpac/include/gpac/math.h:41:18: error: math.h: No such file or directory
make[1]: *** [utils/color.o] Error 1
make[1]: Leaving directory `/home/skottish/gpac/src'
make: *** [lib] Error 2
[skottish@iasE gpac]$ ls /home/skottish/gpac/include/gpac/
avparse.h esi.h media_tools.h nodes_svg_sani.h svg_types.h
base_coding.h events.h mediaobject.h nodes_x3d.h sync_layer.h
bifs.h ietf.h module.h options.h term_info.h
bifsengine.h internal modules path2d.h terminal.h
bitstream.h ismacryp.h mpeg4_odf.h renderer.h thread.h
color.h iso639.h mpegts.h scene_manager.h token.h
config.h isomedia.h network.h scenegraph.h tools.h
constants.h laser.h nodes_mpeg4.h scenegraph_svg.h user.h
crypt.h list.h nodes_svg_da.h scenegraph_vrml.h utf.h
download.h math.h nodes_svg_sa.h setup.h xml.h
GPAC doesn't like itself and x264 doesn't like it either...
Last edited by skottish (2008-05-19 01:02:36)

Disk Error, Hal.dll Error, No bootable device error - Every other error.

Hi,
I've been trying for ages to install xp using bootcamp. I have windows xp sp1, which i've slipstreamed to create an SP2 version. I also have access to the family backups of every OS we've ever bought, including a mix cd of windows xp MCE, XP home, XP professional - all SP2.
I moved to the mac a year or so ago - I've installed windows more times than I've rolled out of bed in the morning.
I had it working back when I was running Tiger - I upgraded to leopard - decided I wanted to try a reinstall of windows, formatted the drive and followed all the steps to install.
The main issue is that when I insert the windows install CD - it never gives me a chance to format the disk. I tried installing parallels and using that to boot up XP, and it does give me an chance - but after that install is finished I get the Hal.dll error.
I removed the bootcamp drive but after installing refit - it still shows up on the boot menu. Somehow, my HDD's GUID partition table & MBR for the windows partition is messed up.
At the end of the day - I've tried everything I can think of to install windows. And it just won't go. It used to work - what's changed? Any suggestions?
Cheers in advance.

I too had problems with Hal.dll and "Disk Error".
Installing XP on my Mac Mini with 10.5.1 Leopard (fresh install on a new HDD), I got the Hal.dll error (my 2nd time with this lovely error, the first being on a iMac with Leopard). According to Billbear from this thread:
http://forum.onmac.net/showthread.php?t=2793&page=5
You will get Hal.dll when you try to install XP on a partition that isn't the last partition on the disk. I tried this solution, and it worked for me. I previously had:
1) Leopard
2) XP
3) User partition
And changed it to:
1) User partition
2) Leopard
3) XP
Next, however, I got a different error -- the dreaded "Disk Error". I tried the Apple support solution (formatting as NTFS instead of converting from FAT to NTFS), but I got the same error. I read somewhere (can't remember which thread, since I looked at so many) that you might get the problem if XP wasn't installing on C: drive. So I changed my partitioning from
1) User partition (FAT)
2) Leopard (HFS+)
3) XP (FAT)
To:
1) User partition (HFS+)
2) Leopard (HFS+)
3) XP (FAT)
The installer saw the XP partition as C: and was able to install smoothly (Quick reformatting to NTFS). I then used Disk Utility to change the User partition from HFS+ to FAT, and everything works fine!

No luck installing Windows XP SP2 on Macbook hal.dll error

1. I partitioned 45GB with Boot Camp Assistant.
2. Loaded Win XP SP2 CD and started installation.
3. Formatted BOOTCAMP partition on NTFS Quick (Also tried NTFS normal [slow])
4. After it copies everything to the drive and reboots I get a hal.dll missing/corrupt error.
I have tried repartitioning dozens of times and have tried 3 different Windows CDs
Thanks for your help
Message was edited by: pesqair

Startup from the windows CD,
delete the 200MB sized partition and the Bootcamp partition.
Then make a new NTFS partition from the new space and install XP.
It's the 200MB partition that has something to do with boot record, Bootcamp does not recognize it's own partition as bootpartition!
Good luck installing windows!

Hal.dll error error message: here is the solution !

Thanks to endership for the procedure. For people who were getting the hal.dll missing file error message or for those who are wondering about the right way to install Windows XP SP2 with Bootcamp, here is the steps you have to follow.
1) First, get an original Windows XP SP2 cd and be sure that your CD is bootable and that you can access the recovery console in a repair function (not all the cds got the function, so be careful).
2)After, you go in Apple applications, utilities and you click on the boot camp assistant
3)If you got a Windows partition already created that is not working, resulting from a bad installation of Windows with bootcamp, just merge the two partitions (windows and mac os x) using the restore function.
4)Use 32 Go for Windows (default option) and be sure that your Windows cd is in the drive and launch the installation.
Computer will reboot in the installation program after that all the drivers has been loaded (the blue screen lasting about 5 minutes).
5)Once your are in the installation menu, just select the option that takes you to the repair console.
6)You will get a C: command line, sort of MS-DOS. Like mentionned enderfish, type "diskpart" to visualize the partitions created and be sure that the c: drive is labeled "bootcamp". Just return to repair console in the c: command line.
7)type the following command line:
FORMAT c: /Q /FS:NTFS
You will get a quick format of the c: drive in the NTFS file system. It will also probably work in FAT32, but I've never tried.
8)After that the format has been done, hit the POWER button to reboot.
9)You will be back in the installation menu; you'll also have to wait once again during 5 minutes for the drivers loading process.
10)Once you get in the installation blue screen, just choose the partition that has been created and choose to let the file system intact.
11)Windows XP will be copying install files on the HD, install Windows XP SP2.
12)Once, the installation is done and you entered in Windows (if you followed the instructions carefully), insert in the cd drive, the Leopard CD and install Windows drivers.
13)Reboot
14)Enjoy!
Message was edited by: Bert770

In my experience (because this happened to me), I found that it was a -user error- (mine). I reviewed Apple's instructions (which said to reformat the BOOTCAMP partition) and DELETED the BOOTCAMP "C:" partition (from within the XP installer) first. When you do this, it combines with partition with the "unused" 128MB partition that separates the Mac partition from "C:".
Apparently the 128MB partition really -is- used for something; probably to help redirect XP to the proper location to find hal.dll (which is why the file -even if repaired/replaced- continues to be reported as missing/corrupted). Even XP's automatic repair won't fix this issue (as it proceeds to copy -everything- anew and still fail upon reboot with the same error).
The answer seems to be "don't delete the C: partition". Instead, just select it, hit ENTER and, -in the next screen-, format the partition (Quick is OK). Everything proceeds properly at that point.
I just finished doing seven iMacs and tried quite a number of alternate solution (suggested here and elsewhere). The only thing that worked consistently was following Apple's directions!
By the way, once I got one Mac working properly (using FAT32 as I had only a 32GB partition and I wanted to have the PC partition appear on the Mac's Desktop if we booted into OSX), I imaged the partition and tried restoring it to another Mac on which I had only used BootCamp Assistant to partition the drive. Booting into XP produced the same hal.dll error. However, if I restored to a partition that had already had a successful XP installation done to it in the proper manner, this replacement of the partition's data with the image's data was successful. (I don't know why. I tried both a "master" image and a "compressed" image; only the compressed image worked and only as noted above.)
I'm not writing this to come off as a guru; rather, this is simply what ended up working for me and I thought others might benefit from knowing what mis-steps I took (and would then not follow in those mis-steps).
Barry

BSOD hal.dll+12903 and ntoskrnl.eve+185543

I have been working on this PC for quit some time the person before me had no records of what was wrong with the PC or what he did to correct it. The PC shuts down at random and freezes at times, I had changed the UPS, the power cord and even noticed that
the heat sink was loose fixed that. Still the PC kept freezing, I decided to go ahead and re-install Win7 now its BSOD and I used Bluescreenview to view the errors and hal.dll and ntoskrnl.exe appeared. I ran a mem test and it was ok ran an HD test and still
good. Any help is appreciated thanks in advance.
Running Win 7 pro 64bit
4gig ram
video: NVIDIA GeForce 8400GS
mobo: P5N-E SLI
==================================================
Dump File         : 061914-34788-01.dmp
Crash Time        : 6/19/2014 9:02:30 AM
Bug Check String :
Bug Check Code    : 0x00000124
Parameter 1       : 00000000`00000000
Parameter 2       : fffffa80`04cbe038
Parameter 3       : 00000000`b2000000
Parameter 4       : 00000000`00010014
Caused By Driver : hal.dll
Caused By Address : hal.dll+12903
File Description : Hardware Abstraction Layer DLL
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor         : x64
Crash Address     : ntoskrnl.exe+6f880
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\061914-34788-01.dmp
Processors Count : 2
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 270,984
Dump File Time    : 6/19/2014 9:04:35 AM
==================================================
==================================================
Dump File         : 061914-38735-01.dmp
Crash Time        : 6/19/2014 8:55:48 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00041790
Parameter 2       : fffffa80`017ac900
Parameter 3       : 00000000`0000ffff
Parameter 4       : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f880
File Description : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.17273 (win7_gdr.130318-1532)
Processor         : x64
Crash Address     : ntoskrnl.exe+6f880
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\061914-38735-01.dmp
Processors Count : 2
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 270,984
Dump File Time    : 6/19/2014 8:57:53 AM
==================================================

Tmtz15
There wer all related to hardware and called BCC124
Stop 0x124 is a hardware error
If you are overclocking try resetting your processor to standard settings and see
if that helps.
If you continue to get BSODs here are some more things you may want to consider.
This is usually heat related, defective hardware, memory or even processor though
it is"possible" that it is driver related (rare).
Stop 0x124 - what it means and what to try
Synopsis:
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.
Generic "Stop 0x124" Troubleshooting Strategy:
1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable
ways.
2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
It is good practice to run the latest drivers anyway.
4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
Their website should provide detailed instructions as to the brand and model-specific procedure.
5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is
free from defects - only that none were encountered during the test passes.
7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games,
utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine
is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.
Should you find yourself in the situation of having performed all of the steps
above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.
More advanced reading can be found here from a MS MVP IT PRO
http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/
Wanikiya and Dyami--Team Zigzag

Bootcamp: hal.dll and disk error SOLVED. Simple workaround

Similar Messages

Maybe you are looking for