I had previously done a boot camp on my Macbook 13-inch mid-2010 laptop years ago. However recently I have updated my Macbook's OS X to El Capitan Version 10.11.1 and now Windows crashes with a blue screen of death every time I try to load it. I can only assume that updating the Mac OS X is the cause of the problem. Therefore is there anyway I can alleviate this situation?
MacBook
1. What is the version of Windows (W7?).
2. Are Windows Updates set to Automatic?
3. Is it possible to take a photo of the BSoD and post it?
4. This is usually indicates the corruption of Windows BCD (Boot Configuration Data).
The windows software I used for the bootcamp was Microsoft Windows XP.
If the problem is corrupted data, how would I fix it?
What OS X version did you upgrade from? There are two distinct possibilities,
1. Partitions could have been corrupted, or,
2. WXP data was overwritten, partially, in most cases.
Let us check partitioning first.
Can you post the output of the following Terminal commands?
diskutil list
diskutil cs list
sudo gpt -vv -r show /dev/disk0
sudo fdisk /dev/disk0
The "sudo" commands will prompt for your password, and it will not be echoed back. You may also see a warning about improper use of "sudo" and potential data loss due to "abuse" of the command.
The OS X I upgraded from was 10.6.8. Where can one find the Terminal commands output?
Open Applications -> Utilities -> Terminal.
Triple click each of the following lines and Copy (Command+C) and Paste (Command+V) in the Terminal. Post the output as a reply.
diskutil list
diskutil cs list
sudo gpt -vv -r show /dev/disk0
sudo fdisk /dev/disk0
-diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *250.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 128.5 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
4: Microsoft Basic Data 120.7 GB disk0s4
-diskutil cs list
No CoreStorage logical volume groups found
-sudo gpt -vv -r show /dev/disk0
gpt show: /dev/disk0: mediasize=250059350016; sectorsize=512; blocks=488397168
gpt show: /dev/disk0: Suspicious MBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 488397167
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 250947768 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
251357408 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
252626944 235769856 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
488396800 335
488397135 32 Sec GPT table
488397167 1 Sec GPT header
-sudo disk /dev/disk0
Disk: /dev/disk0 geometry: 30401/255/63 [488397168 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [ 409640 - 250947768] HFS+
3: AB 1023 254 63 - 1023 254 63 [ 251357408 - 1269536] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [ 252626944 - 235769856] HPFS/QNX/AUX
Can you post the output of
sudo dd if=/dev/rdisk0s4 count=1 2>/dev/null | hexdump -C
This will show the first header block on BC/Windows partition.
exdump -C
Password:
00000000 eb 52 90 4e 54 46 53 20 20 20 20 00 02 08 00 00 |.R.NTFS .....|
00000010 00 00 00 00 00 f8 00 00 3f 00 ff 00 00 c8 0e 0f |........?.......|
00000020 00 00 00 00 80 00 80 00 ff 8f 0d 0e 00 00 00 00 |................|
00000030 00 00 0c 00 00 00 00 00 ff d8 e0 00 00 00 00 00 |................|
00000040 f6 00 00 00 01 00 00 00 25 86 c4 30 95 c4 30 8e |........%..0..0.|
00000050 00 00 00 00 fa 33 c0 8e d0 bc 00 7c fb b8 c0 07 |.....3.....|....|
00000060 8e d8 e8 16 00 b8 00 0d 8e c0 33 db c6 06 0e 00 |..........3.....|
00000070 10 e8 53 00 68 00 0d 68 6a 02 cb 8a 16 24 00 b4 |..S.h..hj....$..|
00000080 08 cd 13 73 05 b9 ff ff 8a f1 66 0f b6 c6 40 66 |...s......f...@f|
00000090 0f b6 d1 80 e2 3f f7 e2 86 cd c0 ed 06 41 66 0f |.....?.......Af.|
000000a0 b7 c9 66 f7 e1 66 a3 20 00 c3 b4 41 bb aa 55 8a |..f..f. ...A..U.|
000000b0 16 24 00 cd 13 72 0f 81 fb 55 aa 75 09 f6 c1 01 |.$...r...U.u....|
000000c0 74 04 fe 06 14 00 c3 66 60 1e 06 66 a1 10 00 66 |t......f`..f...f|
000000d0 03 06 1c 00 66 3b 06 20 00 0f 82 3a 00 1e 66 6a |....f;. ...:..fj|
000000e0 00 66 50 06 53 66 68 10 00 01 00 80 3e 14 00 00 |.fP.Sfh.....>...|
000000f0 0f 85 0c 00 e8 b3 ff 80 3e 14 00 00 0f 84 61 00 |........>.....a.|
00000100 b4 42 8a 16 24 00 16 1f 8b f4 cd 13 66 58 5b 07 |.B..$.......fX[.|
00000110 66 58 66 58 1f eb 2d 66 33 d2 66 0f b7 0e 18 00 |fXfX..-f3.f.....|
00000120 66 f7 f1 fe c2 8a ca 66 8b d0 66 c1 ea 10 f7 36 |f......f..f....6|
00000130 1a 00 86 d6 8a 16 24 00 8a e8 c0 e4 06 0a cc b8 |......$.........|
00000140 01 02 cd 13 0f 82 19 00 8c c0 05 20 00 8e c0 66 |........... ...f|
00000150 ff 06 10 00 ff 0e 0e 00 0f 85 6f ff 07 1f 66 61 |..........o...fa|
00000160 c3 a0 f8 01 e8 09 00 a0 fb 01 e8 03 00 fb eb fe |................|
00000170 b4 01 8b f0 ac 3c 00 74 09 b4 0e bb 07 00 cd 10 |.....<.t........|
00000180 eb f2 c3 0d 0a 41 20 64 69 73 6b 20 72 65 61 64 |.....A disk read|
00000190 20 65 72 72 6f 72 20 6f 63 63 75 72 72 65 64 00 | error occurred.|
000001a0 0d 0a 4e 54 4c 44 52 20 69 73 20 6d 69 73 73 69 |..NTLDR is missi|
000001b0 6e 67 00 0d 0a 4e 54 4c 44 52 20 69 73 20 63 6f |ng...NTLDR is co|
000001c0 6d 70 72 65 73 73 65 64 00 0d 0a 50 72 65 73 73 |mpressed...Press|
000001d0 20 43 74 72 6c 2b 41 6c 74 2b 44 65 6c 20 74 6f | Ctrl+Alt+Del to|
000001e0 20 72 65 73 74 61 72 74 0d 0a 00 00 00 00 00 00 | restart........|
000001f0 00 00 00 00 00 00 00 00 83 a0 b3 c9 00 00 55 aa |..............U.|
00000200
This looks standard, as expected. What OS X version did you upgrade from? There are a couple of new devices created by newer versions of OS X, which can cause a BSoD. Do you recall the details of the BSoD? You may need Windows Startup Repair using your original XP Installer or XP SP3 DVD.
My Mac originally had an OS X version 10.6.8. Only recently did I update it to version 10.11.1
The BSoD says something along of the lines of:
"A problem has been detected and windows has been shut down to prevent damage to your computer
UNMOUNTABLE_BOOT_VOLUME"
&
"Technical Information:
***STOP:0x000000ED (0x8A55f030, 0xC000014F, 0x00000000, 0x00000000)"
Since the problem seems to be a corrupted file(s) , could this technically work?
"1. Insert your XP installation disc into an optical drive and boot up your computer.
2. When you see a welcome screen, hit the R key on your keyboard. This will enter you into recovery mode with a DOS prompt.
3. Now type chkdsk /p and hit Enter. This will launch a utility which will check for errors on your hard drive.
4. After the process is done, type fixboot and hit Enter to repair any damaged boot files which may have become corrupted. When asked to say yes or no, type the Y key on your keyboard.
5. Type exit and press the Enter key to reboot your computer."
With slight modifications, yes. Insert your WXP Installation disk (XP SP3 is preferred). In System Preferences -> Startup Disk click on your BC Windows (not the CD/DVD with WXP Installer) and click on Restart. It should boot from the Optical drive and then you can run the steps 2-5.
Booted up the Windows XP disk and did everything said in the directions. the chkdsk /p revealed that there were some errors so I typed fixboot. It then said everything was repaired. Restarted the computer and tried loading Windows, but it still gave me the UNMOUNTABLE_BOOT_VOLUME BSoD.
Any other solutions to fixing this issue?
Can you see files in the BC/WXP volume from the OS X side in Finder?
I can see all the files in the WXP Installation Disk in Mac OS X Finder
Windows Crashes Upon Loading
