Random bluescreens with different messages

TwoCables · 10 Mar 2013

I'm waiting for people to come in who know how to interpret the SF Diagnostic tool.

Samekh922 · 10 Mar 2013

TwoCables said:

I'm waiting for people to come in who know how to interpret the SF Diagnostic tool.

Ahh i see, thank you very very much! D: I appreciate your help. :)

Samekh922 · 12 Mar 2013

hmm? D:

Samekh922 · 12 Mar 2013

Oh i forgot to say that sometimes i get BSODS also when i´m shutting down my pc.
1. They only occur when booting
2. They only occur when shutting system down.
3. When i surfing on interned or idling.
4.Never when gaming or doing any other intensive tasks. Games run fine with heavy settings and 3dmark11 wont crash my system.

TwoCables · 13 Mar 2013

Ok, well since I'm the only one who wants to help, I guess I'll just continue assuming that this is a problem with the CPU's core voltage.

Download, extract, and open CPU-Z from here: CPUID - System & hardware benchmark, monitoring, reporting (this is a direct link to the .zip file containing CPU-Z)

Let your computer idle and report the voltages you see in CPU-Z.

Samekh922 · 13 Mar 2013

TwoCables said:

Ok, well since I'm the only one who wants to help, I guess I'll just continue assuming that this is a problem with the CPU's core voltage.

Download, extract, and open CPU-Z from here: CPUID - System & hardware benchmark, monitoring, reporting (this is a direct link to the .zip file containing CPU-Z)

Let your computer idle and report the voltages you see in CPU-Z.

I did what you asked and also included the temps from speccy. :)

TwoCables · 13 Mar 2013

Hmm. There's a chance that increasing the core voltage might help. This will raise it for all loading conditions from idle to full. Here's how to do it without changing the actual behavior where it sits nice and low while idling:

Reboot
Hold down the Delete key during the actual reboot of your motherboard (the point right before you see the motherboard booting back up). You can release it when you get the UEFI BIOS to start up.
Click "Exit/Advanced Mode" on the top-right
Choose "Advanced Mode"
Switch to the "Ai Tweaker" tab (click it or press the Right Arrow key on your keyboard)
Click "DIGI+ VRM" in the list of options
Inside the DIGI+ VRM area, scroll down - or press Page Down - to "CPU Offset Voltage".
Where it says "Auto", type 0.005 and press Enter
Press F10 to save and exit

If you can successfully get into Windows, then report what core voltage you see in CPU-Z while your computer is idling. In Windows, you can use Alt+Print Screen to take a screenshot of only the active window.

I'm just curious about how much of a difference it made from 0.0872V.

If you can't get into Windows using this offset voltage of +0.005V, then go back and use 0.010 and try again. If that doesn't get you into Windows, then use 0.015 and try again. If that doesn't get you into Windows, then try 0.020 and try again.

Arc · 13 Mar 2013

Not happy to see you again, Samekh992

Follow all the nice suggestions you have received from TwoCables. At the same time, if you two allow me, I would suggest you two more things.

As you are saying that mostly the BSODs happen after boot animation, you need to Troubleshoot Application Conflicts by Performing a Clean Startup. Free up the startup.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept then restart.

Also, got this one from your Crash Dump:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 0000000009ac01b8, Memory contents of the pool block
Arg4: fffffa8008c34cc0, Address of the block of pool being deallocated

According to Carrona.org, STOP 0x000000C2: BAD_POOL_CALLER
Usual causes: Device driver, Memory

So better we take precautions in those areas, too. Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it comes clean, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

@ TwoCables, I always noticed you do great troubleshooting. Proud to have a knowledgeable person like you with us. If anytime any specialized people is needed to have an extra eye, just call @ More help requested [5] :) Saying it for your post #11 here .... you can call them anytime :)

TwoCables · 13 Mar 2013

Wow, Arc! Thank you for telling me about the More Help is Requested thread!

Regarding Samekh922's issue: he's getting random BSODs in low-load situations. So my guess is the core voltage is never high enough for these situations in order to keep the system stable. The only thing wrong with this diagnosis is everything is at stock and no changes have been made! Oh my head hurts. hehehe :)

Arc · 13 Mar 2013

Be here :)
I am sure that your guidance will be enough to recover Samekh922's issue. I am also here, if there are any more crash dumps to read