BSOD on Different Times and Different Errors

Same bugcheck and culprit over and over again, 3b and ntkrnlmp.exe. This is definitely hardware.

Just going to run through a quick checklist here because we've been through a lot of posts now...

1. Did you run Memtest?

2. Did you run a GPU stress testing program such as Furmark?

3. Did you run a chkdsk or an sfc /scannow in elevated command prompt (cmd as admin)?

4. You've enabled driver verifier and we've already taken care of what that has shown?

5. You are not overclocked, right?

6. Have you ensured that all memory voltages and timings are set correctly in the BIOS?

7. Have you tried a clean installation of Windows?

Just a basic checklist so we can move on.

I'd recommend enabling Driver Verifier one last time as we've made a lot of changes since we last ran it, we might see something new. Just to make sure this IS hardware.

Great, thanks for the check list :) We've just been through 4 pages thus far, and rather than me going to look, I'd rather ask you to get a definitive answer.

Newest dump attached is a different bugcheck (A), verifier enabled this time, but we're still getting ntkrnlmp.exe. Let me elaborate on why we're getting constant ntkrnlmp.exe causes. When Windows doesn't catch the driver in the act, if there is one, it will blame a core Microsoft file or driver. If we enable Driver Verifier (which we have) and it's still showing core MS files and drivers, it's definitely hardware in your case as we've reformatted twice already with no avail, so there is no OS corruption.

You can go ahead and disable verifier now.

I will also elaborate on your answers to my questions (your answers that were somewhat unsure / questions, at least).

5. You are not overclocked, right?
I think I'm not since the PCI Latency Timer is set to 32 which is the lowest and the default in the BIOS.

If you're not sure you're overclocked, you probably aren't. Overclocking is bringing your components over stock frequencies in the BIOS for more power.

Also, could you teach me about the question #6, I don't know how to check that one.

All modules have different timings & voltages. I'm not so sure your issue is memory related because you're not getting errors in Memtest, but I'd like for you to make sure anyway.

First off: Download CPU-z and install it. Once you've done that, screencap the memory and SPD tabs for me. In the SPD tab there will be a slot drop down menu, if you have more than one module, take screepcaps of all of your modules detected.

Second: Link me to your memory / type to me the memory model #.

Hi, I've asked the BSOD Team if someone can kindly further assist you from this point on as I simply don't have enough time to devote so I can help to the best of my abilities.

I am sorry and good luck.

Oh! Okay. Thanks for your help. :)

shriekyphantom said:

Oh! Okay. Thanks for your help. :)

ePeen asked us to see if we can help.

Whats the status atm?

He gave me a checklist.

shriekyphantom said:

1. Did you run Memtest?
Yep, many times and it came clean.

2. Did you run a GPU stress testing program such as Furmark?
Nope. I'll try it now.

3. Did you run a chkdsk or an sfc /scannow in elevated command prompt (cmd as admin)?
Yep. I ran the cmd as an admin and scheduled for a CHKDSK. Also clean.

4. You've enabled driver verifier and we've already taken care of what that has shown?
Yep. Many times.

5. You are not overclocked, right?
I think I'm not since the PCI Latency Timer is set to 32 which is the lowest and the default in the BIOS.

6. Have you ensured that all memory voltages and timings are set correctly in the BIOS?
I don't know but the settings in the BIOS is the default.

7. Have you tried a clean installation of Windows?
Yep. Actually, this is the second installation of Windows in this laptop.

He's supposed to check if the memory voltages and timings are set correctly. He gave this checklist because even though how many times I update the drivers which causes the BSoD according to the dump (driver verifier is on), that same driver still causes the BSoD.

shriekyphantom said:

Here's the screen cap. I didn't put slots 2 and 4 because they don't contain any information.

https://www.sevenforums.com/attachmen...s-untitled.jpg

For the RAM, I'm not sure if this is the right one but it matches the Manufacturer and Part Number displayed in CPU-Z.

Transcend Information JM1333KSN-4G
Welcome to the Transcend Info Website

shriekyphantom said:

Here's the screen cap. I didn't put slots 2 and 4 because they don't contain any information.

For the RAM, I'm not sure if this is the right one but it matches the Manufacturer and Part Number displayed in CPU-Z.

Transcend Information JM1333KSN-4G
Welcome to the Transcend Info Website

EDIT: Here's three dump if you still asking.

EDIT: If it is hardware, what do you think it is?

Three different apparent causes, none appeared to have driver verifier enabled (perhaps the mis-behaving driver wasnt in the set you specified).

Two of three were related to a memory exception. Usually that is a driver, but it can be RAM, power, etc.

I would continue to run verifier but with all drivers being examined. That will slow you down a bit but may lead to the ultimate cause.

Since it is probably a driver a clean re-install (without re-installing the same software you now have) probably would help.

zigzag3143 said:

shriekyphantom said:

Here's the screen cap. I didn't put slots 2 and 4 because they don't contain any information.

For the RAM, I'm not sure if this is the right one but it matches the Manufacturer and Part Number displayed in CPU-Z.

Transcend Information JM1333KSN-4G
Welcome to the Transcend Info Website

EDIT: Here's three dump if you still asking.

EDIT: If it is hardware, what do you think it is?

Three different apparent causes, none appeared to have driver verifier enabled (perhaps the mis-behaving driver wasnt in the set you specified).

Two of three were related to a memory exception. Usually that is a driver, but it can be RAM, power, etc.

I would continue to run verifier but with all drivers being examined. That will slow you down a bit but may lead to the ultimate cause.

Since it is probably a driver a clean re-install (without re-installing the same software you now have) probably would help.

I'll turn the driver verifier on and selecting all the drivers including Microsoft?
We also ran Memtest and CHKDSK, the HDD and RAM are clean.