none
Bluescreen, BCCode: 1a

    Question

  • Hi, 

    I just installed 2x2gb of Ram into my machine (using Win7 Pro 64-bit) i am now getting bluescreen after bluescreen. here are my minidumps: https://skydrive.live.com/redir.aspx?cid=b32896fc2fca4c64&resid=B32896FC2FCA4C64!324&parid=B32896FC2FCA4C64!321

     

    any help would be greatly appreciated.

    Friday, February 03, 2012 3:52 PM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000005001, The subtype of the bugcheck.
    Arg2: fffff70001080000
    Arg3: 0000000000005eaf
    Arg4: 0000000000005eaf
    Debugging Details:
    ------------------
    BUGCHECK_STR:  0x1a_5001
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  CCC.exe
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff80002d04627 to fffff80002c91c40
    STACK_TEXT:  
    fffff880`0994a0e8 fffff800`02d04627 : 00000000`0000001a 00000000`00005001 fffff700`01080000 00000000`00005eaf : nt!KeBugCheckEx
    fffff880`0994a0f0 fffff800`02c9ef19 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x3994b
    fffff880`0994a200 fffff800`02c8fd6e : 00000000`00000000 00000000`1f380000 fffffa80`03bccb01 00000000`1e085590 : nt!MmAccessFault+0x359
    fffff880`0994a360 00000000`775b1d84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`1e0854d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775b1d84
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+3994b
    fffff800`02d04627 cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+3994b
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    FAILURE_BUCKET_ID:  X64_0x1a_5001_nt!_??_::FNODOBFM::_string_+3994b
    BUCKET_ID:  X64_0x1a_5001_nt!_??_::FNODOBFM::_string_+3994b
    Followup: MachineOwner
    ---------
    -------------------------------------------------------------------------------------
    The BSOD occured when CCC.exe was running. More about it: http://www.file.net/process/ccc.exe.html
    Please start by updating your ATI drivers and check results.
    If this does not help then:
    • Update all possible drivers you have
    • Uninstall all unused programs
    • Disable all security softwares that you have
    • Run msconfig and disable all startup items / services except Microsoft ones
    • Run memtest86+ to check if all is okay with your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support
    If this does not help then upload c:\windows\MEMORY.DMP file after zipping it. Once done, post a link here.
    You can also contact Microsoft CSS for assistance.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Sunday, February 05, 2012 11:33 AM

All replies

  • Sounds like you got a bad batch of memory.  You can use the memory diagnostic tool and check for memory errors

    1. Open Memory Diagnostics Tool by clicking the Start button, clicking Control Panel, clicking System and Maintenance, clicking Administrative Tools, and then clicking Memory Diagnostics Tool.

     If you are prompted for an administrator password or confirmation, type the password or provide confirmation.

    1. Choose between the two options for when to run the Memory Diagnostics Tool:

    ·         You can restart your computer and run the tool immediately.

    ·         You can restart your computer and run the tool later.

    Use the below mentioned link for further assistance on Memory diagnostic tool-


    http://windows.microsoft.com/en-US/windows-vista/How-do-I-know-if-my-computer-has-a-memory-problem


    Hope this helps. Let us know the results.

    Rich Prescott | Infrastructure Architect, Windows Engineer and PowerShell blogger | MCITP, MCTS, MCP

    Engineering Efficiency
    @Rich_Prescott
    Windows System Administration tool 2.0
    AD User Creation tool
    Friday, February 03, 2012 7:25 PM
  • Check your memory.  A lot of BSODs can be traced to bad memory.

    Windows 7 has a built-in rudimentary memory checker that can help.

    Boot with a Windows 7 DVD.  At the first screen, hit <SHIFT>+<F10>.  You will see that you are at x:\Sources>.  CD into Recovery (cd recovery).  Type RecEnv.exe, click Next.  Select the top radio button that reads, "Use recovery tools . . . ."  Select Windows Memory Diagnostic and chose the restart now option.  

    For a more thorough check, however, head over to http://www.memtest.org/ and download the latest version.  Burn the ISO to a disk or make a bootable USB drive.  Boot and follow the on-screen instructions. 

     

    A not-so-nice screen of failed memory.





    Saturday, February 04, 2012 4:09 AM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000005001, The subtype of the bugcheck.
    Arg2: fffff70001080000
    Arg3: 0000000000005eaf
    Arg4: 0000000000005eaf
    Debugging Details:
    ------------------
    BUGCHECK_STR:  0x1a_5001
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  CCC.exe
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff80002d04627 to fffff80002c91c40
    STACK_TEXT:  
    fffff880`0994a0e8 fffff800`02d04627 : 00000000`0000001a 00000000`00005001 fffff700`01080000 00000000`00005eaf : nt!KeBugCheckEx
    fffff880`0994a0f0 fffff800`02c9ef19 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x3994b
    fffff880`0994a200 fffff800`02c8fd6e : 00000000`00000000 00000000`1f380000 fffffa80`03bccb01 00000000`1e085590 : nt!MmAccessFault+0x359
    fffff880`0994a360 00000000`775b1d84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`1e0854d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775b1d84
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+3994b
    fffff800`02d04627 cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+3994b
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    FAILURE_BUCKET_ID:  X64_0x1a_5001_nt!_??_::FNODOBFM::_string_+3994b
    BUCKET_ID:  X64_0x1a_5001_nt!_??_::FNODOBFM::_string_+3994b
    Followup: MachineOwner
    ---------
    -------------------------------------------------------------------------------------
    The BSOD occured when CCC.exe was running. More about it: http://www.file.net/process/ccc.exe.html
    Please start by updating your ATI drivers and check results.
    If this does not help then:
    • Update all possible drivers you have
    • Uninstall all unused programs
    • Disable all security softwares that you have
    • Run msconfig and disable all startup items / services except Microsoft ones
    • Run memtest86+ to check if all is okay with your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support
    If this does not help then upload c:\windows\MEMORY.DMP file after zipping it. Once done, post a link here.
    You can also contact Microsoft CSS for assistance.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Sunday, February 05, 2012 11:33 AM