Bsod Error Codes Windows 7 Overclocking
Contents |
BlasterIn WinAquatuningFeenixView MoreSelect OneAquatuningAsusFeenixIn WinSound Blaster Alphabetical Article List # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z ( All ) Common BSOD Error Code List for Overclocking By: Bobicon, tinytomlogan12, and bsod error codes windows 7 64 bit Broodyr Posted 11/25/11 • Last updated 6/15/12 • 86,136 views • 26 comments Common BSOD
Bsod Error Codes List
Error Codes for Overclocking 0x101 = increase vcore 0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it bsod error codes event viewer is on i7 45nm, usually means too little VVT/QPI for the speed of Uncore on i7 32nm SB, usually means too little vCore 0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore 0x1A =
Bsod Error Codes List And Solutions
Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage 0x1E = increase vcore 0x3B = increase vcore 0x3D = increase vcore 0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage 0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances 0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower bsod error codes reasons & troubleshoot uncore if you're higher than 2x 0x109 = Not enough or too Much memory voltage 0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU) 0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /rBSOD Codes for Sandy Bridge 0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT) 0x101 = add more vcore 0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT 0x1E = add more vcore 0x3B = add more vcore 0xD1 = add QPI/VTT voltage “0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances” 0X109 = add DDR3 voltage 0x0A = add QPI/VTT voltage For a complete list of BSOD error codes that may or may not be related to overclocking vist this link. You may also want to give this other article I wrote a read if you are wondering how to disable auto restart after a BSOD. Comments (26) There are no comments yet Aznboy1993 11/29/11 at 3:26pmThank you. This will be an invaluable reference to any of my (and everyone else's) future overclocking ventures. Defunctronin 12/8/11 at 2:47pmThanks, I've had a hell of a time understanding my BSOD codes when I'm overclocking. I'm usually able to get it stable via trial and error along with stress testing, but this is a wonderful time saver. Thanks again =D!
list Discussion in 'Overclocking & Cooling' started by jlewis02, Feb 11, 2011. Feb 11, 2011 at 4:54 AM #1 jlewis02 New Member Joined: May 13, 2006 Messages: 773 (0.20/day) Thanks Received: 95 System Specs
Bsod Error Codes Microsoft
Processor: i7 930@4ghz 1.30v Motherboard: Asus Rampage II Extreme Cooling: Megahalems Memory: 3x2gb OCZ
Blue Screen Error Codes Windows 7
1600mhz 8-8-8-24 Video Card(s): HD5850 Hard Disk(s): 128gb SSD Corsair M4,500gb,750gb Optical Drive: Samsung Blu-ray LCD/CRT Model: Asus 23in 1920X1080 Case: windows vista blue screen error codes CoolerMaster HAF 932 Sound Card: X-Fi Power Supply: Corsair tx750w Software: 7 Home 64bit BSOD Codes for i7 x58 chipset 0x101 = increase vcore 0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test http://www.overclock.net/a/common-bsod-error-code-list-for-overclocking to see which one it is on i7 45nm, usually means too little VVT/QPI for the speed of Uncore on i7 32nm SB, usually means too little vCore 0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore 0x1E = increase vcore 0x3B = increase vcore 0x3D = increase vcore 0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage 0x9C = QPI/VTT most http://www.techpowerup.com/forums/threads/the-overclockers-bsod-code-list.140238/ likely, but increasing vcore has helped in some instances 0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x 0x109 = Not enough or too Much memory voltage 0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU) 0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r BSOD Codes for SandyBridge 0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT) 0x101 = add more vcore 0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT 0x1E = add more vcore 0x3B = add more vcore 0xD1 = add QPI/VTT voltage “0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances” 0X109 = add DDR3 voltage 0x0A = add QPI/VTT voltage Please feel free to comment, advise, correct, and add to this list. I am not the original author and will not take credit for it. I simply thought that it should be posted by itself. I am only repeating the info that I got here and at XtremeSystems.I would like for everyone to help me set it up for other systems as well. I found this and thought I would pos
Laptops tips Best laptops Laptops buying advice Laptops news Tablets Tablet reviews Best tablets Tablet tips Tablets buying advice Tablets news Business Business tech tutorials Business tech buying advice Business tech news Reviews Smartphones Laptops Tablets http://www.pcadvisor.co.uk/how-to/windows/guide-bsod-codes-3638935/ PCs Software Apps Printers Storage Devices Wearable Tech Digital Home Wi-Fi and Networking Games consoles http://www.pcgamer.com/blue-screen-of-death-survival-guide-every-error-explained/ Tech accessories Audio Displays Graphics cards Cameras Computer Mice and Keyboards How To Windows Security Apple Android Smartphones Tablets Software Laptops Broadband Gadgets Games Smart Home Audio Photo & Video Printing Components Desktop PCs Peripherals PC Upgrades Linux Business Enterprise Social Networks Tech Industry Internet 3D Storage Downloads Windows downloads Mac downloads Linux downloads iPad & iPhone error codes downloads Android downloads Windows Mobile downloads Audio, Video & Photo downloads Backup & Recovery downloads Design & Illustration downloads Developer & Programming downloads Disc Burning downloads Finance & Accounts downloads Games downloads Hobbies & Home Entertainment downloads Internet Tools downloads Kids & Education downloads Networking Tools downloads Office & Business downloads Operating Systems & Distros downloads Portable Applications downloads Security downloads Social Networking downloads System & Desktop Tools downloads Forums Tech Helproom Windows bsod error codes Help Digital Home & Smartphones Help Consumer Rights Advice Apple Help Games Speakers Corner Beta Testing All All News Reviews How-Tos Opinions Downloads Forums Search PC Advisor Reviews News How to Group Tests Features Opinions Buying Advice New Products Shop Forums Advisors Twitter Facebook Google+ LinkedIn YouTube RSS Hot Topics Google event Google Pixel New Nexus 7 (2016) Google Home Daydream VR Chromecast Ultra Home How-To Windows How-To Guide to BSOD codes Guide to BSOD codes: how to solve your Blue Screen of Death on a Windows computer Guide to BSOD codes Most Windows users have at some point in their life experienced or know of people who have had BSODs. In this guide we will aim to cover a few of the most common BSOD codes and a very rough guide on how to solve it. If you've ever experienced a Blue Screen of Death (BSOD) you'll want to solve your problem. By Christopher Minasians | 21 Apr 16 Share Tweet Send Hi. I saw this on PC Advisor and thought you should see it too. Comments Microsoft is better known for its operating system Windows, but if you've ever asked a Windows users if they've had any problems with their PC, they'll probably tell you about their BSODs and the w
Paul Lilly Shares Every Blue Screen of Death (BSoD) deciphered (Updated!)If you're returning here by way of bookmark, first off, please accept our condolences. There's only reason you spend time reading a Blue Screen of Death (BSoD) article, and that's to try and solve a problem you're having with your own system. If we could give out a teddy bear stuffed with cash to each person that visited this article, we'd do it. Sadly, we don't have teddy bears, and what little cash we have is usually spent at the pub.Secondly, you must we wondering, "Oh snap! I see change, and I hate change! Where's the old BSoD article I bookmarked?!" Not to fear, we realize you hate change, which is why come hell or high water, you're sticking it out with Windows XP even after Microsoft stopped supporting it on April 8, 2014. We have your back, and the original article is still here. All of it. So what are we doing here?The first is we're updating verbiage where necessary. If there was something that seemed difficult to understand before, it should now be easier to decipher. The second thing we've done is added some new information. You see, BSoDs are far less common in the Windows 8/8.1 era, and that was true in the Windows 7 days as well. We've updated this article to explain what happened and what's changed.Finally, we've added a picture gallery. No, it's not filled with cute fuzzy kittens and lolcats, though we're not opposed to either one. It is, however, populated with some of the most embarrassing and comical BSoDs to have ever occurred. Hopefully you'll get a chuckle out of it, or at the very least come to realize that the BSoD you're dealing with isn't as bad as could be.Sound like a plan? Great! Let's get started!Picture this: It’s late at night, you’re sitting at your computer playing a game or working on a project when, suddenly, Windows freezes completely. All your work is gone, and you find a blue screen full of gibberish staring back at you. Windows is dea