BSOD and constant crashes with Photoshop after adding more RAM

Page 1 of 3 123 LastLast

  1. Posts : 13
    Windows 7 Ultimate x64
       #1

    BSOD and constant crashes with Photoshop after adding more RAM


    Hi,
    I just got new memory sticks for my computer. And it was doing wonders for a month or so now. But last few days were impossible because of the constant crashes while using Photoshop or Illustrator.
    Also I ran a bunch of Windows updates recently as well, but it seems like it only made the situation worse.
    MemTest and Windows Memory diagnostics didn't show any errors.
    SO here I am, hoping that someone here can help me to understand and fix this annoying issue.
    Thanks in advance.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    It is a stop 0x124. Hardware issue.

    You are saying that you have added more RAM, and then it all started. It is possible, if the additional RAM is mismatch. Remove the additional RAM. Check the situation at the original RAM first. Is it still crashing? If yes, let us know, we will go for further steps.

    If not, then the additional memory is mismatch.
    _____________________________________________________________________________________
    BSOD ANALYSIS:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa800832b038, 0, 0}
    
    Probably caused by : AuthenticAMD
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa800832b038, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`0337e5b0 fffff800`030d8ca9 : fffffa80`0832b010 fffffa80`06eb2040 00000000`0000000a 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`0337ead0 fffff800`02fb9e87 : fffffa80`0832b010 fffff800`030332d8 fffffa80`06eb2040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`0337eb00 fffff800`02f21285 : fffff800`03094ae0 fffff800`02e9723d 00000000`00000010 00000000`00000206 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`0337eb40 fffff800`02e97251 : fffff880`011d7e00 fffff800`02f21260 fffffa80`06eb2000 fffffa80`06eb2040 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`0337eb70 fffff800`0312bede : 00000000`00000000 fffffa80`06eb2040 00000000`00000080 fffffa80`06ca1840 : nt!ExpWorkerThread+0x111
    fffff880`0337ec00 fffff800`02e7e906 : fffff880`03189180 fffffa80`06eb2040 fffff880`031940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`0337ec40 00000000`00000000 : fffff880`0337f000 fffff880`03379000 fffff880`0337e0d0 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: AuthenticAMD
    
    IMAGE_NAME:  AuthenticAMD
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 13
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Thanks Arc for a fast reply. Your solution helped but just temporarily.
    So I switched back to the original memory sticks. And right after that I couldn't even start Windows, not even in a Safe Mode. I had to boot from the installation CD and run a system repair. I got back to normal for two days.
    But this afternoon I got a crash again. I wasn't even using Photoshop or any other demanding software, just browsing the web via Google Chrome.
    I'm attaching another portion of files for you to analyze. I really hope that there's nothing serious with the mother board or the processor (I replaced them less than a year ago).
    Thanks again!!
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    Changing/replacing RAM does not have any bearing on bootloader. So I cannot say why it happened.

    No new crash dump is there in the zip after that one of 24th. And event logs are not giving any idea of a further BSOD, too.

    There is an event about storage controllers.
    Event[34256]:
    Log Name: System
    Source: Disk
    Date: 2013-02-05T13:32:42.234
    Event ID: 11
    Task: N/A
    Level: Error
    Opcode: N/A
    Keyword: Classic
    User: N/A
    User Name: N/A
    Computer: Black_Maze
    Description:
    The driver detected a controller error on \Device\Harddisk2\DR2.
    The controller is AMD SATA Controller, which is of 2001.
    Code:
        Image name: amd_sata.sys
        Timestamp:        Tue Dec 13 02:22:00 2011 (4EE66970)
    Update it from AMD Chipset Drivers, it is a part of the chipset driver.

    Though there is no BSOD dump or event, cannot say anything specifically. But you hay have a try by uninstalling PeerBlock.
      My Computer


  5. Posts : 13
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Thank you. I will follow your advice. I don't even know why I still have PeerBlock, I used it like once...

    P.S. are you saying changing RAM didn't cause the BSOD in the first place??
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    meeory said:
    P.S. are you saying changing RAM didn't cause the BSOD in the first place??
    Lol ... does it anyhow mean that I have said it? I have said
    Arc said:
    Changing/replacing RAM does not have any bearing on bootloader. So I cannot say why it happened.
    again your statement

    meeory said:
    So I switched back to the original memory sticks. And right after that I couldn't even start Windows, not even in a Safe Mode. I had to boot from the installation CD and run a system repair. I got back to normal for two days.
    Its unnatural. RAM has nothing to do with bootloader. Changing RAM cannot make windows unbootable in a way that startup repair can recover it.
      My Computer


  7. Posts : 13
    Windows 7 Ultimate x64
    Thread Starter
       #7

    Alright, thanks for clearing this up.

    So got another Blue Screen few minutes ago while checking Facebook... I'm running it on the original RAM.

    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 124
    BCP1: 0000000000000000
    BCP2: FFFFFA80052678F8
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Any further suggestions?
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    meeory said:
    Alright, thanks for clearing this up.

    So got another Blue Screen few minutes ago while checking Facebook... I'm running it on the original RAM.

    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 124
    BCP1: 0000000000000000
    BCP2: FFFFFA80052678F8
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Any further suggestions?
    A said earlier, ox124 is a hardware issue.

    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Stress test the CPU.
    Hardware - Stress Test With Prime95

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
    At least 30% free is safe. Also let us know the wattage of the PSU.
      My Computer


  9. Posts : 13
    Windows 7 Ultimate x64
    Thread Starter
       #9

    Thank you, going to run all the test tomorrow (was out of town for the weekend).

    Here is another question though: my computer randomly wakes up from the sleeping mode and doesn't stay 'sleeping' for a long time, keeps booting up. Is it an indicator of a software or a hardware issue?
      My Computer


  10. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #10

    It restarts during sleep. Any PnP device or its driver may cause it. It may be troubleshooted later, but first let us concentrate on the issue under analysis?
      My Computer


 
Page 1 of 3 123 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 22:42.
Find Us