locked
BSOD, something.dll, happened many times RRS feed

  • Question

  • I got a few BSOD recently but not sure how to read the dump files.  Could someone please download from the link below and have a look at the dump files and tell me why I got BSOD?  Your kind assistance will be greatly appreciated.

    http://www.mediafire.com/myfiles.php

    Thank you,

    Vincent
    Saturday, December 18, 2010 5:20 AM

Answers

  • Hi,

     

    It seems that your Windows 7 have a startup issue now, to fix it, I suggest you use Windows 7 installation disk to repair:

     

    Note: Please ensure that the DVD-ROM is the first booting device.

     

    1.    Please insert the Windows 7 DVD and reboot the computer.

    2.    When we are prompted to press a key to boot from the DVD, please press Enter or the space bar.

    3.    Choose your language settings, and then click Next.

    4.    Click Repair your computer.

    5.    Select the operating system you want to repair, and then click Next.

    6.    On the System Recovery Options menu, click Startup Repair. Startup Repair might prompt you to make choices as it tries to fix the problem, and if necessary, it might restart your computer as it makes repairs.

     

    If Startup Repair still fails, please use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windows Vista or Windows 7.

     

    Hope it helps.

     

    Alex Zhao


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Cloud_TS Monday, December 27, 2010 1:36 AM
    Wednesday, December 22, 2010 10:15 AM

All replies

  • It doesn't look like you quite have the link correct for your files, can
    you upload to skydrive instead and post a link:
     
     

    -- Mike Burr
    MS Technologies - Development - *nix
    Saturday, December 18, 2010 5:27 AM
  • I just upload the dump files to skydrive.  Please download the file and take a look when you have a chance:

     

    http://cid-87a169526aaf5ecc.office.live.com/browse.aspx/.Documents

     

    Thank you Mike!

    -Vincent

    Saturday, December 18, 2010 6:00 AM
  • The most likely cause is AVG. I would try updating it to the latest
    version, if this doesn't fix it, then uninstall it and install something
    like Microsoft Security Essentials. Please post any further dumps that
    are generated after trying the above suggestion(s).
     
    0: kd>  !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
     
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffaa00abe7dd8, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff880014ed187, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000005, (reserved)
     
    Debugging Details:
    ------------------
     Could not read faulting driver name
     
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef30e0
     fffffaa00abe7dd8
     
    FAULTING_IP:
    Ntfs!NtfsFindPrefixHashEntry+762
    fffff880`014ed187 0fb78718020000  movzx   eax,word ptr [rdi+218h]
     
    MM_INTERNAL_CODE:  5
     
    CUSTOMER_CRASH_COUNT:  1
     
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
     
    BUGCHECK_STR:  0x50
     
    PROCESS_NAME:  AVGIDSAgent.ex
     
    CURRENT_IRQL:  0
     
    TRAP_FRAME:  fffff8800ac3ebb0 -- (.trap 0xfffff8800ac3ebb0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000000007e rbx=0000000000000000 rcx=0000000000000400
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880014ed187 rsp=fffff8800ac3ed40 rbp=fffff8a0001c9bc0
     r8=0000000012368a00  r9=0000000000000000 r10=0000000000000002
    r11=fffff8800ac3ed88 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    Ntfs!NtfsFindPrefixHashEntry+0x762:
    fffff880`014ed187 0fb78718020000  movzx   eax,word ptr [rdi+218h] ds:00000000`00000218=????
    Resetting default scope
     
    LAST_CONTROL_TRANSFER:  from fffff80002d3a8c1 to fffff80002cbb740
     
    STACK_TEXT:
    fffff880`0ac3ea48 fffff800`02d3a8c1 : 00000000`00000050 fffffaa0`0abe7dd8 00000000`00000000 fffff880`0ac3ebb0 : nt!KeBugCheckEx
    fffff880`0ac3ea50 fffff800`02cb982e : 00000000`00000000 fffff8a0`0aef8de0 fffff8a0`00b76100 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x40e8b
    fffff880`0ac3ebb0 fffff880`014ed187 : fffff880`0ac3f2f0 00000000`0000007c fffff8a0`001c9bc0 fffffa80`0b235060 : nt!KiPageFault+0x16e
    fffff880`0ac3ed40 fffff880`014edce2 : fffffa80`0db10270 fffffa80`07e95350 fffff8a0`001c9bc0 fffffa80`07eb8101 : Ntfs!NtfsFindPrefixHashEntry+0x762
    fffff880`0ac3ee70 fffff880`014e828d : fffffa80`0db10270 fffffa80`0ec6d940 fffff880`0ac3f050 fffff880`0ac3f098 : Ntfs!NtfsFindStartingNode+0x452
    fffff880`0ac3ef40 fffff880`01451c0d : fffffa80`0db10270 fffffa80`0ec6d940 fffff880`0ac3f2f0 fffff880`012a1000 : Ntfs!NtfsCommonCreate+0x3dd
    fffff880`0ac3f120 fffff800`02ccae5a : fffff880`0ac3f260 fffff880`012a032e fffffa80`0d698320 fffffa80`0d698320 : Ntfs!NtfsCommonCreateCallout+0x1d
    fffff880`0ac3f150 fffff880`01451b2f : fffff880`01451bf0 fffff880`0ac3f260 fffff880`00000000 fffff880`014f332d : nt!KeExpandKernelStackAndCalloutEx+0xda
    fffff880`0ac3f230 fffff880`014ee9c0 : 00000000`00000000 00000000`00000000 fffff880`0ac3f480 fffffa80`0ec6d940 : Ntfs!NtfsCommonCreateOnNewStack+0x4f
    fffff880`0ac3f290 fffff880`0129f23f : fffffa80`07e94030 fffffa80`0ec6d940 fffffa80`0ac37100 fffffa80`0b742da0 : Ntfs!NtfsFsdCreate+0x1b0
    fffff880`0ac3f440 fffff880`012be2b9 : fffffa80`0ec6d940 fffffa80`07eb8010 fffffa80`0ec6d900 fffffa80`08716de0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
    fffff880`0ac3f4d0 fffff880`083f155b : fffffa80`0d6982f0 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!FltpCreate+0x2a9
    fffff880`0ac3f580 fffffa80`0d6982f0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : AVGIDSFilter+0x555b
    fffff880`0ac3f588 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0ec6dd28 : 0xfffffa80`0d6982f0
     STACK_COMMAND:  kb
     
    FOLLOWUP_IP:
    AVGIDSFilter+555b
    fffff880`083f155b ??              ???
     
    SYMBOL_STACK_INDEX:  c
     
    SYMBOL_NAME:  AVGIDSFilter+555b
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: AVGIDSFilter
     
    IMAGE_NAME:  AVGIDSFilter.Sys
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c5896d9
     
    FAILURE_BUCKET_ID:  X64_0x50_AVGIDSFilter+555b
     
    BUCKET_ID:  X64_0x50_AVGIDSFilter+555b
     
    Followup: MachineOwner
    ---------
     
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
     
    Use !analyze -v to get detailed debugging information.
     
    BugCheck 34, {50830, fffff8800a88d468, fffff8800a88ccd0, fffff80002d77d15}
     
    Probably caused by : memory_corruption ( nt!MiLogPageAccess+e5 )
     
    Followup: MachineOwner
    ---------
     
    0: kd>  !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
     
    CACHE_MANAGER (34)
        See the comment for FAT_FILE_SYSTEM (0x23)
    Arguments:
    Arg1: 0000000000050830
    Arg2: fffff8800a88d468
    Arg3: fffff8800a88ccd0
    Arg4: fffff80002d77d15
     
    Debugging Details:
    ------------------
     EXCEPTION_RECORD:  fffff8800a88d468 -- (.exr 0xfffff8800a88d468)
    ExceptionAddress: fffff80002d77d15 (nt!MiLogPageAccess+0x00000000000000e5)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
     
    CONTEXT:  fffff8800a88ccd0 -- (.cxr 0xfffff8800a88ccd0)
    rax=0000000000000001 rbx=fffffa80123fb000 rcx=f8a00429dbf80000
    rdx=fffff6fcc03ec748 rsi=fffffa8001836920 rdi=fffff6fcc03ec748
    rip=fffff80002d77d15 rsp=fffff8800a88d6a0 rbp=0000000000000000
     r8=fffff9807d8e9001  r9=000000000000a24a r10=fffff780c0000488
    r11=fffff780c0000000 r12=fa800cb5585004c0 r13=0000000000000029
    r14=fffffa80123fbff8 r15=fffff8a00429dbf8
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    nt!MiLogPageAccess+0xe5:
    fffff800`02d77d15 410fba64243814  bt      dword ptr [r12+38h],14h ds:002b:fa800cb5`585004f8=????????
    Resetting default scope
     
    CUSTOMER_CRASH_COUNT:  1
     
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    CURRENT_IRQL:  0
     
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
     
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
     
    EXCEPTION_PARAMETER1:  0000000000000000
     
    EXCEPTION_PARAMETER2:  ffffffffffffffff
     
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ea90e0
     ffffffffffffffff
     
    FOLLOWUP_IP:
    nt!MiLogPageAccess+e5
    fffff800`02d77d15 410fba64243814  bt      dword ptr [r12+38h],14h
     
    FAULTING_IP:
    nt!MiLogPageAccess+e5
    fffff800`02d77d15 410fba64243814  bt      dword ptr [r12+38h],14h
     
    BUGCHECK_STR:  0x34
     
    LAST_CONTROL_TRANSFER:  from fffff80002c151ab to fffff80002d77d15
     
    STACK_TEXT:
    fffff880`0a88d6a0 fffff800`02c151ab : 00000003`00000000 00000000`0000a24a fffffa80`03321f90 fffff880`0a88d8c8 : nt!MiLogPageAccess+0xe5
    fffff880`0a88d6f0 fffff800`02f881b5 : fffff980`7d8e9000 fffff8a0`2cb76810 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2bee8
    fffff880`0a88d9d0 fffff800`02c8a567 : 00000000`00000000 fffffa80`0e1b1f80 00000000`00000000 00000000`000c0000 : nt!CcUnmapVacb+0x5d
    fffff880`0a88da10 fffff800`02c61274 : 00000000`00000001 fffffa80`09326070 fffffa80`130ab500 00000000`00000000 : nt!CcUnmapVacbArray+0x1b7
    fffff880`0a88daa0 fffff800`02c64d1c : fffffa80`130ab5c0 00000000`00000011 fffffa80`130ab5c0 fffff880`00000000 : nt!CcDeleteSharedCacheMap+0x140
    fffff880`0a88db10 fffff800`02c65520 : fffffa80`0d99f500 fffff880`0a88dc18 00000000`00000000 fffff880`00000000 : nt!CcWriteBehind+0x5bc
    fffff880`0a88dbc0 fffff800`02c7e961 : fffffa80`06d176d0 fffff800`02c65358 fffff800`02e78140 00000000`00000002 : nt!CcWorkerThread+0x1c8
    fffff880`0a88dc70 fffff800`02f15c06 : 00000000`00000000 fffffa80`0b537b60 00000000`00000080 fffffa80`06ca8b30 : nt!ExpWorkerThread+0x111
    fffff880`0a88dd00 fffff800`02c4fc26 : fffff800`02debe80 fffffa80`0b537b60 fffffa80`08a33040 00000000`00000202 : nt!PspSystemThreadStartup+0x5a
    fffff880`0a88dd40 00000000`00000000 : fffff880`0a88e000 fffff880`0a888000 fffff880`0a88cc40 00000000`00000000 : nt!KxStartSystemThread+0x16
     SYMBOL_STACK_INDEX:  0
     
    SYMBOL_NAME:  nt!MiLogPageAccess+e5
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: nt
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
     
    STACK_COMMAND:  .cxr 0xfffff8800a88ccd0 ; kb
     
    IMAGE_NAME:  memory_corruption
     
    FAILURE_BUCKET_ID:  X64_0x34_nt!MiLogPageAccess+e5
     
    BUCKET_ID:  X64_0x34_nt!MiLogPageAccess+e5
     
    Followup: MachineOwner
    ---------
     
    0: kd>  kv
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff880`0a88c498 fffff800`02d05b63 : 00000000`00000034 00000000`00050830 fffff880`0a88d468 fffff880`0a88ccd0 : nt!KeBugCheckEx
    fffff880`0a88c4a0 fffff800`02cc3c5d : fffffa80`1310b000 00000000`3966744e 00000000`00004000 fffff800`02e00880 : nt!CcDebugExceptionFilter+0x23
    fffff880`0a88c4e0 fffff800`02c9fd1c : fffff6fb`00000000 fffffa80`00000001 00000000`00000000 fffff880`0a88c6c0 : nt! ?? ::FNODOBFM::`string'+0x1b29
    fffff880`0a88c520 fffff800`02c9740d : fffff800`02dbd888 fffff880`0a88dbc0 00000000`00000000 fffff800`02c01000 : nt!_C_specific_handler+0x8c
    fffff880`0a88c590 fffff800`02c9ea90 : fffff800`02dbd888 fffff880`0a88c608 fffff880`0a88d468 fffff800`02c01000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`0a88c5c0 fffff800`02cab9ef : fffff880`0a88d468 fffff880`0a88ccd0 fffff880`00000000 fffff6fc`c03ec748 : nt!RtlDispatchException+0x410
    fffff880`0a88cca0 fffff800`02c70d82 : fffff880`0a88d468 fffffa80`123fb000 fffff880`0a88d510 fffffa80`01836920 : nt!KiDispatchException+0x16f
    fffff880`0a88d330 fffff800`02c6f68a : fffff800`02c6d576 fffff800`02c6d5e2 fffffa80`07ad3780 fffffa80`08dd1001 : nt!KiExceptionDispatch+0xc2
    fffff880`0a88d510 fffff800`02d77d15 : 00000000`00000000 fffffa80`123fb000 00000000`00000000 fffffa80`07e65010 : nt!KiGeneralProtectionFault+0x10a (TrapFrame @ fffff880`0a88d510)
    fffff880`0a88d6a0 fffff800`02c151ab : 00000003`00000000 00000000`0000a24a fffffa80`03321f90 fffff880`0a88d8c8 : nt!MiLogPageAccess+0xe5
    fffff880`0a88d6f0 fffff800`02f881b5 : fffff980`7d8e9000 fffff8a0`2cb76810 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2bee8
    fffff880`0a88d9d0 fffff800`02c8a567 : 00000000`00000000 fffffa80`0e1b1f80 00000000`00000000 00000000`000c0000 : nt!CcUnmapVacb+0x5d
    fffff880`0a88da10 fffff800`02c61274 : 00000000`00000001 fffffa80`09326070 fffffa80`130ab500 00000000`00000000 : nt!CcUnmapVacbArray+0x1b7
    fffff880`0a88daa0 fffff800`02c64d1c : fffffa80`130ab5c0 00000000`00000011 fffffa80`130ab5c0 fffff880`00000000 : nt!CcDeleteSharedCacheMap+0x140
    fffff880`0a88db10 fffff800`02c65520 : fffffa80`0d99f500 fffff880`0a88dc18 00000000`00000000 fffff880`00000000 : nt!CcWriteBehind+0x5bc
    fffff880`0a88dbc0 fffff800`02c7e961 : fffffa80`06d176d0 fffff800`02c65358 fffff800`02e78140 00000000`00000002 : nt!CcWorkerThread+0x1c8
    fffff880`0a88dc70 fffff800`02f15c06 : 00000000`00000000 fffffa80`0b537b60 00000000`00000080 fffffa80`06ca8b30 : nt!ExpWorkerThread+0x111
    fffff880`0a88dd00 fffff800`02c4fc26 : fffff800`02debe80 fffffa80`0b537b60 fffffa80`08a33040 00000000`00000202 : nt!PspSystemThreadStartup+0x5a
    fffff880`0a88dd40 00000000`00000000 : fffff880`0a88e000 fffff880`0a888000 fffff880`0a88cc40 00000000`00000000 : nt!KxStartSystemThread+0x16
    0: kd>  .trap fffff880`0a88d510
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=f8a00429dbf80000
    rdx=fffff6fcc03ec748 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002d77d15 rsp=fffff8800a88d6a0 rbp=0000000000000000
     r8=fffff9807d8e9001  r9=000000000000a24a r10=fffff780c0000488
    r11=fffff780c0000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!MiLogPageAccess+0xe5:
    fffff800`02d77d15 410fba64243814  bt      dword ptr [r12+38h],14h ds:0200:00000000`00000038=????????
    0: kd>  kv
      *** Stack trace for last set context - .thread/.cxr resets it
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff880`0a88d6a0 fffff800`02c151ab : 00000003`00000000 00000000`0000a24a fffffa80`03321f90 fffff880`0a88d8c8 : nt!MiLogPageAccess+0xe5
    fffff880`0a88d6f0 fffff800`02f881b5 : fffff980`7d8e9000 fffff8a0`2cb76810 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2bee8
    fffff880`0a88d9d0 fffff800`02c8a567 : 00000000`00000000 fffffa80`0e1b1f80 00000000`00000000 00000000`000c0000 : nt!CcUnmapVacb+0x5d
    fffff880`0a88da10 fffff800`02c61274 : 00000000`00000001 fffffa80`09326070 fffffa80`130ab500 00000000`00000000 : nt!CcUnmapVacbArray+0x1b7
    fffff880`0a88daa0 fffff800`02c64d1c : fffffa80`130ab5c0 00000000`00000011 fffffa80`130ab5c0 fffff880`00000000 : nt!CcDeleteSharedCacheMap+0x140
    fffff880`0a88db10 fffff800`02c65520 : fffffa80`0d99f500 fffff880`0a88dc18 00000000`00000000 fffff880`00000000 : nt!CcWriteBehind+0x5bc
    fffff880`0a88dbc0 fffff800`02c7e961 : fffffa80`06d176d0 fffff800`02c65358 fffff800`02e78140 00000000`00000002 : nt!CcWorkerThread+0x1c8
    fffff880`0a88dc70 fffff800`02f15c06 : 00000000`00000000 fffffa80`0b537b60 00000000`00000080 fffffa80`06ca8b30 : nt!ExpWorkerThread+0x111
    fffff880`0a88dd00 fffff800`02c4fc26 : fffff800`02debe80 fffffa80`0b537b60 fffffa80`08a33040 00000000`00000202 : nt!PspSystemThreadStartup+0x5a
    fffff880`0a88dd40 00000000`00000000 : fffff880`0a88e000 fffff880`0a888000 fffff880`0a88cc40 00000000`00000000 : nt!KxStartSystemThread+0x16
     

    -- Mike Burr
    MS Technologies - Development - *nix
    Saturday, December 18, 2010 7:00 AM
  • Hi Mike, I uninstalled AVG and switched to Microsoft Security Client instead.  So far I haven't had any BSOD and I hope that I won't have them any more.  However, I keep getting this error message from Microsoft Security Client:

    An error has occured in the program.  Try to open it again.  If this problem continues, you'll need to reinstall Microsoft Security Client.

    Error code:  0x8007064e

    I can't find MSC in control panel nor do I see it in the program folder.  How do I reinstall MSC?

    Sunday, December 19, 2010 8:44 AM
  • I assume that you are talking about Forefront Client Security? It shows for me as Microsoft Forefront Client Security Antimalware Service in Control Panel\Programs and Features. Based on the error code, it needs to be reinstalled or repaired:

    # as an HRESULT: Severity: FAILURE (1), Facility: 0x7, Code 0x64e
    # for hex 0x64e / decimal 1614 :
     ecInvWkstn                          ec.h
     ERROR_PRODUCT_UNINSTALLED                   winerror.h
    # Product is uninstalled.
    # 2 matches found for "8007064e"


    -- Mike Burr
    MS Technologies - Development - *nix
    Sunday, December 19, 2010 6:18 PM
  • You know what?  The I tried to reinstall MSC and it failed again.  Just like the first time, the installation freezed my computer for a long time then I got the same error message telling me the installation failed and that I need to restart and try again.  The computer freezed during the restart and now my computer wouldn't boot.  I tried to physically turn off my computer and turn it back on a few times, but the booting process always feezed at the staring windows icon.  What should I do now?
    Monday, December 20, 2010 12:49 AM
  • Hi,

     

     

    Could you Use Last Known Good Configuration to start Windows 7?

     

    I suggest you test this issue in Clean Boot Mode.

     

    If the issue persists, as for this system freezing issue, we generally need to analyze the performance monitor logs and memory dump files to locate the root cause. Unfortunately, debugging is beyond what we can do in the forum because of the nature of forum support. A support call to our product service team is needed for the debugging service. I'd like to recommend that you contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently. To obtain the phone numbers for specific technology request please take a look at the web site listed below:

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

     

    If you are outside the US please see http://support.microsoft.com for regional support phone numbers.

     

    Alex Zhao


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, December 21, 2010 10:37 AM
  • Hi Alex:

    Thank you for your suggestions.  I managed to get into windows and finished MSE installation.  I ran a memory check with the windows 7 installation disk and windows started right after the check was over.  However, now my computer won't boot unless I have the windows 7 installation disk in the DVD drive.  If I don't, I get this error message:

     

    DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER.

     

    What do I need to do to fix this problem?

    Tuesday, December 21, 2010 10:44 AM
  • Hi,

     

    It seems that your Windows 7 have a startup issue now, to fix it, I suggest you use Windows 7 installation disk to repair:

     

    Note: Please ensure that the DVD-ROM is the first booting device.

     

    1.    Please insert the Windows 7 DVD and reboot the computer.

    2.    When we are prompted to press a key to boot from the DVD, please press Enter or the space bar.

    3.    Choose your language settings, and then click Next.

    4.    Click Repair your computer.

    5.    Select the operating system you want to repair, and then click Next.

    6.    On the System Recovery Options menu, click Startup Repair. Startup Repair might prompt you to make choices as it tries to fix the problem, and if necessary, it might restart your computer as it makes repairs.

     

    If Startup Repair still fails, please use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windows Vista or Windows 7.

     

    Hope it helps.

     

    Alex Zhao


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Cloud_TS Monday, December 27, 2010 1:36 AM
    Wednesday, December 22, 2010 10:15 AM