Now I love my Mac even more

Page 3 of 4 FirstFirst 1234 LastLast

  1. Posts : 13,354
    Windows 7 Professional x64
       #21

    kaipu said:
    zigzag3143 said:
    kaipu said:
    Just crashed thrice with in about 20 mins.
    This time its Adobe Lightroom I was working in.

    Here are the crash dumps:

    Well two of three of these point directly to memory corruption. The other may be memory as well. I know you have run SFC, but am unsure if you have run memtestx86 for at least 7 passes. You may have to run memtest one stick at a time to find which is bad. You may also want to test the mobo slots in the same way

    I DID NOTICE THAT CAPTUREONE WAS RUNNING IN TWO OF THESE.

    Let us know if you need help


    Ken
    Code:
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Fri Jun 18 11:01:54.573 2010 (GMT-4)
    System Uptime: 0 days 0:06:38.009
    BugCheck 50, {fffff6800211a718, 0, fffff80002a951e2, 2}
    Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1c2 )
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  CaptureOne.exe
    Hi Ken,
    Thanks for the reply.

    Yes I did run Memtest86 with all the sticks in place and it passed near about 9 passes successfully.
    Do I really need to run it on individual sticks?

    Here's the screenshot of the last test:


    It happens all the time, while running Adobe Bridge, Adobe Lightroom etc.
    I'll uninstall the CaptureOne and see if it makes any difference.
    No, there is no need to run it on individual sticks. If it passed on all of them, it is safe to say each stick and slot passed.

    Please enable driver verifier: Using Driver Verifier to identify issues with Drivers

    You should also test your hard drive, on account of the first dmp. See this link: HD Diagnostic
      My Computer


  2. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #22

    After you run Driver Verifier and if you have another BSOD, I suggest you uninstall your Adobe software and see if that solves the problem. I am not very happy with some Adobe products.

    Make sure for diagnosing that you uninstall all 3rd party firewalls, anti-virus programs, and anti-malware programs (if they are resident programs). Install MSE and turn on Windows Firewall. Since these are MS programs, they are very unlikely to cause problems.

    If uninstalling Adobe software solves the problem, re-install one at a time and run for a while. Create a restore point and and re-install the next one and so forth.
      My Computer


  3. Posts : 14
    Windows 7 Home Premium 64-bit
       #23

    I was also just starting to think that you have a corrupted install. Carl is probably right, considering that you've already run systems file checker and memtest. I hope this solves it.
      My Computer


  4. Posts : 14
    Windows 7 64 bit
    Thread Starter
       #24

    Just crashed 7 times… Doing different things like browsing pictures folder with windows picture viewer, Uninstalling softwares (I uninstalled all Adobe software except for adobe flash).

    Here are the dump files:
      My Computer


  5. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #25
      My Computer


  6. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #26

    All of these dumps indicate hardware problems. In the 10 dumps, you had only 4 different error codes. The first of these, the dump from yesterday gives a stop error code of 124. Read through this link:

    [2-Int] Stop 0x124 - what it means and what to try

    Here are the other three error codes


    STOP 0x0000001A: MEMORY_MANAGEMENT

    Usual causes: Device driver, memory, kernel

    STOP 0x000000C1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

    Usual causes: Device driver, ?Memory

    STOP 0x00000019: BAD_POOL_HEADER

    Usual causes: Device driver

    Notice that device driver is mentioned as a possible cause in all three of these and in the 124 error code as well. Your next step is to run Driver Verifier.
      My Computer


  7. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #27

    Here are the dmp analyzes

    Code:
     *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa8006852038, 0, 0}
    
    Probably caused by : hardware
    
    Followup: MachineOwner
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {5003, fffff70001080000, 107d3, 31bf2009}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b86 )
    
    Followup: MachineOwner
    ---------
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000005003, The subtype of the bugcheck.
    Arg2: fffff70001080000
    Arg3: 00000000000107d3
    Arg4: 0000000031bf2009
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_5003
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  Photoshop.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002ae18c6 to fffff80002a79600
    
    STACK_TEXT:  
    fffff880`06d2a2e8 fffff800`02ae18c6 : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`000107d3 : nt!KeBugCheckEx
    fffff880`06d2a2f0 fffff800`02a93f2c : fffff680`0018df78 fffff880`06d2a3c0 00000000`00000000 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x21b86
    fffff880`06d2a340 fffff800`02a776ee : 00000000`00000001 00000000`00000000 00000000`39040801 00000000`00000004 : nt!MmAccessFault+0xc4c
    fffff880`06d2a4a0 000007fe`fbb6cb60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`0012d7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fbb6cb60
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+21b86
    fffff800`02ae18c6 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+21b86
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb
    
    FAILURE_BUCKET_ID:  X64_0x1a_5003_VRF_nt!_??_::FNODOBFM::_string_+21b86
    
    BUCKET_ID:  X64_0x1a_5003_VRF_nt!_??_::FNODOBFM::_string_+21b86
    
    Followup: MachineOwner
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C1, {fffff9801e68aaf0, fffff9801e68a2e4, 2f0508, 32}
    
    Probably caused by : win32k.sys ( win32k!xxxMsgWaitForMultipleObjects+108 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    
    SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
    Special pool has detected memory corruption.  Typically the current thread's
    stack backtrace will reveal the guilty party.
    Arguments:
    Arg1: fffff9801e68aaf0, address trying to free
    Arg2: fffff9801e68a2e4, address where one bit is corrupted
    Arg3: 00000000002f0508, (reserved)
    Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xC1_32
    
    SPECIAL_POOL_CORRUPTION_TYPE:  32
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  csrss.exe
    
    CURRENT_IRQL:  1
    
    LAST_CONTROL_TRANSFER:  from fffff80002b4c523 to fffff80002abc600
    
    STACK_TEXT:  
    fffff880`02961468 fffff800`02b4c523 : 00000000`000000c1 fffff980`1e68aaf0 fffff980`1e68a2e4 00000000`002f0508 : nt!KeBugCheckEx
    fffff880`02961470 fffff800`02bc35d3 : fffff880`00000003 fffffa80`092b4060 00000000`00000297 fffff800`02f4fdfe : nt!MiCheckSpecialPoolSlop+0x83
    fffff880`029614b0 fffff800`02bef356 : fffff800`02a4c000 00000000`2b707249 00000000`00935c00 00000000`00000001 : nt!MmFreeSpecialPool+0x1d3
    fffff880`029615e0 fffff800`02f61026 : fffffa80`08ee9302 fffffa80`08ee9310 00000000`00000000 fffff980`1e68aaf0 : nt!ExFreePool+0x9f3
    fffff880`02961690 fffff800`02f615ec : fffff800`02a98f35 fffff980`1e68aaf0 00000000`00000000 fffffa80`0981a630 : nt!VfIoFreeIrp+0xe6
    fffff880`029616c0 fffff800`02a98f35 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IovFreeIrpPrivate+0x5c
    fffff880`02961700 fffff800`02ac395d : fffffa80`0981a5e0 00000000`00000000 fffff960`00177924 00000000`00000000 : nt!KiDeliverApc+0x13d
    fffff880`02961780 fffff800`02abfc4b : 00000000`00000000 00000000`00000002 fffffa80`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x3dd
    fffff880`02961810 fffff960`001187f0 : fffff900`00000002 fffffa80`09155080 fffff900`00000001 fffff880`0000000d : nt!KeWaitForMultipleObjects+0x271
    fffff880`02961ac0 fffff960`0011970c : 00000000`00000000 fffff900`c0127010 fffff960`0035f340 fffff900`c012b640 : win32k!xxxMsgWaitForMultipleObjects+0x108
    fffff880`02961b40 fffff960`000d4634 : fffffa80`00000001 fffffa80`0000000c fffffa80`0981a5e0 fffff6fc`40014a70 : win32k!xxxDesktopThread+0x254
    fffff880`02961bc0 fffff960`00153fa6 : fffffa80`00000001 fffff960`0035f340 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x64
    fffff880`02961bf0 fffff800`02abb853 : fffffa80`0981a5e0 00000000`00000004 000007ff`fffae000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
    fffff880`02961c20 000007fe`fcd63d3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`01dcfd48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fcd63d3a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    win32k!xxxMsgWaitForMultipleObjects+108
    fffff960`001187f0 8bf0            mov     esi,eax
    
    SYMBOL_STACK_INDEX:  9
    
    SYMBOL_NAME:  win32k!xxxMsgWaitForMultipleObjects+108
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: win32k
    
    IMAGE_NAME:  win32k.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bdc4376
    
    FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_win32k!xxxMsgWaitForMultipleObjects+108
    
    BUCKET_ID:  X64_0xC1_32_VRF_win32k!xxxMsgWaitForMultipleObjects+108
    
    Followup: MachineOwner
    
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 19, {3, fffff80002c049f0, fffff80002c049f0, fffff80402c049f0}
    
    Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )
    
    Followup: Pool_corruption
    ---------
    
    0: kd> !analyze -v
    
    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Arguments:
    Arg1: 0000000000000003, the pool freelist is corrupt.
    Arg2: fffff80002c049f0, the pool entry being checked.
    Arg3: fffff80002c049f0, the read back flink freelist value (should be the same as 2).
    Arg4: fffff80402c049f0, the read back blink freelist value (should be the same as 2).
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x19_3
    
    CUSTOMER_CRASH_COUNT:  2
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002ba8d6f to fffff80002a75600
    
    STACK_TEXT:  
    fffff800`00ba2c28 fffff800`02ba8d6f : 00000000`00000019 00000000`00000003 fffff800`02c049f0 fffff800`02c049f0 : nt!KeBugCheckEx
    fffff800`00ba2c30 fffff800`02fe5527 : 00000000`00000000 00000000`00000010 00000000`00000002 fffffa80`00000000 : nt!ExFreePool+0x536
    fffff800`00ba2d20 fffff800`02fe5420 : fffffa80`08efc050 00000000`00000010 fffffa80`00000028 fffff880`03a5bdd7 : hal!HalBuildScatterGatherList+0xfb
    fffff800`00ba2d90 fffff880`03a5a52e : fffffa80`08efc050 00000000`00000000 fffffa80`08efcd20 fffffa80`07637310 : hal!HalGetScatterGatherList+0x44
    fffff800`00ba2df0 fffff880`03a57e86 : fffffa80`0961f2d0 fffffa80`08efc050 fffff800`02fe53dc fffffa80`08efc1a0 : USBPORT!USBPORT_Core_iMapTransfer+0x24a
    fffff800`00ba2e70 fffff880`03a48f89 : fffffa80`08efc050 00000000`00000000 fffffa80`08efcd02 fffffa80`08efcd20 : USBPORT!USBPORT_Core_UsbMapDpc_Worker+0x296
    fffff800`00ba2ed0 fffff800`02a80cdc : fffff800`02befe80 fffffa80`08efcd20 fffffa80`08efcd38 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
    fffff800`00ba2f00 fffff800`02a7b765 : 00000000`00000000 fffffa80`094d1b60 00000000`00000000 fffff880`03a48db0 : nt!KiRetireDpcList+0x1bc
    fffff800`00ba2fb0 fffff800`02a7b57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
    fffff880`0217cf00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!ExFreePool+536
    fffff800`02ba8d6f cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!ExFreePool+536
    
    FOLLOWUP_NAME:  Pool_corruption
    
    IMAGE_NAME:  Pool_Corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: Pool_Corruption
    
    FAILURE_BUCKET_ID:  X64_0x19_3_VRF_nt!ExFreePool+536
    
    BUCKET_ID:  X64_0x19_3_VRF_nt!ExFreePool+536
    
    Followup: Pool_corruption
    I posted only one example of each error code.
    Last edited by CarlTR6; 19 Jun 2010 at 18:57.
      My Computer


  8. Posts : 13,354
    Windows 7 Professional x64
       #28

    Almost certainly caused by hardware.

    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
      My Computer


  9. Posts : 14
    Windows 7 64 bit
    Thread Starter
       #29

    Jonathan_King said:
    Almost certainly caused by hardware.

    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
    Thanks Jonathan,

    I did that for 9 Passes and all the passes were successfully passed.
    Here is the final picture:
      My Computer


  10. Posts : 14
    Windows 7 64 bit
    Thread Starter
       #30

    CarlTR6 said:
    Thanks Carl,
    Highly appreciate your help.

    I also did the "Driver Verifier" thing but don't know how its supposed to work.
    I set it up and restarted the PC but nothing happened, How can I know that its running?
    Does it create any log?
    I thought its not running and tried to set it up again but it set "No Changes Were Made", Does it mean that its running?

    Many a times I get this message that "Com Surrogate" stopped working.

    I left the PC open last night and set the power options to never sleep HDD and Monitor, and it crashed twice while nothing was happening.
    Then I thought of backing up my data and doing a clean reinstall, but it crashed everytime I tried copying the data to my external drive.

    Please help guys, this is killing me.

    Here are the dump files:
    The latest two are while I was copying the data.
    The middle one is "Com Surrogate".
    The Last two are the ones while the computer was ideal.
      My Computer


 
Page 3 of 4 FirstFirst 1234 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 02:27.
Find Us