none
求助: 电脑启动不了,如何解决 ? RRS feed

  • 问题

  • 我的电脑装的是VISTA sp1  系统,每次总要启动好几次才能进入windows ,机器总是蓝屏报错 ,而且每次各不一样,
    它有个特点,就是每次如果长时间不开机(过一晚上)的话 重启,就特别容易蓝屏 ,但是反复重启后,如果能正常进入系统的话。相对的蓝屏的机会就会少些。就是说,冷机器,错误多,热机器错误相对的少些。
    今天机器启动又是是蓝屏,如下:


    Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Complete Dump File: Full address space is available

    Symbol search path is: SRV*c:\temp*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
    Machine Name:
    Kernel base = 0x81c18000 PsLoadedModuleList = 0x81d2fc70
    Debug session time: Sun Feb 15 09:27:27.998 2009 (GMT+8)
    System Uptime: 0 days 0:00:20.779
    Loading Kernel Symbols
    ...............................................................
    ..............................................................
    Loading User Symbols
    ..............
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {c0527038, 0, 81ccd6fe, 9}

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: kernel32!pNlsUserInfo                         ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: kernel32!pNlsUserInfo                         ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : ksecdd.sys ( ksecdd!HashFirstUserModeCallerBlobs+7f )

    Followup: MachineOwner
    ---------

    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: c0527038, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 81ccd6fe, If non-zero, the instruction address which referenced the bad memory
     address.
    Arg4: 00000009, (reserved)

    Debugging Details:
    ------------------

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: kernel32!pNlsUserInfo                         ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: kernel32!pNlsUserInfo                         ***
    ***                                                                   ***
    *************************************************************************

    READ_ADDRESS:  c0527038

    FAULTING_IP:
    nt!memcpy+9e
    81ccd6fe 8a06            mov     al,byte ptr [esi]

    MM_INTERNAL_CODE:  9

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  csrss.exe

    CURRENT_IRQL:  0

    TRAP_FRAME:  89ca0ff4 -- (.trap 0xffffffff89ca0ff4)
    ErrCode = 00000000
    eax=00000002 ebx=80d2002e ecx=00004e46 edx=00000002 esi=c0527038 edi=80d2002e
    eip=81ccd6fe esp=89ca1068 ebp=89ca1070 iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    nt!memcpy+0x9e:
    81ccd6fe 8a06            mov     al,byte ptr [esi]          ds:0023:c0527038=??
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 81c72b54 to 81cbd0f5

    STACK_TEXT: 
    89ca0fdc 81c72b54 00000000 c0527038 00000000 nt!MmAccessFault+0x10a
    89ca0fdc 81ccd6fe 00000000 c0527038 00000000 nt!KiTrap0E+0xdc
    89ca1070 81e4275d 80d2002e c0527038 00004e48 nt!memcpy+0x9e
    89ca1108 81c6fa1a 00004e78 80d1b000 00004e78 nt!NtQueryDirectoryObject+0x28b
    89ca1108 81c6e175 00004e78 80d1b000 00004e78 nt!KiFastCallEntry+0x12a
    89ca119c 81dbfb16 8000037c 80d1b000 00004e78 nt!ZwQueryDirectoryObject+0x11
    89ca120c 81dbf54c 89ca1230 80cfb000 00000000 nt!IopGetLegacyVetoListDrivers+0xcb
    89ca1240 81d73e99 bb7cb51e 00020000 89ca16e0 nt!IoGetLegacyVetoList+0x4a
    89ca128c 81e50e27 89ca1614 bb7cb1a2 89ca1648 nt!ExpQueryLegacyDriverInformation+0x1e
    89ca1630 81c6fa1a 0000002b 80cfb000 00020000 nt!NtQuerySystemInformation+0x1ec9
    89ca1630 81c6e3b9 0000002b 80cfb000 00020000 nt!KiFastCallEntry+0x12a
    89ca16b8 8783e384 0000002b 80cfb000 00020000 nt!ZwQuerySystemInformation+0x11
    89ca1754 8783e638 87835f64 00000000 00000040 ksecdd!HashFirstUserModeCallerBlobs+0x7f
    89ca1aa8 8783d9af 00000000 00000000 89ca1ac8 ksecdd!GatherRandomKey+0x204
    89ca1b0c 8783da46 00000001 00000008 8783e0bd ksecdd!ScavengeOnce+0x2a
    89ca1b60 8783e0b4 8650bbc8 00000030 89ca1b98 ksecdd!RandlibSystemPrng+0x54
    89ca1b70 8783e0f9 89ca1b88 8650bbc8 00000030 ksecdd!NewGenRandomEx+0x1b
    89ca1b98 8783b105 00000000 00000000 8650bbc8 ksecdd!NewGenRandom+0x3c
    89ca1c00 8783b3a8 8650bbc8 00000000 8650bbc8 ksecdd!KsecDeviceControl+0x121
    89ca1c2c 81cd3fd3 847fab08 00000030 85e853c0 ksecdd!KsecDispatch+0xa6
    89ca1c44 81e64615 8650bc58 85e853c0 85e85430 nt!IofCallDriver+0x63
    89ca1c64 81e64dba 847fab08 8650bc58 0082f000 nt!IopSynchronousServiceTail+0x1d9
    89ca1d00 81e4ea8d 847fab08 85e853c0 00000000 nt!IopXxxControlFile+0x6b7
    89ca1d34 81c6fa1a 000000dc 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
    89ca1d34 77b09a94 000000dc 00000000 00000000 nt!KiFastCallEntry+0x12a
    0082ef68 77b08444 765ec2a3 000000dc 00000000 ntdll!KiFastSystemCallRet
    0082ef6c 765ec2a3 000000dc 00000000 00000000 ntdll!ZwDeviceIoControlFile+0xc
    0082efcc 7771476e 000000dc 00390008 00000000 KERNEL32!DeviceIoControl+0x14a
    0082f028 777119d7 00000000 00000000 0082f05c ADVAPI32!GatherRandomKeyFastUserMode+0xb5
    0082f090 77711959 0082f114 0082f0a4 0019b894 ADVAPI32!RandomFillBuffer+0x5b
    0082f0a8 77711926 0082f114 00000100 0082f0e0 ADVAPI32!SystemPrng+0x30
    0082f0b8 77711901 0082f0d0 0082f114 00000100 ADVAPI32!NewGenRandomEx+0x1b
    0082f0e0 777118d6 00000000 00000000 0082f114 ADVAPI32!NewGenRandom+0x3c
    0082f0f8 767ae3f6 0082f114 00000100 0019b894 ADVAPI32!SystemFunction036+0x14
    0082f218 767c6f3b 0019b894 00000010 0082f35c RPCRT4!GenerateRandomNumber+0x84
    0082f22c 760b88fb 0019b894 0082f374 00193bd8 RPCRT4!UuidCreate+0x11
    0082f26c 760a90a3 0082f34c 001a0920 0082f32c sxs!CClsidMap::MapReferenceClsidToConfiguredClsid+0xaf
    0082f360 760b4b7e 00195538 00195468 00000000 sxs!SxspComClassRedirectionContributorCallback+0x6c4
    0082f3d4 760a64d2 001924c8 001a0920 00195538 sxs!CActivationContextGenerationContextContributor::Fire_ElementParsed+0x73
    0082f430 760ac186 00000003 000001b0 00000000 sxs!CNodeFactory::CreateNode+0x760
    0082f4a0 760b0776 00194868 ffffffff 00192b70 sxs!XMLParser::Run+0x2fb
    0082f528 760b242e 001924c8 00003f3c 001a08d8 sxs!SxspIncorporateAssembly+0x542
    0082f568 760b004b 001924c8 0019ae70 001931f0 sxs!SxspIncorporateAssembly+0xb8
    0082f5a0 760b1325 001924c8 00000000 77ad3883 sxs!SxspCloseManifestGraph+0x7c
    0082f654 7626ad01 0082f724 762701f0 77ade2ce sxs!SxsGenerateActivationContext+0x48c
    0082f79c 7626b41d 00000000 ffffffff 0182f7c4 basesrv!BaseSrvSxsCreateActivationContextFromStruct+0x437
    0082fab8 762650e2 00000000 000000c8 7ffd5000 basesrv!BaseSrvSxsDoSystemDefaultActivationContext+0x441
    0082fb38 762859e4 000000c8 0082fc4c 813acd36 basesrv!BaseSrvCreateProcess+0x1fe
    0082fcac 77ac7ca3 00000080 77358c22 00000000 CSRSRV!CsrApiRequestThread+0x3b1
    0082fcec 77aee489 76285633 00000080 00000000 ntdll!__RtlUserThreadStart+0x35
    0082fd04 00000000 76285633 00000080 00000000 ntdll!_RtlUserThreadStart+0x1b


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    ksecdd!HashFirstUserModeCallerBlobs+7f
    8783e384 85c0            test    eax,eax

    SYMBOL_STACK_INDEX:  c

    SYMBOL_NAME:  ksecdd!HashFirstUserModeCallerBlobs+7f

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: ksecdd

    IMAGE_NAME:  ksecdd.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  47918d80

    FAILURE_BUCKET_ID:  0x50_ksecdd!HashFirstUserModeCallerBlobs+7f

    BUCKET_ID:  0x50_ksecdd!HashFirstUserModeCallerBlobs+7f

    Followup: MachineOwner
    ---------

    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: c0527038, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 81ccd6fe, If non-zero, the instruction address which referenced the bad memory
     address.
    Arg4: 00000009, (reserved)

    Debugging Details:
    ------------------

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: kernel32!pNlsUserInfo                         ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: kernel32!pNlsUserInfo                         ***
    ***                                                                   ***
    *************************************************************************

    READ_ADDRESS:  c0527038

    FAULTING_IP:
    nt!memcpy+9e
    81ccd6fe 8a06            mov     al,byte ptr [esi]

    MM_INTERNAL_CODE:  9

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  csrss.exe

    CURRENT_IRQL:  0

    TRAP_FRAME:  89ca0ff4 -- (.trap 0xffffffff89ca0ff4)
    ErrCode = 00000000
    eax=00000002 ebx=80d2002e ecx=00004e46 edx=00000002 esi=c0527038 edi=80d2002e
    eip=81ccd6fe esp=89ca1068 ebp=89ca1070 iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    nt!memcpy+0x9e:
    81ccd6fe 8a06            mov     al,byte ptr [esi]          ds:0023:c0527038=??
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 81c72b54 to 81cbd0f5

    STACK_TEXT: 
    89ca0fdc 81c72b54 00000000 c0527038 00000000 nt!MmAccessFault+0x10a
    89ca0fdc 81ccd6fe 00000000 c0527038 00000000 nt!KiTrap0E+0xdc
    89ca1070 81e4275d 80d2002e c0527038 00004e48 nt!memcpy+0x9e
    89ca1108 81c6fa1a 00004e78 80d1b000 00004e78 nt!NtQueryDirectoryObject+0x28b
    89ca1108 81c6e175 00004e78 80d1b000 00004e78 nt!KiFastCallEntry+0x12a
    89ca119c 81dbfb16 8000037c 80d1b000 00004e78 nt!ZwQueryDirectoryObject+0x11
    89ca120c 81dbf54c 89ca1230 80cfb000 00000000 nt!IopGetLegacyVetoListDrivers+0xcb
    89ca1240 81d73e99 bb7cb51e 00020000 89ca16e0 nt!IoGetLegacyVetoList+0x4a
    89ca128c 81e50e27 89ca1614 bb7cb1a2 89ca1648 nt!ExpQueryLegacyDriverInformation+0x1e
    89ca1630 81c6fa1a 0000002b 80cfb000 00020000 nt!NtQuerySystemInformation+0x1ec9
    89ca1630 81c6e3b9 0000002b 80cfb000 00020000 nt!KiFastCallEntry+0x12a
    89ca16b8 8783e384 0000002b 80cfb000 00020000 nt!ZwQuerySystemInformation+0x11
    89ca1754 8783e638 87835f64 00000000 00000040 ksecdd!HashFirstUserModeCallerBlobs+0x7f
    89ca1aa8 8783d9af 00000000 00000000 89ca1ac8 ksecdd!GatherRandomKey+0x204
    89ca1b0c 8783da46 00000001 00000008 8783e0bd ksecdd!ScavengeOnce+0x2a
    89ca1b60 8783e0b4 8650bbc8 00000030 89ca1b98 ksecdd!RandlibSystemPrng+0x54
    89ca1b70 8783e0f9 89ca1b88 8650bbc8 00000030 ksecdd!NewGenRandomEx+0x1b
    89ca1b98 8783b105 00000000 00000000 8650bbc8 ksecdd!NewGenRandom+0x3c
    89ca1c00 8783b3a8 8650bbc8 00000000 8650bbc8 ksecdd!KsecDeviceControl+0x121
    89ca1c2c 81cd3fd3 847fab08 00000030 85e853c0 ksecdd!KsecDispatch+0xa6
    89ca1c44 81e64615 8650bc58 85e853c0 85e85430 nt!IofCallDriver+0x63
    89ca1c64 81e64dba 847fab08 8650bc58 0082f000 nt!IopSynchronousServiceTail+0x1d9
    89ca1d00 81e4ea8d 847fab08 85e853c0 00000000 nt!IopXxxControlFile+0x6b7
    89ca1d34 81c6fa1a 000000dc 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
    89ca1d34 77b09a94 000000dc 00000000 00000000 nt!KiFastCallEntry+0x12a
    0082ef68 77b08444 765ec2a3 000000dc 00000000 ntdll!KiFastSystemCallRet
    0082ef6c 765ec2a3 000000dc 00000000 00000000 ntdll!ZwDeviceIoControlFile+0xc
    0082efcc 7771476e 000000dc 00390008 00000000 KERNEL32!DeviceIoControl+0x14a
    0082f028 777119d7 00000000 00000000 0082f05c ADVAPI32!GatherRandomKeyFastUserMode+0xb5
    0082f090 77711959 0082f114 0082f0a4 0019b894 ADVAPI32!RandomFillBuffer+0x5b
    0082f0a8 77711926 0082f114 00000100 0082f0e0 ADVAPI32!SystemPrng+0x30
    0082f0b8 77711901 0082f0d0 0082f114 00000100 ADVAPI32!NewGenRandomEx+0x1b
    0082f0e0 777118d6 00000000 00000000 0082f114 ADVAPI32!NewGenRandom+0x3c
    0082f0f8 767ae3f6 0082f114 00000100 0019b894 ADVAPI32!SystemFunction036+0x14
    0082f218 767c6f3b 0019b894 00000010 0082f35c RPCRT4!GenerateRandomNumber+0x84
    0082f22c 760b88fb 0019b894 0082f374 00193bd8 RPCRT4!UuidCreate+0x11
    0082f26c 760a90a3 0082f34c 001a0920 0082f32c sxs!CClsidMap::MapReferenceClsidToConfiguredClsid+0xaf
    0082f360 760b4b7e 00195538 00195468 00000000 sxs!SxspComClassRedirectionContributorCallback+0x6c4
    0082f3d4 760a64d2 001924c8 001a0920 00195538 sxs!CActivationContextGenerationContextContributor::Fire_ElementParsed+0x73
    0082f430 760ac186 00000003 000001b0 00000000 sxs!CNodeFactory::CreateNode+0x760
    0082f4a0 760b0776 00194868 ffffffff 00192b70 sxs!XMLParser::Run+0x2fb
    0082f528 760b242e 001924c8 00003f3c 001a08d8 sxs!SxspIncorporateAssembly+0x542
    0082f568 760b004b 001924c8 0019ae70 001931f0 sxs!SxspIncorporateAssembly+0xb8
    0082f5a0 760b1325 001924c8 00000000 77ad3883 sxs!SxspCloseManifestGraph+0x7c
    0082f654 7626ad01 0082f724 762701f0 77ade2ce sxs!SxsGenerateActivationContext+0x48c
    0082f79c 7626b41d 00000000 ffffffff 0182f7c4 basesrv!BaseSrvSxsCreateActivationContextFromStruct+0x437
    0082fab8 762650e2 00000000 000000c8 7ffd5000 basesrv!BaseSrvSxsDoSystemDefaultActivationContext+0x441
    0082fb38 762859e4 000000c8 0082fc4c 813acd36 basesrv!BaseSrvCreateProcess+0x1fe
    0082fcac 77ac7ca3 00000080 77358c22 00000000 CSRSRV!CsrApiRequestThread+0x3b1
    0082fcec 77aee489 76285633 00000080 00000000 ntdll!__RtlUserThreadStart+0x35
    0082fd04 00000000 76285633 00000080 00000000 ntdll!_RtlUserThreadStart+0x1b


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    ksecdd!HashFirstUserModeCallerBlobs+7f
    8783e384 85c0            test    eax,eax

    SYMBOL_STACK_INDEX:  c

    SYMBOL_NAME:  ksecdd!HashFirstUserModeCallerBlobs+7f

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: ksecdd

    IMAGE_NAME:  ksecdd.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  47918d80

    FAILURE_BUCKET_ID:  0x50_ksecdd!HashFirstUserModeCallerBlobs+7f

    BUCKET_ID:  0x50_ksecdd!HashFirstUserModeCallerBlobs+7f

    Followup: MachineOwner
    谁能提点好的建议,帮忙看看是什么原因,谢谢

    2009年2月15日 2:05

答案

  •  Your debugger is not using the correct symbols    
    说明你的DEBUG没有导入正确的SYMBOLS,在这种情况下你的错误分析是不会正确的!
    请按照一下步骤:

    首先下载windebug

     

    http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

    说下debug方法
    1.
    我的电脑,属性->高级->启动,最下面的内存调试选最后一项的全部,确定后重新启动
    2.
    蓝屏后不要急着重启,系统会保存整个内存内容,然后会自动重启
    3.
    找到C:\Windows\Minidump\

    4. 下载安装windwos debug tools, 我这有下载地址,或微软网站
    http://public.hshh.org/SysTools/debug/dbg_x86_6.6.07.5.exe
    5.
    安装后创建一个临时目录,例如 c:\temp
    6.
    启动 windbg
    7. windbg
    界面: file->symbol file path (ctrl+s) 输入:
    SRV*c:\temp*http://msdl.microsoft.com/download/symbols
    然后确定
    8. windbg
    界面: file->open crash dump(ctrl+d),打开9. 打开例如C:\Windows\Minidump\Mini122208-01.dmp后,等待提示
    当出现 Use !analyze -v to get detailed debugging information. 字样后,在下面输入框
    !analyze -v
    10.
    等待分析完毕,可以知道什么导致的出错
    11. windbg
    使用中需要网上下载调试内容,这个速度嘛,取决于你的网络了。

    -----------------------------------------------------------------------

     

    你把敲完!analyze -v后的信息发上来!

     


    Microsoft Certified Systems Engineer 如果您觉得对您有帮助,请在“是否有帮助”点“是”;如果你觉得回复很满意,请“标记为已解答”
    2009年2月16日 7:52

全部回复

  • 从楼主描述的情况来说可能是硬件问题引起的
    楼主能否提供您PC的配置和购买日期

    Vista UI
    2009年2月15日 12:44
    版主
  •  Your debugger is not using the correct symbols    
    说明你的DEBUG没有导入正确的SYMBOLS,在这种情况下你的错误分析是不会正确的!
    请按照一下步骤:

    首先下载windebug

     

    http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

    说下debug方法
    1.
    我的电脑,属性->高级->启动,最下面的内存调试选最后一项的全部,确定后重新启动
    2.
    蓝屏后不要急着重启,系统会保存整个内存内容,然后会自动重启
    3.
    找到C:\Windows\Minidump\

    4. 下载安装windwos debug tools, 我这有下载地址,或微软网站
    http://public.hshh.org/SysTools/debug/dbg_x86_6.6.07.5.exe
    5.
    安装后创建一个临时目录,例如 c:\temp
    6.
    启动 windbg
    7. windbg
    界面: file->symbol file path (ctrl+s) 输入:
    SRV*c:\temp*http://msdl.microsoft.com/download/symbols
    然后确定
    8. windbg
    界面: file->open crash dump(ctrl+d),打开9. 打开例如C:\Windows\Minidump\Mini122208-01.dmp后,等待提示
    当出现 Use !analyze -v to get detailed debugging information. 字样后,在下面输入框
    !analyze -v
    10.
    等待分析完毕,可以知道什么导致的出错
    11. windbg
    使用中需要网上下载调试内容,这个速度嘛,取决于你的网络了。

    -----------------------------------------------------------------------

     

    你把敲完!analyze -v后的信息发上来!

     


    Microsoft Certified Systems Engineer 如果您觉得对您有帮助,请在“是否有帮助”点“是”;如果你觉得回复很满意,请“标记为已解答”
    2009年2月16日 7:52
  • 谢谢 大家,问题现在得到解决,主要问题是内存条的问题。后来厂家更换了内存条后, 再也没有蓝屏了。看样子还是硬件方面的问题啊

    2009年2月25日 11:00
  • 最终还是内存不兼容所导致!!一般金士顿的内存兼容性是比较好的!不过金士顿的假内存条也比较多!
    内存兼容性的问题应该注意两点:
    1.不要不同内存品牌的混插
    2.不要速率不同的内存条混插
    3。不要大小不同的内存混插
    2009年3月7日 12:09