locked
BCCode:_a RRS feed

  • Question

  • Hi there,

    I'm having a problem with bluescreen recently.

    Here's my minidump file links --> https://onedrive.live.com/redir?resid=30E04329F800A6F6!582&authkey=!ANHl-q1wfOT-B4U&ithint=folder%2c

    Thanks,

    Sunday, March 16, 2014 4:13 PM

Answers

  • Ranboy

    This one was inconclusive (we need 2 more) but points to hardware (probably HD).  In the interim I would run a CHKDSK & System file check

    Please run a system file check (SFC)

    All instructions are in our Wiki article below...
    Should you have any questions please ask us.

    System file check (SFC) Scan and Repair System Files

    CHKDSK /R /F
    Chkdsk disclaimer: While performing chkdsk on the hard drive if any bad sectors are found  any data available on that sector might be lost so as usual backup your data.
    Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.
    Do this for each hard drive on your system.
    When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

    Then reboot and let the test run.
    It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.
    http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/


     See "CHKDSK LogFile" below in order to check the results of the test.

    CHKDSK LogFile:

    Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
    Expand the Windows logs heading, then select the Application log file entry.
    Double click on the Source column header.
    Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
    Copy/paste the results into your next post. 

    
    System Uptime: 0 days 1:03:44.398
    Probably caused by : hardware ( nt!KiInsertTimerTable+170 )
    
    
    
    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: fffff2800c3f345d, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, 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: fffff80002a82d30, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002caf100
    GetUlongFromAddress: unable to read from fffff80002caf1c0
     fffff2800c3f345d Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KiInsertTimerTable+170
    fffff800`02a82d30 084c3b7d        or      byte ptr [rbx+rdi+7Dh],cl
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  Photoshop.exe
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    TRAP_FRAME:  fffff88008467900 -- (.trap 0xfffff88008467900)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000009858 rbx=0000000000000000 rcx=000000000000a705
    rdx=fffff88005da5a70 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002a82d30 rsp=fffff88008467a90 rbp=fffffa800515b140
     r8=fffffffffffffff5  r9=00000000000000a0 r10=fffff80002bf2e80
    r11=00000000002f5400 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz ac po nc
    nt!KiInsertTimerTable+0x170:
    fffff800`02a82d30 084c3b7d        or      byte ptr [rbx+rdi+7Dh],cl ds:00000000`0000007d=??
    Resetting default scope
    
    MISALIGNED_IP: 
    nt!KiInsertTimerTable+170
    fffff800`02a82d30 084c3b7d        or      byte ptr [rbx+rdi+7Dh],cl
    
    LAST_CONTROL_TRANSFER:  from fffff80002a77169 to fffff80002a77bc0
    
    STACK_TEXT:  
    fffff880`084677b8 fffff800`02a77169 : 00000000`0000000a fffff280`0c3f345d 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`084677c0 fffff800`02a75de0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`09800560 : nt!KiBugCheckDispatch+0x69
    fffff880`08467900 fffff800`02a82d30 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`0000000f : nt!KiPageFault+0x260
    fffff880`08467a90 fffff800`02a6d752 : fffffa80`098004a0 fffffa80`098004a0 00000000`00000000 00000000`00000000 : nt!KiInsertTimerTable+0x170
    fffff880`08467af0 fffff800`02a7d992 : 00000000`073aff40 fffff960`0009415c 00000000`000000a0 00000000`00000000 : nt!KiCommitThreadWait+0x332
    fffff880`08467b80 fffff800`02d6dcce : fffffa80`098004a0 00000000`073aff40 00000000`00000000 00000000`000000a0 : nt!KeDelayExecutionThread+0x186
    fffff880`08467bf0 fffff800`02a76e53 : fffffa80`098004a0 00000000`00000000 ffffffff`ffff3cb0 00000000`00000000 : nt!NtDelayExecution+0x59
    fffff880`08467c20 00000000`772115fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`073afe88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772115fa
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiInsertTimerTable+170
    fffff800`02a82d30 084c3b7d        or      byte ptr [rbx+rdi+7Dh],cl
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!KiInsertTimerTable+170
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  6.1.7601.18247
    
    MODULE_NAME: hardware
    
    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
    
    BUCKET_ID:  X64_IP_MISALIGNED
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_ip_misaligned
    
    FAILURE_ID_HASH:  {45769616-fd06-8c70-4b8b-74a01eddc0cd}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Sunday, March 16, 2014 7:42 PM
    Sunday, March 16, 2014 4:32 PM

All replies

  • Ranboy

    This one was inconclusive (we need 2 more) but points to hardware (probably HD).  In the interim I would run a CHKDSK & System file check

    Please run a system file check (SFC)

    All instructions are in our Wiki article below...
    Should you have any questions please ask us.

    System file check (SFC) Scan and Repair System Files

    CHKDSK /R /F
    Chkdsk disclaimer: While performing chkdsk on the hard drive if any bad sectors are found  any data available on that sector might be lost so as usual backup your data.
    Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.
    Do this for each hard drive on your system.
    When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

    Then reboot and let the test run.
    It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.
    http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/


     See "CHKDSK LogFile" below in order to check the results of the test.

    CHKDSK LogFile:

    Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
    Expand the Windows logs heading, then select the Application log file entry.
    Double click on the Source column header.
    Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
    Copy/paste the results into your next post. 

    
    System Uptime: 0 days 1:03:44.398
    Probably caused by : hardware ( nt!KiInsertTimerTable+170 )
    
    
    
    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: fffff2800c3f345d, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, 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: fffff80002a82d30, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002caf100
    GetUlongFromAddress: unable to read from fffff80002caf1c0
     fffff2800c3f345d Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KiInsertTimerTable+170
    fffff800`02a82d30 084c3b7d        or      byte ptr [rbx+rdi+7Dh],cl
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  Photoshop.exe
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    TRAP_FRAME:  fffff88008467900 -- (.trap 0xfffff88008467900)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000009858 rbx=0000000000000000 rcx=000000000000a705
    rdx=fffff88005da5a70 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002a82d30 rsp=fffff88008467a90 rbp=fffffa800515b140
     r8=fffffffffffffff5  r9=00000000000000a0 r10=fffff80002bf2e80
    r11=00000000002f5400 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz ac po nc
    nt!KiInsertTimerTable+0x170:
    fffff800`02a82d30 084c3b7d        or      byte ptr [rbx+rdi+7Dh],cl ds:00000000`0000007d=??
    Resetting default scope
    
    MISALIGNED_IP: 
    nt!KiInsertTimerTable+170
    fffff800`02a82d30 084c3b7d        or      byte ptr [rbx+rdi+7Dh],cl
    
    LAST_CONTROL_TRANSFER:  from fffff80002a77169 to fffff80002a77bc0
    
    STACK_TEXT:  
    fffff880`084677b8 fffff800`02a77169 : 00000000`0000000a fffff280`0c3f345d 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`084677c0 fffff800`02a75de0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`09800560 : nt!KiBugCheckDispatch+0x69
    fffff880`08467900 fffff800`02a82d30 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`0000000f : nt!KiPageFault+0x260
    fffff880`08467a90 fffff800`02a6d752 : fffffa80`098004a0 fffffa80`098004a0 00000000`00000000 00000000`00000000 : nt!KiInsertTimerTable+0x170
    fffff880`08467af0 fffff800`02a7d992 : 00000000`073aff40 fffff960`0009415c 00000000`000000a0 00000000`00000000 : nt!KiCommitThreadWait+0x332
    fffff880`08467b80 fffff800`02d6dcce : fffffa80`098004a0 00000000`073aff40 00000000`00000000 00000000`000000a0 : nt!KeDelayExecutionThread+0x186
    fffff880`08467bf0 fffff800`02a76e53 : fffffa80`098004a0 00000000`00000000 ffffffff`ffff3cb0 00000000`00000000 : nt!NtDelayExecution+0x59
    fffff880`08467c20 00000000`772115fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`073afe88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772115fa
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiInsertTimerTable+170
    fffff800`02a82d30 084c3b7d        or      byte ptr [rbx+rdi+7Dh],cl
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!KiInsertTimerTable+170
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  6.1.7601.18247
    
    MODULE_NAME: hardware
    
    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
    
    BUCKET_ID:  X64_IP_MISALIGNED
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_ip_misaligned
    
    FAILURE_ID_HASH:  {45769616-fd06-8c70-4b8b-74a01eddc0cd}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Sunday, March 16, 2014 7:42 PM
    Sunday, March 16, 2014 4:32 PM
  • Thank you very much for the quick response.
    Sunday, March 16, 2014 4:40 PM
  • Ranboy

    Let us know how it works out.


    Wanikiya and Dyami--Team Zigzag

    Sunday, March 16, 2014 5:12 PM