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,633 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 9 of 9

  • by Loner T,

    Loner T Loner T Aug 15, 2016 7:43 AM in response to Moschtermeedchen
    Level 7 (23,633 points)
    Safari
    Aug 15, 2016 7:43 AM in response to Moschtermeedchen

    If both OSes work properly, and you can switch between the two without any issues, then the partitions are working as defined. On the Windows side, check if you can see the Macintosh HD partition and on the OSX side, you should be able to see files in the Windows volume.

     

    If that is working, then we do not need to do anything more.

  • by Moschtermeedchen,

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

    I enabled AppleHfs.sys and AppleMNT.sys again and I don't get the blue screen anymore and I can see the Mac partition and even its recovery partition in the Windows "computer" menu. Everything's working well!

    Thank you very very much for your help and most of all for your patience! Your amazing knowledge was such a comfort for me, considering that I was running out of helpful advice and it seemed that I would be stuck with a screwed up Windows partition. While other sources would suggest surface solutions, you were willing to get to the core of the problem. Thank you for that!

     

    PS: As a last request, could you maybe write a reply where you sum up the solution to my problem, so that I can mark it with the "This solved my question" so that it shows up right at the beginning of the thread? That would be great!

  • by Loner T,Solvedanswer

    Loner T Loner T Aug 15, 2016 3:01 PM in response to Moschtermeedchen
    Level 7 (23,633 points)
    Safari
    Aug 15, 2016 3:01 PM in response to Moschtermeedchen

    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.

  • by Moschtermeedchen,

    Moschtermeedchen Moschtermeedchen Aug 16, 2016 1:46 AM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 16, 2016 1:46 AM in response to Loner T

    I really hate to come back to this, but this morning I booted into the Mac partition to set Bootcamp as startup disk and it doesn't show up in the window. Everything else works fine, I can choose bootcamp partition when I start the computer and I can boot it without problems and everything works. The only thing now is that whenever I start the computer I have to push the alt-key to choose the windows partition.

  • by Loner T,

    Loner T Loner T Aug 16, 2016 4:04 AM in response to Moschtermeedchen
    Level 7 (23,633 points)
    Safari
    Aug 16, 2016 4:04 AM in response to Moschtermeedchen

    Did you install any third-party NTFS software on the OS X side?

  • by Moschtermeedchen,

    Moschtermeedchen Moschtermeedchen Aug 16, 2016 4:08 AM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 16, 2016 4:08 AM in response to Loner T

    No, I uninstalled Tuxera after you told me about its problems and other than that I only have the default programs that come with Mac.

  • by Loner T,

    Loner T Loner T Aug 16, 2016 4:16 AM in response to Moschtermeedchen
    Level 7 (23,633 points)
    Safari
    Aug 16, 2016 4:16 AM in response to Moschtermeedchen

    You may still have remnants of Tuxera. For example, please see Re: Re: Unable to mount Bootcamp in Finder after Yosemite update . You may need to check if Tuxera has file cleanup instructions. The other option is to re-install OS X,which does not modify non-OS files. I suggest a good backup of OS X and Windows, before you you proceed further.

  • by Moschtermeedchen,

    Moschtermeedchen Moschtermeedchen Aug 16, 2016 4:32 AM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 16, 2016 4:32 AM in response to Loner T

    You were right about Tuxera. I had to uninstall it from the System Preference pane. After I uninstalled it, OS X found the bootcamp partition again and I could choose it as my startup disk. Now everything's fine Thank you!

  • by Loner T,

    Loner T Loner T Aug 16, 2016 4:51 AM in response to Moschtermeedchen
    Level 7 (23,633 points)
    Safari
    Aug 16, 2016 4:51 AM in response to Moschtermeedchen

    Excellent. Please post back if you run into any issues.

first Previous Page 9 of 9