Think I fried my 2500K :'(

[NdMk2o1o]

Was overclocking yesterday and messing with the vcore anyway normally I have it set manually though thought I would try the offset mode, anyway the issue is my efi bios doesn't have the best mouse support and when trying to scroll down boxes it becomes buggy, I ended up setting it to +0.5v which is the highest setting and misread it as 0.05v booted and BSOD, now I get an instant BSOD even at stock settings, tried everything

 

[AsRock]

Tried removing the cmos battery for a hour ?.. And you checked the mobo just to see if thats gone and not the cpu ?.

 

[NdMk2o1o]

not tried removing battery for an hour no, though have reset cmos, at stock settings trying to reinstall Win7 x64 it loads the files and then when the windows flag icon appears it BSOD there, the message is

MACHINE_CHECK_EXCEPTION with code STOP: 0x0000009c (0x0000000000000001, 0xfffff8800376bb30, 0x00000000bf800000, 0x0000000000000115)

 

[TRWOV]

It could also be a RAM stick or HDD although getting it while overclocking the CPU is a strong indicator of a failed CPU or board.

Have you tried the CPU in another board?

 

[NdMk2o1o]

Nope dont have another board/CPU to test none of my friends have an SB setup either

 

[NdMk2o1o]

it's odd, it will load one of my OC profiles which is 4.2ghz and start windows insallation so I am thinking it's probably not the CPU however I still get the BSOD once the windows icon appears, how can I troubleshoot this without another rig

 

[overclocker]

run in safe mode ? Try underclocking as much as you can. Remove all ram but one stick. hope this helps

 

[mjkmike]

Have you looked for damage. Take the side panel off and look through the CPU hole. Also look at any thing on the front of the board.

 

[NdMk2o1o]

it wont run my oc profile as I previously thought it was running default settings anything other than these and it wont post, oh and am shit out of luck if its the CPU as even though it was a retail chip amazon only offer 30 days so would have to go direct to intel

have removed all drives except my dvd drive and when it gets to the same point of windows installation it BSOD so I can't start in safe mode as I have no windows installation to boot into, removed everything except 1 stick ram, gpu and cpu and still the same, only posting at default options FFS

 

[JATownes]

Remove battery as stated before, and wait an hour or so. I had a DFI board that did this too. Removing the battery and letting it sit for a bit did the trick.

 

[NdMk2o1o]

I highly doubt this will make any difference, what will this do apart from clear cmos which I have done numerous times? regardless I am going out anyway so I will do it though I don't expect anything to have changed when I come back

 

[FreedomEclipse]

Hard luck bro

 

[Anusha]

that BSOD code is very BAD it seems. points to a problem with the CPU >_<

http://en.wikipedia.org/wiki/Machine_Check_Exception

no chance of finding a Linux Live CD, just to confirm that the CPU is really screwed?

 

[Darkleoco]

Ouch, overclocking does have its dangers sometimes it seems :/

 

[crazyeyesreaper]

most likely the chip is damaged and if you used XMP profiles your fucked intel will refuse RMA

 

[Iceni]

most likely the chip is damaged and if you used XMP profiles your fucked intel will refuse RMA

why would intel refuse RMA on XMP. It's intel tech.... Just a personal curiosity.

 

[erocker]

Remove battery as stated before, and wait an hour or so. I had a DFI board that did this too. Removing the battery and letting it sit for a bit did the trick.

I highly doubt this will make any difference, what will this do apart from clear cmos which I have done numerous times? regardless I am going out anyway so I will do it though I don't expect anything to have changed when I come back

Remove the battery. It can and may make a difference. I've had plenty of boards where just resetting the CMOS wasn't enough, but removing the battery was. It's easy to do.

 

[NdMk2o1o]

Battery's out, will leave it an hour or so and check, what seems more likely the board or the CPU is fried if this doesn't fix it?

 

[erocker]

Based off of what you did I don't see how anything could of fried.

 

[NdMk2o1o]

Based off of what you did I don't see how anything could of fried.

Nor me but never had anything like this happen so I am worried, what does the vcore offset actually do cause as mentioned I set it at +0.5v (stupid glitchy mouse control in efi bios ) so what would that actually mean for the CPU as mentioned it wouldnt boot anyway so was only running like that for a minute

 

[LAN_deRf_HA]

My friends MSI P67 G45 has a very similar issue with the mouse even on the latest bios. Pretty annoying but at least the keyboard works.

 

[eidairaman1]

http://www.aumha.org/a/stop.htm

 

[qubit]

I'm cautiously optimistic that you haven't fried it. You've removed the battery as has been suggested, which is great. I'd like to also add that you should move the cmos clear link over, as described in the mobo manual. It's not clear from the posts above if you've actually done this bit. If not, it's a very important step to try.

 

[NdMk2o1o]

So after removing the battery for an hour then only having one stick of RAM and the dvd drive connected I turned it on, it posted and the Win7 dvd started loading, it actually made it past where it did before and took me to the installation options with no BSOD woohoo so exiting the windows installation cause I had no drives attached anyway I proceeded to install the other 3 sticks of RAM, my soundcard and plugged my other drives in, startedup, posted and started to load windows, then bam, the same BSOD happened proceeded to remove all the drives except the dvd, kept all 4 ram sticks in and the same BSOD, removed the soundcard too BSOD took 3 sticks out BSOD, tried a different stick, BSOD rinse and repeat until I tested all 4 sticks seperately (and in different slots) with no change??? WTF gives?

 

[sneekypeet]

I would pull the CPU off the board and examine both the socket and the back of the CPU at this point. Not saying you did any damage here, but I had a similar response from my PC when I blew the socket up