Realtek ethernet driver error code 35, Compaq CQ58, Windows 8.1

[blueistwo]

iv'e found that using a bios that does not support efi, the realtek driver works.  However not haveing efi can cause probles booting a system built with efi in the first place. Mine did continue to boot windows but was auable to boot from the recovery partition. I have now reverted back and I am now going to wait for there to be a bois or efi update.

My brothere has a CQ57 also with Windows 8.1, the same realtek hardware using the same driver and is working fine. His CQ57 has a bios without efi.

There are bios without efi  available for the motherboad used in CQ58. The OS will beed to installed cleanly so there are not any problems booting.

[Adriarnna]

I performed some further digging and came up with the following.

The on board LAN 'Realtek PCIe FE Family Controller'  will not enable on a windows 8.1 platofrm on the HP Compaq notebook model CQ58-201SA and instead generates the following errors.

While Windows 8.1 Device Manager gives the impression that a suitable device driver is installed for this hardware it is unable to assign system resources (IO address, DMA, IRQ) to it an and thus disables it with a message stating that I need to contact my hardware vendor for either an updated BIOS or Firmware.

In Windows Device Manager where it shows a yellow "!" under the "Network Adaptors" entry I see the following on the General tab of the device properties windows.

"Your computer's firmware does not include enough information to properly configure and use this device. To use this device contact your computer manufacturer to obtain a firmware or BIOS update. (Code 35)'

Further investigation into the system reveals the following error codes, easily found again on the properties display for the device listed in the Device Manager window under "Networking Adaptors". You will most likely find two entries in the Details tab on the "Property" drop down list with additional information in the "Values" area.

1)

Property: Problem code

Value: 00000023

2)

Property: Problem status

Value: The resources for this device conflict with the MCFG table.

C0000908

I am trying to find more information on the thw two error codes of 00000023 and C0000908 but the reference to the MCFG table leads me to believe that something is going on with the way that Windows is obtaining data from the memory Mapped ConFiGuration space table.

Question Could Windows 8.0 have used the 2.1 specification and Windows 8.1 is using the newer 3.0 specification?

I know we all seem to be focusing on teh drivers which originate in one form or another from Realtek, but I am starting to question if we should be looking at theinternal changes made by Microsoft or perhaps, HP would be good enough to tweak the firmware code and release an updated BIOS. It does seem as though the drivers install but just cannot get the addressing data they need from the operating system which in turn is trying to pull that data from the firmware.

A long line of guesses and assumptions there.

Appended:

Digging around I found that the error C0000908 is a windows status error.

"C0000908 STATUS_BAD_MCFG_TABLE The resources required for this device conflict with the MCFG table."

The only reference I have so far found to 00000023 is to 0x00000023 FAT_FILE_SYSTEM which I have some difficulty accepting since the file system on the drive is NTFS unless one of the hidden partitions uses FAT.

I am beginning to wonder if I should run a SFC and DISM check and repair on the system and see if that throws up any problems.

[blueistwo]

I've come to a simialr conclusion that it not a driver error but some kind of communication error between one sytem and another. Windows is unable to assign resorces to it.

I've ran SFC scannow before it came up with no errors.

[DanyZaffa]

So in your opinion, Hp must release a new bios version?

[blueistwo]

Yes

[DanyZaffa]

Yes but very soon! It's impossibile that a team like Hp doesn't fix this incredibile error!

[Adriarnna]

Well the results of running SFC and DISM are this.

Using and elevated command prompt I ran 'SFC /scannow' which found errors. I allowed it to complete then exited the command prompt and rebooted the notebook.

On startup I repeated the above for a second time with the same result, of erros found and fixed, so I rebooted yet again.

On the third startup, I ran the above for the final time with the result that it still found errors which it tried to fix. so for teh final time I rebooted the notbook.

On this forth restart I once again opened an elevated command prompt at the administrator level and ran the DISM application using the following sequence.

First I typed:

Dism /Online /Cleanup-Image /CheckHealth

This found errors so I moved onto the second command sequence:

Dism /Online /Cleanup-Image /ScanHealth

Which informed me that the errors could be repaired, so finally I typed in the third and last sequence:

Dism /Online /Cleanup-Image /RestoreHealth

Which successfully repaired all errors found. I exited the command prompt and rebooted the notebook only to find that the repair had disabled various others driver as a result of those drivers being "unsigned" or "out of date". This was easily fixed by reinstalling the appropriate drivers I had thought to download and save to the hard disk prior to performing this sequence.

At this time I can only come to one conclusion and that is there is a issue between windows and the way it interacts now in Windows 8.1 between the drivers and the BIOS/UEFI which it did NOT before with Windows 8.0.

I require my notebook for work and have reached the limit of my willingness to experiment to try and find a solution or work around to the issues created by the Windows 8.1 so called update released by Microsoft. I hope to see some form of patch or update produced by HP for the particular model of notebook I use but I can no longer continue to try and use it in its current configuration.

As I write this I am in the process of backing up all user generated information and data and collecting my application installation disks together as it is my intent to perform a Factory Reset through the Recovery Manager.

To everyone else out there I wish you well and hope you find a asolution to your issues. To the HP techs I extend my thanks for all the ideas, suggestions and advice. I hope you guys get permission from management to say something substantial soon with regards to Microsofts attempts to produce a working operating system out of the mess that is Windows 8.0.

Good luck folks and keep the faith.

[djeveritt]

On asking, and while in warranty, as to why the silence on the forum and can they help I got "We have identified your PC as a DSG unit; i.e. Product sold through European retailer DSG international. This means that HP would not provide any technical assistance for your unit. Should there be any software, repair or replacement of any hardware component you will have to contact your place of purchase due to the warranty terms between HP and the Retailer."

Nice eh? The badge says HP and they deny all responsibility. ... I have delt with DSG before, teenage monkeys untrained and I'll informed that have no clue... Plus I am not sending the unit anywhere.

Guess I will just have to.not use the wired either et and hope in time HP take some responsibility and provide a BIOS update.

Dave

[MarvinTheRobot]

This is complete absurdity and hypocrisy from their part. Looks like they will not release the BIOS update, and even if they do, they might not include the fix for this particular problem.

I think I might need to revert to Windows 8.0 if that is possible...

[DanyZaffa]

After a long call with Hp Assistance center, He said that the problem is well-know and a bios update will be release as soon as possible.