Share via

BSOD - memory leak?

Anonymous
2016-06-24T01:15:56+00:00

I have been getting BSoD's periodically since i built my new pc. It seems to happen when i leave the computer run for a long period without use (usually 24+ hours) and I think it may be a memory leak from what i've read but i cannot find the source or solution using my normal methods (AKA Google) so i'm hoping i can get some direction here.

I've run memtest on both sticks of ram seperately and no errors though i only did one pass each.

- <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="2016-06-24T00:20:52.776005700Z" />

<EventRecordID>17193</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="8" />

<Channel>System</Channel>

<Computer>Casey-PC</Computer>

<Security UserID="S-1-5-18" />

</System>

- <EventData>

<Data Name="BugcheckCode">122</Data>

<Data Name="BugcheckParameter1">0xfffff6fb80008000</Data>

<Data Name="BugcheckParameter2">0xffffffffc00000c0</Data>

<Data Name="BugcheckParameter3">0x1cfd97880</Data>

<Data Name="BugcheckParameter4">0xfffff70001000000</Data>

<Data Name="SleepInProgress">true</Data>

<Data Name="PowerButtonTimestamp">0</Data>

</EventData>

</Event>

links to my recent DMP files, msinfo, and speccy (xml) below

https://drive.google.com/folderview?id=0B-78LjsjiA2JelJsa2VVSmUwM2M&usp=drive\_web

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

5 answers

Sort by: Most helpful
  1. Anonymous
    2016-06-25T18:55:03+00:00

    I've been busy today getting ready for my cousins wedding so my last message was kinda brief. When i had driver verifier running the computer did stop working; the screen went black and nothing would bring it back up however the computer never fully shut down. mouse keyboard and tower all had power still. it was also making an add noise but i don't know if that was do the crash or not. i tried twice and waited but eventually had to just turn the tower off manually as i got no BSoD. 

    The good thing is these errors do not typically affect my day to day so i can still use the computer and as long as i shut it down after i'm done (which i should probably do anyway) there are no crashes. it has never crashed during active use either, just in sleep mode. I just wanted to elaborate on my earlier responses. 

    Link to EventViewer logs below. I added it to the above link so it'll still have my specs and other dmp files

    https://drive.google.com/open?id=0B-78LjsjiA2JelJsa2VVSmUwM2M

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-06-25T15:46:57+00:00

    Please check for a dump located @ C:\windows called memory.dmp.  Also please upload your event viewer logs

    It appears to be related to hardware & SleepInProgress

    Please read this wiki to find out how to find and upload your event viewer logs

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-06-25T15:21:21+00:00

    Okay so driver verifier is running. my computer crashes now but doesnot give me a BSoD and I don't get a dump file. Any idea why that would be?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-06-24T01:48:28+00:00

    I'm running driver verifier now and i'll post result when it crashes. I've already run memtest on each individual ram stick and returned no errors

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-06-24T01:33:44+00:00

    **These crashes were related to memory corruption (probably caused by a driver).**Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless verifier does not find the cause, or you want to.

    If you are over-clocking anything reset to default before running these tests.

    In other words STOP!!!  If you do not know what this means you probably are not



    1-Driver verifier (for complete directions see our wiki here)

    **2-Memtest. (**You can read more about running memtest here)

    Was this answer helpful?

    0 comments No comments