Share via

Windows 7 SP1 crashes with blue screen and error code 0x00000034 after restoring system with system repair disc and system image

Anonymous
2016-08-10T16:22:37+00:00

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 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 and I can only run it in safe mode which means that I can neither download nor install updates 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 complete analysis of the dmp file for further details:

Microsoft (R) Windows Debugger Version 10.0.14321.1024 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Jim\Desktop\Minidump\080916-32807-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*

Executable search path is:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7601.23455.amd64fre.win7sp1_ldr.160516-0600

Machine Name:

Kernel base = 0xfffff80003058000 PsLoadedModuleList = 0xfffff8000329a730

Debug session time: Tue Aug  9 20:36:38.754 2016 (UTC + 2:00)

System Uptime: 0 days 0:01:37.628

Loading Kernel Symbols

.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.

Run !sym noisy before .reload to track down problems loading symbols.

..............................................................

................................................................

.......................................................

Loading User Symbols

Loading unloaded module list

...

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 34, {107, ffffffffc0000420, 0, 0}

*** WARNING: Unable to verify timestamp for AppleHFS.sys

*** ERROR: Module load completed but symbols could not be loaded for AppleHFS.sys

Probably caused by : AppleHFS.sys ( AppleHFS+7f65 )

Followup:     MachineOwner


2: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

CACHE_MANAGER (34)

    See the comment for FAT_FILE_SYSTEM (0x23)

Arguments:

Arg1: 0000000000000107

Arg2: ffffffffc0000420

Arg3: 0000000000000000

Arg4: 0000000000000000

Debugging Details:


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  7601.23455.amd64fre.win7sp1_ldr.160516-0600

SYSTEM_MANUFACTURER:  Apple Inc.

SYSTEM_PRODUCT_NAME:  MacBookPro9,2

SYSTEM_SKU:  System SKU#

SYSTEM_VERSION:  1.0

BIOS_VENDOR:  Apple Inc.

BIOS_VERSION:  MBP91.88Z.00D3.B0D.1602221713

BIOS_DATE:  02/22/2016

BASEBOARD_MANUFACTURER:  Apple Inc.

BASEBOARD_PRODUCT:  Mac-6F01561E16C75D06

BASEBOARD_VERSION:  MacBookPro9,2

DUMP_TYPE:  2

BUGCHECK_P1: 107

BUGCHECK_P2: ffffffffc0000420

BUGCHECK_P3: 0

BUGCHECK_P4: 0

EXCEPTION_RECORD:  ffffffffc0000420 -- (.exr 0xffffffffc0000420)

Cannot read Exception record @ ffffffffc0000420

CPU_COUNT: 4

CPU_MHZ: 9be

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: 1B'00000000 (cache) 15'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x34

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  BESITZER-PC

ANALYSIS_SESSION_TIME:  08-10-2016 14:03:23.0711

ANALYSIS_VERSION: 10.0.14321.1024 x86fre

LAST_CONTROL_TRANSFER:  from fffff80003145d68 to fffff800030c7400

STACK_TEXT:  

fffff8800716ba38 fffff80003145d68 : 0000000000000034 0000000000000107 ffffffffc0000420 0000000000000000 : nt!KeBugCheckEx

fffff8800716ba40 fffff800033e12da : 0000000000000000 fffff8800716bbb8 fffffa800000d5c0 0000000000000000 : nt! ?? ::FNODOBFM::`string'+0x3e378

fffff8800716bb00 fffff88001233f65 : 0000000000000000 00000000c8f5c8c0 fffffa800000d5c0 000000000000d5c0 : nt!CcPinRead+0xde

fffff8800716bbb0 0000000000000000 : 00000000c8f5c8c0 fffffa800000d5c0 000000000000d5c0 fffff8800716bc00 : AppleHFS+0x7f65

STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  732095016dd40618beb04c0763f6dfd8e00cafff

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  8fa19faf9b9093bdbcf2d77fa09d70b43ae1a965

THREAD_SHA1_HASH_MOD:  0a20901097feea01d5c41ea080af0faf30329ef6

FOLLOWUP_IP:

AppleHFS+7f65

fffff880`01233f65 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  AppleHFS+7f65

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AppleHFS

IMAGE_NAME:  AppleHFS.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f287d19

FAILURE_BUCKET_ID:  X64_0x34_AppleHFS+7f65

BUCKET_ID:  X64_0x34_AppleHFS+7f65

PRIMARY_PROBLEM_CLASS:  X64_0x34_AppleHFS+7f65

TARGET_TIME:  2016-08-09T18:36:38.000Z

OSBUILD:  7601

OSSERVICEPACK:  1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-05-16 23:17:48

BUILDDATESTAMP_STR:  160516-0600

BUILDLAB_STR:  win7sp1_ldr

BUILDOSVER_STR:  6.1.7601.23455.amd64fre.win7sp1_ldr.160516-0600

ANALYSIS_SESSION_ELAPSED_TIME: f23

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x34_applehfs+7f65

FAILURE_ID_HASH:  {41ae3f49-a7e9-25ef-caf4-de94004e5e06}

Followup:     MachineOwner

Many thanks in advance for your help

Jim Dengler

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

4 answers

Sort by: Most helpful
  1. Anonymous
    2016-08-12T10:44:55+00:00

    Hi Richard,

    perhaps the message translation in bullet 3 was not as conclusive as it should have been. In German it referred clearly to the installation disc and errors on that media. Removing the present installation, Boot Camp and Windows, and restoring again Boot Camp, Windows 7 system with installation disc, Boot Camp updates, system image etc would be now the 3rd time and I am quite sure we would end up with the same results.

    Based on the analysis of the dmp-file from the first and later-on from subsequent crashes, which always showed the same results, we followed another thread which led us to a solution in Apple Communities posted by David 888888 on March 22 2011 https://discussions.apple.com/thread/2780698?start=0&tstart=0 :

    "I was getting the BSOD when rebooting into Boot Camp 3.1 after attempting to update Windows 7 64-bit security patches in Windows Update. I found a solution that was posted by an IT Consultant. The problem is with the Apple system drivers for mounting HFS volumes. These files are AppleHFS.sys and AppleMNT.sys. Apple needs to fix these drivers to resolve the BSOD issues. In the meantime, here is what you can do to fix the problem:

    1. Boot into Windows Safe Mode (at black screen before startup continue to press F2, then press F8 for safe mode)
    2. Navigate to c:\windows\system32\drivers\
    3. Rename AppleHFS.sys to AppleHFS.sys.BACKUP
    4. Rename AppleMNT.sys to AppleMNT.sys.BACKUP
    5. Reboot into normal Windows mode

    You may notice after rebooting that Windows will no longer mount your HFS OS X volumes because these HFS system drivers are now disabled. One solution is to install MacDrive which does a better job than Apple's driver at mounting HFS volumes."

    We renamed both files in our system and our problem was solved. The only drawback is that Windows does not recognize the mac partition and an exchange of files is no more possible, however this does not hamper us.

    You will notice that in the Apple Communities discussions older Boot Camp partitions, 3.1 and 3.2, are quoted where 3.2 brought the solution. We are running now BC 5.1.5621 and the same bug seems to reappear. In our former installation we ran an older BC version which did not provoke the discussed issue.

    We sort of destroyed that installation by trying to reduce the size of the mac partition to get more space for Windows. We did this with Mac disc utilities. After reduction, a new partition was created from that space and Windows disappeared and was not recoverable again. We had to repartition the whole internal disc and reinstall everything which led in the Windows part to our above named problem.

    Last but not least, every body should be aware, that when you install a Windows partition you have to be careful in allotting space, because you will not be able to change the distribution afterwards without deinstalling Boot Camp/Windows, repartition your hard disc and reinstall Boot Camp/Windows again.

    For us we consider our problem as solved. Many thanks for your time and suggestions.

    All the best

    Jim Dengler

    0 comments No comments
  2. Anonymous
    2016-08-12T01:29:49+00:00

    Hi Jean,

    Based on the third bullet, there are some files and components that is corrupted. I strongly suggest that you back up all your files and clear re-install your operating system.

    Please make sure to not interrupt the installation. Remove your internet connections during the process.  Please put it back as soon as the installation is complete.

    Thank  you,

    Richard Tie

    0 comments No comments
  3. Anonymous
    2016-08-11T10:19:52+00:00

    Hi Richard,

    thank you for your answer.

    We tried all 3 methods listed in that post you linked to:

    • in method 1 computer found no errors
    • in method 2 with >bootrec /rebuildBcd we got the message: "Total number of identified Windows installations: 0"
    • in method 3 we got this message (translated from German with Google Translate): "On the data media is not a recognized file system.Make sure that all required file system drivers are loaded and that the volume is not corrupted."

    We used the original Windows 7 SP1 installation disc.

    The all-over situation has not improved, so any further help would be appreciated.

    Many thanks in advance

    Jim Dengler

    0 comments No comments
  4. Anonymous
    2016-08-11T04:41:33+00:00

    Hi Jean,

    Here's a link to resolve this issue, follow the post of Andre Da Costa: http://answers.microsoft.com/en-us/windows/forum/all/error-code-0x0000034-in-windows-7/4dcb8d38-a206-40ed-bced-55e4a4de9bf2

    Thank you,

    Richard Tie

    0 comments No comments