Solved BugcheckCode 59

[Mattx3]

All drivers are up-to-date.
I was just browsing, It happened sometimes when I was playing GTA V.

- <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="2015-05-03T22:45:40.832012900Z" />
<EventRecordID>15916</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Matheus-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">59</Data>
<Data Name="BugcheckParameter1">0xc0000005</Data>
<Data Name="BugcheckParameter2">0xfffff80002ff3188</Data>
<Data Name="BugcheckParameter3">0xfffff8800781af90</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

*PS: This mini-dumps t is an old case driver has already been solved, but those blue screens that are not creating mini-dups more. (Yes, I have marked the option to save them).


Since already grateful,

Matt.

 

[whs]

How much RAM do you have ?

 

[Arc]

How much RAM do you have ?

8 GB, 4x2, but each stick is of different brand.

  Size                          4096MB
  Form Factor                   09h - DIMM
  Device Locator                ChannelB-DIMM0
  Bank Locator                  BANK 2
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1333MHz
 [COLOR=Red] Manufacturer                  Kingston[/COLOR]

  Size                          4096MB
  Form Factor                   09h - DIMM
  Device Locator                ChannelA-DIMM0
  Bank Locator                  BANK 0
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1333MHz
[COLOR=Red]  Manufacturer                  857F[/COLOR]

@ Mattx3; Before doing anything else, I will suggest you to run the computer with a single RAM stick only, of either brand. See how it goes. Report us for any further BSOD with 4 GB RAM in use.

 

[Mattx3]

How much RAM do you have ?

8GB. (4x2)

 

[Arc]

See post #3 above.

 

[Layback Bear]

I agree with Arc. The starting place is to have matched ram.

 

[whs]

This is listed as cause and solution for this code:

Cause
One possible cause of this bug check is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

Resolution
To resolve a nonpaged pool memory depletion problem: Add new physical memory to the computer. This will increase the quantity of nonpaged pool memory available to the kernel.

 

[Arc]

This is listed as cause and solution for this code:

Resolution
To resolve a nonpaged pool memory depletion problem: Add new physical memory to the computer. This will increase the quantity of nonpaged pool memory available to the kernel.

I am suggesting the user to remove either one RAM stick.

 

[Layback Bear]

When the memory does not match their is a chance that the motherboard and or the operating system is unable to use the ram in the correct fashion.

 

[whs]

I think you guys are right, Removing one of the RAM sticks will probably fix the problem. Then look for matching sticks.

 

[Arc]

It may not. In most of the cases stop 0x59 is caused by corrupt indexing (almost all that I have dealt with); but mismatch RAM should not be there.

I will not look at the RAM info if you havent asked. But thank you so much that you have asked. It revealed a big scope of various issues.

We will guide him accordingly depending on the resulting situation after removing the RAM.

 

[Mattx3]

Ok, for now since the thread creation gave no blue screen with the two connected memories.
I'll see if the problem persists and test a memory, then the other.

Thank you for your willingness to help gentlemens,

Matt.

@Edit,

Now, It just happened a BSOD. I will try remove a stick, I come to inform you.

By the way, here the Events Log:

- <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="2015-05-05T07:48:48.236015400Z" />
<EventRecordID>16308</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Matheus-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">25</Data>
<Data Name="BugcheckParameter1">0x20</Data>
<Data Name="BugcheckParameter2">0xfffffa800de2a1e0</Data>
<Data Name="BugcheckParameter3">0xfffffa800de2a800</Data>
<Data Name="BugcheckParameter4">0x4620008</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

w/o a minidump.

One of my RAMs is from my old computer (like.. 2 years old almost)

 

[Mattx3]

No BSOD yet, probably it's the RAM. I will buy another, but, any chance of some detail involving this memory?

Well, anyway, thanks a lot for the help guys.


Matt.

 

[Arc]

RAMs should be bought in KITs. A Kit is a package of two or more RAM sticks designed and tested to work together.

Apparently 4 GB of RAM would be enough for you. But if you plan to buy more, buy a KIT.

What detail you want?

I will buy another, but, any chance of some detail involving this memory?

.