Topic: P67A-GD65 problem (Read 5756 times)

DooGie · « **on:** 23-December-11, 22:00:06 »

Flashed my bIOS to the latest 1.16 yesterday and everything appears to be working fine.

However since the update every time I boot up the PC I see this entry "Driver PCI returned invalid ID for a child device (FFFFFFFFFFFFFFFF00)." in Windows Event Viewer log.
I've uninstalled and re-installed drivers to try and correct this but so far no result.

Any suggestions would be welcome.

Running Windows 7 x64.

Ex Forum Mod · « **Reply #1 on:** 23-December-11, 23:32:22 »

See my signature below for example of further information to provide about your PC components.

>> Posting Guide <<

DooGie · « **Reply #2 on:** 24-December-11, 00:33:39 »

Done

semp · « **Reply #3 on:** 26-December-11, 09:50:25 »

i think the new bios still has problems. do you have 4 sticks of ram? if so remove 2, that may fix some of them. i am flashing to an older version i had that worked gread, d but had no support for my gaming keyboard/mouse in bios. gonna try e first. but i know for sure that 1.15 has a big problem with not recognizing 4 sticks of ram.

i get the same errors you get but it switches from mouse to video cards to something else. i get ram errors with 1.16 even though it passed all the mem test, but according to bios ram failed the test.

DooGie · « **Reply #4 on:** 26-December-11, 21:21:17 »

Quote from: semp on 26-December-11, 09:50:25

i think the new bios still has problems. do you have 4 sticks of ram? if so remove 2, that may fix some of them. i am flashing to an older version i had that worked gread, d but had no support for my gaming keyboard/mouse in bios. gonna try e first. but i know for sure that 1.15 has a big problem with not recognizing 4 sticks of ram.

i get the same errors you get but it switches from mouse to video cards to something else. i get ram errors with 1.16 even though it passed all the mem test, but according to bios ram failed the test.

No I'm only running 2 sticks of RAM. I only updated to BIOS 1.16 because of the improved gaming mouse compatibility, I'll live with the error message until 1.17 is released and give that a try.
If I'm still getting the same problem after that I'll revert to version 1.9.

Ex Forum Mod · « **Reply #5 on:** 27-December-11, 03:08:32 »

I have BIOS 1.C and only problem with it is my mouse (MS wireless) doesn't work in BIOS which doesn't bother me any. No problems with anything else.

DooGie · « **Reply #6 on:** 27-December-11, 18:33:10 »

Just updated to BIOS v1.17 and still getting the" Driver PCI returned invalid ID for a child device (FFFFFFFFFFFFFFFF00)." error reported in Windows Event Viewer.

rseiler · « **Reply #7 on:** 03-January-12, 05:54:06 »

It's not particular to MSI, that's for sure:
http://communities.intel.com/message/146617

Perhaps between the two of us we can figure it out. I have a feeling it's pretty common, since it's not something that many people are even going to notice--unless it causes a problem like I linked to in the post.

DooGie · « **Reply #8 on:** 03-January-12, 16:26:45 »

Yeah I'd already seen that post on the Intel forum. Trouble is when the error is googled there aren't many instances showing up.

For now I'll stick with version 1.17 as the error doesn't seem to cause me any probs.

As for what's causing it I've currently got no idea, it only started showing after I flashed the bios to v1.16. Previously I was running 1.9 and getting no error. So it must be something in the bios coding or a setting thats been changed.

DooGie · « **Reply #9 on:** 04-January-12, 22:57:24 »

rseiler if you are happy about using regedit can you do a search of your registry for FFFFFFFFFFFFFFFF00 .
If it exists does it relate to the Renesas USB 3.0 driver?

It exists on my system and it seems to point to the fact that Windows thinks it's a PCI device not a USB one at bootup. Hence the error message.

However how can a BIOS update cause this?

rseiler · « **Reply #10 on:** 05-January-12, 00:03:29 »

Yes, using RegScanner (which is easier for things like this), it shows up 176 times here. It looks directly tied to Renesas, since many of the entries also mention PCI\VEN_1033&DEV_0194&SUBSYS_201C8086&REV_04. This started happening even before Windows had finished installing for me, so before I even installed the Renesas driver. Perhaps it's something the driver could address though. Or perhaps it's a Windows issue, since as you said, maybe it's confusing it for a PCI device.

Does anyone who also has this device not show this event in the System log?

DooGie · « **Reply #11 on:** 08-January-12, 17:07:28 »

I've found that it is definitely caused by the Renesas USB 3 support.

As I don't have any USB 3 devices I decided to disable USB 3 support in the BIOS. The result is that the Driver PCI returned invalid ID for a child device (FFFFFFFFFFFFFFFF00) error message no longer appears.

rseiler · « **Reply #12 on:** 08-January-12, 17:25:04 »

If something comes along that you think might fix it, such as a BIOS/driver update, do enable it again so that you can see if it does. Most people aren't going to want to disable it.

DooGie · « **Reply #13 on:** 08-January-12, 17:31:06 »

Yes I was planning on doing that rseiler.

I may try and get hold of a USB 3 device and see if the error is still generated with it plugged in.

rseiler · « **Reply #14 on:** 08-January-12, 23:41:34 »

I had one idea: what if in the old version of the BIOS you were running, the default state was USB3 disabled? When you upgraded, that default was enabled. Possible?

Melkorbane · « **Reply #15 on:** 22-January-12, 19:11:05 »

I have the GD55 and I also started seeing this error after updating from 1.B to 1.H
I have a usb 3.0 stick and use it all the time before my update, so I'm pretty sure the onboard 3.0 controller is enabled by default for previous versions.
And yes, the error is still there when I reboot with the stick plugged in.

I'm not experiencing any problems other than the message so it's not really a big deal, but the error is still quite annoying...

DooGie · « **Reply #16 on:** 22-January-12, 22:41:28 »

Quote from: Melkorbane on 22-January-12, 19:11:05

I'm not experiencing any problems other than the message so it's not really a big deal, but the error is still quite annoying...

I agree, it isn't a big deal but it shouldn't be happening.
I'll bet that a lot of P67A users are getting the same error but never look at Windows Event Viewer so they don't know it's occuring.
I've reported the problem to MSI Customer Service but the reply wasn't really of much help. Just along the lines of "Have you cleared the CMOS" etc.

pydayFup · « **Reply #17 on:** 27-January-12, 02:30:19 »

Hi

Should every virtual site in 42go have its own cronolog process?

I have 287 virtual sites on a server and about 290 cronolog
processes. There are a few websites that have 2 cronolog
processes. This causes a problem every couple of days with the
log file resulting in webalizer stopping to work just for these sites.

Any idéas?

Regards
Mirsad

Froggy Gremlin · « **Reply #18 on:** 27-January-12, 02:59:43 »

Quote from: pydayFup on 27-January-12, 02:30:19

Hi

Should every virtual site in 42go have its own cronolog process?

I have 287 virtual sites on a server and about 290 cronolog
processes. There are a few websites that have 2 cronolog
processes. This causes a problem every couple of days with the
log file resulting in webalizer stopping to work just for these sites.

Any idéas?

Regards
Mirsad

And the mystery system is?

Ex Forum Mod · « **Reply #19 on:** 27-January-12, 03:23:08 »

pydayFup, what on earth do your server questions have to do with this topic?

If you have MSI hardware and are having problems with it then start your own new topic instead of hijacking this one.

>> Please read and comply with the Forum Rules <<

>> Posting Guide <<

Uberhood · « **Reply #20 on:** 30-January-12, 20:39:42 »

I have the same problem. The error "Het stuurprogramma PCI heeft een ongeldige id voor een ondergeschikt apparaat geretourneerd (FFFFFFFFFFFFFFFF00)." sorry for the Dutch language but it's the same error you people recieve.
This happens every time when I boot the system starting from the beginning of 2012. This is exactly the time I upgraded from 1.C to 1.H

I do have USB3.0 support enabled but don't use any USB3.0 ports or devices. I am using the latest Renesas drivers btw.

DooGie · « **Reply #21 on:** 30-January-12, 22:08:21 »

Hi Uberhood. As I posted earlier in the thread, if you have no USB 3.0 devices you can safely disable USB 3.0 in the BIOS and the error message does not occur.

Having said that, it is a problem that MSI should be tackling as it is definitely a problem that has arisen since BIOS version 1.16 was released. The same error is also occuring with some Intel mobos apparently.

MiL-2 · « **Reply #22 on:** 09-February-12, 16:07:12 »

New 1.I bios came out yesterday. Did anyone also tried updating NEC Renesas firmware? I updated mine to 3.0.2.8 in DOS. If anyone interested I can give you how-to and files.

Bernhard · « **Reply #23 on:** 09-February-12, 16:19:23 »

Quote

Having said that, it is a problem that MSI should be tackling as it is definitely a problem that has arisen since BIOS version 1.16 was released. The same error is also occuring with some Intel mobos apparently.

DooGie, if you have found a definite bug that is apparant in a BIOS version, and you can readily reproduce it, then MSI needs to be advised to address that in the next BIOS release. Thats the only way. >>How to contact MSI.<<

DooGie · « **Reply #24 on:** 09-February-12, 16:53:58 »

Quote from: Bernhard on 09-February-12, 16:19:23

DooGie, if you have found a definite bug that is apparant in a BIOS version, and you can readily reproduce it, then MSI needs to be advised to address that in the next BIOS release. Thats the only way. >>How to contact MSI.<<

I reported the issue to MSI support on January 12th and got a reply which did not prove useful.

"Dear Sir/Madam:
Thank you for contacting MSI Technical Support.

Regarding your concern, please refer to the following procedure to verify:
1. Please unplug the power-cord and clear CMOS (How to clear CMOS. Please refer to the manual-->Hardware setup-->Jumpers-->Clear CMOS jumper for how to clear CMOS). Then enter BIOS setting，choose F1 when by pressing the “Delete" key during POST, Load Optimized Defaults and save&exit, and then check. "

I reported back to them that I had cleared the cmos but the problem still existed. I've heard no more from them since that.

I decided to flash back to bios version 1.12 (1c) and I've had no problems since so I'll just stick with that version.

Bernhard · « **Reply #25 on:** 09-February-12, 16:59:24 »

Thanks for the feedback.
No harm done in submitting another report explaining the procedure followed and what you have done to solve the problem. Also add the link to this thread.

Uberhood · « **Reply #26 on:** 25-February-12, 15:25:27 »

The problem has been fixed at least for me with beta BIOS version J1

For download see jacks post: http://forum-en.msi.com/index.php?topic=144655.750

Please let me know if it is fixed for you people as wel. Thank you MSI :D

DooGie · « **Reply #27 on:** 26-February-12, 23:41:05 »

Quote from: Uberhood on 25-February-12, 15:25:27

The problem has been fixed at least for me with beta BIOS version J1
For download see jacks post: http://forum-en.msi.com/index.php?topic=144655.750

Please let me know if it is fixed for you people as wel. Thank you MSI :D

Nice to hear Uberhood. However I understand it doesn't fix the random reboot issue :(
Still that's a different issue posted in another thread.
As I posted in that other thread I'm now staying with BIOS 1.12, It's working well for me.

Uberhood · « **Reply #28 on:** 27-February-12, 21:43:03 »

Quote from: DooGie on 26-February-12, 23:41:05

Nice to hear Uberhood. However I understand it doesn't fix the random reboot issue :(
Still that's a different issue posted in another thread.
As I posted in that other thread I'm now staying with BIOS 1.12, It's working well for me.

Same here DooGie, I've also gone back to 1.12, haven't had a single random reboot issue as well. Even the MSI red rocket team member suggest 1.12 as the best BIOS version for the p67a gd65 motherboard so.. If there are no significant changes in the future I will remain at this BIOS.

pcdoctor · « **Reply #29 on:** 27-February-12, 22:05:39 »

Hi I just today I updated the bios to the latest version just released X, which suffered a problem for the raid updated the bios and the problem disappeared, but am having another problem
The USB 3.0 ports do not work properly what I mean:
If you joined and connected a usb 3.0 hd suddenly disconnects and then reconnects making it impossible to operate this function to format post with hd hd thing and not because of other tried and perfect pc equipped with USB ports 3.o
Now how can I fix problem with all
My config: i7-8 gb ddr3 1600-2hd raid 0-cross fire 6950 - pci lan 10/100/1000 PCI slot in addition to the first position near the cpu socket sk GD65 motherboard P67A-GD65(B3 Sorry but I'm using a translator to communicate

Ex Forum User · « **Reply #30 on:** 27-February-12, 22:47:08 »

Quote from: pcdoctor on 27-February-12, 22:05:39

Hi I just today I updated the bios to the latest version just released X, which suffered a problem for the raid updated the bios and the problem disappeared, but am having another problem
The USB 3.0 ports do not work properly what I mean:
If you joined and connected a usb 3.0 hd suddenly disconnects and then reconnects making it impossible to operate this function to format post with hd hd thing and not because of other tried and perfect pc equipped with USB ports 3.o
Now how can I fix problem with all
My config: i7-8 gb ddr3 1600-2hd raid 0-cross fire 6950 - pci lan 10/100/1000 PCI slot in addition to the first position near the cpu socket sk GD65 motherboard P67A-GD65(B3 Sorry but I'm using a translator to communicate

If you havent. Clear Cmos http://forum-en.msi.com/faq/article/how-to-clear-the-cmos

pcdoctor · « **Reply #31 on:** 28-February-12, 15:17:16 »

Ok deleted the bios but the problem persists no units connected to USB 3.0 disconettono .. I also installed the new drivers but nothing remains the problem ..
Nb: I have already replaced 3 motherboards and suffer the same problem ...
Could not there a way to solve?

Inform you that the USB 3.0 controller firmware has the following firmware: 4015
the driver and 2.1.19.0

pcdoctor · « **Reply #32 on:** 03-March-12, 15:47:13 »

Hi there are updates to the problem of USB 3.0 for this product?

News:

Author Topic: P67A-GD65 problem (Read 5756 times)