Ok, I hope this covers all of it. CPUZ screenshots zipped and attached.
All bios settings are default/auto
Ram settings:
tCL 9
tRCD 9
tRP 9
tRAS 24
tRFC 107
tWR 10
tWTR 5
tRRD 5
tRTP 5
tFAW 25
CHA RTL 46
CHB RTL 48
tWL 7
RttNoM(?) 20
RttWR 120
Voltages: (ASROCK vdrop control: [w/ vdrop] )
CPU: 1.075 V
DRAM: 1.615V
CTRL ReF -0.000V
DATA ReF -0.000V
VTT 1.219V
PCH 1.079V
CPU PLL 1.853V
Other voltage info
Vcore : 1.04 V
+3.30: 3.408V
+5.00V: 5.160V
+12.0V: 12.160V
Ok, ran memtests and windows extended two passes, no issues. been running the verify crash enforcer, lol. 5 BSODs today so, I am uploading the new bsod compilation. Good luck!
None of the crashes were verified. Make sure verifier is enabled by running a command prompt and typing:If you see a list of things flash up on the screen and scroll through, it is enabled. If you get a short message or a message that displays too fast to read, it is not enabled properly.Code:verifier /query
Crashes indicate hard disk problems or issues with avast! You should start by re-installing avast!. First uninstall it with the avast! uninstall utility. Then download a fresh copy of it. Install the fresh copy.
Well, that sucks. I figured it had to be running because my computer was operating at ~5x slower than usual. Will redo the steps in hopes that it will work properly this time.
Also, uninstalled and reinstalled avast!.
Nice work with avast!.
Let us know when you have new .dmps after Verifier is enabled.
Ok, I definitely had verifier running as every time I started my computer I performed "verifier /query" to check. I tried w/o avast!, with AVG, and without both (just windows defender). Seems to happen with all of them. Yet the blue screens always look different.
Thanks again for your continued help.
Only one crash was Verifier enabled, and it pointed to a Windows driver involving your hard disk encryption. That may be a false positive or it may mean you have hard disk related problems. All crashes are indicating hardware, basically.
Disable Verifier prior to doing the next steps.
Run some hardware checks.
- If you are overclocking any hardware, please stop.
- If you have an SSD, make sure the following are up to date:
- SSD firmware
- BIOS Version
- Chipset Drivers
- Hard disk controller drivers/SATA drivers
- If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
- Run all but the advanced tests with SeaTools for HDDs.
- Monitor temperatures during the following tests.
Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
- Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
- Follow the steps for doing CPU stress test using IntelBurnTest
Quote