Solved BSOD 0x0000000a 0x0000001e 0x00000050 0x0000003b

[Useless User]

If you are going to buy a new one, why not try a 4930K? I'm pretty sure it will run on that board, will be an upgrade and is about the same price.

I actually contemplate that one, if compatible, which it should be. Here, it costs the same as the Intel i7-3930K (€500). If the new processor won't remedy the problem, I'm going to jump from my ground floor window ; )

I have never done an RMA. The dealerships where I bought all parts for all PCs in December 2011 no longer exist; but I should look deeper into how an RMA works. Maybe I should then try to RMA the ASUS mainboards, too.

 

[essenbe]

I would. as long as they are still in the warranty period. Even if I didn't use them, I would RMA them and get another board an d CPU. If nothing else, you could sell them get some of that money back, or at least build another rig with them. I would still consider the 4930K if you are going to buy. I', almost positive they use the same socket. You could check your board's list and make sure they issued a bios update enabling the board to use them. You would just have to update your bios.

I just checked, and your board lists it under CPU support. It even lists the 4960X. http://support.asus.com/cpusupport/list.aspx?SLanguage=en&p=1&s=42&m=P9X79 PRO&os=&hashedid=ITjeO1wq0nRUPfej

BIOS Update http://support.asus.com/cpusupport/detail.aspx?SLanguage=en&p=1&m=P9X79&cpu=Core i7-4930K (3.4GHz, L3:12M, 6C, HT, 130W, rev.S1)&pcb=ALL&sincebios=4210&memo=

 

[Useless User]

Update: Bought an i7-4930k as replacement processor. Let's hope that was it. Then, I can read the numbers off the i7-3930k and send it to Intel - the 3 year warranty runs out in three weeks.

If that was not it - the only thing I have not yet bought twice is the PC-case ; )

 

[essenbe]

When you swap CPU's check the CPU socket very closely for any bent CPU pins. If there is even 1 bent pin it will kill the whole set up. They are very difficult to see too. Magnifying glass is in order.

 

[Useless User]

Sure, did that with each mainboard change in this never ending saga.

If it turns out that it was the processor (for whatever reason), I would be very surprised why Intel's very own diagnostics tools did not identify the processor to be damaged in the first place.

 

[Useless User]

So, a new i7-4930K arrived. I took the i7-3930K out and put the new one in. This all takes place on a new ASUS P9X79 mainboard (BIOS 4608) with new 4 x 4 GB Kingston memory of the type I use in all dumb compute boxes and a new AMD FirePro graphics card. I have a whole box of new hardware components at my lab now.

I also bought a nifty little €5 set for breadboarding (LEDs, switches, BIOS-beep speaker, etc.). Switching on, I get one short beep and into the BIOS - processor/memory are recognised. So far, so good. I now try for the n-th time to install Windows 7 Professional.

I downloaded the drivers from each vendor's (Intel, AMD, Realtek, Asmedia, etc.) website, not from ASUS.

This is fun... not.

 

[essenbe]

Please let me know how it goes. I know how clean installs go. I do one every 3 months or so. I do a lot of stuff with my computer few people do. I do it, just to keep it clean and as light as possible. I know what it's like. In the FWIW department, I always download drivers from the Asus site. I have learned that many manufacturers alter the drivers to work right with their boards. That does not mean what you did is wrong. Try it and it may work better. Please let me know. The chipset driver is probably the most important and I make sure I install it first.

This is a good guide on how to install Windows. It may tell you some things that will make it easier. http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html

I would like to know how you progress. I would recommend you not install the Asus AI Suite, at least at first.

 

[essenbe]

I just re read the last few posts in this thread and saw that you mentioned RMAs. I have done my share and it is an experience, believe me. But, if it was me, I would RMA every single component I replaced. bar none, as long as they are still under warranty. The only problem you may have is convincing them it is defective. Most ram has a lifetime warranty and you usually have little trouble with an RMA, especially if it failed a memory test. A word to the wise. Every thing I RMA, I would recommend you take excellent pictures of. The way many manufacturers get out of replacing components is to say they found damage and it was customer abuse. Pictures of everything, both sides can help them 'change their position'. With Motherboards several pictures are really necessary, especially of the CPU socket showing the CPU pins clearly.

 

[Useless User]

Yes, I know the clean install routine by heart by now... No ASUS Suite II installed. I don't need it. I only installed the minimum drivers and my simulation software so far. Now, Windows 7 is downloading 165 updates with 681,5 MB to be installed, so I will go for a walk...

As for RMAing some of the processors and mainboards, which I should do, I dusted and photographed everything. Once I get the original invoices back from the tax office, I'll send the whole shebang in. I only have two weeks left in the 3 year warranty period (Intel/ASUS/AMD).

 

[essenbe]

Sometimes it is easier on you and the computer to uncheck all but the first 25 and install them 25 at a time. It takes a little longer, but sometimes it works better. I would not install the graphics driver it tries to install. Download that from AMD Download Drivers

 

[Useless User]

So, three hours after receiving the new processor, the 165 updates installed and configured themselves. This is the first time since this saga began that it worked just like that, as if out of the box. I have not installed any other software or changed something in the BIOS. Now, I let the PC run a maxed out simulation...

 

[essenbe]

Well done. Congratulations, that's a very strange case. I have always said the CPU is the last thing to suspect. You have proved me wrong. I hope your good luck continues. Please keep me posted. I would love to hear of your continuing success.

 

[Useless User]

Ok, no BSOD after two hours maxed out simulation. Usually, in each new hardware configuration, the PC had crashed by now. I consider the problem solved: It was the processor, which I will now RMA. Thanks for all your help; it was a long and winding journey!

My conclusion from all of this is: PCs are still not modern devices, compared with many other products - why a faulty processor passes all of Intel's very own tests is beyond my comprehension. Processors should be able to self-diagnose their functionality, saving the user hours or, rather, days of futile work.

 

[essenbe]

Well let me know in a week or so, if it is still doing well. I'm surprised, CPU, as I stated, is the last thing I would suspect. Not that I don't believe you, just surprised. I have seen cases where it was the CPU, but they are quite rare. I would be sure to tell Intel all that you have been through and all that it has cost you. Not that they will do anything about it, but I would just have to tell them, just me being me. I do know Intel puts them through rigorous tests to make sure there is nothing wrong, but I guess with this technology, things can still fall through the cracks.

 

[Useless User]

What else could it have been? The only thing (apart from the CPU) I did not change once during my ordeal were case and cables...

With the new CPU, all I had to do was to: put it in, install Windows, install drivers - no issues (yet). But just the fact that I could 1. download the 165 updates and 2. install them in one go tells me something. Now, I have spare mainboards, graphics cards and memory so I can buy a new case and another CPU to build another compute box - or sell it all on Ebay.

 

[essenbe]

Can you RMA the CPU? I would certainly try. If it is too late, I would show Intel the dates on the receipts from everything you bought trying to fix it, when it was the CPU all along. If we did not live so far apart, you would already have a potential customer, especially if you were able to RMA the CPU.

 

[Useless User]

I intend to RMA the CPU to Intel, I have two weeks left in the three year warranty period.

 

[essenbe]

Great job and absolutely perfect timing. Just think, you may then have a second 'beast' of a computer. Most people wish they had just 1. You can have 2 now. Besides, for all the grief and expense you have been through, you deserve something to show for it. I envy you. Not the grief or expense, just having 2 absolutely fantastic computers. Now you can do twice the work in half the time.

 

[Useless User]

Well, the "repaired" box is still computin'...

Still, so much time wasted without actually learning anything. If there'd been a "self-test module" in the CPU, I would have saved in total 11 full workdays of fiddlin' around.

 

[essenbe]

I agree with you, but I guess we could say that about every piece of hardware and especially Operating Systems. In fact, with what I do, I would be very happy if there were a module that could be trusted which would say, you have a hardware or software or driver problem. With what I do everyday, most times that is the first thing you need to find out and the thing you spend the most time on. But, I do agree the CPU should have one. It's very rare that it is the CPU, but it is also one of the hardest to diagnose. I'll even go you one better. Since almost everything in a computer runs through the CPU, why couldn't that module also say, I'm getting insufficient data from the hard drive, or the ram is very sporadic in the information it is giving me or the power supply is not giving me the power I require.

The truth is, the dump files most of the time always blames the CPU first. The reason is, whatever is wrong in the computer, be it another piece of hardware or even a driver, it is the CPU that recognizes something is wrong and issues the shutdown order. Because it issues the shut down order, it is blamed for the crash. So, why couldn't the CPU module that does that give 1 more piece of information? I'm issuing the shutdown order because there is a problem and tell why it issued it? You certainly had more than your share of problems and way more than most people. But, in my world, I see it a little different than you would or probably should. I am sure the CPU somewhere knows why it is issuing that order, why couldn't it tell us? Then I would probably have to find something else to do in my 'spare time'.