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

        I have an ASUS G73JW that is having this problem for the past 48 hours -- all okay up until then and I have had the machine since Dec 2010 and it is now Aug 2011. Did you ever resolve the issue and if so, what and / or how?

        • 106. Re: whea-logger event id:17 warnings in windows event viewer
          StanfordBinet

          Two ways I got it to go away - one, to turn off error reporting, two - to run the generic MS  (non-accelerated) drivers.

           

          I RMA'd it, though it appears to be a problem with error reporting, not an error with the functioning of the card ...

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

            This problem is very specific. It has nothing to do with the motherboard (as you obviously know, since you are on an ASUS), and everything to do with timing on the PCIe not being met by the video card (in my case, a Radeon 4800 series) in some configurations (in my case, 1920 x 1080p). In my case, I badgered ATI until they gave me a card with a new video BIOS that changed the timing. It would have been easier to change the resolution, but that is the native timing for my displays. If you have this problem, and you have it with video, first try to change to a less strenuous resolution. If that changes it, the easiest thing you can do is get a different card, or else live with the reports of missed timing.  Good luck!

            • 108. Re: whea-logger event id:17 warnings in windows event viewer
              Ggg

              Same here.  I have a G73JW ASUS laptop.  It seemed to be running fine till about two three months ago the graphics card started overheating.  Sent it in, mentioned the errors in the windows log they said they would look at that too.  Got it back and they just said they cleaned the fan and temp was now 80 degrees celsius instead of 100 and sent my laptop back.  so I googled the error and found this stie.

               

               

              G73JW Laptop - Intel I7 -

              Nvidia Geforce GTX 460M1.5gb

              8GB of ram

              running windows premium 64 bit

               

               

              Going to call ASUS back tomorrow, but wanted you to know your not the only one and they seemd to be giving me the run around now.  Oh well another week or two without a computer.

               

              • 109. Re: whea-logger event id:17 warnings in windows event viewer
                knowlengr

                HP 8640 - same error. My machine was sent back to HP four times before they replaced it with a different model. They swapped video cards, disk drives, and tried all the resolution tweaks, to no avail. The machine produced these errors from day 1, but especially when it was under "load" from devices, such as USB. Turning off the error reporting did not fix it because Windows was introducing latency to handle the error reporting (at least) and causing audio dropouts.Am skeptical that this is not a MB error given the evidence, but I could be persuaded otherwise.

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

                  knowlengr: I won't try to dissuade you. This Intel forum topic, until recently, was about the DX58SO and a specific type of WHEA 17 error. The DX58SO X58 design has plenty of bandwidth on the PCIe, which tends to get soaked up by high-end video, so the reports were almost always cured by changing video characteristics. Now that you and others are now talking ASUS, HP, etc., it is entirely possible that the timing is not being met by the mobo. You are also right that in all cases, turning off the report only stops the system from complaining, but there is nothting wrong with Windows EER -- that just shoots the messenger.

                  • 111. Re: whea-logger event id:17 warnings in windows event viewer
                    mslayton

                    whea logger event id 17 error fixed on my system by following the instructions on this page:

                     

                    http://forum.notebookreview.com/hp-business-class-notebooks/585523-potential-fix-nvidia-owners-stop-whea-event-17-errors.html

                     

                    Up and running now for over 2 hours without any whea errors!!!!!!!

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

                      This fix has a lot of configuration changes and updates that don't do any harm, and one that makes a difference: running the video at full power. While it will improve the nVidia timing, the lap will run hotter and burn battery faster. You will see fewer timing errors this way, but nVidia will evenually fix the driver timing, so you might consider trying a more laptop-friendly power setting after each driver update until you don't see the errors (and, likely, you will still see a few running at full power anyway).

                      • 113. Re: whea-logger event id:17 warnings in windows event viewer
                        tzimmer

                        Hello.

                        Please retest with latest DX58SO BIOS (SOX5810J.86A.5599).  There is a workaround in this latest BIOS which may stop the WHEA events.  Thanks.

                        • 114. Re: whea-logger event id:17 warnings in windows event viewer
                          i3v

                          My G73jw is experiencing this event every startup, about a minute after power-on.

                          Reinstallation "infinst_autol.exe -overide -overall" had no effect...

                          And I doubt a second part, about Nvidia card profiles might help, since nvidia control panel is still not loaded when it occurs.

                           

                          Maybe, this solution might help those who experience too many such messages at a time...

                           

                          I, myself, won't pay attention to this error, if not those two complete hangs (like BSOD, but even without a blue screen) I've experienced today...

                           

                          Another thing to mention - there's a newer infinst_autol package availible...

                          1 4 5 6 7 8 Previous Next