locked
Error 1001 + Memory Problem RRS feed

  • Question

  • So after 2 system crashes I went looking online for the cause of the event ID error 1001. My search led me to this forum where I learned about a memory test which ended up informing me that I had a memory problem. 

    Error 1: Playing Minecraft when crash occured

    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff96000136884, 0xfffff88009dd4030, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 042511-25880-01.

    XML:

     

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
      <EventID Qualifiers="16384">1001</EventID>
      <Version>0</Version>
      <Level>2</Level>
      <Task>0</Task>
      <Opcode>0</Opcode>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2011-04-26T03:30:32.000000000Z" />
      <EventRecordID>153358</EventRecordID>
      <Correlation />
      <Execution ProcessID="0" ThreadID="0" />
      <Channel>System</Channel>
      <Computer>llama-7</Computer>
      <Security />
      </System>
    - <EventData>
      <Data Name="param1">0x0000003b (0x00000000c0000005, 0xfffff96000136884, 0xfffff88009dd4030, 0x0000000000000000)</Data>
      <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
      <Data Name="param3">042511-25880-01</Data>
      </EventData>
      </Event>

     

    Error 2: Exiting Starcraft 2 when crash occured

    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff880043ca6fa, 0xfffff88003f45788, 0xfffff88003f44fe0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 042711-29421-01.

    XML:

     

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
      <EventID Qualifiers="16384">1001</EventID>
      <Version>0</Version>
      <Level>2</Level>
      <Task>0</Task>
      <Opcode>0</Opcode>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2011-04-28T03:22:40.000000000Z" />
      <EventRecordID>158441</EventRecordID>
      <Correlation />
      <Execution ProcessID="0" ThreadID="0" />
      <Channel>System</Channel>
      <Computer>llama-7</Computer>
      <Security />
      </System>
    - <EventData>
      <Data Name="param1">0x0000007e (0xffffffffc0000005, 0xfffff880043ca6fa, 0xfffff88003f45788, 0xfffff88003f44fe0)</Data>
      <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
      <Data Name="param3">042711-29421-01</Data>
      </EventData>
      </Event>

     


    So now I come to the community with a cry for help. I am a pretty tech savvy guy but I have never come across this kind of problem before and I don't know what to do from here. I have contacted the memory manufacturer and am awaiting a reply.

    Does a memory problem mean I need to replace my RAM?

     

    EDIT:

    I ran the memory test again and this time Windows did not find any memory problem!!

    So now I don't even know what is going on.

     

     

    PC Specs:

    Asus CG Series

    Win 7 Home Premium 64-bit edition

    AMD Phenom II X6

    Radeon 5770 Graphics card.

    8GB RAM

     

     


    Thursday, April 28, 2011 4:46 AM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff880043ca6fa, The address that the exception occurred at
    Arg3: fffff88003f45788, Exception Record Address
    Arg4: fffff88003f44fe0, Context Record Address

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP:
    dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+f3a
    fffff880`043ca6fa 4d8b1b          mov     r11,qword ptr [r11]

    EXCEPTION_RECORD:  fffff88003f45788 -- (.exr 0xfffff88003f45788)
    ExceptionAddress: fffff880043ca6fa (dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x0000000000000f3a)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff

    CONTEXT:  fffff88003f44fe0 -- (.cxr 0xfffff88003f44fe0)
    rax=fffff8a002cdcbd0 rbx=0000000000000000 rcx=ffdff8a010f6f0e0
    rdx=fffff8a00d5acec0 rsi=fffff8a010f6f010 rdi=0000000000000000
    rip=fffff880043ca6fa rsp=fffff88003f459c0 rbp=fffffa8008ec9000
     r8=0000000000001000  r9=0000000000000000 r10=0000000000000001
    r11=ffdff8a010f6f118 r12=0000000000000000 r13=0000000000000001
    r14=fffffa8008a77ac0 r15=fffff8a010f6f118
    iopl=0         nv up ei ng nz na po cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
    dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0xf3a:
    fffff880`043ca6fa 4d8b1b          mov     r11,qword ptr [r11] ds:002b:ffdff8a0`10f6f118=????????????????
    Resetting default scope

    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_PARAMETER1:  0000000000000000

    EXCEPTION_PARAMETER2:  ffffffffffffffff

    READ_ADDRESS:  ffffffffffffffff

    FOLLOWUP_IP:
    dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+f3a
    fffff880`043ca6fa 4d8b1b          mov     r11,qword ptr [r11]

    BUGCHECK_STR:  0x7E

    LAST_CONTROL_TRANSFER:  from fffff880043ba25d to fffff880043ca6fa

    STACK_TEXT: 
    fffff880`03f459c0 fffff880`043ba25d : fffffa80`08a77ac0 fffff8a0`10f6f010 fffffa80`0b18f000 fffffa80`08ec9000 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0xf3a
    fffff880`03f45b30 fffff880`043b5358 : fffffa80`08db9810 00000000`00000080 00000000`00000000 fffff880`03f45ca0 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x96d
    fffff880`03f45c50 fffff880`043d316d : fffffa80`00000000 fffffa80`06a15010 00000000`0000000f fffff880`043d4f09 : dxgmms1!VidMmiProcessTerminationCommand+0x4c
    fffff880`03f45ca0 fffff880`043d23f8 : fffff880`0308cfc0 fffffa80`077c2c00 00000000`00000000 fffffa80`06a15010 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
    fffff880`03f45cd0 fffff880`043d1e96 : 00000000`00000000 fffffa80`077c2c00 00000000`00000080 fffffa80`06a15010 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
    fffff880`03f45d00 fffff800`03169cce : 00000000`0ce38485 fffffa80`08a88a10 fffffa80`069aa990 fffffa80`08a88a10 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`03f45d40 fffff800`02ebdfe6 : fffff880`03088180 fffffa80`08a88a10 fffff880`03093040 fffff880`0122c384 : nt!PspSystemThreadStartup+0x5a
    fffff880`03f45d80 00000000`00000000 : fffff880`03f46000 fffff880`03f40000 fffff880`03f45680 00000000`00000000 : nt!KxStartSystemThread+0x16


    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+f3a

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: dxgmms1

    IMAGE_NAME:  dxgmms1.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

    STACK_COMMAND:  .cxr 0xfffff88003f44fe0 ; kb

    FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+f3a

    BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+f3a

    Followup: MachineOwner
    ---------

    0: kd> lmvm dxgmms1
    start             end                 module name
    fffff880`0439a000 fffff880`043e0000   dxgmms1    (pdb symbols)          c:\symbols\dxgmms1.pdb\0901C357E9E846EE8C2FBCC8107163201\dxgmms1.pdb
        Loaded symbol image file: dxgmms1.sys
        Image path: \SystemRoot\System32\drivers\dxgmms1.sys
        Image name: dxgmms1.sys
        Timestamp:        Sat Nov 20 10:49:53 2010 (4CE799C1)
        CheckSum:         00047A89
        ImageSize:        00046000
        File version:     6.1.7601.17514
        Product version:  6.1.7601.17514
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     dxgmms1.sys
        OriginalFilename: dxgmms1.sys
        ProductVersion:   6.1.7601.17514
        FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
        FileDescription:  DirectX Graphics MMS
        LegalCopyright:   © Microsoft Corporation. All rights reserved.

    -------------------------------------------------------------------------------------------------------------

    The BSOD is caused by dxgmms1.sys which belongs to DirectX Graphics MMS.

    Try to install that and check if this solve your problem: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&displayLang=en


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

    Microsoft Student Partner
    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
    • Marked as answer by Miya Yao Thursday, May 5, 2011 8:51 AM
    Thursday, April 28, 2011 7:46 PM

All replies

  • Bug Check 0x3B: http://msdn.microsoft.com/en-us/library/ff558949(VS.85).aspx

    Please use Microsoft Skydrive to uplaod C:\Windows\MEMORY.DMP file and post a link here (Zip it before uploading it).

    If you want to read dump files without my help, use Windbg and refer to this Microsoft article:

    http://support.microsoft.com/kb/315263

     


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

    Microsoft Student Partner
    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

    Thursday, April 28, 2011 9:26 AM
  • Skydrive won't accept my .dmp file cuz it was over the size limit even zipped up.

    The .dmp file unzipped is over 500MB.

    I really would like someone to take a look at the .dmp since I have little to no experience with this issue. I will try and figure it out but if you see this before I have posted a link please give some advice.

    I really appreciate people who dedicate time to forums and I thank you. 

    Thursday, April 28, 2011 4:29 PM
  • Use 7ZIP to divide it and upload it again.


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

    Microsoft Student Partner
    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
    Thursday, April 28, 2011 5:52 PM
  • I hope I did this correctly. In order to meet the upload limit this .dmp I had to split it 4 ways, each partis titled accordingly. 7Zip split the .dmp into 402 files and I zipped them into packages of 100 files each.

    https://cid-40f4f16b17b69818.office.live.com/self.aspx/.Documents/dump%5E_part1.zip

    https://cid-40f4f16b17b69818.office.live.com/self.aspx/.Documents/dump%5E_part2.zip

    https://cid-40f4f16b17b69818.office.live.com/self.aspx/.Documents/dump%5E_part3.zip

    https://cid-40f4f16b17b69818.office.live.com/self.aspx/.Documents/dump%5E_part4.zip

     

    I was reading http://msdn.microsoft.com/en-us/library/ff558949(VS.85).aspx and it talks about graphics card drivers being a possible issue. I did update my graphics card driver last night in hopes that it would resolve the issue. I hope that the .dmp file can help shed some more light on the issue and possibly find the source of the issue or confirm my graphics card theory.

     

    If I uploaded these files incorrectly let me know.

     

     

    Thursday, April 28, 2011 6:31 PM
  • Hello,

    the folder is not set for public access. Please update that.

    Start by updating the graphic card driver and check if this solve the problem.


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

    Microsoft Student Partner
    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
    Thursday, April 28, 2011 6:55 PM
  • Updated - You should be able to DL now.

     

    I updated the driver last night and so far no crashes however, the crashes took place at random times. I played a few games in Starcraft with no issues.

    Thursday, April 28, 2011 7:03 PM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff880043ca6fa, The address that the exception occurred at
    Arg3: fffff88003f45788, Exception Record Address
    Arg4: fffff88003f44fe0, Context Record Address

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP:
    dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+f3a
    fffff880`043ca6fa 4d8b1b          mov     r11,qword ptr [r11]

    EXCEPTION_RECORD:  fffff88003f45788 -- (.exr 0xfffff88003f45788)
    ExceptionAddress: fffff880043ca6fa (dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x0000000000000f3a)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff

    CONTEXT:  fffff88003f44fe0 -- (.cxr 0xfffff88003f44fe0)
    rax=fffff8a002cdcbd0 rbx=0000000000000000 rcx=ffdff8a010f6f0e0
    rdx=fffff8a00d5acec0 rsi=fffff8a010f6f010 rdi=0000000000000000
    rip=fffff880043ca6fa rsp=fffff88003f459c0 rbp=fffffa8008ec9000
     r8=0000000000001000  r9=0000000000000000 r10=0000000000000001
    r11=ffdff8a010f6f118 r12=0000000000000000 r13=0000000000000001
    r14=fffffa8008a77ac0 r15=fffff8a010f6f118
    iopl=0         nv up ei ng nz na po cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
    dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0xf3a:
    fffff880`043ca6fa 4d8b1b          mov     r11,qword ptr [r11] ds:002b:ffdff8a0`10f6f118=????????????????
    Resetting default scope

    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_PARAMETER1:  0000000000000000

    EXCEPTION_PARAMETER2:  ffffffffffffffff

    READ_ADDRESS:  ffffffffffffffff

    FOLLOWUP_IP:
    dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+f3a
    fffff880`043ca6fa 4d8b1b          mov     r11,qword ptr [r11]

    BUGCHECK_STR:  0x7E

    LAST_CONTROL_TRANSFER:  from fffff880043ba25d to fffff880043ca6fa

    STACK_TEXT: 
    fffff880`03f459c0 fffff880`043ba25d : fffffa80`08a77ac0 fffff8a0`10f6f010 fffffa80`0b18f000 fffffa80`08ec9000 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0xf3a
    fffff880`03f45b30 fffff880`043b5358 : fffffa80`08db9810 00000000`00000080 00000000`00000000 fffff880`03f45ca0 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x96d
    fffff880`03f45c50 fffff880`043d316d : fffffa80`00000000 fffffa80`06a15010 00000000`0000000f fffff880`043d4f09 : dxgmms1!VidMmiProcessTerminationCommand+0x4c
    fffff880`03f45ca0 fffff880`043d23f8 : fffff880`0308cfc0 fffffa80`077c2c00 00000000`00000000 fffffa80`06a15010 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
    fffff880`03f45cd0 fffff880`043d1e96 : 00000000`00000000 fffffa80`077c2c00 00000000`00000080 fffffa80`06a15010 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
    fffff880`03f45d00 fffff800`03169cce : 00000000`0ce38485 fffffa80`08a88a10 fffffa80`069aa990 fffffa80`08a88a10 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`03f45d40 fffff800`02ebdfe6 : fffff880`03088180 fffffa80`08a88a10 fffff880`03093040 fffff880`0122c384 : nt!PspSystemThreadStartup+0x5a
    fffff880`03f45d80 00000000`00000000 : fffff880`03f46000 fffff880`03f40000 fffff880`03f45680 00000000`00000000 : nt!KxStartSystemThread+0x16


    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+f3a

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: dxgmms1

    IMAGE_NAME:  dxgmms1.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

    STACK_COMMAND:  .cxr 0xfffff88003f44fe0 ; kb

    FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+f3a

    BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+f3a

    Followup: MachineOwner
    ---------

    0: kd> lmvm dxgmms1
    start             end                 module name
    fffff880`0439a000 fffff880`043e0000   dxgmms1    (pdb symbols)          c:\symbols\dxgmms1.pdb\0901C357E9E846EE8C2FBCC8107163201\dxgmms1.pdb
        Loaded symbol image file: dxgmms1.sys
        Image path: \SystemRoot\System32\drivers\dxgmms1.sys
        Image name: dxgmms1.sys
        Timestamp:        Sat Nov 20 10:49:53 2010 (4CE799C1)
        CheckSum:         00047A89
        ImageSize:        00046000
        File version:     6.1.7601.17514
        Product version:  6.1.7601.17514
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     dxgmms1.sys
        OriginalFilename: dxgmms1.sys
        ProductVersion:   6.1.7601.17514
        FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
        FileDescription:  DirectX Graphics MMS
        LegalCopyright:   © Microsoft Corporation. All rights reserved.

    -------------------------------------------------------------------------------------------------------------

    The BSOD is caused by dxgmms1.sys which belongs to DirectX Graphics MMS.

    Try to install that and check if this solve your problem: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&displayLang=en


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

    Microsoft Student Partner
    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
    • Marked as answer by Miya Yao Thursday, May 5, 2011 8:51 AM
    Thursday, April 28, 2011 7:46 PM
  • Ok, I have been playing games for the past hour to try and cause a crash but so far I cannot.

    I am also installing the DirectX from the link. I guess all I can do now is wait and see. I thank you very much for your help.

     

    If the problem comes back I will post in this thread again.

    Thursday, April 28, 2011 8:12 PM
  • So my system just crashed again about 10 mins ago.

     

    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff88005201ea6, 0xfffff8800398db30, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 050511-14726-01.

     

    XML

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
      <EventID Qualifiers="16384">1001</EventID>
      <Version>0</Version>
      <Level>2</Level>
      <Task>0</Task>
      <Opcode>0</Opcode>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2011-05-05T19:11:00.000000000Z" />
      <EventRecordID>175683</EventRecordID>
      <Correlation />
      <Execution ProcessID="0" ThreadID="0" />
      <Channel>System</Channel>
      <Computer>LLAMA-7</Computer>
      <Security />
      </System>
    - <EventData>
      <Data Name="param1">0x0000003b (0x00000000c0000005, 0xfffff88005201ea6, 0xfffff8800398db30, 0x0000000000000000)</Data>
      <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
      <Data Name="param3">050511-14726-01</Data>
      </EventData>
     </Event>
    My recent investigations point to a memory problem. I did an extended suite memory scan with Windows Memory Diagnostics and it reported that I have a memory problem.
    Any advice.

    Thursday, May 5, 2011 7:18 PM
  • My recent investigations point to a memory problem. I did an extended suite memory scan with Windows Memory Diagnostics and it reported that I have a memory problem.

     

    You have to replace the faulty RAM as it will continue causing BSODs.

     


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

    Microsoft Student Partner
    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

    Thursday, May 5, 2011 7:46 PM
  • To be honest I am little skeptical about the memory tester since it has told me on separate occasions that I did and did not have memory problems after running the same Windows Memory Diagnostice utility. I am currently running the test for each stick of memor to isolate a faulty stick (if there is one).

    Do memory problems just happen like this? Like one day everything is fine and then the next the memory is faulty? I'm just trying to understand what causes these problems, how they can be avoided, and maybe figure out if I have done something to cause it.


    Also, can this memory problem manifest itself through a driver error? That seems like the what is occuring but since I haven't confirmed the memory problem (will be able to confirm in a few hours).


    Thursday, May 5, 2011 10:28 PM
  • Reviewingthe subjectI suggestyou review the followinglink:

    http://support.microsoft.com/kb/977321/es

    If you see audit events in the same time you will notice that there are two events which you describe the following link:

    http://social.technet.microsoft.com/Forums/windows/es-ES/e9e0967f-cbda-406e-8bc8-236f62d0fd8b/windows-7-freezing-with-simultaneous-security-audit-event-4624-and-4672?forum=w7itproperf&prof=required
    Wednesday, January 22, 2014 11:02 PM