Solved Intel burn test is the only thing crashing my PC

I've recently upgraded from the H60 to the H80i, lapped my 2500k to a mirror finish and decided to use the extra 20c (that's right 20c difference in full load temps) to boost my overclock from 3.8 to 4.3ghz. I ran prime95 for 8 hours and received no errors, with a max temp of 68c. Today, I decided to try Intel burn test. I let it run while getting ready for work, and after about 15 minutes I noticed that MSI afterburner crashed. I rebooted @ stock 3.3ghz and ran the tool and noticed afterburner crashed again, so I assumed at this point it was Afterburner. I rebooted at 4.3ghz and went to work with it running, came back to my PC, it was still on, unresponsive, with a black screen, just wondering if you guys can pinpoint if it's the Nvidia driver that's crashing or what? I feel like this would happen on stock clock settings, but I'm unsure.

I've attached my dm log collector results. Thanks in advance!

Basically, what you are telling me is you do not have a BSOD problem, you have an unstable overclock problem. Set everything back to default levels.

Stock

Applied all stock settings and ran Intel Burn when I left for work today, came home to the same black screen.

That is Acronis virtual disk driver

Open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

also :



Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.



What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.






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

Thank you for the awesome reply. I tried everything and found no errors at all with the command prompt after three searches. Driver verifier did not crash my system, but I did manage to crash it by running 7 instances of memtest. I checked CPU-Z and my RAM is the same, but I recently RMA'd 2 of the 4 sticks and noticed that the new ones have a different tRC at 1600mhz (which is what the RAM is rated for and what I am running them at) and the old ones have XMP 1.1 while the new ones have 1.3. Is there any way the difference in RAM timings could be my source as the crashed occur on stock CPU clock settings?

Hardware

Motherboard: Asrock Extreme3 Gen3
Processor: Intel 2500k @4.2ghz on Corsair H80i
Memory: 4x 4GB Team Extreem Dark 1600mhz
Video Card: MSI GTX 970 Gaming edition
SSD: Corsair Force GT 128gb SSD
Hard Drives: 2x 3TB WD Red NAS drive
Optical Drives: 2x LG Supermulti DVD Drive GH24NSB0B
Case: Antec P182
Power Supply: Corsair 600w
Sound: Onboard optical spdif to Sony 5.1 surround
Display: Optoma GT1080 on 100" electric screen
OS: Windows 7 Ultimate 64 bit

Any time you mix ram modules, you are not going to get the best performance and are risking instability.

Would you please tell me how you ran 7 instances of memtest+? If you ran it the way The instructions are, I don't see how that is possible. The instructions for Memtest86+





Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask

Running the iso now and going to bed. Thanks a lot essenbe, you're the best! I downloaded a Windows exe memtest... MemTest: RAM reliability tester for Windows which says to run multiple instances to use all ram. Clearly, I am a noob. I appreciate all of your help so far, hopefully we can pinpoint the issue. If it's a RAM issue, I'm sure I can RMA the original pair for a new, updated set. Team has excellent customer service.

If you want to test your ram, do it the right way. The test will take about 9-10 hours and you have to run a minimum of 8 passes all at the same time. You can't run 5 passes and come back later and run 3 more. They have to be run all at the same time. Please follow the instructions exactly.







Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask

Ok, so I ran memtest for about 31 hours for a total of 15 passes, 0 errors. I noticed that while running, my first core was extremely slow every time it was in use. I exited and rebooted and noticed it took windows about 40 seconds to load (It usually takes ~15 seconds). I uninstalled Acronis, I only had it installed to recover some game save files from my old C:. I ran linpack through OCCT before work and my PC crashed with a proper blue screen. This is a fresh Windows installation less than a week old.

What is your Vcore set to? In bios what is the value of your +12V, +5V and +3.3V? Make sure your SSD Firmware is up to date. Look at your ram settings in bios, look at the sata controller and see what it is set to. Make sure your SSD is connected to port 0 or 1. Set you bios to optimized defaults, set your sata controller to what it is right now, set the frequency, timings and Dram Voltage to manufacturer's specs. Save and exit. Please let me know the values of the voltages.

I updated my SSD's firmware, it was way out of date. Restored my motherboards defaults, set the SATA controller back to AHCI. Set my RAM back to 9-9-9-24 @ 1600mhz. I loaded the motherboard's optimized 4.2ghz setting. The SSD's always been on P0 and my 3TB drive with all my games installed in on P1. The rest of my ports are SATA2. Here's a screenshot (under full load) from HWMonitor with my temps and voltages, and one from the ASRock tuner to show what the voltages are set to in BIOS.

Edit: Just ran linpack for 20 minutes and got a BSOD. Reset CPU to stock 3.3 with 3.6ghz turbo boost, running linpack again. Crashed again in about 15 minutes @ stock. New screenshots of voltages added.

View attachment 341429

View attachment 341430

View attachment 341431

View attachment 341432

1. In the instructions I gave, there is no where in there about your board's 4.2 settings.

2. You are never going to have a stable overclock unless you can run stock stable.

3. You never use your board's auto overclocking to overclock. Period! If you want to overclock, start studying and learn how to do it through bios, manually. Have some idea of what every setting means before you change it.

4. Go back and read #2.

I set my RAM to 1333, processor to 3.3ghz everything totally stock and watched HWMonitor while running linpack. Everything stayed around the same, 80w on the CPU under full load, got through 10 instances of linpack. I used the ASRock tuner to push the multiplier to 42 and ran linpack again 8 more times, 90w under load on the CPU, stock voltage of 1.285. I rebooted to set the 42 multiplier in bios and restarted. Ran linpack and noticed the processor was only getting 65w now. It hit 113w after a couple minutes and immediately froze. I rebooted, set everything back to stock 3.3ghz RAM at 1333 instead of 1600, trying to recreate the stability I had before. Crashed after a couple minutes.

Maybe putting 113W through a 95W CPU damaged it. What you should do is clear CMOS (How To Clear CMOS (Reset BIOS) [Easy, 10 to 15 Min]) When you boot back up, it should send you straight to bios. Clearing CMOS will make BIOS Forget every setting in there including date and time. The first thing you have to do is set optimized defaults (F5) set the date and time, memory timings, voltage and frequency, set the sata controller to what it is right now or you will not boot, set the boot order.

Now, on that particular board, in the overclocking section if you leave it set to auto, it will not set your multiplier right. Set the first section (options are Auto, XMP or Manual) set it to manual. Set your BCLK to 100 and the Multiplier to 37. Now, this part you will have to play with. Set the CPU voltage to manual and the Vcore to 1.250V. By setting it to manual, you will not drop the voltage down on idle, but it will not go above that number either. All you want to do is see what voltage is required to run at stock settings. If it will not boot into Windows, increase the vCore 0.005 (in other words set the Vcore to 1.255), save and exit. Keep doing that until it boots. It should boot at 1.250. Download and install Core Temp (Core Temp) and CPUz, which I assume you already have. Never use but 1 temp monitoring program at a time. Download Intel Burn Test. Set it on standard and the times to run 5. Open core temp, CPUz set to the CPU tab and IBT. Start IBT, after a couple of passes, take a screenshot of all 3 windows at the same time while it is running and post them here.

Reset CMOS, took out the older sticks of RAM, as I'm still not convinced they're problem free. Booted right up at 1.250v at 100.0 BCLK and stock multiplier of 33 (which I assume you meant instead of 37).

No, I meant 37. 37 is your stock boost clock. I also did not want HW Monitor I wanted CPUz (CPU-Z CPUID - System & hardware benchmark, monitoring, reporting). I also want your GPU card at stock.

Ok sorry. everything's been set to what you said. Power's more than 95w on the CPU.

Something is not right at all. Go into bios and look under, probably advanced, CPU settings and see what the 'C' states are. You should have C1e, C3 and C6 probably and maybe the C States package and set them all to enabled. And try it again.

Also, try setting your CPU Voltage to 1.210. If you BSOD, keep bumping it up 0.005 at a time.