locked
new pc randomly restarts with 'Memory Management' message on BSOD RRS feed

  • Question

  • From the first day on, my newly assembled PC randomly crashed and restarted,  with 'Memory Management' error message. I have followed all the advices could be found here, including checking the memory and updating the drivers, to no avail. Don't know what to do anymore. Help please.

    The event log:

    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          9/29/2013 7:32:56 AM
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (2)
    User:          SYSTEM
    Computer:      PC2013
    Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
        <EventID>41</EventID>
        <Version>2</Version>
        <Level>1</Level>
        <Task>63</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000002</Keywords>
        <TimeCreated SystemTime="2013-09-29T05:32:56.254811800Z" />
        <EventRecordID>1365</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>PC2013</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">26</Data>
        <Data Name="BugcheckParameter1">0x41790</Data>
        <Data Name="BugcheckParameter2">0xfffffa800a71b7f0</Data>
        <Data Name="BugcheckParameter3">0xffff</Data>
        <Data Name="BugcheckParameter4">0x0</Data>
        <Data Name="SleepInProgress">false</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
      </EventData>
    </Event>
    Sunday, September 29, 2013 5:28 PM

Answers

  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

    WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you dont know what it is you probably are not overclocking.
    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
    If you are overclocking stop.  (chances are if you dont know if you are, you are not)
    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  
    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy (compress them)
    *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
    Link for how to  upload below.
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.

    Blue Screen View & Who Crashed are often wrong and should only be used in an emergency...

    Basic troubleshooting Windows/hardware here
    You can read more about BSODS here
    You can learn how to test your memory here
    Asking an effective question gets help faster read how here
    Driver verifier-Tracking down a mis behaving driver  here



    Wanikiya & Dyami--Team Zigzag

    • Proposed as answer by Andre.Ziegler Sunday, September 29, 2013 6:08 PM
    • Marked as answer by ZigZag3143x Tuesday, October 1, 2013 9:15 PM
    Sunday, September 29, 2013 5:35 PM

All replies

  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

    WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you dont know what it is you probably are not overclocking.
    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
    If you are overclocking stop.  (chances are if you dont know if you are, you are not)
    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  
    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy (compress them)
    *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
    Link for how to  upload below.
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.

    Blue Screen View & Who Crashed are often wrong and should only be used in an emergency...

    Basic troubleshooting Windows/hardware here
    You can read more about BSODS here
    You can learn how to test your memory here
    Asking an effective question gets help faster read how here
    Driver verifier-Tracking down a mis behaving driver  here



    Wanikiya & Dyami--Team Zigzag

    • Proposed as answer by Andre.Ziegler Sunday, September 29, 2013 6:08 PM
    • Marked as answer by ZigZag3143x Tuesday, October 1, 2013 9:15 PM
    Sunday, September 29, 2013 5:35 PM
  • Hi Wanikiya & Dyami,

    Thank you for your reply.

    I have uploaded the minidump files, system information files, event logs as well as 2 screen captures to skydrive, here is the link.

    https://skydrive.live.com/download?resid=A9E1B03B76AC08E5!254&authkey=!AKO1dtpWv5Rc4ZE

    In the mean time I have scanned RAM with memtest86+ and CPU-Z, could find no problem.

    Look forward to hear from you guys again.

    Yi

    Wednesday, October 2, 2013 7:15 AM
  • ZY_18

    Both event viewer logs have exactly one event.  Neither of them are useful.  We would need a long for at least 24 hours before and after the crash occurs


    Wanikiya & Dyami--Team Zigzag

    Wednesday, October 2, 2013 9:14 PM