Solved Increasing BSODs over time; most recent 3b and 1e

[The Tower]

Dating back to sometime November, I've been having an increasing amount of BSODs overtime. The first couple were within a month of each other; the next few have been within days. I originally thought the BSODs were due to an Nvidia beta driver I installed in preparation to Far Cry 3, but I disregarded this after I rolled back to my previous driver and later had another BSOD.

After another with the code 1000007e, I did a safe mode driver sweep of my Nvidia drivers and installed the then-latest WHQL drivers. In addition, I noticed a common occurrence in my event viewer regarding something called Adobe AIR. Research into this indicated having an outdated version could result in blue screens, and so I had it updated from 1.0 to the latest (3.5).

Hoping the issue was resolved, I was greeted a few days later I came up with a 3b BCCode. Then today I hit a 1e. Nuts.

These blue screens seem to be random and unrelated to any heating issues. So far, they have only come when I've been browsing, not when playing games.

Due to the increase over time, my current train of thought leads me to think it may be RAM going bad (damnit). I'll be running a Memtest shortly, though that will take a long while due to having 16 gigs. In the meantime, I'll attach the two recent dumps for you fine folks to look at.

 

[koolkat77]

Welcome

Here's some information on the usual causes of the BSOD-s.

[FONT="Courier New"][SIZE="3"]STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes:  System service, Device driver, graphics driver, [B]?memory[/B]

STOP 0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 
Usual causes: None

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:  Device driver, [B]hardware[/B], System service, compatibility, Remote control programs, [B]memory[/B], BIOS[/SIZE][/FONT]

Please take memtest in the following manner:

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

Let us know the results.

One question: Do you use any antivirus?

 

[The Tower]

Current status: ran through Memtest. First run resulted in a single error near the very end of the second pass.

While not *technically* overclocked, I had my RAM manually set at 1600, given that that's what they're supposed to be. However, my motherboard detects them as 1333 on Auto for whatever reason. So for a second run, I set the RAM speed back to Auto (and thus 1333) and let it run for eight full passes. Over eighteen hours later, no errors were detected.

The error at the 1600 speed both concerns and perplexes me. My history with bad memory and Memtest tells me that a single error means problems, but also that bad memory usually shows up multiple errors on the first pass, and usually pretty early. Additionally, I had this RAM set at 1600 for over a year and had no issues whatsoever. Combining that with the thorough 1333 run, and I'm not sure whether or not to rule out the RAM as a possibility.

Re: antivirus: not actively. Keeping Windows up to date and being smart has resulted in not having a virus in a decade for me. Whenever my computer acts weird and I get some antivirus programs to check, they always come up negative - and I later discover the problem to be something else.

However, later today I will be running a Windows Defender Offline full scan, if just to rule out another possibility.

In the meantime, I'd appreciate it if you guys could look through the dumps and see if anything odd catches your eyes.

 

[Dave76]

Your motherboard defaults at 1333 MHz for the RAM, unless it is slower.
Setting it at 1600MHz is standard, that's what it's rated for.
RAM can fail at any point in the test (memtest86+), the usual tests that fail are #5 and #7.

Sometimes the RAM needs a little tweaking, like with 16GB. How many RAM cards do you have?
Let's get some info, then I can recommend some adjustments.
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

All your crashes are pointing to memory corruption.

Your System Event Logs stop at Date: 2012-10-25.
To check the System Event Log settings.
1. Start Event Viewer.
2. In the console tree, expand Windows Logs and select System.
3. On the Action menu, click Properties.
4. In the General Tab, ensure 'Enable logging' is checked.
Maximum log size should be 20480
Under 'When maximum event log size is reached': select 'Overwrite events as needed (oldest events first)'
Click OK.

If you are still not getting new System Event Logs, you can 'Clear Log' on the same page.

Event[33258]:
  Log Name: System
  Source: atapi
  Date: 2012-10-20T18:36:14.289
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Lain
  Description: 
The driver detected a controller error on \Device\Ide\IdePort0.

What IDE device do you have installed?

Event[33259]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-10-20T18:36:18.984
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Lain
  Description: 
Processor 0 in group 0 exposes the following:

3 idle state(s)
18 performance state(s)
[COLOR="Red"]8 throttle state(s)[/COLOR]

This usually indicates the CPU is overheating.
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Your Media Player Classic Home Cinema is crashing repeatedly, check for an update.

Update your Creative Audio driver, it's old.
ctac32k.sys Wed Jul 02 2008

Your Intel RST driver wasn't listed in the dump files, but it's in the drivers list.
iaStorV Intel RAID Controller Kernel 6/10/2010
That's an old version, update to:
Intel® Rapid Storage Technology Version: 11.2.0.1006
Don't install any versions newer than this one, they are known to cause instability.

 

[The Tower]

How many RAM cards do you have?

Four sticks, 4GB each.

Let's get some info, then I can recommend some adjustments.
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

View attachment 249330

View attachment 249331

View attachment 249332

View attachment 249333

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

Couldn't find the "CPU integrated memory controller voltage", so here's everything that seemed relevant:

CPU Multi-Steps Load-Line [Level 4]
CPU Vcore: 1.225v [Auto] (this, of course, flucuates)
DRAM Voltage: 1.500v [Auto]

QPI/VTT Voltage: 1.050v [Auto]
System Agent Voltage: 0.920v [Auto]
CPU PLL: 1.800v [Auto]

Your System Event Logs stop at Date: 2012-10-25.
To check the System Event Log settings.
1. Start Event Viewer.
2. In the console tree, expand Windows Logs and select System.
3. On the Action menu, click Properties.
4. In the General Tab, ensure 'Enable logging' is checked.
Maximum log size should be 20480
Under 'When maximum event log size is reached': select 'Overwrite events as needed (oldest events first)'
Click OK.

If you are still not getting new System Event Logs, you can 'Clear Log' on the same page.

That's odd. All settings are correct. I'll Clear Log, then.

What IDE device do you have installed?

Even odder. I have none. Everything is SATA.

Actually, I don't think this motherboard even has an IDE port GIGABYTE - Motherboard - Socket 1155 - GA-Z68X-UD4-B3 (rev. 1.0)

This usually indicates the CPU is overheating.
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Averaging about 36C at idle across all cores.

Ten minutes of a Prime95 torture test focused on heat gave maximum of 55C on any core.

Your Media Player Classic Home Cinema is crashing repeatedly, check for an update.

Ah, that thing can have issues, but is usually reliable. Doubt it has any connection here, but I'll get it updated just in case.

Update your Creative Audio driver, it's old.
ctac32k.sys Wed Jul 02 2008

Actually, I'm using a modded driver (PAX) for my sound card, as Creative's drivers are infamously abysmal. Always have a pain with those, and since these have given me no trouble or conflicts, I have the desire to leave it be like a rusty sea mine.

Your Intel RST driver wasn't listed in the dump files, but it's in the drivers list.
iaStorV Intel RAID Controller Kernel 6/10/2010
That's an old version, update to:
Intel® Rapid Storage Technology Version: 11.2.0.1006
Don't install any versions newer than this one, they are known to cause instability.

Not even sure what that is, though I know I don't use RAID (haven't done one in over a decade). Regardless, all the ones on that page don't list Windows 7 as a supported OS.

 

[Dave76]

How many RAM cards do you have?

Four sticks, 4GB each.

Couldn't find the "CPU integrated memory controller voltage", so here's everything that seemed relevant:

CPU Multi-Steps Load-Line [Level 4]
CPU Vcore: 1.225v [Auto] (this, of course, flucuates)
DRAM Voltage: 1.500v [Auto]

QPI/VTT Voltage: 1.050v [Auto]
System Agent Voltage: 0.920v [Auto]
CPU PLL: 1.800v [Auto]

QPI/VTT Voltage is the CPU integrated memory controller voltage.
Set the RAM frequency 'System Memory Multiplier' to 'Manual' and 16 (1600MHz).
Set the DRAM Voltage to 'Manual' and bump to 1.550v.
Set the QPI/VTT Voltage to 'Manual' and bump to 1.100v.
Also set the first four RAM timings manually to 9-9-9-24 and the 'Command Rate' to 2T, leave the rest on 'Auto'.

Run memtest86+ with all cards installed, minimum of 7 full passes, best to run overnight.
Let us know the results.

That's odd. All settings are correct. I'll Clear Log, then.

Sometimes BSoD report program gets cut off and the files don't finish loading.

Even odder. I have none. Everything is SATA.

Actually, I don't think this motherboard even has an IDE port GIGABYTE - Motherboard - Socket 1155 - GA-Z68X-UD4-B3 (rev. 1.0)

The USB ports can get reported as IDE, or an IDE external drive.
What external devices do you have installed?
Include keyboard and mouse, make and model.

Averaging about 36C at idle across all cores.

Ten minutes of a Prime95 torture test focused on heat gave maximum of 55C on any core.

Good temps.
What CPU cooler do you have?

Ah, that thing can have issues, but is usually reliable. Doubt it has any connection here, but I'll get it updated just in case.

Re Media Player Classic: These can and do have very serious impact on the OS and are known to be the cause of many different types of crashes, and are hard to track down.
We see these issues all the time.

Update your Creative Audio driver, it's old.
ctac32k.sys Wed Jul 02 2008

Actually, I'm using a modded driver (PAX) for my sound card, as Creative's drivers are infamously abysmal. Always have a pain with those, and since these have given me no trouble or conflicts, I have the desire to leave it be like a rusty sea mine.

Modded drivers aren't known for their stability, leave it for now but we may need to come back to it.

Your Intel RST driver wasn't listed in the dump files, but it's in the drivers list.
iaStorV Intel RAID Controller Kernel 6/10/2010
That's an old version, update to:
Intel® Rapid Storage Technology Version: 11.2.0.1006
Don't install any versions newer than this one, they are known to cause instability.

Not even sure what that is, though I know I don't use RAID (haven't done one in over a decade). Regardless, all the ones on that page don't list Windows 7 as a supported OS.

That's the first time I haven't seen Windows 7 and Windows 8 listed as supported, I have this version on two 7&8 dual boot machines, an 8 desktop and a 7 laptop. No problems/issues, it is supported, confirmed by the date.

Intel RST driver is for AHCI and RAID settings, you don't have to have anything in RAID to use this driver.
This is the driver that enables Trim for your SSD, so is very important.

In Device Manager > IDE ATA/ATAPI controllers, right click the 'Intel...' and choose 'Properties' then the 'Drivers Tab'. It will show you the date and version.

 

[The Tower]

QPI/VTT Voltage is the CPU integrated memory controller voltage.
Set the RAM frequency 'System Memory Multiplier' to 'Manual' and 16 (1600MHz).
Set the DRAM Voltage to 'Manual' and bump to 1.550v.
Set the QPI/VTT Voltage to 'Manual' and bump to 1.100v.
Also set the first four RAM timings manually to 9-9-9-24 and the 'Command Rate' to 2T, leave the rest on 'Auto'.

Run memtest86+ with all cards installed, minimum of 7 full passes, best to run overnight.
Let us know the results.

20 hours and 9 passes later with all those manual settings added, and no errors.

The USB ports can get reported as IDE, or an IDE external drive.
What external devices do you have installed?
Include keyboard and mouse, make and model.

Actively, just my mouse. Razer DeathAdder 3500 DPI 3.5G. My keyboard, while being USB, is connected to the PS/2 port via adapter. The keyboard is a Leopold Tenkeyless Cherry Brown, model FC200RT/AB.

Additionally, I do have several external hard drives that I hook up from time to time. None of these were active during any of the bluescreens.

Good temps.
What CPU cooler do you have?

Cooler Master Hyper 212 Plus. Basically a monster of a cooler at a reasonable price. And I only have one of two possible 120mm fans connected!

Though it is winter. The temps will obviously be higher in the summer (March through October here in Phoenix), but this thing still keeps the CPU at acceptable temps.

Re Media Player Classic: These can and do have very serious impact on the OS and are known to be the cause of many different types of crashes, and are hard to track down.
We see these issues all the time.

The version I have is a specially made version that comes with CCCP (Combined Community Codec Pack), so I can't go straight up replacing it with the base version (at least that's my understanding). However, this did just make me check and discover a new CCCP release just came out, so hey!

Modded drivers aren't known for their stability, leave it for now but we may need to come back to it.

Neither are Creative's own drivers. I'd be done with Sound Blaster if another sound card manufacturer had a front I/O drive.

Anyways, I'll keep it be for now.

Your Intel RST driver wasn't listed in the dump files, but it's in the drivers list.
iaStorV Intel RAID Controller Kernel 6/10/2010
That's an old version, update to:
Intel® Rapid Storage Technology Version: 11.2.0.1006
Don't install any versions newer than this one, they are known to cause instability.

Not even sure what that is, though I know I don't use RAID (haven't done one in over a decade). Regardless, all the ones on that page don't list Windows 7 as a supported OS.

That's the first time I haven't seen Windows 7 and Windows 8 listed as supported, I have this version on two 7&8 dual boot machines, an 8 desktop and a 7 laptop. No problems/issues, it is supported, confirmed by the date.

Intel RST driver is for AHCI and RAID settings, you don't have to have anything in RAID to use this driver.
This is the driver that enables Trim for your SSD, so is very important.

In Device Manager > IDE ATA/ATAPI controllers, right click the 'Intel...' and choose 'Properties' then the 'Drivers Tab'. It will show you the date and version.

For the moment, I'm going to leave this be. After the last Memtest, I think I'll wait to see if a BSOD happens again in the near future. If I have none in two months, I'll come back and set this as solved. If I do hit one, I'll start going through the other suggestions.

Thanks for your help so far!

 

[Dave76]

You're welcome.

Good news on the RAM testing.

If you're stable for a week, then you can mark this thread solved.
This helps others with similar issues.

Leave everything else as is for now, best not to change too many things at once.
I would recommend to update the Intel RST driver to Version: 11.2.0.1006, when your system is stable. You should get some performance improvement.

Let us know how your system is running.

 

[The Tower]

Oh deary.

Despite a nice, full day of extreme usage, including a three hour plus stint of Prime95, I get up today and, after a cold boot, decide to do some more Prime95 testing while I watch football. Within seconds of starting the Blend torture test I get a blue screen. Code 1e. *sigh* Dump attached.


View attachment 249867

 

[Dave76]

Stop code 1e is a memory crash.
Bump QPI/VTT Voltage to 1.150v.
Run memtest86+ again, minimum of 7 full passes, best to run overnight.

KMODE_EXCEPTION_NOT_HANDLED (1e)
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b6100
GetUlongFromAddress: unable to read from fffff800034b61c0
 0000000000000000 Nonpaged pool
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!ExpInterlockedPopEntrySListFault16+0

For a quick stability test run OCCT.
OCCT stability checking tool
Run the CPU:OCCT test for at least 30 minutes, be sure to monitor your CPU and GPU temps.
Set the time before you start.
When its done, pass or fail, it will make some graphs. Post these here as they are useful for analyses.

Let us know the results.

 

[The Tower]

For a quick stability test run OCCT.
OCCT stability checking tool
Run the CPU:OCCT test for at least 30 minutes, be sure to monitor your CPU and GPU temps.
Set the time before you start.
When its done, pass or fail, it will make some graphs. Post these here as they are useful for analyses.

Let us know the results.

Here's that test run for 30 minutes (1 idle at beginning, 5 idle at end):

View attachment 249910

View attachment 249911

View attachment 249912

View attachment 249913

View attachment 249914

View attachment 249915

View attachment 249916

View attachment 249917

View attachment 249918

View attachment 249919

View attachment 249920

View attachment 249921

View attachment 249922

View attachment 249923

View attachment 249924

View attachment 249925

View attachment 249926

View attachment 249927

View attachment 249928

View attachment 249929

View attachment 249930

As for the voltage adjustment and Memtest, I'll be setting that now before I goto sleep, and let it run throughout tomorrow's football games.

 

[Dave76]

The graphs look good except for the Vcore, it's at 1.21v at idle and 1.175-1.87 under load.
It should be below 0.900v at idle and 1.20v under load, it's reversed itself and not giving the correct voltages.
Noticed this in your CPUZ snip, and your post 'CPU Vcore: 1.225v [Auto] (this, of course, flucuates)', wanted to confirm it.
Your CPU frequency is 3.3GHz under load, Turbo should be 3.7GHz. Did you disable Turbo in the BIOS?

Have you changed any BIOS settings before the changes I requested?
If your CPU Vcore on 'Auto' is not giving you the correct voltages, this can cause system instability.

Let's check the BIOS, if it has been corrupted.
You can use your Dual BIOS, check the CPU Vcore voltages.
Or:
In your BIOS 'Set to Load Optimized Defaults', save and exit.
Clear CMOS
Go to BIOS and 'Set to Load Optimized Defaults', save and exit.

You can use either method below to clear CMOS.
Page 30 of your motherboard manual.

17) CLR_CMOS (Clearing CMOS Jumper)
Use this jumper to clear the CMOS values (e.g. date information and BIOS configurations) and reset the CMOS values to factory defaults. To clear the CMOS values, place a jumper cap on the two pins to temporarily short the two pins or use a metal object like a screwdriver to touch the two pins for a few seconds.
• Always turn off your computer and unplug the power cord from the power outlet before clearing the CMOS values.
• After clearing the CMOS values and before turning on your computer, be sure to remove the jumper cap from the jumper. Failure to do so may cause damage to the motherboard.
• After system restart, go to BIOS Setup to load factory defaults (select Load Optimized Defaults) or manually configure the BIOS settings (refer to Chapter 2, "BIOS Setup," for BIOS configurations).

Page 24 of your motherboard manual.

You may clear the CMOS values by removing the battery:
1.Turn off your computer and unplug the power cord.
2.Gently remove the battery from the battery holder and wait for one minute. (Or use a metal object like a screwdriver to touch the positive and negative terminals of the battery holder, making them short for 5 seconds.)
3.Replace the battery.
4. Plug in the power cord and restart your computer.
•Always turn off your computer and unplug the power cord before replacing the battery.

Open CPUZ, check the CPU voltage at idle.
With CPUZ open, start OCCT for a short test, check CPU voltage at load.
Then test for stability, this may solve all of the previous issues.
Let us know the results.

Your motherboard manual: GA-Z68X-UD4-B3

 

[The Tower]

When you mentioned the voltages reversing under load and idle, it brought back a recollection of when I was experimenting with overclocking on this box. At the time, I had to use the CPU Multi-Step Load Line to correct the Vcore voltages. Set at Level 4, it kept it at the necessary voltage to keep the system stable (at least, from what I recall). I believe I reverted back to stock settings as it was hitting summer and I wasn't too pleased with the temperatures I was seeing on the CPU. In any case, I had left the Multi-Step Load Line activated and still set to Level 4.

Realizing this, I went back into BIOS and disabled that setting. A test in OCCT showed the voltages in the Vcore acting more proper: low when idle, fluctuates in general use, higher and at a peak when under full load.

At this point, I figured it possible the problem was resolved. Two days of heavy usage and no blue screen. Of course, if I'm making this post, that means something went wrong.

Today, from a cold boot, just after I log in to Windows and everything (which is, not much) is still loading, BSOD. Code? 1e. Comedy.

(dump attached to this post)

So, after a reboot and creating a dump, I also did a 40 minute OCCT run. I'll add them here to see if they're of any use.

View attachment 250556

View attachment 250557

View attachment 250558

View attachment 250559

View attachment 250560

View attachment 250561

View attachment 250562

View attachment 250563

View attachment 250564

View attachment 250565

View attachment 250566

View attachment 250567

View attachment 250568

View attachment 250569

View attachment 250570

View attachment 250571

View attachment 250572

View attachment 250573

View attachment 250574

View attachment 250575

View attachment 250576


My next step will be clearing the CMOS and resetting the BIOS, a step I wanted to avoid doing as there are certain settings I'll need to put back in place (motherboard ports I don't use, onboard audio to disable, hard drive order, etc.). However, at this point I'm really starting to think it's some hardware failure, and I'm almost hoping it's the RAM so I can just get that replaced and end this hassle. Though, if something else can be done to not require that, that would be nice.

 

[Dave76]

Check all of the BIOS settings you want to change later, good idea to keep a BIOS settings template (list of your preferred BIOS settings).
Re-set the BIOS to Optimized Defaults, re-boot.
Shutdown, Clear CMOS.
Re-set the BIOS to Optimized Defaults, re-boot.
Then make your changes.
You can save the setting in BIOS, on the BIOS Save & Exit page, there should be a Save and a Load option.

Your CPU frequency is stationary at 3.31GHz, it should be going to 1.6GHz when at idle.
This is why I would re-set BIOS to optimized defaults, it will clear any other settings that may be causing issues.
BIOS settings can and will cause many issues if they aren't set correctly.

Last crash:

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350e100
GetUlongFromAddress: unable to read from fffff8000350e1c0
 0000000000000000 Nonpaged pool
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!ExpInterlockedPopEntrySListFault16+0

Appears to be RAM caused, re-set BIOS settings first and we'll look at it again.

 

[The Tower]

Check all of the BIOS settings you want to change later, good idea to keep a BIOS settings template (list of your preferred BIOS settings).
Re-set the BIOS to Optimized Defaults, re-boot.
Shutdown, Clear CMOS.
Re-set the BIOS to Optimized Defaults, re-boot.
Then make your changes.
You can save the setting in BIOS, on the BIOS Save & Exit page, there should be a Save and a Load option.

Your CPU frequency is stationary at 3.31GHz, it should be going to 1.6GHz when at idle.
This is why I would re-set BIOS to optimized defaults, it will clear any other settings that may be causing issues.
BIOS settings can and will cause many issues if they aren't set correctly.

Did this in the order stated (and confirmed CMOS reset by seeing that ugly Full Screen LOGO that I always disable), made my changes, and the results are... curious. Note that the only BIOS changes I made had to do with Integrated Peripherals and Advanced BIOS features (Hard Disk Boot Priority, Boot Device Order, disabling Full Screen LOGO and changing Init Display First to PCIE x16). Everything else - all memory timings, CPU settings, etc. - were left at their default settings that the loading of BIOS Optimized Defaults set them as.

The Vcore is still acting more proper, but the core speed is not dropping to the much lower mark it should when idle (it used to do this, I recall, many months ago). The multiplier also seems to be defaulting to x34, with Turbo active thus fluctuating up to x37 at times. Any idea as to why the lower-idle speed (Intel's C1E, I believe it's called) isn't kicking in?

In addition, here's a quick seven minute OCCT test I ran after doing the resets. I'm no expert on voltages, but compared to my previous tests some look a bit... strange.

View attachment 250689

View attachment 250690

View attachment 250691

View attachment 250692

View attachment 250693

View attachment 250694

View attachment 250695

View attachment 250696

View attachment 250697

View attachment 250698

View attachment 250699

View attachment 250700

View attachment 250701

View attachment 250702

View attachment 250703

View attachment 250704

View attachment 250705

View attachment 250706

View attachment 250707

 

[Dave76]

Check that your Power Options are set to Balanced and not Performance.
The lower idle speed is called 'CPU EIST Function' in your BIOS. This should be set to Auto by Load Optimized Defaults.

The CPU frequency seems to be going from 3.7 GHz before the test starts, this is normal single core frequency, and then going to 3.5 GHz when the test starts, this is normal 3&4 core frequency.
Vcore is getting high voltage spikes because the idle frequency is 3.7 GHZ instead of 1.6 GHz, the CPU useage is normal.

Seems like EIST is not working, check the BIOS setting.
If it is set to 'Auto' and not working switch to your secondary BIOS, re-set to Optimized Defaults and test it.

 

[The Tower]

Preemptive tl;dr: no blue screens in a week. Now, for the explanation and current status:

When you mentioned Power Options, I checked for it in BIOS, but could find nothing. However, with that mention, it made me think of the Power Options in Windows - which made me consider the EIST not functioning properly could be on Windows' end.

I remember altering the Power Options when I first installed Windows 7, as it had a tendency to turn off my hard disks after some time, which became very annoying very quickly. However, I didn't touch anything else, and never visited the options again.

Some research later, and I discover the Processor power management in the advanced settings had a different default setting to what it had at the time. Default, the Minimum processor state is 5%, which is what mine had to be at one time. For whatever reason, my custom settings had it at 100%. The only thing I can think of that would've caused this is, when I did the beta video card drivers update back in November, I probably also did a Windows update at the same time. It's possible that in this update, it changed my custom power plan. Not sure why, but that's the only thing I can think of.

Anyways, I changed the Minimum processor state to 5%, went back to BIOS to switch everything back to auto and defaults - along with turning off Turbo for the purpose of this test - and checked it. Result: EIST seems to be acting normal; the CPU's core speed being in flux, and highest when under full load.

After week of it set like this, and no blue screens, I'm thinking this was probably the problem - the voltage would drop when idle or not under full load, but the CPU would stay at the static core speed.

I did an OCCT test after a cold boot today. I'll post the results below. After this, if nothing looks out of the ordinary, I think I'll test with getting the RAM back to the desired 1600 speed. For now, glad to at least have the system stable (or so I hope, knock on wood).

View attachment 252084

View attachment 252085

View attachment 252086

View attachment 252087

View attachment 252088

View attachment 252089

View attachment 252090

View attachment 252091

View attachment 252092

View attachment 252093

View attachment 252097

View attachment 252098

View attachment 252099

View attachment 252100

View attachment 252101

View attachment 252102

View attachment 252103

To my eyes, everything looks correct here, except for the +VCC and VCC3 dropping in voltage some when under full load. It's not much in the way of voltage, but I just want to check to see if it's normal.

 

[Dave76]

Nice work, that could explain the issues you were having.
These graphs look better.

Let me what BIOS settings you are going to change to get the RAM at 1600MHz.

 

[The Tower]

Currently, I'm testing the system with Turbo re-enabled (so far so good). I think tomorrow I may set the RAM back to 1600. What settings would you recommend I change to do this?

 

[Dave76]

Set your RAM frequency manually to 1600MHz.
Also set the first four RAM timings manually to 9-9-9-24 and the 'Command Rate' to 2T, leave the rest on 'Auto'.
Test for stability, memtest86+ for 7 full passes.

Let us know the results.