Numerous BSOD playing games, recently error 0xd1

Good news that the crashes are at least lowering in frequency.
The only stupid question is the one you don't ask.

You can either continue to use your system normally or run OCCT and memtest86+.
If you get another crash then run the two tests.
One of the reasons to run these tests is to see how your system responds under stress when the games are not running.

The standard BIOS update rule is to not update unless needed, if there are issues that can be resolved.
You can hold off on the BIOS update for now.

Let us know if you get another crash, or if you go a week without any.

Edit: Good news on the memtest86+.
I will be adding to this post, as I analyze further.
First thing to do is update the BIOS to v1.70.

Dave76 said:

It appears your motherboard is having USB issues that AsRock is trying to fix with new BIOS updates.
AsRock Z77 Extreme4 BIOS updtes
Read the 'Descriptions' most of the updates have 'Improve USB compatibility' listed.
You previous crashes had USB issues.
Also listed is a patch for G.Skill RAM, though not your's, it may help stability.
Update your BIOS to version 1.70.
ASRock BIOS Upgrade Instruction
Use Method 1.

Welcome to bleeding edge hardware.
Sometimes it takes a while for the manufacturers to get all of the BIOS and hardware settings tweaked on new hardware. This is why there usually are a few BIOS updates when new motherboards come out, also real world settings for the new CPUs, chipsets, etc.

The handy testing and information programs can also take a while to get their software working correctly with the new hardware.
Due to this we need to confirm some of your settings readings from OCCT.
The OCCT graphs are showing a few questionable readings.
FSB 112 MHz and the CPU frequency at 3.601 GHz, your previous CPUZ snips are showing the correct FSB of 100 MHz and corresponding CPU idle frequency of 1.60 GHz, these are what they should be.
The CPU temps shown on the OCCT graphs are high, again need to confirm.

Open the below programs and run OCCT again.
With the below programs running you can check the readings, frequency, voltage and temps.
Let OCCT idle for at least one minute before you run the CPU test, to get all the system idle info.

1.Download HWiNFO64 click on the 'Sensors' button, use this to compare the CPU Core temps, and Vcore and DIMM voltages. At Idle and while testing, with OCCT.

2. Open CPUZ and check the CPU frequency and FSB.

3. 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 at idle and when testing with OCCT.

One thing that the OCCT graphs did show were some voltage fluctuations. Need to confirm these with the other programs, they don't generate graphs so you will need to monitor them.

Last crash:
STOP 0x000000C2: BAD_POOL_CALLER
Usual causes: Device driver, ?Memory

Code:

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: 000000000000000b, type of pool violation the caller is guilty of.
Arg2: fffffa800b6af2b0
Arg3: 0000000000000400
Arg4: fffffa800b6af5c0
FAULTING_IP: 
nt!ObpFreeObject+20b
fffff800`0317f97b 48c7432000000000 mov     qword ptr [rbx+20h],0
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  dwm.exe - the Desktop Window Manager is responsible for the graphical effects such as 3D effects, live windows previews and windows transparencies.
IMAGE_NAME:  dxgmms1.sys
FAILURE_BUCKET_ID:  X64_0xc2_b_dxgmms1!VIDMM_PROCESS_HEAP::Free+7e

This is usually caused by a bad driver but, can be due to a RAM or CPU fault.
Since the RAM tested good, may need to come back to this, let's check on the CPU with the other monitoring programs and OCCT.

System event logs:
Again the WLAN errors, if you can't get a wired connection you should get a PCI wireless card. These are much better than the USB dongle, as mentioned before they are known to cause crashes.
There are a lot of these, again.

Code:

Event[67]:
  Log Name: System
  Source: Microsoft-Windows-WLAN-AutoConfig
  Date: 2012-06-24T16:30:31.404
  Event ID: 10000
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: ComputerG
  Description: 
WLAN Extensibility Module has failed to start.
Module Path: C:\Windows\system32\athExt.dll
Error Code: 126
-------------------------------------------------------------------------------------------------------------------------------
Event[103]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2012-06-24T01:30:37.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: ComputerG
  Description: 
Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: Not available
Cab Id: 0
Problem signature:
P1: x64
P2: USB\VID_0CF3&PID_9271&REV_0108
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 
Attached files:
These files may be available here:
C:\Users\Grant\AppData\Local\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_f4d4e2f268b2c0df1daf618a2e14f5e555c9d3b_1391667f

Analysis symbol: 
Rechecking for solution: 0
Report Id: ba46fa7e-bdbd-11e1-8d6b-bc5ff436b217
Report Status: 6

What firmware are you running on your Crucial M4 SSD?

Good information again, this does help analyzing these issues.
The M4 firmware is the latest version, though there are some reported issues.

CPU core temps seem a bit high.

Intel® Core™ i5-3570K Processor
Tcase is 67.4°C, add 5°C for individual CPU core temps max is 72.4°C.
These are the Intel recommended levels, overclockers usually exceed these by 5-10°C.

Check that the CPU cooler is firmly attached.
If loose, remove cooler, clean and re-apply thermal paste, re-install CPU cooler.
You might want to consider an aftermarket CPU cooler, there are good coolers for around $30.

Your AsRock Z77 Extreme4 motherboard manual for reference.

Your OCCT graphs are showing a voltage fluctuation, which is worse at idle, this could be causing instability.
For comparison purposes, OCCT graphs from a quick test on my system.
Attachment 218387Attachment 218386Attachment 218385
The Vcore from my graphs.
Attachment 218396

The OCCT graphs from your last test.
Attachment 218394Attachment 218393
The graph on the right shows a large Vcore fluctuation when the system is at idle, and not very stable when at load.

Vcore from the OCCT test with the CPU error.
Attachment 218400
This may be caused by the PSU, a quality PSU is worth every penny.
We can try a few things first.

Let's bump the Vcore and see if it will be more stable.
Linked your motherboard manual above, it's not very helpful.
Go to BIOS and tell me what options your have, should be 'Auto', 'Manual', hopefully a way to add small increases to the Auto setting called 'Offset', this will let it run Speed Step and run cool at idle.
Try an offset of 0.050v, be sure to check the CPU Core temps with Real Temp.
If it boot ok and is stable, then run OCCT, watch the core temps, don't go over 80°C.

I got a PCI wireless card and installed it, seems to be working fine. I checked the CPU fan and it was in fact not as tight as it could be. I ran OCCT and after failing almost immediately the first two times it ran for a full test again and I attached the graphs. CPU temps are maxing out around 72 and hovering in the high 60s/low 70s. RealTemp shows temps slightly hotter maxing out at 74 and also fluctuating in the high 60s/low 70s. Voltages appear to still be fluctuating.

Haven't had a chance to check for more BSODs today, I'll try tomorrow. I did an offset of vcore +.05v and there was an error immediately when it began load, vcore still fluctuates. I'll try for a full test tomorrow.
Thanks again, I'm glad you mentioned the CPU fan.

lian9 said:

After the 2 BSODs I took karlsnooks' advice and ran the game. The game did not crash within 5 minutes and in fact ran for about 30 minutes with no issue. I then put the cover back on like before and played the game again. The game played fine for about 2.5 hours without a blue screen, the longest it has ever gone.

The problems don't sound like heat issues. I'd say you can scratch that angle from the list.

lian9 said:

Memtest ran for 7 passes without any erros.

Scratch that one too.

I know ivy bridge runs hotter than previous generations of cpus, not sure if this is too hot though. I'm using a stock fan on it and haven't overclocked it. Turbo boost must be why it's at 3.6GHz.

For stock clocks with stock fan it looks normal.

Since the CPU is 3.4Ghz normally, with Turbo Enabled - on a single core it's default max is 3.8Ghz. When multiple cores are 'under load' - it's 3.6ghz

lian9 said:

HWiNFO64:
idle temps: 35, 38, 38 ,36 ---fluctuating by about 2 degrees
max load temps: 76, 80, 81, 78 ---usually the temps were fluctuating in the mid/high 70s

All within the normal range for stock cooler. But it doesn't hurt to triple check that all the 'plugs' are firmly secure.

(Ideally when you install the stock cooler, you use a 1,3/2,4 method.

ie Firmly attach plug one then diagonally attach plug 3; then plug 2 and lastly plug 4 instead of plugging and locking in a 'clockwise' pattern. This ensures an even attachment)

VCore: idle at 1.032, load at 1.096, currently at 1.008. ---This fluctuated under idle from ~0.98 to ~1.12, under load it was around 1.096 occasionally changing to 1.104. The fluctuations weren't happening very often.

The drops are vdroop/vdrop - voltage drops. That's normal. Whether it's a manual setting, or on AUTO - the voltage set in the BIOS will differ to what's reported inside Windows.

Out of all your errors, the core failures under OCCT are the biggest 'stand out" issue. This can cause crash dumps to erroneously point the finger in numerous directions. (Like your wireless card)

The fact that you are failing / having core errors with OCCT suggests insufficient vcore (cpu voltage) under load.

This is the first place to concentrate on.



There are a few things you can try during the trouble shooting phase:

► remove the wireless card (just for the moment. It eliminates one variable)

► Increase Additional Turbo Voltage. Since you aren't Overclocking, this should be your first adjustment. Basically you're increasing the vcore when Turbo kicks in.

+


► Adjust your LLC (Load Line Calibration) This is the setting that dictates how much vdrop/vdroop is allowed. It basically forces a more constant voltage.


Alternatively you can basically Overclock by:


► Disabling Turbo and Increasing your overall CPU voltage. With stock cooling, you'd be looking at aiming for for the same speeds/volts you'd get with Turbo On, except it would be more uniform. For Ivy, a +040 offset is more realistic than +.005.

As it stands, we're looking at eliminating hardware issues first. We can look at software/drivers later if need be.


But for now:


► In the OC tweaking section of your BIOS, increase the "Additional Turbo Voltage".

Atm, this is most likely on AUTO so you'll have to experiment with the manual settings. I believe the default is around 0.04v - This will need to be increased. Use CPU-Z to monitor to monitor the vcore adjustments. Use OCCT to test.

► Disable Internal PLL Overvoltage (not needed unless aiming for a really high overclock)

For now, you can leave the rest of the settings on Auto. If it still fails OCCT, we can look at extending plane/ duration settings later.

► If you have not already done so, enable your RAMS X.M.P profile. This will set all your RAMS timings/voltages for you.

► CPU Load-Line Calibration - I'm not sure about your boards settings. It may be a simple enable/disable/Auto or it might have increments.

If it's a simple enable/disable setting - Enable it. If it has increments set it to around 50% to begin with. If you still fail OCCT, you can set it to maximum.


Using the apps mentioned by Dave, Monitor the max vcore and temps. You are correct in the fact that IVY does run hotter. You are more likely to hit a thermal wall than a voltage one.

Don't be surprised, or alarmed if you see core temps in the low-mid 90c's

Thanks for the input smarteyeball.

lian9, I asked smarteyeball to have a look at this thread, he is very good at overclocking and stabilizing CPUs, and he has a Ivy Bridge CPU.
If you follow his advice your CPU will be more stable.