none
windows vista SP2 Blue screen 0x000000D1 RRS feed

  • 问题

  • Loading Dump File [C:\Windows\Minidump\Mini040414-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\temp*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6002.18686.x86fre.vistasp2_gdr.120824-0336
    Machine Name:
    Kernel base = 0x85e4f000 PsLoadedModuleList = 0x85f66c70
    Debug session time: Fri Apr  4 20:13:19.336 2014 (GMT+8)
    System Uptime: 0 days 1:38:16.461
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 10E, {1f, 82454008, 0, 2d9ed4}

    Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_GLOBAL::ReferenceAllocationForSubmission+bb )

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

    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
    The video memory manager encountered a condition that it can't recover from. By crashing,
    the video memory manager is attempting to get enough information into the minidump such that
    somebody can pinpoint what lead to this condition.
    Arguments:
    Arg1: 0000001f, The subtype of the bugcheck:
    Arg2: 82454008
    Arg3: 00000000
    Arg4: 002d9ed4

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


    BUGCHECK_STR:  0x10e_1f

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  dwm.exe

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 91f45230 to 85f1cabf

    STACK_TEXT:  
    81013724 91f45230 0000010e 0000001f 82454008 nt!KeBugCheckEx+0x1e
    8101374c 91ec87ae 00000000 0000010e 0000001f watchdog!WdLogEvent5+0x130
    81013778 91ec826b 00000000 8ac0ead0 00000a86 dxgkrnl!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xbb
    810137e0 91ec76ae 9c36c830 00000000 8bd2df60 dxgkrnl!VIDMM_GLOBAL::PrepareDmaBuffer+0x6a9
    810138e8 91ec6b87 88be7888 8b6d2008 81013928 dxgkrnl!VidSchiSubmitRenderCommand+0x126
    810138f8 91ea7768 88be7888 88be7888 8c022720 dxgkrnl!VidSchiSubmitQueueCommand+0x61
    81013928 91ec6aaa 8b7ce000 8101394c 8c022720 dxgkrnl!VidSchiSubmitQueueCommandDirect+0x1ae
    81013950 91ec673c 01be7888 91f45100 a58b4440 dxgkrnl!VidSchiSubmitCommandPacketToQueue+0x171
    81013974 91ecadb8 8c022720 81013a94 00000000 dxgkrnl!VidSchSubmitCommand+0x2bf
    81013b90 91eca69e 81013bac 10ed1949 0041d41c dxgkrnl!DXGCONTEXT::Render+0x513
    81013d58 85e99c3a 0041d41c 0041d560 77155cd4 dxgkrnl!DxgkRender+0x272
    81013d58 77155cd4 0041d41c 0041d560 77155cd4 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0041d560 00000000 00000000 00000000 00000000 0x77155cd4


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    dxgkrnl!VIDMM_GLOBAL::ReferenceAllocationForSubmission+bb
    91ec87ae c7451079f5ffff  mov     dword ptr [ebp+10h],0FFFFF579h

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  dxgkrnl!VIDMM_GLOBAL::ReferenceAllocationForSubmission+bb

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: dxgkrnl

    IMAGE_NAME:  dxgkrnl.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4d383dc1

    FAILURE_BUCKET_ID:  0x10e_1f_dxgkrnl!VIDMM_GLOBAL::ReferenceAllocationForSubmission+bb

    BUCKET_ID:  0x10e_1f_dxgkrnl!VIDMM_GLOBAL::ReferenceAllocationForSubmission+bb

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

    1: kd> !process
    GetPointerFromAddress: unable to read from 85f8686c
    PROCESS 8bff5020  SessionId: none  Cid: 0e58    Peb: 7ffd8000  ParentCid: 0598
        DirBase: bd57f6c0  ObjectTable: a8ca7840  HandleCount: <Data Not Accessible>
        Image: dwm.exe
        VadRoot 8a5bb178 Vads 193 Clone 0 Private 6223. Modified 118728. Locked 2116.
        DeviceMap 81339998
        Token                             a8cf7030
        ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    ffdf0000: Unable to get shared data
        ElapsedTime                       00:00:00.000
        UserTime                          00:00:00.000
        KernelTime                        00:00:00.000
        QuotaPoolUsage[PagedPool]         254152
        QuotaPoolUsage[NonPagedPool]      9304
        Working Set Sizes (now,min,max)  (11812, 12800, 524272) (47248KB, 51200KB, 2097088KB)
        PeakWorkingSetSize                14328
        VirtualSize                       157 Mb
        PeakVirtualSize                   161 Mb
        PageFaultCount                    200824
        MemoryPriority                    BACKGROUND
        BasePriority                      13
        CommitCharge                      9618

            *** Error in reading nt!_ETHREAD @ 8c02c030
    2014年4月10日 6:17

全部回复

  • 显卡驱动配置错误,这个有可能但不一定是硬件问题。蓝屏之前是否更改过显示驱动设置?


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | Loading Dump File [C:\Windows\Minidump\Mini040414-01.dmp]
    | Mini Kernel Dump File: Only registers and stack trace are available

    2014年4月12日 8:48
    版主
  • 谢谢回复

    是的,安装显卡驱动更新

    2014年4月19日 4:34
  • 那么请先卸载安装的更新,看看能否恢复正常。如果可以,这个更新可能存在兼容性问题,可以向驱动制造商反馈并等候下一版本。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 谢谢回复
    | 是的,安装显卡驱动更新

    2014年4月20日 3:39
    版主
  • 再次求助,之后我玩大型网游出现以下蓝屏 Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\Mini042114-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\temp*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6002.18686.x86fre.vistasp2_gdr.120824-0336
    Machine Name:
    Kernel base = 0x85e3c000 PsLoadedModuleList = 0x85f53c70
    Debug session time: Mon Apr 21 00:30:12.612 2014 (GMT+8)
    System Uptime: 0 days 3:23:09.007
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000006, 93883c1d, b925b7e4, 0}

    Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_SEGMENT::MakeRangePageable+8 )

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

    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000006, The exception code that was not handled
    Arg2: 93883c1d, The address that the exception occurred at
    Arg3: b925b7e4, Trap Frame
    Arg4: 00000000

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%08lx referenced memory at 0x%08lx. The required data was not placed into memory because of an I/O error status of 0x%08lx.

    FAULTING_IP:
    dxgkrnl!VIDMM_SEGMENT::MakeRangePageable+8
    93883c1d 8b02            mov     eax,dword ptr [edx]

    TRAP_FRAME:  b925b7e4 -- (.trap 0xffffffffb925b7e4)
    ErrCode = 00000000
    eax=bfff0000 ebx=00000000 ecx=b1527268 edx=bfff0000 esi=bef86598 edi=b1527268
    eip=93883c1d esp=b925b858 ebp=b925b858 iopl=0         nv up ei ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
    dxgkrnl!VIDMM_SEGMENT::MakeRangePageable+0x8:
    93883c1d 8b02            mov     eax,dword ptr [edx]  ds:0023:bfff0000=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x8E

    PROCESS_NAME:  Game.exe

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 93864153 to 93883c1d

    STACK_TEXT:  
    b925b858 93864153 bfff0000 2aa16dbe 88b7aef0 dxgkrnl!VIDMM_SEGMENT::MakeRangePageable+0x8
    b925b928 9385bc2e bef86598 00000000 8bb11ad8 dxgkrnl!VIDMM_MEMORY_SEGMENT::EvictResource+0x8fe
    b925b990 9385aea6 b925bac0 b925ba60 b925ba8c dxgkrnl!VIDMM_GLOBAL::ProcessDeferredCommand+0x610
    b925b9a8 9385ae2c b925ba84 8bb11ad8 8bb11ad8 dxgkrnl!VidMmiProcessSystemCommand+0x20
    b925b9c4 93851ba1 88969be0 8873b8b8 b925ba04 dxgkrnl!VidSchiSubmitSystemCommand+0x2d
    b925b9d4 93832768 8bb11ad8 8bb11ad8 8b4df580 dxgkrnl!VidSchiSubmitQueueCommand+0x7b
    b925ba04 93851aaa 89dfc000 b925ba28 8873b8b8 dxgkrnl!VidSchiSubmitQueueCommandDirect+0x1ae
    b925ba2c 9385be2d 01b11ad8 89e6c000 89e6c000 dxgkrnl!VidSchiSubmitCommandPacketToQueue+0x171
    b925ba44 9385bee6 8873b8b8 9385ae86 b925ba84 dxgkrnl!VidSchSubmitSystemCommand+0xa6
    b925ba70 9385bf59 b925ba84 bef86598 88b7aef0 dxgkrnl!VIDMM_GLOBAL::QueueSystemCommandAndWait+0x40
    b925baa8 9385c357 b925bac0 00000000 b6d6db30 dxgkrnl!VIDMM_GLOBAL::QueueDeferredCommandAndWait+0x3c
    b925bae4 9385c8f2 00000000 00000000 beea45b8 dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+0x8d
    b925bb04 938629dd b6d6db30 00000000 beea45f8 dxgkrnl!VIDMM_GLOBAL::CloseAllocation+0x37
    b925bb70 9389e969 00000000 00000000 ba92e370 dxgkrnl!DXGDEVICE::DestroyAllocations+0x176
    b925bba0 9383fff9 8b0f0378 b925bbcc 9389e656 dxgkrnl!DXGDEVICE::~DXGDEVICE+0xc0
    b925bbac 9389e656 00000001 895d64f0 895d6520 dxgkrnl!DXGDEVICE::`scalar deleting destructor'+0xd
    b925bbcc 93859a6d beea45b8 895d64f0 00000000 dxgkrnl!DXGADAPTER::DestroyDevice+0xd4
    b925bc08 938597b7 85e64aff ffb8a1c8 00000000 dxgkrnl!DXGPROCESS::Destroy+0x7d
    b925bc40 a0cfbc8f ffb8a244 a0e32f38 00000000 dxgkrnl!DxgkProcessCallout+0x108
    b925bc54 a0cfbe0c ffb8a244 00000000 ffb8a1c8 win32k!DxDdProcessCallout+0x1b
    b925bc7c a0cfb920 ffb8a1c8 00000001 8b1a7420 win32k!GdiProcessCallout+0x170
    b925bc98 86054998 88ea4098 00000000 1fe232c1 win32k!W32pProcessCallout+0x5d
    b925bd04 86054fe7 00000000 00000000 8a014d78 nt!PspExitThread+0x4a0
    b925bd24 8602d353 8a014d78 00000000 00000001 nt!PspTerminateThreadByPointer+0x5b
    b925bd54 85e86c3a ffffffff 00000000 0012f9d8 nt!NtTerminateProcess+0x1e0
    b925bd54 774e5cd4 ffffffff 00000000 0012f9d8 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012f9d8 00000000 00000000 00000000 00000000 0x774e5cd4


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    dxgkrnl!VIDMM_SEGMENT::MakeRangePageable+8
    93883c1d 8b02            mov     eax,dword ptr [edx]

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  dxgkrnl!VIDMM_SEGMENT::MakeRangePageable+8

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: dxgkrnl

    IMAGE_NAME:  dxgkrnl.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4d383dc1

    FAILURE_BUCKET_ID:  0x8E_dxgkrnl!VIDMM_SEGMENT::MakeRangePageable+8

    BUCKET_ID:  0x8E_dxgkrnl!VIDMM_SEGMENT::MakeRangePageable+8

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

    1: kd> !process
    GetPointerFromAddress: unable to read from 85f7386c
    PROCESS 88ea4098  SessionId: none  Cid: 0224    Peb: 7ffd5000  ParentCid: 1414
        DirBase: bd140960  ObjectTable: b6df2c88  HandleCount: <Data Not Accessible>
        Image: Game.exe
        VadRoot 88bdf970 Vads 6762 Clone 0 Private 133368. Modified 93633. Locked 65.
        DeviceMap 83c05648
        Token                             bee8a5b0
        ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    ffdf0000: Unable to get shared data
        ElapsedTime                       00:00:00.000
        UserTime                          00:00:00.000
        KernelTime                        00:00:00.000
        QuotaPoolUsage[PagedPool]         267664
        QuotaPoolUsage[NonPagedPool]      324832
        Working Set Sizes (now,min,max)  (91380, 50, 345) (365520KB, 200KB, 1380KB)
        PeakWorkingSetSize                181804
        VirtualSize                       680 Mb
        PeakVirtualSize                   1151 Mb
        PageFaultCount                    4390969
        MemoryPriority                    BACKGROUND
        BasePriority                      8
        CommitCharge                      140329
        Job                               88a8a8f0

            THREAD 8a014d78  Cid 0224.12e4  Teb: 7ffdf000 Win32Thread: 00000000 RUNNING on processor 1
    2014年4月20日 16:42
  • 还是显示驱动有问题,而且可能是因为磁盘故障引起显示驱动文件无法正确加载。建议对所有硬盘分区进行一下完整扫描。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 再次求助,之后我玩大型网游出现以下蓝屏 Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
    | Copyright (c) Microsoft Corporation. All rights reserved.|

    2014年4月20日 23:17
    版主
  • 请问如何对所有硬盘分区进行一下完整扫描,谢谢!
    2014年4月21日 17:00
  • 在网上观看视频时再次出现新蓝屏分析。。。

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


    Loading Dump File [C:\Windows\Minidump\Mini042214-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\temp*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6002.18686.x86fre.vistasp2_gdr.120824-0336
    Machine Name:
    Kernel base = 0x85e17000 PsLoadedModuleList = 0x85f2ec70
    Debug session time: Tue Apr 22 09:36:13.356 2014 (GMT+8)
    System Uptime: 0 days 1:11:52.391
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {a000002, 1b, 0, 85ec10b3}

    Probably caused by : ntkrpamp.exe ( nt!KiTimerListExpire+1af )

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

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0a000002, memory referenced
    Arg2: 0000001b, IRQL
    Arg3: 00000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 85ec10b3, address which referenced memory

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from 85f4e868
    Unable to read MiSystemVaType memory at 85f2e420
     0a000002

    CURRENT_IRQL:  1b

    FAULTING_IP:
    nt!KiTimerListExpire+1af
    85ec10b3 668b4302        mov     ax,word ptr [ebx+2]

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  FlashPlayerPlug

    LAST_CONTROL_TRANSFER:  from 85ec0e2b to 85ec10b3

    STACK_TEXT:  
    8039df28 85ec0e2b 8039df70 85f0f902 8039df78 nt!KiTimerListExpire+0x1af
    8039df88 85ec1595 00000000 00000000 000437d1 nt!KiTimerExpiration+0x22a
    8039dff4 85ebf235 d16bad10 00000000 00000000 nt!KiRetireDpcList+0xba
    8039dff8 d16bad10 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    85ebf235 00000000 0000001b 00c7850f bb830000 0xd16bad10


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!KiTimerListExpire+1af
    85ec10b3 668b4302        mov     ax,word ptr [ebx+2]

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!KiTimerListExpire+1af

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  5037809b

    FAILURE_BUCKET_ID:  0xA_nt!KiTimerListExpire+1af

    BUCKET_ID:  0xA_nt!KiTimerListExpire+1af

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

    0: kd> !process
    GetPointerFromAddress: unable to read from 85f4e86c
    PROCESS 89110a90  SessionId: none  Cid: 16d8    Peb: 7ffdf000  ParentCid: 0d30
        DirBase: bd328a00  ObjectTable: ad93d648  HandleCount: <Data Not Accessible>
        Image: FlashPlayerPlug
        VadRoot 88c27ac8 Vads 239 Clone 0 Private 7921. Modified 24445. Locked 0.
        DeviceMap a4d76a20
        Token                             ca330c48
        ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    ffdf0000: Unable to get shared data
        ElapsedTime                       00:00:00.000
        UserTime                          00:00:00.000
        KernelTime                        00:00:00.000
        QuotaPoolUsage[PagedPool]         312568
        QuotaPoolUsage[NonPagedPool]      11768
        Working Set Sizes (now,min,max)  (12249, 50, 345) (48996KB, 200KB, 1380KB)
        PeakWorkingSetSize                14027
        VirtualSize                       216 Mb
        PeakVirtualSize                   228 Mb
        PageFaultCount                    141288
        MemoryPriority                    BACKGROUND
        BasePriority                      8
        CommitCharge                      13782
        Job                               89110d20

            *** Error in reading nt!_ETHREAD @ 89236030

    2014年4月22日 1:52
  • 管理员权限打开命令提示符,对所有驱动器执行 CHKDSK /F,例如 CHKDSK /F C:。

    系统分区会提示要在下一次启动时才能执行,重启即可。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 请问如何对所有硬盘分区进行一下完整扫描,谢谢!
    |

    2014年4月22日 2:33
    版主
  • 请问Probably caused by : ntkrpamp.exe ( nt!KiTimerListExpire+1af )也是硬盘故障引起吗?谢谢!
    2014年4月22日 3:42
  • 有可能。NTKrpamp.EXE 是 Windows Kernel 核心系统文件,文件自身受损的可能性不大,一般都是其它问题引起 Windows Kernel 运行失败,比如硬盘错误。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 请问Probably caused by : ntkrpamp.exe ( nt!KiTimerListExpire+1af )也是硬盘故障引起吗?谢谢!
    |

    2014年4月24日 3:35
    版主
  • 又出现不一样的蓝屏,分析如下Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\Mini042714-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\temp*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6002.18686.x86fre.vistasp2_gdr.120824-0336
    Machine Name:
    Kernel base = 0x85e16000 PsLoadedModuleList = 0x85f2dc70
    Debug session time: Sun Apr 27 16:35:11.419 2014 (GMT+8)
    System Uptime: 0 days 5:00:55.245
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 9407b2e9, afef1a18, 0}

    Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+1f )

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

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 9407b2e9, The address that the exception occurred at
    Arg3: afef1a18, Trap Frame
    Arg4: 00000000

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP:
    dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+1f
    9407b2e9 8b38            mov     edi,dword ptr [eax]

    TRAP_FRAME:  afef1a18 -- (.trap 0xffffffffafef1a18)
    ErrCode = 00000000
    eax=00000000 ebx=8b037000 ecx=00000000 edx=00000000 esi=8c18fa48 edi=00000000
    eip=9407b2e9 esp=afef1a8c ebp=afef1abc iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+0x1f:
    9407b2e9 8b38            mov     edi,dword ptr [eax]  ds:0023:00000000=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x8E

    PROCESS_NAME:  Game.exe

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 9407b8f2 to 9407b2e9

    STACK_TEXT:  
    afef1abc 9407b8f2 8c18fa48 00000000 88cfb448 dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+0x1f
    afef1adc 940819dd 835f9bf8 00000000 88cfb488 dxgkrnl!VIDMM_GLOBAL::CloseAllocation+0x37
    afef1b48 940bd969 00000000 00000000 a3fd0be8 dxgkrnl!DXGDEVICE::DestroyAllocations+0x176
    afef1b78 9405eff9 8a36e378 afef1ba4 940bd656 dxgkrnl!DXGDEVICE::~DXGDEVICE+0xc0
    afef1b84 940bd656 00000001 8d2379a0 8d2379d0 dxgkrnl!DXGDEVICE::`scalar deleting destructor'+0xd
    afef1ba4 94078a6d 88cfb448 8d2379a0 00000000 dxgkrnl!DXGADAPTER::DestroyDevice+0xd4
    afef1be0 940787b7 85e3eaff fce7f808 00000000 dxgkrnl!DXGPROCESS::Destroy+0x7d
    afef1c18 a135bc8f fce7f884 a1492f38 00000000 dxgkrnl!DxgkProcessCallout+0x108
    afef1c2c a135be0c fce7f884 00000000 fce7f808 win32k!DxDdProcessCallout+0x1b
    afef1c54 a135b920 fce7f808 00000001 8ce2af08 win32k!GdiProcessCallout+0x170
    afef1c70 8602e998 89f021c0 00000000 77d0dfd4 win32k!W32pProcessCallout+0x5d
    afef1cdc 8600b487 00000000 88760288 88760201 nt!PspExitThread+0x4a0
    afef1cf4 85ec9f1a 8c1d8238 afef1d20 afef1d2c nt!PsExitSpecialApc+0x22
    afef1d4c 85e60ce6 00000001 00000000 afef1d64 nt!KiDeliverApc+0x1dc
    afef1d4c 76f35cd4 00000001 00000000 afef1d64 nt!KiServiceExit+0x56
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0c0fff08 00000000 00000000 00000000 00000000 0x76f35cd4


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+1f
    9407b2e9 8b38            mov     edi,dword ptr [eax]

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+1f

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: dxgkrnl

    IMAGE_NAME:  dxgkrnl.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4d383dc1

    FAILURE_BUCKET_ID:  0x8E_dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+1f

    BUCKET_ID:  0x8E_dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+1f

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

    0: kd> !process
    GetPointerFromAddress: unable to read from 85f4d86c
    PROCESS 89f021c0  SessionId: none  Cid: 0a70    Peb: 7ffd9000  ParentCid: 06ac
        DirBase: bd34da00  ObjectTable: b6b6dbb8  HandleCount: <Data Not Accessible>
        Image: Game.exe
        VadRoot 8c2e51c0 Vads 7147 Clone 0 Private 216815. Modified 127208. Locked 3865.
        DeviceMap a65f5378
        Token                             83520468
        ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    ffdf0000: Unable to get shared data
        ElapsedTime                       00:00:00.000
        UserTime                          00:00:00.000
        KernelTime                        00:00:00.000
        QuotaPoolUsage[PagedPool]         396944
        QuotaPoolUsage[NonPagedPool]      343624
        Working Set Sizes (now,min,max)  (135894, 50, 345) (543576KB, 200KB, 1380KB)
        PeakWorkingSetSize                163925
        VirtualSize                       1089 Mb
        PeakVirtualSize                   1132 Mb
        PageFaultCount                    3681516
        MemoryPriority                    BACKGROUND
        BasePriority                      8
        CommitCharge                      225997
        Job                               88965730

            THREAD 88760288  Cid 0a70.0d14  Teb: 7fd36000 Win32Thread: 00000000 RUNNING on processor 0

    0: kd> .trap 0xffffffffafef1a18
    ErrCode = 00000000
    eax=00000000 ebx=8b037000 ecx=00000000 edx=00000000 esi=8c18fa48 edi=00000000
    eip=9407b2e9 esp=afef1a8c ebp=afef1abc iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+0x1f:
    9407b2e9 8b38            mov     edi,dword ptr [eax]  ds:0023:00000000=????????
    0: kd> lmvm dxgkrnl
    start    end        module name
    9404e000 940ee000   dxgkrnl    (pdb symbols)          c:\temp\dxgkrnl.pdb\08B27E993FBE4EB1988D3F44AD9EE24E2\dxgkrnl.pdb
        Loaded symbol image file: dxgkrnl.sys
        Mapped memory image file: c:\temp\dxgkrnl.sys\4D383DC1a0000\dxgkrnl.sys
        Image path: dxgkrnl.sys
        Image name: dxgkrnl.sys
        Timestamp:        Thu Jan 20 21:50:57 2011 (4D383DC1)
        CheckSum:         000A384D
        ImageSize:        000A0000
        File version:     7.0.6002.22573
        Product version:  7.0.6002.22573
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     dxgkrnl.sys
        OriginalFilename: dxgkrnl.sys
        ProductVersion:   7.0.6002.22573
        FileVersion:      7.0.6002.22573 (vistasp2_ldr.110120-0254)
        FileDescription:  DirectX Graphics Kernel
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    2014年4月27日 16:22
  • 这次是显示驱动的问题。你可以尝试重装显示驱动,但不一定是驱动自身的问题,依然有可能是硬盘损坏引起驱动文件无法正确加载。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 又出现不一样的蓝屏,分析如下Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
    | Copyright (c) Microsoft Corporation. All rights reserved.

    2014年4月27日 23:56
    版主
  • 我需要重装Windows vista系统,但是原装光碟是Windows vista SP1的,而我现在已经更新到Windows vista SP2了,请问如果重装系统后能升级至windows vista SP2吗和如何重装系统,谢谢!
    2014年4月30日 7:27
  • 如果想修复原系统是不行的,必须用 with SP2 的安装程序。如果是格盘全新重装就可以,安装好系统后可以单独安装 SP2。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 我需要重装Windows vista系统,但是原装光碟是Windows vista SP1的,而我现在已经更新到Windows vista SP2了,请问如果重装系统后能升级至windows vista SP2吗和如何重装系统,谢谢!

    2014年5月1日 4:24
    版主
  • 不是很明白,请问意思是买电脑附带的windows vista SP1(OPERATING SYSTEM)光碟只能修复原系统,不能格盘全新安装吗?
    2014年5月1日 11:12
  • 不是。我是说如果打算用安装光盘修复硬盘中已经存在的系统,那么安装光盘包含的 Service Pack 版本就不能比硬盘中系统的 Service Pack 版本低;如果只是想全新安装一个系统就无所谓了,安装光盘是什么版本都可以,安装好之后再另行升级。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 不是很明白,请问意思是买电脑附带的windows vista SP1(OPERATING SYSTEM)光碟只能修复原系统,不能格盘全新安装吗?
    |

    2014年5月2日 5:19
    版主
  • 明白了,谢谢!那么是reinstall windows还是format了再用原装光碟install才对?
    2014年5月2日 6:27
  • 如果原系统已经没有什么保留的必要,重要的数据也都备份,还是用安装光盘格式化硬盘后全新安装比较彻底。

    如果原系统损坏的幅度不太大,还可以启动到桌面,同时安装光盘的版本也不比系统低,可以尝试用升级安装的方法修复系统。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 明白了,谢谢!那么是reinstall windows还是format了再用原装光碟install才对?
    |

    2014年5月4日 3:58
    版主
  • 求助!
    因为Watchdog.sys导致了蓝屏,显卡的驱动也更新到最新了玩游戏还是显示watchdog.sys引起这次蓝屏。谢谢
    2014年6月10日 3:38
  • 还是原先那个系统?还是已经重新全新安装过?


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 求助!
    | 因为Watchdog.sys导致了蓝屏,显卡的驱动也更新到最新了玩游戏还是显示watchdog.sys引起这次蓝屏。谢谢

    2014年6月10日 22:26
    版主
  • 重装换windows 7了,显卡是NVIDIA GT610,我看见显卡驱动安装时有提到watchdog,它是不是N卡的驱动来的?
    2014年6月11日 2:04
  • 我在正常模式下执行sfc /scannow走到50%左右就蓝屏死机,可是在安全模式执行sfc /scannow却走到100%结束没出现蓝屏死机,请问这是怎么回事?谢谢
      补充一下,sfc /scannow的结果是正常没有损坏的文件
    • 已编辑 Denimlim 2014年6月11日 8:08
    2014年6月11日 8:06
  • 如果 Windows 7 安装源没有问题的话,你的硬盘可能有毛病,建议检测一下所有硬盘分区。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 我在正常模式下执行sfc /scannow走到50%左右就蓝屏死机,可是在安全模式执行sfc /scannow却走到100%结束没出现蓝屏死机,请问这是怎么回事?谢谢

    2014年6月11日 23:26
    版主
  • WatchDog.SYS 不是专门的 N 卡显示驱动,而是一种“看门狗”计时器测试用驱动,很多其它设备驱动要用到它而已。

    详情可参考一下:
    http://msdn2.microsoft.com/en-us/library/ms856963.aspx

    http://msdn2.microsoft.com/en-us/library/ms797877.aspx


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 重装换windows 7了,显卡是NVIDIA GT610,我看见显卡驱动安装时有提到watchdog,它是不是N卡的驱动来的?
    |

    2014年6月11日 23:30
    版主
  • If you test your display driver without an attached debugger, you can prevent the watchdog timer from generating a bug check. To do so, create the following REG_DWORD entry in the registry, and set its value to 1:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Watchdog\Display\DisableBugCheck
    
    

    The techniques described in this topic are only for debugging and testing. Do not release a driver that creates or alters BreakPointDelay or DisableBugCheck.

    不是很明白,如何在注册表创建watchdog项,因为注册表里control没有watchdog项,谢谢

    2014年6月14日 2:23
  • 这个一般是开发人员用到的。你的问题应该是显示驱动自身存在兼容问题,看看有没有其它版本可更新?


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | If you test your display driver without an attached debugger, you can prevent the watchdog timer from generating a bug check. To do so, create the following REG_DWORD entry in the registry, and set its value to 1:

    2014年6月14日 23:54
    版主
  • 唉~5年的电脑了,去年年尾才开始常出现故障蓝屏死机,最近用杀毒软件扫描也是死机重启,avast扫描死机,avira扫描也死机重启,真不懂是什么故障。。。
    2014年6月15日 16:22
  • 查查硬盘吧,最好把硬盘拆下来接在别的计算机上,做磁盘扫描及查杀病毒,看看这两项操作在其它计算机上能否完成。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 唉~5年的电脑了,去年年尾才开始常出现故障蓝屏死机,最近用杀毒软件扫描也是死机重启,avast扫描死机,avira扫描也死机重启,真不懂是什么故障。。。

    2014年6月15日 23:12
    版主
  • 请问显卡的驱动应该根据Windows update 检测到的驱动安装还是从显卡自动更新程序检测到的官网驱动安装?比如:我的显卡是NVIDIA GT610,Windows update检测到的最新驱动版本是335,而显卡的自动更新程序检测的最新是338版本,应该安装哪个才正确。
    2014年6月18日 2:19
  • 两者都可,但 Microsoft Update 对驱动的更新往往不如官网更快,可以其中版本较高的为准。

    但是驱动这种东西也不是 100% 版本越新就一定越好,只是大多数如此。到底哪个版本最稳定还是要亲自试过才知道。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 请问显卡的驱动应该根据Windows update 检测到的驱动安装还是从显卡自动更新程序检测到的官网驱动安装?比如:我的显卡是NVIDIA GT610,Windows update检测到的最新驱动版本是335,

    2014年6月19日 23:46
    版主
  • 谢谢回复! 我电脑一直都安装这些程序:

    Adobe Air,

    adobe flash player 14 activeX,

    adobe flash player 14 plugin,

    adobe reader XI -simplified,

    adobe shockwave player 12.1,

    bing bar,

    Microsoft .Net Framework 4.5.1,

    Microsoft office file validation add-in,

    Microsoft office home and student 2007,

    Microsoft onedrive,

    microsoft security essentials,

    Microsoft silverlight,

    Microsoft SQL server 2005 compact edition (ENU),

    Microsoft visual C++ 2010 x86 redistributable - 10.0.40219,

    Microsoft visual C++ 2012  redistributable(x86) - 11.0.61030,

    Microsoft visual C++ 2013 redistributable (x86)- 12.0.21005,

    mozilla firefox 29.0.1 (x86 zh-CN),

    mozilla maintenance service,

    MSXML 4.0 SP2 (KB954430),

    MSXML 4.0 SP2 (KB973688),

    My Dell,

    Windows essentials 2012。

    请问我有安装到会冲突的程序或者缺少什么没装吗?我的系统是Windows 7 SP1 32位.

    2014年6月20日 4:55
  • 这些程序应该都没有问题的。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 谢谢回复! 我电脑一直都安装这些程序:
    | Adobe Air,

    2014年6月20日 23:20
    版主
  • 我电脑用了5年,已确定有硬件老化或故障但是不知道是硬盘还是主板,请问如何检测到是主板还是硬盘故障,error - checking是不是检测硬盘的,测了没问题,内存也测了没问题,主板如何检测呢

    电脑开机时正常关机也是。。但是在运行大型软件时容易死机(滑鼠没反应只能按住启动键强行关机)或者它自动重启,在玩大型网游,开火狐浏览面子书时,在线观看视频,用skype有时也会。
    • 已编辑 Denimlim 2014年6月30日 4:32
    2014年6月30日 4:27
  • 只能用替换法检测。硬盘好测,主板替换起来比较麻烦,不如送修。

    通常只有在完全排除其它所有设备之后,最后怀疑主板。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 我电脑用了5年,已确定有硬件老化或故障但是不知道是硬盘还是主板,请问如何检测到是主板还是硬盘故障,error - checking是不是检测硬盘的,测了没问题,内存也测了没问题,主板如何检测呢

    2014年6月30日 23:33
    版主
  • 谢谢。硬盘用电脑原厂的软件My Dell测过了正常,唯有主板没法测,换装了windows 7感觉到机器像飞的速度比以前windows vista系统强好多,给Windows 7一个赞。主板上有看见一颗电池,好像一直没换过不知道有没有什么关系呢?
    2014年7月1日 2:10
  • 电池没电最多无法保存时间设置而已。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 谢谢。硬盘用电脑原厂的软件My Dell测过了正常,唯有主板没法测,换装了windows 7感觉到机器像飞的速度比以前windows vista系统强好多,给Windows 7一个赞。主板上有看见一颗电池,好像一直没换过不知道有没有什么关系呢?

    2014年7月3日 23:41
    版主
  • 请问原本用DDR2内存的主板可以使用DDR3显存的独立显卡吗?显存需要和内存一样吗?还是可以使用DDR3/DDR4/DDR5的显卡。我的电脑是 Dell Inspiron 545s,BIOS Version:A12。谢谢
    2014年7月26日 5:04
  • 你的电脑可以识别显卡就可以,显存不必非与内存相同。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Denimlim>;

    | 请问原本用DDR2内存的主板可以使用DDR3显存的独立显卡吗?显存需要和内存一样吗?还是可以使用DDR3/DDR4/DDR5的显卡。我的电脑是 Dell Inspiron 545s,BIOS Version:A12。谢谢

    2014年7月26日 23:42
    版主