Question Assistance with analysing dump files for recent BSODs ?

[JKein]

Hello,

I've been receiving multiple BSOD's that seem to happen while I'm playing, and it's getting annoying to deal with. I have few mini dump files recently saved but I do not know how to read them comprehensively. Can someone assist in tracking the cause for these BSODs? I have a feeling there could be several causes. Thank you.

(Here is the gdrive link for my most recent dmp files: https://drive.google.com/drive/folders/1NifpXUj4WknTEsJSEzjWONRcJNdYVWR7?usp=sharing )

 

[ubuysa]

Hello and welcome to the forum.

Thanks for the dump upload, sadly they look to be pointing at a hardware problem. There are three different failures...

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_STACKPTR_ERROR_nt!KeAccumulateTicks - this BSOD happened because the processor wasn't able to respond to the clock synchronisation interrupt. Notice that we have a stack pointer error here too.
FAILURE_BUCKET_ID:  0x1a_41202_nt!MiGetPageProtection - this BSOD happened because of a virtual memory error (the PTE was invalid)
FAILURE_BUCKET_ID:  0x1AA_nt!RtlpGetStackLimitsEx - this BSOD happened because a memory structure called a stack was corrput.

The common denominator with all these BSODs is RAM. I can see from the dumps that you have two 8GB RAM cards installed, but although they offer similar specs, they are not identical. One is part number HMAA1GS6CJR6N-XN and the other is part number HMA81GS6DJR8N-XN. RAM should always be purchased in matched sets, you can sometimes get away with adding another RAM card of exactly the same part number, but mixing part numbers often leads to instability.

You could try testing your RAM with Memtest86 as described below, but in this case it would be wiser to remove one RAM card and run with just one for a day or two - long enough to have normally had a BSOD. Then swap the RAM cards over and run on just the other one for a day or two - long enough to have normally had a BSOD.

To run Memtest86....

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

 

[JKein]

Hello and welcome to the forum.

Thanks for the dump upload, sadly they look to be pointing at a hardware problem. There are three different failures...

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_STACKPTR_ERROR_nt!KeAccumulateTicks - this BSOD happened because the processor wasn't able to respond to the clock synchronisation interrupt. Notice that we have a stack pointer error here too.
FAILURE_BUCKET_ID:  0x1a_41202_nt!MiGetPageProtection - this BSOD happened because of a virtual memory error (the PTE was invalid)
FAILURE_BUCKET_ID:  0x1AA_nt!RtlpGetStackLimitsEx - this BSOD happened because a memory structure called a stack was corrput.

The common denominator with all these BSODs is RAM. I can see from the dumps that you have two 8GB RAM cards installed, but although they offer similar specs, they are not identical. One is part number HMAA1GS6CJR6N-XN and the other is part number HMA81GS6DJR8N-XN. RAM should always be purchased in matched sets, you can sometimes get away with adding another RAM card of exactly the same part number, but mixing part numbers often leads to instability.

You could try testing your RAM with Memtest86 as described below, but in this case it would be wiser to remove one RAM card and run with just one for a day or two - long enough to have normally had a BSOD. Then swap the RAM cards over and run on just the other one for a day or two - long enough to have normally had a BSOD.

To run Memtest86....

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

Thank you for the response. I see, and I thought I could get away with only buying one ram stick... so much for that.

Since I am at a different location right now, sadly I cannot afford to go with both options for now. I do not have another pc/laptop available with me, nor can I take out one RAM stick and run it for a day or two. If there are any other suggestions, I'd be glad to hear those out, but for now, I have no choice but to come back here after a few days for updates.

 

[ubuysa]

Troubleshooting is rarely easy, comfortable, or convenient. The bottom line is that you need to test your RAM and I've described the two way of doing that.

Your only other option is to buy a new pack of two matched RAM cards that are compatible with your laptop and scrap the two that you have. That has the disadvantage of being a tad more expensive.

You're call.