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 4 of 9 last Next

  • by Loner T,

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

    If you reboot your Mac and use Alt/Option, can you boot into Windows. Tuxera will interfere with Apple's System Preferences -> Startup Disk. if Windows boots, you should be able to switch back to OSX using the Control Panel -> Bootcamp menu.

  • by Moschtermeedchen,

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

    I can't boot into Windows. It gives me a black screen saying that there has been an error starting windows. It suggests a hardware or software change as cause and recommends inserting the windows installation disk and choosing system repair. Status: 0x000000e, Info: Access to required device not possible.

  • by Loner T,

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

    Tuxera is known to cause file system issues. You will need Startup Repair using the Windows installer. Your Mac supports creating a USB Installer using BC Assistant and an ISO or a DVD.

     

    Please see Install Windows 7 and earlier on your Mac using Boot Camp - Apple Support and specifically, step 11.

  • by Moschtermeedchen,

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

    Should i uninstall Tuxera? Also, do I now have to reinstall Windows from scratch again?

  • by Loner T,

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

    Yes, uninstall it and test. You may only need startup repair, not a full re-installation.

  • by Moschtermeedchen,

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

    After step 11 what shall I do? My BC assistant only shows me the option to remove Windows 7 so I can't continue with the further steps described in the link.

    It's currently close to 1 AM where I live. I really need to go to sleep so I'll probably be able to continue in about 9 hours.

  • by Loner T,

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

    Assuming you have a 2012 MBP, the first two options will let you create a USB installer. You do not need to use Remove (the last option). After step 11, your now have a USB Installer.

     

    You can connect the USB Installer, reboot and hold Alt/Option key, and select the Windows icon from the USB in boot manager, and once the Installer screen shows, look at the bottom left corner, you should have a Repair option.

     

    The sequence should look similar to the photo album at http://imgur.com/a/1DaOE#0 . There is also a command line utility called bootrec.exe which is documented in https://support.microsoft.com/en-us/kb/927392 . You should first try the /rebuildBCD, if Startup Repair does not fix the issue.

     

    Post back when you are ready and we can go further.

  • by Moschtermeedchen,

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

    I selected the USB installer and got a different Windows installation screen than the one in the imgur-link. When I click "continue" I get no option menu with "repair your computer" link, instead it already asks me to choose the OS to be installed. I only get the screen with the "repair your computer" option when I insert the Windows 7 installation disc.

  • by Loner T,

    Loner T Loner T Aug 13, 2016 5:54 AM in response to Moschtermeedchen
    Level 7 (23,898 points)
    Safari
    Aug 13, 2016 5:54 AM in response to Moschtermeedchen

    If you can see all your Windows files, in OSX Finder, please copy them to an external disk for safety.

     

    Insert the installation disc and reboot and choose the Windows icon from the installation disc. Run chkdsk on C:, and try and repair. If it does not fix the problem, switch to command line prompt, run bootrec.exe /rebuildBCD on C: (not your installation disc, because you will get an error). You may also need to run fixboot and fixmbr .

  • by Moschtermeedchen,

    Moschtermeedchen Moschtermeedchen Aug 13, 2016 7:42 AM in response to Loner T
    Level 1 (8 points)
    Windows Software
    Aug 13, 2016 7:42 AM in response to Loner T

    I ran chkdsk /F on C: . It tells me that the filesystem is NTFS, that the current volume can't be locked and that the F command can't be executed as the volume is write-protected. Is that a problem?

  • by Loner T,

    Loner T Loner T Aug 13, 2016 7:47 AM in response to Moschtermeedchen
    Level 7 (23,898 points)
    Safari
    Aug 13, 2016 7:47 AM in response to Moschtermeedchen

    Run diskpart.exe (https://technet.microsoft.com/en-us/library/cc766465%28v=ws.10%29.aspx?f=255&MSP PError=-2147217396) and use the attributes command as shown to clear the read-only attribute on C:. If you accidentally try to run chkdsk on the installation disk, it will give you an error.

     

    attributes

    attributes volume[{set | clear}] [{hidden | readonly| nodefaultdriveletter | shadowcopy}] [noerr]

    volume

    Displays the attributes of the selected volume.

    set

    Sets the specified attribute (hidden, read-only, nodefaultdriveletter, or shadowcopy volume) on the selected volume.

    clear

    Clears the specified attribute (hidden, read-only, nodefaultdriveletter, or shadowcopy volume) from the selected volume.

    hidden

    Specifies that the volume is hidden.

    readonly

    Specifies that the volume is read-only.

    nodefaultdriveletter

    Specifies that the volume does not receive a drive letter by default.

    shadowcopy

    Specifies that the volume is a shadow copy volume.

    noerr

    For scripting only. When an error is encountered, DiskPart continues to process commands as if the error did not occur. Without the noerr parameter, an error causes DiskPart to exit with an error code.

  • by Moschtermeedchen,

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

    I cleared the read-only on C: , ran chkdsk C: /F and can now successfully boot into Windows again.

  • by Loner T,

    Loner T Loner T Aug 13, 2016 9:34 AM in response to Moschtermeedchen
    Level 7 (23,898 points)
    Safari
    Aug 13, 2016 9:34 AM in response to Moschtermeedchen

    The remaining step is to absorb the free space after Recovery HD into Windows. Can you use http://www.howtogeek.com/howto/windows-vista/using-gparted-to-resize-your-window s-vista-partition/ as a reference and extend your Windows partition. Unfortunately, you will need Startup Repair and chkdsk again and will have to recreate the MBR as you did earlier in step 3.

     

    Once you have completed that, create new backups of OSX and Windows and create a Windows System Restore point.

  • by Moschtermeedchen,

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

    Just to make sure I don't mess anything up:

    1. Use Gparted and resize the partition

    2. Use the Windows installation DVD to get into the system repair options and use the chkdsk C: /f command.

    3. Boot into Mac partition and use gdisk dev/rdisk0 command to rewrite MBR (like in your post from August 12, 10:28 PM, right?)

    4. Boot into Windows to check if everything works.

    5. Create new backups of OS X and Windows and create a Windows Restore Point.

    I'm a bit stressed out by all of this, so I just want to be sure I do all the steps in the right order. Thank you for your patience with me!

  • by Loner T,

    Loner T Loner T Aug 13, 2016 10:59 AM in response to Moschtermeedchen
    Level 7 (23,898 points)
    Safari
    Aug 13, 2016 10:59 AM in response to Moschtermeedchen

    In step 2, you may also need bootrec /fixmbr and /fixboot. Otherwise the steps are correct.

first Previous Page 4 of 9 last Next