1 2 3 4 5 6 Previous Next 114 Replies Latest reply on Oct 29, 2012 5:51 PM by i3v Go to original post
      • 45. Re: whea-logger event id:17 warnings in windows event viewer
        FoghornLeghorn

        I'm not in a rush on the RAM, but it is an eventuality if things continue like they are.  I did try your technique with the driver and it did squelch the messages (if I remember correctly), but the system did eventually hang.

        • 46. Re: whea-logger event id:17 warnings in windows event viewer
          hmf

          To all on this thread: This has now escalated to 2nd tier support at AMD. They have requested more information, I've supplied it, yada yada... I just called AMD and they are still working on it.

          • 47. Re: whea-logger event id:17 warnings in windows event viewer
            Sial_Axetder

            Let us know what happens. BTW, hmf, thanks for doing what is you're doing. This is the most I've got from this issue anywhere. I guess I'll give that driver reload trick a try - can't hurt.

            • 48. Re: whea-logger event id:17 warnings in windows event viewer
              hmf

              Unfortunately, AMD have closed my case again (third time). More unfortunately (for them), I am stubborn and getting mad. Here is what I wrote:

               

              You closed my case again You have been unresponsive to several service requests (most recent 8200286304 and 8200290933). Each time you have passed this issue to higher levels, only to close the service request without resolution or notification. This has been going on for over a year. Please respond. My next escallation is to correspond directly with your SVP here in Sunnyvale.

              • 49. Re: whea-logger event id:17 warnings in windows event viewer
                Sial_Axetder

                eesh, this is crazy. Anyways a minor update from me: Driver reload didn't help any. I was able to reproduce these without rebooting. System locked and these were the last warnings in EV. (I am a bit of a gamer so to test, load a game - ME2 - go until it locks).

                I did have some success, during W7 RC, with the Enzyme drivers. I might try those again.

                • 50. Re: whea-logger event id:17 warnings in windows event viewer
                  hmf

                  I finally got a response from ATI / AMD:

                   

                  "Most of the people having this error are indeed running  ATI HD4000 series product on that particular motherboard.


                  "However, there are several cases in the thread that have seen the same problem using Nvidia graphic card. One of the user has no problem, no error on his HD4000 series graphic card until he changes to this intel board.


                  "I do not believe this an AMD/ATI issue and it does not appear to be wide spread with thousands of users with a problem.


                  "In any case if you are willing to send your system to us I will make sure that our engineers will look into it."

                   

                  Since I only have one working system left (after shipping one to Intel and getting it back in broken pieces), and it is in service (with a GeForce card) for the next few months, we stalled. Hard to believe AMD is unwilling or unable to test this without my machine. I asked them to see if they can somehow get an i7 / DX58SO, and I'll see if Intel might donate to poor AMD. If we get somewhere, I'll let you know. If not, I will try it from the top at AMD here in Sunnyvale.

                  • 51. Re: whea-logger event id:17 warnings in windows event viewer
                    shiny

                    Well i am having the same problem with my ATI4670 on a Biostar P4M900 Micro 775 Ver. 6.x ( yea yea i know ). Which makes me wonder if the root of the problem is the Mobo. Moreover it was working fine for a year already, why would it go nuts over the weekend ?

                    • 52. Re: whea-logger event id:17 warnings in windows event viewer
                      hmf

                      Either the service organization of AMD only works on problems that affect "thousands of users" or they feel that I am exagerating and think it is good customer relations policy to reply sarcastically. I've started corresponding with a vice president of AMD in Austin, Tx., to see how the corporation feels about this. My hunch is they don't want their service group telling customers to buzz off.

                      • 53. Re: whea-logger event id:17 warnings in windows event viewer
                        Sial_Axetder

                        Sarcastic, what's wrong with them just saying 'we have no idea what the problem is'? Eventually I think you'll get thrown into a loop, if you haven't already.

                        • 54. Re: whea-logger event id:17 warnings in windows event viewer
                          hmf

                          I suppose it would feel less demeaning to hear "we have no idea" but that still would be frustrating. Perhaps the "thousands of users" comment was not facetious, but if not, it speaks volumes about how they view the problems of an individual customer. Anyway, AMD says it is willing to look at the problem if I send them a system. Since only one is left intact after one was destroyed in transit to/from Intel, that won't happen until I can pull the remaining one out of service and put back in their video card. So, they've effectively made me go away, loop or no loop.

                          • 55. Re: whea-logger event id:17 warnings in windows event viewer
                            FoghornLeghorn

                            An update to my issues…

                             

                            [brief recap]

                            I have three identical systems based on DX58SO, i7-920 and ATI HD 4850 video cards.  OSs is either W7-x64 or W2008-x64 depending upon function within my environment.  All experience the error message being discussed in this thread with varying degrees of frequency with the system that is my primary workstation being the worst.  My workstation began locking up (W7-x64) about 48 days ago; my initial attempts to change settings and drivers were ineffective but I continued to search for what started this mess.

                            [/brief recap]

                             

                            My workstation often locked up several times a day or may run a day or two in between events.  This system is used for business 100% so I can’t blame gaming for any of the issues.  After trying many different video driver releases I finally remembered which set of ATI drivers seemed to give me a stable environment.  I rolled back the video drivers to ATI’s set from December of 2009 (9-12) and my workstation seemed to gain back the lost system stability as I was able to run 5 days straight without any crashing (I would manually restart the system as the OS would start to get snarled towards the end of the week).  The WHEA messages were still just as abundant as always.  Things were back to normal for a good three weeks.

                             

                            A little over a week ago I suddenly started getting BSOD, which is a first for my experience.  System wouldn’t boot due to BSOD (corrupted display on BSOD) unless going into Safe Mode.  Borrowed identical video card from another system and BSOD goes away.  Install original card and BSOD returns.  Rinse and repeat.

                             

                            Contacted video card vendor (Gigabyte) to arrange an RMA and while I had a spare ATI X300 video card to install, I decided it was time to throw a few $$ on a NVIDIA-based card.  I used to have a spare NVIDIA card but gave that away to a customer last summer so I purchased a GT 240-based video card made by PNY.  Install drivers and reboot and no more BSOD.  No more locking up of the OS.  And for a full week not a single WHEA error.

                            • 56. Re: whea-logger event id:17 warnings in windows event viewer
                              shiny

                              Well, in defense of ATI, in my case it turned out that my mobo capacitors have gone wild, so when i changed the mobo everything returned to normal. So it's not really ATI's fault, it's just the first thing that breaks when *something* is wrong hardware wise.

                              • 57. Re: whea-logger event id:17 warnings in windows event viewer
                                bennyr

                                I just wanted to chime in that I've been having the same issue - system locking up repeatedly, each time following a large number of eventID 17 errors from the PCI Express Root Port. However, I have an NVIDIA GeForce GTS 360M video card. I'm afraid I don't have much experience to report as I just discovered this issue on my brand new laptop tonight. I'm going to try reloading the drivers as mentioned above and go from there, will post again if I get any new info.

                                • 58. Re: whea-logger event id:17 warnings in windows event viewer
                                  hmf

                                  I had to give up. AMD can stay unhelpful far longer than I can afford to be polite. If a respectful letter to the SVP (technical) doesn't even get a response, the company is not worth the effort. I replaced the Radeon 4890 with an NVidia (GTX 470). The system is much faster, the log files are useful again, and I find that I can run the memory at full speed without any strange freezes/crashes (two weeks solid stress test w/ no failures or error log entries). I will give away the Radeon cards (with a warning, of course). Now if I could only find an uninstaller that works... the ATI Catalyst "complete" uninstall leaves services, logs, and a huge amount of registry residuum. What a great company.

                                  • 59. Re: whea-logger event id:17 warnings in windows event viewer
                                    jcleland

                                    I've got the same problem: WHEA-Logger event 17's multiple times per second in the system log. My system is an Asus G73JH notebook, Mobility Radeon HD 58xx, Intel 5-series chipset. I've updated the chipset drivers, installed the latest Catalysts, same problem. When the ATI drivers were uninstalled, the problem didn't occur. Once they were installed again, the log messages came back. Have question in to AMD, no reply yet. I'm guessing that Im going to be RMA'ing my computer. The message is annoying and makes my system log useless. The computer runs fine.

                                    1 2 3 4 5 6 Previous Next