May 5, 201313 yr Had 3 of these in the last hour. Plenty of voltage going through the chip. Can anybody help? Version=1EventType=BlueScreenEventTime=130122537849568131ReportType=4Consent=1ReportIdentifier=7b5e1741-b5b5-11e2-a651-e8173ef10db7IntegratorReportIdentifier=050513-5928-01Response.type=4DynamicSig[1].Name=OS VersionDynamicSig[1].Value=6.1.7601.2.1.0.256.1DynamicSig[2].Name=Locale IDDynamicSig[2].Value=1033UI[2]=C:\Windows\system32\wer.dllUI[3]=Windows has recovered from an unexpected shutdownUI[4]=Windows can check online for a solution to the problem the next time you go online.UI[5]=&Check for solutionUI[6]=&Check laterUI[7]=CancelUI[8]=Windows has recovered from an unexpected shutdownUI[9]=A problem caused Windows to stop working correctly. Windows will notify you if a solution is available.UI[10]=CloseSec[0].Key=BCCodeSec[0].Value=116Sec[1].Key=BCP1Sec[1].Value=FFFFFA80087AF010Sec[2].Key=BCP2Sec[2].Value=FFFFF88004B5A2B0Sec[3].Key=BCP3Sec[3].Value=0000000000000000Sec[4].Key=BCP4Sec[4].Value=0000000000000002Sec[5].Key=OS VersionSec[5].Value=6_1_7601Sec[6].Key=Service PackSec[6].Value=1_0Sec[7].Key=ProductSec[7].Value=256_1File[0].CabName=050513-5928-01.dmpFile[0].Path=050513-5928-01.dmpFile[0].Flags=589826File[0].Type=2File[0].Original.Path=C:\Windows\Minidump\050513-5928-01.dmpFile[1].CabName=sysdata.xmlFile[1].Path=WER-7675-0.sysdata.xmlFile[1].Flags=589826File[1].Type=5File[1].Original.Path=C:\Users\Darren\AppData\Local\Temp\WER-7675-0.sysdata.xmlFile[2].CabName=Report.cabFile[2].Path=Report.cabFile[2].Flags=196608File[2].Type=7File[2].Original.Path=Report.cabFriendlyEventName=Shut down unexpectedlyConsentKey=BlueScreenAppName=WindowsAppPath=C:\Windows\System32\WerFault.exe
May 5, 201313 yr At 4.6GHz on a 2500k, yeah, you had a BSOD. ^_^ What are your voltages and BIOS settings? Bring her back to 4.5 and see if you get anymore. You won't tell a difference. ___________________________________________________________________________________ Zachary Waddell -- Caravan Driver -- Facebook: http://www.facebook.com/zwaddell Avsim ToS Avsim Screenshot Rules
May 5, 201313 yr Sorry thats a typo in my rig specs its actually 4.5ghz Vcore = 1.37 1.37V is not a lot of voltage for 4.5GHz overclock. And what other settings? Are you checking the actual voltage with a hardware monitoring program? ___________________________________________________________________________________ Zachary Waddell -- Caravan Driver -- Facebook: http://www.facebook.com/zwaddell Avsim ToS Avsim Screenshot Rules
May 5, 201313 yr Author Yeah I've got hardware monitor open Zach Vcore 1.368 AVCC 3.424 3VCC 3.424 3VSB 3.424 VBAT 3.344 VTT 1.056 Bus 100mhz x 45 multiplier Passed a 4 hour prime95 test earlier today Should i up the Vcore a little?
May 5, 201313 yr Yeah I've got hardware monitor open Zach Vcore 1.368 AVCC 3.424 3VCC 3.424 3VSB 3.424 VBAT 3.344 VTT 1.056 Bus 100mhz x 45 multiplier Passed a 4 hour prime95 test earlier today Should i up the Vcore a little? Maybe just a smidge. Anyway you could provide pics of you BIOS settings, all voltages, timings, etc? ___________________________________________________________________________________ Zachary Waddell -- Caravan Driver -- Facebook: http://www.facebook.com/zwaddell Avsim ToS Avsim Screenshot Rules
May 5, 201313 yr Yeah I've got hardware monitor open Zach Vcore 1.368 AVCC 3.424 3VCC 3.424 3VSB 3.424 VBAT 3.344 VTT 1.056 Bus 100mhz x 45 multiplier Passed a 4 hour prime95 test earlier today Should i up the Vcore a little? Hi Owen, I had this error earlier this year, after reinstalling my windows 7. This BSOD is not related to your overclock. I found some info that Code 1033 can happen becouse of memory problems, graphic card or driver. But i found one microsoft advice which fixed that issue for me in 5min: run command prompt with administrator rights and type "sfc /scannow" without quotes Hit enter and wait for proces to be completed. That should fix your problem. If not, verify your memory and all drivers, and you can use repair function from windows installation disc. BTW, vcore is just fine, you don't need to increase it every time you get BSOD. I don't know how much you need for 4.5GHz with 2500k, but if temps are ok, you are fine. I allways set higher vcore for full stability. Overclocking related BSOD's http://www.xtremesystems.org/forums/showthread.php?266589-The-OverClockers-BSOD-code-list All the best Zeljko Budovic
May 5, 201313 yr Zeljko beat me to it, but you can Google "BCCode 116". There are hundreds of posts concerning this BSOD stop code. This is the official line from Microsoft for this BCCode: The VIDEO_TDR_ ERROR bug check has a value of 0x00000116. This indicates that an attempt to reset the display driver and recover from a timeout failed. Have you updated video card drivers just before the BSODs began? Any other OS updates recently? Any new software installed that could be interacting badly with your video card? Other things to check: If you've recently installed newer video drivers, step back to a known good version for your card. Run a memtest because DRAM has also been implicated in this stop code error. Run a video card memory test as VRAM is another potential culprit. From what I've read there is no single fix related to BCCode 116, and it may take you some time to track down the specific cause/solution for your situation. Good luck. - Jev McKee, AVSIM member since 2006. Specs: i7-2600K oc to 4.7GHz, 8GB, GTX580-1.5GB, 512GB SSD, Saitek Pro Flight Yoke System, FSX-Acceleration
May 5, 201313 yr Thanks for the info guys, I shall check it all out. One other thing in relation to the sfc /scannow command. If you're squeamish about what it might do to your system, you can first run it with this option: sfc /verifyonly This will simply report which, if any, system files need repair. If sfc does report issues, and you're comfortable with running the repair function, you can then run the repair function: sfc /scannow - Jev McKee, AVSIM member since 2006. Specs: i7-2600K oc to 4.7GHz, 8GB, GTX580-1.5GB, 512GB SSD, Saitek Pro Flight Yoke System, FSX-Acceleration
May 5, 201313 yr @coa1117 - you are right, and i said that can be RAM or graphic card / driver related. But i was refering to this line too "DynamicSig[2].Value=1033" When i had this problem, i found that It can be related to all that things above, but usually is just some corupted windows DLL or other windows file which can be repaired with "sfc /scannow". It worked for me, sometimes is much simpler then we think Zeljko Budovic
May 5, 201313 yr Author I've run sfc/scannow with admin rights and nothing came up in the scan. I've got the 314 driver installed for the card. Il run a mem test and a gpu mem test tomorrow and see if that throws anything up. I think it's just gonna be some trial and error testing to get to the bottom of it. Thanks again for the info. Darren.
Create an account or sign in to comment