Moschtermeedchen
Level 1 (8 points)
Windows Software

Q: Boot camp Win 7 0x34 blue screen when starting windows after restore with system image.

The hard disc on the Macbook pro had been repartioned, all boot camp and other drivers updated and Windows installed from the installation DVD. All available Windows updates from 2012 (installation disc is from 2012) until today were installed and Boot camp 5.1 with all its drivers installed. Restoring was started with a system repair disc and system image from an external hard disc. Once Windows loads after the log-in screen, it crashes. A blue screen appears with the error code 0x00000034 and mentioning cache_manager.... Windows restarts itself and I can only use it in safe mode which means that I can neither download nor install upgrades or programs.

Analysing the dmp-file from the first crash with Windows Debugger Tool showed that the problem seems to lie with

AppleHFS.sys and svchost.exe, with Bug Check 34 {107, ffffffffc0000420,0,0}.

 

 

 

Here is the link to the complete analysis of the dmp file for further details:

https://1drv.ms/u/s!AuzUtP_j9nLagwWWqWUTre4qNYmu

 

Many thanks in advance for your help

Moschtermeedchen

MacBook Pro (13-inch Mid 2012), OS X El Capitan (10.11.6), blue screen 0x34

Posted on Aug 11, 2016 1:20 AM

by Loner T,Solvedanswer
Loner T Loner T
Level 7 (23,898 points)
Safari
A:

A Windows System Image restore on a Mac is tricky. In your specific case, the restore created entries which were appropriate for the original size of System Image (297GB), but the underlying partition was 400GB. Since the image was legacy BIOS/MBR mode, which is on page 2. You can see two entries for index 2 and 3, each. AppleHFS.sys should show you entry GPT 2 (start sector 409640), but the System Image has the same entry at start sector 195523144. This causes AppleHFS.sys to bug check and cause the BSoD. There is no device at the start sector 195523144. This causes an endless BSoD loop unless AppleHFS.sys is disabled.

 

We did two fixes.

 

1. Removed the spurious entries 2 and 3 at start sector 195523144 and start sector 389081512. The GPT was rebuilt leaving Free Space between 195523144 and 390352896 (this is the 'missing' 103 GB).

2. After GPT was corrected, trying to repair the original 297GB system image caused the BCD to be renamed as BCD.old. We restored bcd.old to BCD, repaired the original installation and used GParted to coalesce the 297 and 103 GB parts. This required a second repair, reusing the bcd.old. Once Windows was working and GPT was corrected, we rebuilt the MBR to match. Since there are no more spurious entries for GPT2 and GPT3, AppleHFS.sys/AppleMNT.sys now correctly map the partitions and show them on the Windows side.

 

You should create a new System Image backup of this 400GB Windows and discard the old 297GB System Image.

Posted on Aug 15, 2016 3:01 PM

Close
Moschtermeedchen

Q: Boot camp Win 7 0x34 blue screen when starting windows after restore with system image.

  • All replies
  • Helpful answers

first Previous Page 3 of 9 last Next

  • by Moschtermeedchen,

    Moschtermeedchen Moschtermeedchen Aug 12, 2016 11:18 AM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 12, 2016 11:18 AM in response to Loner T

    Here is the screenshot:

    Screen Shot 2016-08-12 at 20.17.44.png

  • by Loner T,

    Loner T Loner T Aug 12, 2016 11:27 AM in response to Moschtermeedchen
    Level 7 (23,898 points)
    Safari
    Aug 12, 2016 11:27 AM in response to Moschtermeedchen

    Please continue the write and confirm. Post the output of

     

    sudo gpt -vv -r show /dev/disk0

  • by Moschtermeedchen,

    Moschtermeedchen Moschtermeedchen Aug 12, 2016 11:37 AM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 12, 2016 11:37 AM in response to Loner T

    Here is the screenshot:

    Screen Shot 2016-08-12 at 20.35.07.png

  • by Loner T,

    Loner T Loner T Aug 12, 2016 12:03 PM in response to Moschtermeedchen
    Level 7 (23,898 points)
    Safari
    Aug 12, 2016 12:03 PM in response to Moschtermeedchen

    Your disk is an MBR disk. Interesting. We may need to rebuild a new GPT. Are you comfortable building a new GPT?

  • by Moschtermeedchen,

    Moschtermeedchen Moschtermeedchen Aug 12, 2016 12:07 PM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 12, 2016 12:07 PM in response to Loner T

    I'm not sure. What kind of consequences are involved/is it risky/difficult?

  • by Loner T,

    Loner T Loner T Aug 12, 2016 12:15 PM in response to Moschtermeedchen
    Level 7 (23,898 points)
    Safari
    Aug 12, 2016 12:15 PM in response to Moschtermeedchen

    We need to use Gdisk, and use the same values, but it will remove the spurious MBR entries and give you a cleaner view of the disk. We are not modifying any data content.

  • by Moschtermeedchen,

    Moschtermeedchen Moschtermeedchen Aug 12, 2016 12:18 PM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 12, 2016 12:18 PM in response to Loner T

    Okay, I'm up for it!

  • by Loner T,

    Loner T Loner T Aug 12, 2016 12:28 PM in response to Moschtermeedchen
    Level 7 (23,898 points)
    Safari
    Aug 12, 2016 12:28 PM in response to Moschtermeedchen

    The commands have explanations in parentheses that do not need to be typed, they are explanations. Please verify values that I took from your previous screen shot.

     

    sudo gdisk /dev/disk0

    p

    o (create a new GPT)

    x (Experts Menu)

    l (letter "L" - sets sector alignment)

    1 (digit 1 - alignment is one sector)

    m (Main menu)

    n

    1

    40

    +409600

    EF00

    n

    2

    409640

    +193843968

    AF00

    n

    3

    194253608

    +1269536

    AB00

    n

    4

    390352896

    +586420224

    0700

    p

    w (Wait here)

    y (not yet)

     

    Post a screen shot.

  • by Moschtermeedchen,

    Moschtermeedchen Moschtermeedchen Aug 12, 2016 12:38 PM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 12, 2016 12:38 PM in response to Loner T

    Here is the screenshot:

    Screen Shot 2016-08-12 at 21.37.29.png

  • by Loner T,

    Loner T Loner T Aug 12, 2016 12:46 PM in response to Moschtermeedchen
    Level 7 (23,898 points)
    Safari
    Aug 12, 2016 12:46 PM in response to Moschtermeedchen

    Looks clean. Please write and confirm. Reboot and check if you can boot OSX and Windows.

  • by Moschtermeedchen,

    Moschtermeedchen Moschtermeedchen Aug 12, 2016 12:58 PM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 12, 2016 12:58 PM in response to Loner T

    When I restarted I couldn't choose the Boot camp partition, and it doesn't show up in the disk utility.

    Here's a screenshot with the sudo gdisk /dev/disk0 and sudo gpt -vv -r show /dev/disk0 command:

    Screen Shot 2016-08-12 at 21.58.01.png

  • by Loner T,

    Loner T Loner T Aug 12, 2016 1:05 PM in response to Moschtermeedchen
    Level 7 (23,898 points)
    Safari
    Aug 12, 2016 1:05 PM in response to Moschtermeedchen

    Can you exit out of Gdisk and run the GPT command in the terminal?

     

    Please also post the output of sudo fdisk /dev/disk0 .

  • by Moschtermeedchen,

    Moschtermeedchen Moschtermeedchen Aug 12, 2016 1:12 PM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 12, 2016 1:12 PM in response to Loner T

    Here is the gpt command screenshot:

    Screen Shot 2016-08-12 at 22.09.38.png

    Here is the fdisk command screenshot:

    Screen Shot 2016-08-12 at 22.11.13.png

  • by Loner T,

    Loner T Loner T Aug 12, 2016 1:28 PM in response to Moschtermeedchen
    Level 7 (23,898 points)
    Safari
    Aug 12, 2016 1:28 PM in response to Moschtermeedchen

    This looks correct. We need to rebuild the MBR for Windows to work.

     

    Rebuild MBR to match the new GPT information thus resetting the Hybrid MBR. Use defaults for other questions (like partition codes). The only values that need modifications are the Boot flags and step 10. Accept all other defaults that Gdisk offers. Please see the sample Q&A as an example. These steps can be repeated if you make a mistake before you get to Step 12, otherwise start from Step 1 for these steps. Step 6 has numbers which are typed with a space between the numbers. Please see the sample Q&A before you execute these steps.

    1. Sudo gdisk /dev/rdisk0
    2. P  (Print list of parts)
    3. R  (Recover)
    4. O (print current Hybrid MBR)
    5. H (chooses Hybrid)
    6. Partitions numbers to be hybridized: 2 3 4
    7. Y  (Good for GRUB question)
    8. N  (part 2 boot flag)
    9. N  (part 3 boot flag)
    10. Y  (part 4 boot flag make NTFS bootable partition)
    11. O  (print current Hybrid MBR)
    12. W (Write the new MBR)
    13. Y (Yes! write the new MBR)
    14. Reboot

     

    Here is sample Q&A for this section. Please notice the Press Enter/Return.

     

    Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): Y

     

    Creating entry for GPT partition #2 (MBR partition #2)

    Enter an MBR hex code (default AF): Press Enter/Return

    Set the bootable flag? (Y/N): N

     

    Creating entry for GPT partition #3 (MBR partition #3)

    Enter an MBR hex code (default AB): Press Enter/Return

    Set the bootable flag? (Y/N): N

     

    Creating entry for GPT partition #4 (MBR partition #4)

    Enter an MBR hex code (default 07): Press Enter/Return

    Set the bootable flag? (Y/N): Y

     

    Test 1 - Does Bootcamp Volume show up in Finder?

    Test 2 - Can you see files in Bootcamp Volume?

    Test 3 - Can you select Bootcamp in System Preferences -> Startup Disk?

    Test 4 - If Test 3 is successful, select Bootcamp and Click Restart.

  • by Moschtermeedchen,

    Moschtermeedchen Moschtermeedchen Aug 12, 2016 1:44 PM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 12, 2016 1:44 PM in response to Loner T

    I did all the steps and rebooted, here are the test results:

    Test 1: Yes, it shows up in Finder.

    Test 2: Yes, I can see files (as an aside, I have installed Tuxera, so I don't know if it is because of that program or not).

    Test 3: No, I cannot select Bootcamp as startup disk. However, Bootcamp shows up at the start screen for choosing partitions.

first Previous Page 3 of 9 last Next