Bluescreen windows crash

[Darren1 2]

Had 3 of these in the last hour. Plenty of voltage going through the chip.

Can anybody help?

 

 

Version=1
EventType=BlueScreen
EventTime=130122537849568131
ReportType=4
Consent=1
ReportIdentifier=7b5e1741-b5b5-11e2-a651-e8173ef10db7
IntegratorReportIdentifier=050513-5928-01
Response.type=4
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Windows\system32\wer.dll
UI[3]=Windows has recovered from an unexpected shutdown
UI[4]=Windows can check online for a solution to the problem the next time you go online.
UI[5]=&Check for solution
UI[6]=&Check later
UI[7]=Cancel
UI[8]=Windows has recovered from an unexpected shutdown
UI[9]=A problem caused Windows to stop working correctly.  Windows will notify you if a solution is available.
UI[10]=Close
Sec[0].Key=BCCode
Sec[0].Value=116
Sec[1].Key=BCP1
Sec[1].Value=FFFFFA80087AF010
Sec[2].Key=BCP2
Sec[2].Value=FFFFF88004B5A2B0
Sec[3].Key=BCP3
Sec[3].Value=0000000000000000
Sec[4].Key=BCP4
Sec[4].Value=0000000000000002
Sec[5].Key=OS Version
Sec[5].Value=6_1_7601
Sec[6].Key=Service Pack
Sec[6].Value=1_0
Sec[7].Key=Product
Sec[7].Value=256_1
File[0].CabName=050513-5928-01.dmp
File[0].Path=050513-5928-01.dmp
File[0].Flags=589826
File[0].Type=2
File[0].Original.Path=C:\Windows\Minidump\050513-5928-01.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-7675-0.sysdata.xml
File[1].Flags=589826
File[1].Type=5
File[1].Original.Path=C:\Users\Darren\AppData\Local\Temp\WER-7675-0.sysdata.xml
File[2].CabName=Report.cab
File[2].Path=Report.cab
File[2].Flags=196608
File[2].Type=7
File[2].Original.Path=Report.cab
FriendlyEventName=Shut down unexpectedly
ConsentKey=BlueScreen
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe
 

 

[ZachLW 37]

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.

[Darren1 2]

Sorry thats a typo in my rig specs its actually 4.5ghz

 

Vcore = 1.37

[ZachLW 37]

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?

[Darren1 2]

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?

[ZachLW 37]

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?

[lodestar 186]

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

[coa1117 53]

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.

 

 

[Darren1 2]

Thanks for the info guys, I shall check it all out.

[coa1117 53]

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

[lodestar 186]

@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

[Darren1 2]

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.