locked
win 7 藍屏 64位元 RRS feed

  • 問題

  •  

    問題簽章:

      問題事件名稱: BlueScreen

      作業系統版本: 6.1.7600.2.0.0.768.3

      地區設定識別碼: 1028

     

    與問題相關的其他資訊:

      BCCode: 1e

      BCP1: 0000000000000000

      BCP2: 0000000000000000

      BCP3: 0000000000000000

      BCP4: 0000000000000000

      OS Version: 6_1_7600

      Service Pack: 0_0

      Product: 768_1

    https://skydrive.live.com/?cid=2d4bf62a6ee525ad&sc=documents&uc=1&id=2D4BF62A6EE525AD%21112#

     

     

    2011年11月11日 上午 06:02

解答

  • 你有超頻或是使用一些記憶體最佳化的工具嗎?因為這一個問題通常都是硬體所引發的

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    Debugger CompCtrlDb Connection::Open failed 80040e4d
    
    EXCEPTION_CODE: (Win32) 0 (0) -    @   Q     C
    
    FAULTING_IP: 
    +3933636337373065
    00000000`00000000 ??              ???
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
    
    BUGCHECK_STR:  0x1E_0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    EXCEPTION_RECORD:  fffff88006a166d8 -- (.exr 0xfffff88006a166d8)
    ExceptionAddress: fffff88001834f57 (CLASSPNP! ?? ::FNODOBFM::`string'+0x0000000000002a3b)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000021
    Attempt to read from address 0000000000000021
    
    TRAP_FRAME:  fffff88006a16780 -- (.trap 0xfffff88006a16780)
    Unable to read trap frame at fffff880`06a16780
    
    LAST_CONTROL_TRANSFER:  from fffff8000407dc2e to fffff80004085ed0
    
    STACK_TEXT:  
    fffff880`06a157b8 fffff800`0407dc2e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`040dc61b : nt!KeBugCheck
    fffff880`06a157c0 fffff800`040abbed : fffff800`04290d94 fffff800`041d3b38 fffff800`04014000 fffff880`06a166d8 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff880`06a157f0 fffff800`040b3250 : fffff800`041d3b30 fffff880`06a15868 fffff880`06a166d8 fffff800`04014000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`06a15820 fffff800`040c01b5 : fffff880`06a166d8 fffff880`06a15f30 fffff880`00000000 00000057`c5cfce00 : nt!RtlDispatchException+0x410
    fffff880`06a15f00 fffff800`04085542 : fffff880`06a166d8 fffffa80`01d0ee70 fffff880`06a16780 00000000`00000005 : nt!KiDispatchException+0x135
    fffff880`06a165a0 fffff800`040840ba : 00000000`00000000 fffffa80`01d0ee70 fffff880`06a16800 fffff880`06a16858 : nt!KiExceptionDispatch+0xc2
    fffff880`06a16780 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiKernelCalloutExceptionHandler+e
    fffff800`0407dc2e 90              nop
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e
    
    FOLLOWUP_NAME:  wintriag
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    
    FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
    
    BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
    
    Followup: wintriag
    


    • 已標示為解答 小鱉 2011年11月11日 下午 03:13
    2011年11月11日 上午 07:40

所有回覆

  • 你有超頻或是使用一些記憶體最佳化的工具嗎?因為這一個問題通常都是硬體所引發的

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    Debugger CompCtrlDb Connection::Open failed 80040e4d
    
    EXCEPTION_CODE: (Win32) 0 (0) -    @   Q     C
    
    FAULTING_IP: 
    +3933636337373065
    00000000`00000000 ??              ???
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
    
    BUGCHECK_STR:  0x1E_0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    EXCEPTION_RECORD:  fffff88006a166d8 -- (.exr 0xfffff88006a166d8)
    ExceptionAddress: fffff88001834f57 (CLASSPNP! ?? ::FNODOBFM::`string'+0x0000000000002a3b)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000021
    Attempt to read from address 0000000000000021
    
    TRAP_FRAME:  fffff88006a16780 -- (.trap 0xfffff88006a16780)
    Unable to read trap frame at fffff880`06a16780
    
    LAST_CONTROL_TRANSFER:  from fffff8000407dc2e to fffff80004085ed0
    
    STACK_TEXT:  
    fffff880`06a157b8 fffff800`0407dc2e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`040dc61b : nt!KeBugCheck
    fffff880`06a157c0 fffff800`040abbed : fffff800`04290d94 fffff800`041d3b38 fffff800`04014000 fffff880`06a166d8 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff880`06a157f0 fffff800`040b3250 : fffff800`041d3b30 fffff880`06a15868 fffff880`06a166d8 fffff800`04014000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`06a15820 fffff800`040c01b5 : fffff880`06a166d8 fffff880`06a15f30 fffff880`00000000 00000057`c5cfce00 : nt!RtlDispatchException+0x410
    fffff880`06a15f00 fffff800`04085542 : fffff880`06a166d8 fffffa80`01d0ee70 fffff880`06a16780 00000000`00000005 : nt!KiDispatchException+0x135
    fffff880`06a165a0 fffff800`040840ba : 00000000`00000000 fffffa80`01d0ee70 fffff880`06a16800 fffff880`06a16858 : nt!KiExceptionDispatch+0xc2
    fffff880`06a16780 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiKernelCalloutExceptionHandler+e
    fffff800`0407dc2e 90              nop
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e
    
    FOLLOWUP_NAME:  wintriag
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    
    FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
    
    BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
    
    Followup: wintriag
    


    • 已標示為解答 小鱉 2011年11月11日 下午 03:13
    2011年11月11日 上午 07:40
  • 什麼是超頻?

    下午又藍屏了

    DMP檔放上去了

     

    2011年11月11日 下午 03:01
  • 超頻的介紹因為你的錯誤有可能是由其他的原因所組成的,所以會建議你先檢查一下

    2011年11月14日 上午 02:31