X58A-UD3R Won't Post

[Atomic_Sheep]

Hi, put in a new CPU into my mb, same as the one I had previously but one that I think hasn't been overclocked, hence the change. My computer wont post. It turns on and off again after a second or so. My SB 1 I think it is red LED flashes when the power button is pressed and flashes just before it powers down. No idea what this means.

[shadowsports]

Greetings,
There are 2 revs of this board. The former has 8 BIOS versions available dating back to 2009.

Which version board do you have?
What BIOS rev are you running?
What CPU are you using?

Did you flash the BIOS prior to install?
Have you attempted to clear or reset the CMOS?

Is it possible the new CPU has missing or bent pins?  I'd verify this.  If you removed your memory, that is another place to look.  An identical processor should not cause the system to bootloop, but if it was faulty or other damage occurred, you could get the POST failure.

I wouldn't bother replacing a working CPU on a board with this architecture and age. Does the old CPU still work?

The key for SB Voltage is below:

SB Voltage
Off: Normal condition
L1: Level 1 (Slight, green)
L2: Level 2 (Moderate, yellow)
L3: Level 3 (High, red)

I'd be more concerned with the LED staying on than briefly flashing.  That could just be it seeing power when the board is switched on, but we aren't there to see it, so it might be indicative of high voltage also.   
 

[Atomic_Sheep]

Thanks for the response.

I'm pretty sure I have the first revision.

I'm using the latest BIOS that is available for my board. I haven't checked which version exactly, but no new revs have come out in some time so I'm pretty sure I'm still current.

No I haven't flashed my BIOS prior to install.

Yes I tried resetting CMOS a few times with no change.

I used to have an i7 930 (I unfortunately sold it already otherwise I would have just put it back in a called it a day), I purchased a second hand Xeon X5670 which I overclcocked to 3.8Ghz. It was working fine for a few weeks until suddenly it crashed and then I started getting BSOD initially only at welcome screen but now I get random BSODs all over the place sometimes 3-4 in a row upon entering welcome screen and then random ones during use.

Therefore I purchased another X5670 to see whether it was just the CPU that I damaged and not the motherboard. It is this latest X5670 that the computer won't start up with.

I'm using intel, they don't have pins.

I have run Memtest overnight, there were no issues identified. I disconnected all HDDs because I read that might be a problem also, but the latter didn't change anything.

Sounds like I have L3 SB voltage warning because the LED that lights up is red. But it doesn't stay one, so maybe this is normal operation. But the computer still won't POST.

[shadowsports]

Greetings,
The page for your board isn't loading for me this AM.  I looked at it yesterday. 

The pins I was referring to are in the socket.  They more resemble "nubbins" but can be smashed or bent. 

Basically, you'd want to verify all connection, reset BIOS, disconnect all peripherals, and test your memory.  You've basically done all of this, except inspect the CPU socket.  I'm willing to bet its fine, but wise to check.

Bench testing is the next step.  (Removing the board from the case).  Now you can closely inspect the board (both sides) and components, electrical capacitors, etc.  You are looking for discolored, bulging or blackened areas.

CPU replacement is not the first thing to change if you experience BSOD.  Normally you would reset the BIOS, ensure there were no overheating issues, test memory, then disconnect all peripherals. 

That said, you know your system best.  If you had reason to think something was damaged electrically because of OC, etc. I would believe you.  It is still wise to check the obvious, anything which was changed out.     

If the LV3 LED is staying on the entire time from power up to reboot loop, then that's the issue.  if its only a brief flicker, it might be something else.  Given the age, I wouldn't invest a great deal in the hardware.  If you have a computer shop nearby, ask them if they can test the CPU for you, but I wouldn't buy anymore hardware until I was certain.  If it POSTs, then you'll know its probably the board.   

[shadowsports]

Page for you board is working again this AM.  Support for X5670 is not listed as supported for the rev. 1.0 PCB of your board.  The X5570 is listed for PCB rev. 2.0 with BIOS "FF" or later.  No reason to think the 5670 wouldn't also be supported.  Shares same specs.  But some chips might not work on rev. 1.0, so if that's the rev you have, you could get one that works and one that doesn't. One is 45nm, the latter 32nm. 

You can compare here:

https://www.gigabyte.com/us/Motherboard/GA-X58A-UD3R-rev-10#support-cpu

Hard to diagnose in a forum, but I wanted you to have as much information as possible. 

 

[Atomic_Sheep]

I purchased yet another CPU and it arrived in the mail today. I got ready to chuck in the new one but after taking out the one that wouldn't post, I noticed dirt on the pins. I vacuumed it out and lo and behold, it started right back up. Unfortunately, I already got a BSOD, so the CPU is unlikely to be the culprit.

[shadowsports]

Amazing what a little dirt can do hugh?

What's left.  Memory, PSU or the board itself.  I'd still recommend a computer shop if you want to further diagnose.  It will cost very little and you don't have to buy anything you'll be stuck with. Otherwise borrow stuff from a friend.

Intel's 8 core coffeelake is just around the corner    Get those CPU's up on eBay.

[Atomic_Sheep]

Yep, went to check the pins as you suggested and boom, there was your problem.
To be honest, I think there is nothing wrong with any of my hardware now that I've been through everything. I think what happened (and correct me if what I'm saying makes no sense), was when the overclock became unstable, it corrupted a driver which has now caused BSOD. I 'm going to re-install my computer and reformat all my HDDs and see if that fixes it, because I think rewriting corrupt data should fix the problem.

The BSOD dump files have all been of 3 types:

0x50 - PAGE_FAULT_IN_NONPAGED_AREA

"Bug check 0x50 can occur after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another possible cause is the installation of a faulty system service or faulty driver code.

Antivirus software can also trigger this error, as can a corrupted NTFS volume."

"0X1A - MEMORY_MANAGEMENT

2.) 061018-21044-01
Probably caused by : memory corruption
Process Name - taskhost.exe
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
"A page table page has been corrupted. On a 64 bit version of Windows, parameter 2 contains the address of the PFN for the corrupted page table page. On a 32 bit version of Windows, parameter 2 contains a pointer to the number of used PTEs, and parameter 3 contains the number of used PTEs."

and

"0X24 - NTFS File system

"The NTFS_FILE_SYSTEM bug check has a value of 0x00000024. This indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives.

Important This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors."

Cause

"One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted hard drive (SATA/IDE) drivers can also adversely affect the system's ability to read and write to disk, thus causing the error."

I have an error next to one of my IDE drivers in device manager as per attachment. But I can't find any information about it. Google results in nothing but I'm guessing it's the ICH10R chip driver but I'm not sure.

[shadowsports]

Your post has come full circle.  From no POST to driver, windows service and file system corruption. 

It sounds like you have got the hardware end of things fixed.  I can't speculate on the other issues as only you know how long they existed.

If you have file system corruption, I'd check the health of my disk.  Your issues might be easily solve-able.  My advice might be considered overkill, but I operate on the premise of do it once right and then you don't have lingering issues to deal with.

I think reinstalling from scratch is a good idea given the issues and level of instability. If your OS is not installed on an SSD, I would check the disk thoroughly and confirm its health before reinstalling.  After install, I would make multiple back ups, so you never have to go through this again.  Back ups should include a base install of the OS, another after you have installed all drivers and software you use regularly.  Now install your games (another back up now is optional), then you have several ways to go back to a stable start point whose integrity is confirmed.  You can experiment if you want now.  You can use system restore for testing, and if that doesn't work, use a back up to re-image to a known stable config.  Moving forward you should make back ups of your system regularly.  All hardware fails, windows updates can cause issues, driver updates can cause issues.  Having to re-install from scratch is a PITA.  Acronis, Macrium and Redo are 3 great ways to protect your system.  Macrium and Redo are free.

One other question?  Are you using an IDE disk for your boot drive connected to the JMicron/Gigabyte GBB36x controller?

System File Checker is an easy option, but if it fails to fix a hidden or underlying issue, you'll be back in the spot you are now in 3 months.  Hence my fresh install (with back ups) recommendation.     

[Atomic_Sheep]

Well looks like I have a hardware fault after all. I re-installed my computer and started getting BSODs and just complete system freezes with the new old processor (the one I didn't overclock), so the problem isn't the processor.

For some reason the only corruption that I was getting was on my external USB hdd that I was using as backup. My RAID 10 data drive and the SSD with Windows installed on it seemed to have uncorrupted data.

I always have a backup of all my data and a base install of my OS.

My boot drive is an SSD connected to either to JMB362 or eSATA (both 3GB/s) not sure which one. I've got my Blu ray and DVD drives connected to one of these as well.

[shadowsports]

Best boot and OS performance would be achieved by connecting your boot drive to the intel controller. I'm not saying re-do your system, but for next time. Of course if you are still having issues after a fresh install of the OS, then you may have to accept that something has indeed failed and move on.