Physical memory dump

Page 1 of 2 12 LastLast

  1. Posts : 5
    Windows 7 Professional 64-bit
       #1

    Physical memory dump


    Windows 7 is x86, the original OS

    I just built this new PC:
    M/B: GA-X58A-UD3R
    M/B cooler: Mugen 2B
    CPU: Core-i7 930
    PSU: 600W extreme power plus
    RAM: (2) 4GB DDR3 - OCZ
    Case: Thermaltake
    OS: Windows 7 Pro x86

    With all that out of the way, what is happening is everytime I start up the computer it now performs a physical memory dump a few seconds after the desktop appears and everything seems loaded. It happened once after no problems of using the new computer for 6 days and then nothing for 3 days. Then it happened again, where there after each time the computer was turned on. Doesn't happen when coming out of sleep/hibernation.

    If I messed something up with the upload I'm sorry, tell me and I'll fix it. I put the PERFMON in the compressed folder if that messes things up I'll repost everything. Any and all help I'll be grateful for. Also side question the CD for the Windows 7 says 64-bit software on it, but the folder for programs is x86 so that means 32-bit correct?
      My Computer


  2. Posts : 507
    Windows 7 Ultimate x64 SP1
       #2

    hi,
    Most of your dumps have error code 0x1e ; 0x1 ; 0x3d ; 0x7e which point to driver causing problem.

    Start with updating your Gigabyte Easy tune because that drivers are out of date, then we'll see if the problem persist.
    Motherboard - GIGABYTE

    These drivers need to do update:
    Code:
    GVTDrv64.sys Tue Sep 05 00:10:02 2006 (44FD22CA)
    WMP54Gv41x64.sys Mon Dec 11 06:37:57 2006 (457D6D45)
    Logs
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    
    Followup: MachineOwner
    ---------
    
    6: kd> !analyze -v
    *******************************************************************************
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3D, {fffff88003121000, 0, 0, fffff8800483f504}
    
    Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Probably caused by : ataport.SYS ( ataport!IdeStartIoCallBack+2e )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff80002db9f9a, fffff880033853e8, fffff88003384c50}
    
    Probably caused by : AppleCharger.sys ( AppleCharger+26c0 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\WMP54Gv41x64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for WMP54Gv41x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for WMP54Gv41x64.sys
    Probably caused by : WMP54Gv41x64.sys ( WMP54Gv41x64+165b8 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    APC_INDEX_MISMATCH (1)
    This is a kernel internal error. The most common reason to see this
    bugcheck is when a filesystem or a driver has a mismatched number of
    calls to disable and re-enable APCs. The key data item is the
    Thread->KernelApcDisable field. A negative value indicates that a driver
    has disabled APC calls without re-enabling them.  A positive value indicates
    that the reverse is true. This check is made on exit from a system call.
    Arguments:
    Arg1: 0000000075692dd9, address of system function (system call)
    Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
    Arg3: 0000000000040000, Thread->KernelApcDisable
    Arg4: fffff88003c77ca0, Previous KernelApcDisable
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    +65e2952f039bdab0
    00000000`75692dd9 ??              ???
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1
    
    PROCESS_NAME:  des2svr.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002a70ca9 to fffff80002a71740
    
    STACK_TEXT:  
    fffff880`03c77ad8 fffff800`02a70ca9 : 00000000`00000001 00000000`75692dd9 00000000`00000000 00000000`00040000 : nt!KeBugCheckEx
    fffff880`03c77ae0 fffff800`02a70be0 : fffffa80`08accb60 fffff880`03c77ca0 ffffffff`fff0bdc0 fffffa80`00008000 : nt!KiBugCheckDispatch+0x69
    fffff880`03c77c20 00000000`75692dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
    00000000`0064f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75692dd9
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiSystemServiceExit+245
    fffff800`02a70be0 4883ec50        sub     rsp,50h
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiSystemServiceExit+245
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    FAILURE_BUCKET_ID:  X64_0x1_nt!KiSystemServiceExit+245
    
    BUCKET_ID:  X64_0x1_nt!KiSystemServiceExit+245
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 5
    Windows 7 Professional 64-bit
    Thread Starter
       #3

    I updated my Easy Tunes 6 and Nvidia driver, but got another dump when I tryied to play SC2(ultra).
      My Computer


  4. Posts : 507
    Windows 7 Ultimate x64 SP1
       #4

    Ok I see that you have updated Gigabyte easy tune, but not for the Linksys Wireless Adapter.
    I've ran your dumps again with various result of bugcheck code (0x34; 0x1e; 0x24; 0x3d; 0x7e)
    Each of them caused by : applecharger, ntkrnlmp.exe, WMP54Gv41x64.sys(Linksys), Ntfs.sys , ataport.sys, CI.dll

    Here are my suggestions :

    1. Perform check disk -> command prompt(as admin) -> chkdsk /r /f -> enter
    2. Do system file checker -> command prompt(as administrator) -> sfc /scannow -> enter
    3. Update your Linksys wireless adapter.
    4. If the problem persist, Enable driver verifier and wait until your windows crash. Then attach the new dump here.

    This driver need to do update:
    Code:
    WMP54Gv41x64.sys Mon Dec 11 21:37:57 2006 (457D6D45)
    Logs
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff80002da5b2a, 0, 4e}
    
    Unable to load image \SystemRoot\system32\DRIVERS\AppleCharger.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for AppleCharger.sys
    *** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
    Probably caused by : AppleCharger.sys ( AppleCharger+26c0 )
    
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff80002d5ef9a, 0, 4e}
    
    Unable to load image \SystemRoot\system32\DRIVERS\AppleCharger.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for AppleCharger.sys
    *** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
    Probably caused by : AppleCharger.sys ( AppleCharger+26c0 )
    
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff88000c0b263, 0, ffffffffffffffff}
    
    Probably caused by : CI.dll ( CI!CiValidateImageData+2f )
    
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 24, {1904fb, fffff880091e5088, fffff880091e48f0, fffff80002acfd46}
    
    Probably caused by : Ntfs.sys ( Ntfs+cb642 )
    
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1, {75692dd9, 0, 40000, fffff88003c77ca0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
    
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Probably caused by : ataport.SYS ( ataport!IdeStartIoCallBack+2e )
    
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Probably caused by : ataport.SYS ( ataport!IdeStartIoCallBack+2e )
    
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\WMP54Gv41x64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for WMP54Gv41x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for WMP54Gv41x64.sys
    Probably caused by : WMP54Gv41x64.sys ( WMP54Gv41x64+165b8 )
    
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff80002ac98b6, fffff880090277d8, fffff88009027040}
    
    Probably caused by : WMP54Gv41x64.sys ( WMP54Gv41x64+3252 )
    
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Probably caused by : afd.sys ( afd!AfdTimeoutPoll+22 )
    
    Followup: MachineOwner
    CACHE_MANAGER (34)
        See the comment for FAT_FILE_SYSTEM (0x23)
    Arguments:
    Arg1: 0000000000050830
    Arg2: fffff8800334d6c8
    Arg3: fffff8800334cf30
    Arg4: fffff80002a86905
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_RECORD:  fffff8800334d6c8 -- (.exr 0xfffff8800334d6c8)
    ExceptionAddress: fffff80002a86905 (nt!ExpInterlockedPopEntrySListFault16)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffff8800334cf30 -- (.cxr 0xfffff8800334cf30)
    rax=0000000019cc0004 rbx=fffff80002c11660 rcx=fffff80002c11670
    rdx=fffbfa8007e69f81 rsi=0000000000000030 rdi=0000000000000030
    rip=fffff80002a86905 rsp=fffff8800334d900 rbp=fffff8800334d9c0
     r8=fffbfa8007e69f80  r9=0000000000000030 r10=fffff80002c11670
    r11=fffff8a008fc8000 r12=0000000011fd08c7 r13=fffff8800334d978
    r14=fffff8800334d970 r15=0000000000000011
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    nt!ExpInterlockedPopEntrySListFault16:
    fffff800`02a86905 498b08          mov     rcx,qword ptr [r8] ds:002b:fffbfa80`07e69f80=????????????????
    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 fffff80002cbb0e0
     ffffffffffffffff 
    
    FOLLOWUP_IP: 
    nt!ExpInterlockedPopEntrySListFault16+0
    fffff800`02a86905 498b08          mov     rcx,qword ptr [r8]
    
    FAULTING_IP: 
    nt!ExpInterlockedPopEntrySListFault16+0
    fffff800`02a86905 498b08          mov     rcx,qword ptr [r8]
    
    BUGCHECK_STR:  0x34
    
    LAST_CONTROL_TRANSFER:  from fffff80002a6e419 to fffff80002a86905
    
    STACK_TEXT:  
    fffff880`0334d900 fffff800`02a6e419 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16
    fffff880`0334d910 fffff800`02a4bcbf : 00000000`00000001 fffff880`0334d9c0 00000000`00000018 00000000`00000030 : nt!PfFbLogEntryReserve+0x59
    fffff880`0334d950 fffff800`02e3e7c9 : 00000000`00000001 00000000`00000001 fffff8a0`0a19f6f0 00000000`00000000 : nt!PfLogEvent+0x4f
    fffff880`0334d9a0 fffff800`02db922e : fffffa80`074efa10 c774d318`a94e263e 00000000`00000000 00000000`00000000 : nt!PfCheckDeprioritizeFile+0x419
    fffff880`0334da10 fffff800`02a9c567 : 00000000`00000000 fffffa80`066f5ff0 00000000`00000000 00000000`00040000 : nt! ?? ::NNGAKEGL::`string'+0x19266
    fffff880`0334da50 fffff800`02a73274 : 00000000`00000001 fffffa80`074eeb20 fffffa80`074efa00 00000000`00000000 : nt!CcUnmapVacbArray+0x1b7
    fffff880`0334dae0 fffff800`02a76d1c : fffffa80`074efa10 00000000`00000011 fffffa80`074efa10 00000000`00000000 : nt!CcDeleteSharedCacheMap+0x140
    fffff880`0334db50 fffff800`02a77520 : fffff800`02c8a100 fffff880`0334dc58 00000000`00000000 fffff800`00000000 : nt!CcWriteBehind+0x5bc
    fffff880`0334dc00 fffff800`02a90961 : fffffa80`06729550 fffff800`02d7fc20 fffff800`02c8a140 fffffa80`00000003 : nt!CcWorkerThread+0x1c8
    fffff880`0334dcb0 fffff800`02d27c06 : 9b279b27`16081608 fffffa80`06723040 00000000`00000080 fffffa80`06705040 : nt!ExpWorkerThread+0x111
    fffff880`0334dd40 fffff800`02a61c26 : fffff880`0316a180 fffffa80`06723040 fffff880`031750c0 56e156e1`baa9baa9 : nt!PspSystemThreadStartup+0x5a
    fffff880`0334dd80 00000000`00000000 : fffff880`0334e000 fffff880`03348000 fffff880`0334d9f0 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!ExpInterlockedPopEntrySListFault16+0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    STACK_COMMAND:  .cxr 0xfffff8800334cf30 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x34_nt!ExpInterlockedPopEntrySListFault16+0
    
    BUCKET_ID:  X64_0x34_nt!ExpInterlockedPopEntrySListFault16+0
    
    Followup: MachineOwner
    ---------
      My Computer


  5. Posts : 712
    Windows 7 x64, Windows XP SP3, Fedora
       #5

    Hi,

    As wish mentioned - your Linksys Wireless driver really needs an update. If you can't locate a suitable updated driver for it then you will have to stop using it as it is blamed directly in several of your BSODs (as WMP54Gv41x64.sys).

    The other 3rd Party driver that is blamed a lot - AppleCharger.sys

    This driver is part of this utility that probably came on your motherboard installation CD.The "quick-charge" utility is not really necessary, and this isn't the first time I have seen it causing BSODs, so you would be wise to uninstall it.

    You can uninstall it with Revo Uninstaller - Revo Uninstaller Pro - Downloads

    Also - you may want to use Revo to get rid of Gigabyte EasyTune6 - as it's driver is still out of date:
    Code:
    GVTDrv64.sys Tue Sep 05 19:10:02 2006 (44FD22CA)
    Regards,
    Reventon

    BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Oct 18 09:03:39.022 2010 (GMT+13)
    System Uptime: 0 days 0:10:07.004
    Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    BUGCHECK_STR:  0x34
    Bugcheck code 00000034
    Arguments 00000000`00050830 fffff880`0334d6c8 fffff880`0334cf30 fffff800`02a86905
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Oct 17 20:16:15.431 2010 (GMT+13)
    System Uptime: 0 days 4:21:27.125
    *** WARNING: Unable to verify timestamp for AppleCharger.sys
    *** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
    Probably caused by : AppleCharger.sys  ( AppleCharger+26c0 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  wininit.exe
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff800`02d5ef9a 00000000`00000000 00000000`0000004e
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Oct 17 15:32:18.499 2010 (GMT+13)
    System Uptime: 0 days 0:01:58.592
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  System
    Bugcheck code 0000001E
    Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Oct 17 15:29:36.681 2010 (GMT+13)
    System Uptime: 0 days 0:04:27.774
    Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x1
    PROCESS_NAME:  des2svr.exe
    Bugcheck code 00000001
    Arguments 00000000`75692dd9 00000000`00000000 00000000`00040000 fffff880`03c77ca0
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Oct 17 15:24:23.046 2010 (GMT+13)
    System Uptime: 0 days 0:00:47.139
    Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3D
    PROCESS_NAME:  System
    Bugcheck code 0000003D
    Arguments fffff880`03121000 00000000`00000000 00000000`00000000 fffff880`0483f504
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Oct 17 15:22:47.795 2010 (GMT+13)
    System Uptime: 1 days 21:15:07.888
    Probably caused by : ataport.SYS ( ataport!IdeStartIoCallBack+2e )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  System
    Bugcheck code 0000001E
    Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Oct 15 18:06:28.789 2010 (GMT+13)
    System Uptime: 0 days 2:46:41.881
    *** WARNING: Unable to verify timestamp for AppleCharger.sys
    *** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
    Probably caused by : AppleCharger.sys ( AppleCharger+26c0 )
    PROCESS_NAME:  System
    BUGCHECK_STR:  0x7E
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    Bugcheck code 1000007E
    Arguments ffffffff`c0000005 fffff800`02db9f9a fffff880`033853e8 fffff880`03384c50
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Oct 15 15:18:36.607 2010 (GMT+13)
    System Uptime: 0 days 0:04:24.700
    *** WARNING: Unable to verify timestamp for WMP54Gv41x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for WMP54Gv41x64.sys
    Probably caused by : WMP54Gv41x64.sys ( WMP54Gv41x64+165b8 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  System
    Bugcheck code 0000001E
    Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Oct 14 22:02:17.706 2010 (GMT+13)
    System Uptime: 0 days 7:12:55.799
    *** WARNING: Unable to verify timestamp for WMP54Gv41x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for WMP54Gv41x64.sys
    Probably caused by : WMP54Gv41x64.sys ( WMP54Gv41x64+3252 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    BUGCHECK_STR:  0x7E
    Bugcheck code 1000007E
    Arguments ffffffff`c0000005 fffff800`02ac98b6 fffff880`090277d8 fffff880`09027040
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Oct 14 14:48:39.611 2010 (GMT+13)
    System Uptime: 0 days 0:00:58.704
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  System
    Bugcheck code 0000001E
    Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Oct 14 14:46:58.002 2010 (GMT+13)
    System Uptime: 0 days 0:00:24.095
    *** WARNING: Unable to verify timestamp for WMP54Gv41x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for WMP54Gv41x64.sys
    Probably caused by : WMP54Gv41x64.sys ( WMP54Gv41x64+e78a )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  System
    Bugcheck code 0000001E
    Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Oct 14 10:51:34.310 2010 (GMT+13)
    System Uptime: 0 days 0:00:12.403
    Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e )
    BUGCHECK_STR:  0x1a_1238
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    Bugcheck code 0000001A
    Arguments 00000000`00001238 fffffa80`082fcd90 00000000`00000802 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Mon Oct 11 15:45:44.915 2010 (GMT+13)
    System Uptime: 0 days 6:02:37.847
    *** WARNING: Unable to verify timestamp for AppleCharger.sys
    *** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
    Probably caused by : AppleCharger.sys  ( AppleCharger+26c0 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  wininit.exe
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff800`02da5b2a 00000000`00000000 00000000`0000004e
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Fri Oct  8 13:37:21.929 2010 (GMT+13)
    System Uptime: 0 days 0:02:54.022
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  System
    Bugcheck code 0000001E
    Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Fri Oct  8 10:01:32.324 2010 (GMT+13)
    System Uptime: 0 days 0:00:28.416
    Probably caused by : afd.sys ( afd!AfdTimeoutPoll+22 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  System
    Bugcheck code 0000001E
    Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      My Computer


  6. Posts : 5
    Windows 7 Professional 64-bit
    Thread Starter
       #6

    Ok, I took care of the Applecharger, and updated Linksys with an appropriate driver (I think, since the only ones were for XP or Vista, so I chose the vista). The lastest dump said ASC .sys. What file is that and what should I do? If the dump is needed to determine then I can get it again.
      My Computer


  7. Posts : 507
    Windows 7 Ultimate x64 SP1
       #7

    @Reventon
    Thanks for the assist

    @Zumpin
    Yes you should attach the new dump here.
      My Computer


  8. Posts : 5
    Windows 7 Professional 64-bit
    Thread Starter
       #8

    Here's the newest batch.
      My Computer


  9. Posts : 712
    Windows 7 x64, Windows XP SP3, Fedora
       #9

    Hi,

    A few dumps, but no clear cause.

    Turn Driver Verifier on and see what it picks up (if anything) - Using Driver Verifier to identify issues with Drivers

    Regards,
    Reventon

    BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Oct 24 09:38:11.907 2010 (GMT+13)
    System Uptime: 0 days 1:08:48.000
    Probably caused by : ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+5f )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  SearchProtocol
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff800`02dcb93f fffff880`08164020 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Oct 24 08:28:14.441 2010 (GMT+13)
    System Uptime: 0 days 0:00:59.534
    Probably caused by : i8042prt.sys ( i8042prt!memmove+64 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3D
    PROCESS_NAME:  System
    Bugcheck code 0000003D
    Arguments fffff880`03121000 00000000`00000000 00000000`00000000 fffff880`048ea504
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Oct 24 08:26:28.441 2010 (GMT+13)
    System Uptime: 0 days 0:03:25.534
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  System
    Bugcheck code 0000001E
    Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Oct 23 15:38:57.833 2010 (GMT+13)
    System Uptime: 0 days 0:02:58.926
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  System
    Bugcheck code 0000001E
    Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Wed Oct 20 12:48:39.054 2010 (GMT+13)
    System Uptime: 0 days 0:03:31.146
    Probably caused by : afd.sys ( afd!AfdPoll32+412 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  iexplore.exe
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff880`042d39d2 fffff880`03d57f00 00000000`00000000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      My Computer


  10. Posts : 5
    Windows 7 Professional 64-bit
    Thread Starter
       #10

    After many a detour in life here's the newest dumps with the verifier on:
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd
All times are GMT -5. The time now is 01:36.
Find Us