Experiencing reboot loop & Ethernet Code 10: ASUS Z77, Windows 7 64-bit

mesopotamian

Distinguished
Apr 10, 2011
72
0
18,630
I have not participated on Tom's Hardware in a very long time. That said I require assistance with a very annoying issue while similar to one that seems ubiquitously common, has a slight twist. As indicated by the title fourm posting I am dealing with a PC that powers on, successfully completes POST but then automatically restarts once the Windows 7 startup animation begins. The twist here is that unlike most other cases were the user's PC goes into an infinite reboot loop, my machine successfully boots after automatic restart to the login screen, were I can begin normal operation of my PC. It's important to note that after the automatic reboot and before the Win 7 startup animation a menu appears offering the selection of running windows startup repair or launching Windows normally.

This hair-raising insanity started after I attempted to fix another annoyance regarding my PC's Ethernet failing to work immediately after logging into Windows. The Ethernet troubles are a consequence of the infamous "Code 10" error regarding the Ethernet driver each time I power on my system and login to Windows. Of course this is easily fixed by going into "Devices and Printers" in the control panel right on the icon for my PC and just clicking troubleshoot. This did not stop me looking for a permanent solution in preventing the code 10 errors from occurring in the first place. I must denote that the code 10 problems were occurring frequently from when I started using a replacement motherboard that ASUS sent me in 2013 but was not taken seriously given that I was not using the Ethernet port at the time. It was only during the past few weeks that I have been able to use Ethernet for my network connectivity after moving to a new residence.

My quest to fix the code 10 grew bigger after a reinstall of Intel chipset drivers went haywire I believe as a result of human error, when I powered down my PC during reboot after the installation (I think I did it during POST). My mistake resulted not booting into Windows after POST and instead displaying an error that there is no valid boot device. This prompted me to format my SSD and do a clean install of Windows 7 and restore whatever I had backed up. Sadly the Code 10 persisted, and right when I am beginning a fresh start, I went to experiment with the Intel Rapid Start and Smart Connect tech. I enabled the appropriate settings in BIOS, installed the software, and created the “Hibernation Partition” for Rapid Start. After everything was said and done, I began to experience the reboot loops that are the main issue to be resolved in this thread. I have subsequently have removed Intel Rapid Start and Smart Connect software, disabled the pertinent BIOS settings and removed the Hibernation Partition for Rapid Start, only to continue experiencing reboot loops.

After experiencing an automatic restart and subsequent successful boot into Windows 7, I do not get a “Code 10” error for Ethernet. Before the reboot loops started I noticed that the Code 10 error also disappears after powering on my PC, and then performing a normal restart.
I apologize for the length of this post, and appreciate any assistance in resolving this issue.

PC Specifications

Corsair Carbide 500R
Intel Core i7 3770k Stock 3.5 Ghz
Cooler Master Hyper 612
Asus P8Z77-V Pro/Thunderbolt- BIOS 2104
Corsair Vengeance LP 16GB 1600Mhz DDR3 (CML16GX3M4A1600C9)
Crucial M4 256GB SSD (OS, and most Apps are installed on this)
Seagate Barracuda 1TB (Used for my PC Game Library, and as mass storage for personal files)
Sapphire Radeon HD 7970 Dual-X (AMD Catalyst 15.5 beta drivers)
Windows 7 Professional 64-bit
 
Solution
What you have there is a clear problem with the HW devices of the board.
If a device fails to initialize after the drivers have loaded for it with a error code 10.
Then your likely cause is a lack of resources, or free IRQ numbers.
Or too many HW devices fighting for the same IRQ numbers.

There is a way to relive this problem.
And often can work.

Simply go into your motherboard bios and turn off any hardware feature of the mobo you don`t use.
Good examples are the serial port devices anf the Lpt printer port. and any Midi options.
That will free up a few Irq numbers or values. And with a bit of luck resolve the problem.
It`s not 100% but give it a try.


What you have there is a clear problem with the HW devices of the board.
If a device fails to initialize after the drivers have loaded for it with a error code 10.
Then your likely cause is a lack of resources, or free IRQ numbers.
Or too many HW devices fighting for the same IRQ numbers.

There is a way to relive this problem.
And often can work.

Simply go into your motherboard bios and turn off any hardware feature of the mobo you don`t use.
Good examples are the serial port devices anf the Lpt printer port. and any Midi options.
That will free up a few Irq numbers or values. And with a bit of luck resolve the problem.
It`s not 100% but give it a try.


 
Solution

mesopotamian

Distinguished
Apr 10, 2011
72
0
18,630


This sounds rather noobish of me, but I don't think that I have the ability to use an internal speaker with my motherboard, unlike other PCs I have used past and present. Where would I be able to obtain an internal speaker if that is possible? Would the led indicators on my motherboard be sufficient in diagnosing the issue after performing the initial procedures you described?

Update: Looks like I have got to purchase this on Amazon, and then find the appropriate connector on my mobo.
 

mesopotamian

Distinguished
Apr 10, 2011
72
0
18,630


I have yet to purchase an internal speaker which will get done ASAP. In the meantime, I disabled Automatic Restart on failure, to create a BSOD instead whenever the reboot loop is supposed to occur. I have not yet recorded the hexadecimal error code, but do have other key information. The error title is DRIVER_IRQL_NOT_LESS_OR_EQUAL, and the offending driver is Pciidex.sys. I will attempt to recreate the BSOD to get the error code, investigate it, and report back. On the other hand I just looked in Event Viewer in Windows 7 to find relevant information on the issues I am dealing with. I am looking under "System" under "Windows Logs," and am unsure which event I should be looking for that would help to explain the problems.

Update: I recreated the BSOD and wrote down the error code. I shot these photos of the BSOD.

IMG_00011.jpg
IMG_00031.jpg


 

mesopotamian

Distinguished
Apr 10, 2011
72
0
18,630


Everything seems to be okay in the Device Manager. I however do have a minor most likely unrelated issue regarding the appearance of an optical drive on my machine, that does not actually exist. The only optical drive on my machine is the Asus DVD burner above the highlighted device. This non-existent drive appeared after my clean reinstall of Win7 before the reboot loops started. It's important to note that there is no Code 10 error with the Intel Ethernet port, which as I said only appears after a successful first-time boot.
Device%20Manager_1.jpg
 

mesopotamian

Distinguished
Apr 10, 2011
72
0
18,630
I was led into taking drastic measures and I had the motherboard replaced by ASUS given that I also had issues regarding a dead USB port and, dysfunctional WiFi in addition to the Ethernet code 10 error. Before the RMA, I did a clean reinstall of Windows 7 which eliminated the BSOD, but still failed to fix the Ethernet "Code 10" error. I nonetheless thank the smart community members here on Tom's Hardware for their assistance.