Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD on a system made for extreme OC

30 Jan 2015   #1
Shept1z

Win 7 64bit
 
 
BSOD on a system made for extreme OC

Hello, please Help! My setup out of the box is suppose to be easy very stable OC to 4.5+. I have had this mobo for over a year and in the past had it running at 4.3 and 4.2 but after a bios update i never tried to get it back there. I started tring recently and get BSOD everytime it is stressed tested or gaming at 4.2. Ran memtest 3.5 passes (10hrs). checked and updated drivers, clean uninstall and reinstall of latest video drivers. i am at a loss and overwhelmed with all the selection in this bios. whats next? Thanks...

rampage 4 extreme - bios 4901
I7 3930k sandy bridge
32gig Patriot Memory’s Viper Xtreme Edition 8-9-8-24 xmp
2x evga 680 gtx ftw 4gig
psu - hx1200
cool - H100
win 7 64
3 monitors
1 ssd & 1 hhd


Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 1/30/2015 6:29:15 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF880035DF180)
Bugcheck code: 0x101 (0x11, 0x0, 0xFFFFF880035DF180, 0x8)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error.
Google query: CLOCK_WATCHDOG_TIMEOUT



On Fri 1/30/2015 6:01:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\013015-12355-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF880009BBD70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 1/22/2015 2:55:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012115-12402-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF880033DFD70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


My System SpecsSystem Spec
.
30 Jan 2015   #2
Wrend

Windows 7 Professional SP1 64bit, Debian GNU/Linux 64bit (virtual machine on a RAM drive)
 
 

Hey, nice system. Pretty similar to mine. I also use to have 2 EVGA 680 FTW+ (4GB) cards.

Let me ask you: What VCores are you running at the different multiplier rates, and how are you specifically going about doing your overclocking? Also, what's the clock speed of your RAM's XMP (1600MHz, 1800, 2400, et cetera), and are you loading the XMP settings?

At 4.2GHz by just raising the multiplier, you should be fine with a VCore of 1.25 or so.

Also, make sure your CPU PLL Voltage is at the stock 1.8. For some reason mine had dropped at some point with out me knowing and was causing stability issues.

For starters, you may want to go to factory default BIOS settings again, and we can work from there to try and get the clock rate up while maintaining stability.
My System SpecsSystem Spec
30 Jan 2015   #3
paulpicks21

Windows 7 Professional 64 bit
 
 

Good reply Wrend. I would say it's either down to Vcore or Ram speed/timings.

A CPUz screenshot of the CPU tab (under load) and Ram tab would be useful.
My System SpecsSystem Spec
.

31 Jan 2015   #4
Shept1z

Win 7 64bit
 
 

No dice, I turned the vcore up to 1.3 and worked my way up to 1.35 and meet the same result. At ever attempt at 4.2 a BSOD. i used IntelBurnTestV2. My memory is DDR3 1600 (PC3 12800) - Timing 8-9-8-24 - Cas Latency 8 - Voltage 1.65V not sure if the 1.65v is a issue. i have tried it with the XMP but same results.

What VCores are you running at the different multiplier rates, and how are you specifically going about doing your overclocking? all of them, I not aware of any other way. I am only using the multiplier. I am only using the ram timing speed 8-9-8-24 and not touching the bus speed.

I started with this guide ASUS Rampage IV Extreme - Easy Overclocking Guide - Republic of Gamers and thought this should be easy....well I guess not


Attached Thumbnails
BSOD on a system made for extreme OC-bsod.jpg  
My System SpecsSystem Spec
31 Jan 2015   #5
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

Quote   Quote: Originally Posted by Shept1z View Post
Ran memtest 3.5 passes (10hrs)
Unfortunately thats insufficient - a minimum of 8 consecutive passes is required to call your RAM "passed".
My System SpecsSystem Spec
01 Feb 2015   #6
Wrend

Windows 7 Professional SP1 64bit, Debian GNU/Linux 64bit (virtual machine on a RAM drive)
 
 

You shouldn't need the VCore that high, especially not at 4.0GHz. If you do, then there is likely something else going on that is wrong, or you have a very weak chip that can't take overclocking. Perhaps you pushed it too high for too long before.

You might want to try reflashing the BIOS, if you can, since you seemed to first notice these problems with a BIOS update.

As I previously stated, you should not need to go above 1.25 VCore for a 4.2GHz clock on the 3930K, definitely not more than 1.3 VCore. So if it isn't stable at that voltage, I wouldn't bother with trying it at higher voltages. Something else is going on, or you have a weak chip. Sorry.
My System SpecsSystem Spec
05 Feb 2015   #7
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

I have a different chipset than you and Wrend, so I can't give you specific advice. What I can tell you is you have to know and understand the bios and what every setting means and what affect it has on other settings. You have to spend the time to set the bios up for overclocking before you even think about Multiplier and Vcore settings. Things like Wrend mentioned such as CPU PLL voltage and C states and Load line calibration have a big effect on Vcore and stability. I know those boards can be real tempermental and some settings really throw everything off, especially ram settings.
My System SpecsSystem Spec
10 Feb 2015   #8
Wrend

Windows 7 Professional SP1 64bit, Debian GNU/Linux 64bit (virtual machine on a RAM drive)
 
 

Yeah, good point, essenbe! Something that seems easy on the outside can likewise easily get thrown off from minor under the hood tweaks.

I set this up in the BIOS now, but still use these settings as my default go to, baseline OC. With sufficient cooling, you should reasonably expect and be able to fairly easily hit at least 4.2GHz stable, and likely higher with some fine tuning. Maybe raise the VCore a little (up to 1.3V) if needed, determined through stability tests. You shouldn't need to raise it any more than that for that clock rate.

I do load the XMP for my RAM first, and then just tweak the CPU after that, but only because I've determined that it seems to work well with it. I'm using two identical matched sets of 32GB of RAM (64GB total, 8×8GB DIMMs) and have it set up so that each matched 32GB set is on the same corresponding four channel slots. 10-10-10-27, 1600MHz, 1.5V. You could try loosening up your timings. I have fairly different RAM from you, so I can't comment more specifically on how yours should work and what settings might be best.

Also, for these settings, do not use the VCore offset; manually set it, otherwise it will throw your VCore off from where it should be.

I hope this helps some, as you do have quite a nice rig, and I'd like for it to work well for you.

You can also try reseating things and/or switching out different components to try and rule out any specific component issues. I understand that this isn't always easy nor feasible. It can sometimes take a lot of work finding the weak link and how to resolve it, but in the end when your system is performing where you want it within what you can reasonably expect from it, it's worth it.

Good luck, and let us know how it goes!

Edit:

I just wanted to also mention that the stability and longevity of my 3930K is very important to me since I keep my computer up and running nearly 24/7 crunching for scientific and humanitarian research (primarily on my GPUs, though I do run some of these tasks on the CPU too), while also hosting a few Minecraft servers for family, friends, and co-workers to play on. Point being that I can pretty easily push this CPU significantly higher and keep it "stable enough" for gaming, running benchmarks, or similar, up to around 4.8GHz or so. 4.6GHz is more of a reasonably high OC for this CPU since I can keep the VCore at a safer level, a little below 1.4V.

From my research on this as well (referring to the site you linked to above), 1.4V is generally considered to be the high end VCore limit for a safe, more consistently used OC (which can limit how high you can potentially get the clock rate of your CPU). Ideally though, you want the VCore as low as you can get it at any given OC while still keeping the system stable. Also, it's a given that you need to have sufficient enough cooling, with your 3930K cores preferably staying below or at least not getting much above 70°C loaded. These are just the generally agreed upon safe higher end limits for longer term OCing of this CPU that I am aware of. Some can be pushed significantly higher without failing, of course, though it isn't considered safe for the continued performance and longevity of the CPU. Every individual CPU is at least a little bit different than the rest and will likewise have at least slightly different capabilities and operational tolerances, even if those differences happen to be too small to discern, though of course some outliers can have much more significant differences. These chips are made to at least perform within their stock clock rates, and likely a bit higher, but how high they can safely be pushed over stock rates is never guaranteed. (Well... unless you happen to pick one up from someone who tests them and resells them at a premium with some kind of a performance guarantee, I suppose, though I don't personally have any experience with that.)

Anyway... long story short: From my own experience using this CPU and what I've heard from many others that use it, 4.2GHz isn't asking that much at all really from your 3930K, and it should very likely be relatively easy to reach. This may be a little controversial, but I actually generally consider this to be the clock rate that owners of this CPU should at least OC it to (assuming they have the know-how to do so) to get more of their money's worth from it, though I'm not saying that it isn't a capable CPU if it isn't overclocked. Of course it's a given that sufficient cooling is needed and that CPU power efficiency isn't a higher priority for the CPU's owner. In your case, this makes me think that there is most likely something else that is holding your CPU back. So hopefully this can be resolved.

BSOD on a system made for extreme OC-4.2.png


My System SpecsSystem Spec
Reply

 BSOD on a system made for extreme OC




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
add an icon to a context menu entry made by the system ?
Hi, is it possible to add an icon to a context menu entry made by the system ? :orb: I would like to have an icon for "Open file location". Regards, Tom
Customization
BIOS update made system crash!!
Hi, I need a help to fix my lappy issue.. Lenovo Z570; WiFI was not detecting the router so i have downloaded drivers and updated from lenovo support store, still the problem was not fixed so i found some suggestion as to update the BIOS. I did the same from lenosupport store it self, after...
General Discussion
windows7 has made my 136GB partition as system reseved and boot!!!!
I have Dell inspiron 15R N5110,with 500 GB HDD,3GB RAM and core-i3 processor. My harddisk has 4 partitions 1) drive C logical 48GB 2) drive D primary 136GB 3) drive E primary 200GB ...
Installation & Setup
BSOD whilst system idle, no recent changes made.
Hi, in the last 2 days I have received 2 BSOD's, the system has been running fine for about 5-6 months with no issues. I couldn't get the perfmon /report, I get a message saying an error occured whilst generating the report. Spec; Win7, retail, installed fresh 5-6 months ago. Thanks in...
BSOD Help and Support
Latest realtek driver made my audio system sound terrible
I just installed the latest driver and now the sound qulity is notso good as before even i ddint change anything in my realteck manger. I dont know if it counts but I my windows is installing automatically another driver HD audio device but I dont think that matter since I have that disabled and...
Sound & Audio
BSOD + extreme lag issues
Hello, I've just had a blue screen and hoped someone could help me interpret it. I dont know if it is related but i am recently having problems playing dawn of war 2 retribution multiplayer despite decent specs and a 20mps connection- dont know if anything is failing here that would affect...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 15:05.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App